[TYPO3-ect] Relations between MVC and FE Forms Library
Elmar Hinz
elmar.DOT.hinz at team.MINUS.red.DOT.net
Thu Jan 26 10:07:31 CET 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I think this is of general interest. ECT has two projects in the pipe, the
model-view-controller project and the forms project. How are they related?
Additionally both are related to kickstarter development.
This question is of interest because the existing MVC extensions contain
form functions themselvs. On the other hand the draft of the forms project
contains actions and BE panel. So it also conatains MVC functionality.
http://wiki.typo3.org/index.php/Forms_Library_for_FE_Extensions
How can we prevent to do it all in double and make it work together? Let me make
a proposal:
- --------------------------------------------------------------------------------
The MVC Framework
- --------------------------------------------------------------------------------
MVC // abstract set of 3 classes
/ \ // extends to
BE MVC FE MVC // successors of t3lib_SCbase and pi_base
| | // extend to
- --------------------------------------------------------------------------------
| | The Generic FE Form System as MVC implementation
- --------------------------------------------------------------------------------
Module Plugin // BE panel and FE plugin
V ? V // use
- --------------------------------------------------------------------------------
V ? V The $TCA Configured Forms Library
- --------------------------------------------------------------------------------
$TCA evaluation layer // configuration of inputs
V // based on
- --------------------------------------------------------------------------------
V The General (x)Forms Library
- --------------------------------------------------------------------------------
input elements library // a simple library of inputs, js and checks
The point is, that the "Generic FE Form System" is only one possible
implementation of it all. The FE and BE extensions you build with it, would in
the same way extend the "MVC Framework". They could use the "$TCA Configured
Forms Library" or only the "General Forms Library" or none of them.
"successors" of t3lib_SCbase and pi_base means that we don't remove them. But we
we offer one alternative based on a MVC model.
For BE modules the question is, if they also should be able to use the forms
library. They have the $TCE available.
Regards
Elmar
- --
Climate change 2006 is killing people: floods in California, drought and fires
in Australia, Texas, Sahel, Oklahoma, South Africa. The Bush administration is
responsible for corruption of the Kyoto Protocol. The US majority is responsible
to the world for reelection of a convictable [...censored by Echelon...].
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD2JFTO976RNoy/18RAqOdAJ42/RizYRxwbWOs0SX7me0DDG4J0ACgvm3M
uUpTgX9wGJMR0TSz6SdtwHw=
=j1zG
-----END PGP SIGNATURE-----
More information about the TYPO3-team-extension-coordination
mailing list