[Typo3-dev] Extension architecture (was: TemplaVoila, normalising the database and XML)

[Frank Benkart [DIACC]]

Ok, I think were on the same way. Or do I'am wrong?

I think every extension is reuseable if it's programmed with a good planned
architecture. I'am writing a lot of extensions the hole week and i'am always
to do that with oop thinking. I don't want to write any code two times.

Yes I think there is a way to do reuseable code in typo3, but for this the
core archtecture must be changed (sorry Kasper). Because why? If you are
thinking in classes, oop, its not a good way to write a class in an php file
and then do the instatiation and output in the same file. Think what goes on
when you are include such a file in an other extension. You have an output.
I think at this point is more abstraction needed. Classes only should do
functionality but do not generate output to the browser. The output for the
browser should managed from one core engine using the classes functions.
This opinion is only for backend modules, meaning that code:

$SOBE->init()
$SOBE->main()
$SOBE->printContent()

I think should be like this:

classInstance->getOutput()

called from the core engine.

If done this very often, using particularly core classes, for exmaple the
pagetree or the list modul.

---------------------------------------
live strong - live typo3

"dan frost" <dan at danfrost.co.uk> schrieb im Newsbeitrag
news:mailman.1.1098740240.23511.typo3-dev at lists.netfielders.de...
> Ditto - but i want to ask something else...
>
> Is there some way that we could make writing re-useable code easier in
> TYPO3?
>
> Here are some of my personal habits:
> - I use ObTS for lots of BE UIs (check it out... ok, ..my own trumpet...
> but it's great!)
> - i put most utility stuff in a lib/ directory and subdivide further in
> their
>
> probably some other stuff... but how about thinking about how to make
> the extensions more uniformly re-useable?
>
> dan
>
>
> >
> > I should put my money where my mouth is: if there is anything I can do
> > to help out in terms of reviewing extensions (which, as I understand it,
> > is a task reserved for the hardcore typo3 gurus -- rightly so, I
> > suspect), I would be happy to help.
> >
> > best,
> > Zach