[Typo3-dev] AJAX - for fe/be

[tapio]

Sven Wilhelm wrote:
>> But it's like Masi said somewhere: Those ideas always lead to rewrites 
>> of core components. And I think this would be the best thing anyway... 
>> we can't assume that the current overall concept with those static SQL 
>> scripts shipped with each extension will get us anywhere near true DBAL.
>> It's the same with other things like the BE-GUI.
>> And refactoring might take 10-times as long as rewriting the stuff.
>> Taking JSR-170, the possibilities of PHP5 and other nice concepts into 
>> account, a rewrite seems to me the only clean cut...
> 
> I have a paper in writing that summarizes reasons for a complete rewrite 
> of the typo3 core. Several points are strong object orientation, 
> interfacing, unified storage api, document model, and much much more.
> As I haven't much time I'm far from writing it finish at the moment, but 
> I hope to have it releaseable in one or two weeks.
> 
> But I see it also like you, rewriting is the most powerful way as you 
> can drop deprecated stuff quite simple and you can concentrate on a 
> clean api and a clean system design.

I hope that you take account also my comment in the topic 'Too many same 
task for 'edit2.gif'

I have discussed about interface in the 'design' list - please read some 
notes from there.

I made an extension in order to simplyfy the BE layout taking off 
everything, which someone doesn't need
tm_contentaccess rewrites some core functions and adds much classes to 
'db_layout.php' and 'alt_doc.php' file in order to get better layout 
control (skin support) and possibility to hide elements, which can't be 
controlled using TypoScript.

What I would like to add is shortcuts between editing an individual 
content element and editing page headers. When you edit a content 
element, you could *always* have a link to the related "header" 
information of the page (in fact generic page properties in the table 
'pages'). And when you go editing the generic page properties, in the 
situation, where you last edited a content element, you would get a link 
back to the content element, which you was recently edited.

That could make usage much simpler and faster.

I tried to add those links but failed.
> 
> Kind regards
> 
> Sven