[TYPO3-ect] lib/div for Backend-Modules?

[Elmar Hinz]

Am Thu, 25 Jan 2007 09:34:22 +0100 schrieb Joerg Schoppet:

> Is it actually possible to create Backend-Modules with these exts?
> 
> If yes, are there any howtos/tutorials ...?
> If no, can it be achieved? I would be willing to contribute to this 
> development.
> 
> Kind Regards
> 
> Joerg Schoppet


Hi Joerg,

while designing lib/div I was always thinking of FE libraries and
postponed planning of the BE until everything would work for the FE. 

Generally I think it should be possible to extend lib/div for BE usage.

There are some differences with the BE:

1.) While the FE is passively called by the Framework BE scripts are
active index.php files that call the framework themself. (So the FE way is
"Inversion of controll")

2.) The BE has a variing base path. It varies by the typo3/ directory.

3.) BE parameters don't work with a designator, but send plain variables.

4.) Different libraries are used.


So what does this mean for a lib/div extension for the BE?

1.) Maybe the index.php could instantiate a BE class of lib/div that does
the instantiation of the necessary libraries.

2.) All lib/div classes inherit from the class tx_lib_selfAwareness now
(see SVN), to find the own positions and names. It would be necessary to
extend this class to do distingish automatically between FE and BE usage
and to do settings accordin to this.

3.) The link object is based on typolink wich is a typical FE class.
Probably a diffenet link class would be necessary for BE links.

4.) I think it is  the link and the image object that use typical FE
libraries. As they are only tools and not part of the MVC struts themself
it should be possible to provide link and image objects for the BE. 


I suggest to work with a branch of lib/div in SVN while experimenting with
the BE implementation. I will rename tx_lib_phpView to
tx_lib_phpTemplateEngine today and extract common function into a common
class for template engines tx_lib_templateEngineBase. Having done this I
think I will be content with all the namings of the classes. That will be
a good point to make a branch.

Regards

Elmar