[Typo3-dev] TYPO3 "extendability" - BE - templates

[dan frost]

Ooooo.... Hmmmm...

You are getting at rendering abstraction, a subject which has been 
aproached many times. The two main thoughts seem to be:

1. Rendering abstraction would be great and save new and older 
developers lots of time

2. It isn't as important as other things

I don't know what Kasper et al think about this at the moment, but I 
know that there are efforts to re-work the fromend so I assume the 
backend isn't the most urgent thing.

Perhaps for a future version we should completely re-hash the backend.

Dan

P.s. I've even been thinking about having ObTS work on the backend!! 
Then you could build new backend modules in TypoScript!

Zorik Pavlenko wrote:
> I wish to discuss with developers of core, whether it might be a good idea
> to keep *ALL* of html in one file (such as template.php).
> 
> There is a template.php file, which is "responsible for backend look". Now,
> while writing zor_rtl extension (for rtl rendering), I had to change the BE
> look. Extending template.php was helpful, but not enough. There's a lot of
> pieces of html here and there.
> 
> I think it is better to keep all html building objects in one file -
> template.php. This will
> 1. make it very easy to completely change/update the look of backend;
> 2. make a standard way of rendering all BE extensions (same html design)
> 3. make easy way to write BE extensions (instead of "<a href=#>bla</a>"
> write "template->makeAtag(bla,#)" )
> 
> Or maybe it does exist already, but I did not find these objects?
> 
> Zorik
> 
>