[TYPO3-ect] upcoming MVC library
Nikolas Hagelstein
hagelstein at shr.cc
Mon Oct 30 13:46:16 CET 2006
Hi,
I am currently trying to get an overview about the basic concepts
off the upcoming MVC FE plugin lib. So i decided to create a tiny
extension
using tx_lib and tx_div.
There are a bunch of issues i eigther do not understand or i am not
clear about
where they head for.
Model:
Currently the model isnt very well equipt at all.
(which goes without saying since it is at a real early state atm).
I would expect the model class being armed with most of the common
datasource
functions (e.g find, findall, getby"field", insert update etc).
Are there any plans about this?
Normally there is a appropriate TCA segment existing for almost every
table (i.e model) will this be used to provide additional information to
the model?
(e.g i18l information,relations etc)?
Controller:
ATM the controller seems to be very flexibel regarding its "application
flow" are there any
plans of integrating a defined course of operations (e.g before/after
filters, validation etc)?
Are there any plans about "action chaining/forwarding/requesting" ?
Furthermore the current way of passing data from the controller to the
view and vice versa needs
to be thought over IMHO (see Views beyond).
Views:
Regarding the "articles" sample the current way of passing data is to
use the exchangeArray function
filled up wiht a bunch of dataobjects which are accessed via e.g
"this->get('field')" withhin the view.
IMHO this is'nt quite sufficient, because:
-It restricts the view form interacting with different datasources.
-Objects are not nessarilly native datastructurs which may break MVC
rules
(at least from a pedantic point of view ;) )
Another great improvment to the view would be to have a helper class
containing
things like HTML functions etc.
ATM it is quite unhandy to define nested views due to the lack of action
chaining.
In generall i would suggest to have a look at already existing MVC libs
(Cake,struts, mojavi, onrails etc) and see how they solve issues instead
of reinventing the wheel.
Just to clearify things i do not what to complain. I like to see T3 and
its api becoming better.
I hope the above is picked as what it is thought for and nobody feels
offended by the above mentioned.
cheers,
Nikolas
More information about the TYPO3-team-extension-coordination
mailing list