[Typo3-dev] BE - mixing modules and regular forms

Elmar Hinz elmar.DOT.hinz at team.MINUS.red.DOT.net
Sat Dec 10 12:09:36 CET 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> 
> 
> That's why it is *low level*. There are lots of places in TYPO3 where

I see the point. I can develop my library towards a layer upon it. It
will be less monolitic then.

> you have a form which is not defined in $TCA, or not even related to a
> DB at all. Like the new pages wizard, or the survey extensions, or ...
> 
> 
> PS: I basically reimplement parts of PEAR::HTML_FORM which we can't use
> for licensing and style issues.

I see. Perhaps you could do it directly as a new PEAR class. Then it
would get additional uses.

Did you think about an controller model (actions) in this context.
Struts or ruby on rails could serve as models here.

Regards

Elmar

P.S.

Do you live in Berlin?

- --
Climate change 2005: Mexico, Guatemala, New Orleans, Sahel, Bangladesh,
Spain, Portugal, Austria, Swiss, France, ...
Production of CO2 is killing people.
Production of CO2 just for fun is killing people just for fun.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDmrdwO976RNoy/18RAn2EAKCJ+zXsvox3foKmOSUIM049s5JzUwCfQ8VW
6bqALuCrxD2PT2QwbHjA1xo=
=QmfG
-----END PGP SIGNATURE-----




More information about the TYPO3-dev mailing list