[Typo3-dev] Better templating: PHP!

[dan frost]

The backend UI is the least of the problems!

The architecture is confused - re-building / 
tweaking parts is much very slower process than it 
should be because, for each, classes render AND 
contain logic; files (e.g. in modules) contain the 
use of a class AND the class itself - so there's 
no chance of being able to re-use that class.

I think that, like so many things, to implement 
what you're suggesting is non-trivial given the 
current architecture of TYPO3.

But i understand that there are serious moves to 
change the architecture in future versions...

dan


Peter Niederlag wrote:
> Hi,
> 
> Elmar Hinz schrieb:
> 
>>>I think the BE could benefit from something like in the FE. Eg one
>>>"master index".php that loads and executes module classes. That would
>>>rid us of the BACK_PATH-problems.
>>>
>>
>>There it is again the question why FE and BE are so stricly separated. A
>>large part of the work has to be done twice. Not only in programming but
>>also in maintenance. You can't simply use the checks of the BE forms for
>>the FE in example. You often have a doubled user administration in FE
>>and BE and so on ...
>>
>>Wouldn't it be more consequent to maintain one library and offer all
>>features where you like to use them.
> 
> 
> IMHO: yes. But that does require a lot of work from what I can tell.
> 
> I never found the time to look into it yet but Dan Frost afaik tried for
> example to make ObTS available in FE and BE.
> 
> Cheers,
> Peter