[TYPO3-mvc] Few proposals for mvc_extjs view branch

Dmitri Pisarev dimaip at gmail.com
Wed Jun 9 11:11:28 CEST 2010


Dear Dennis and others who are interested in mvc_extjs,

As I have already said a couple of times, I really love the new view 
branch (btw, how shall I call it?) of mvc_extjs extension. But there is 
a certain concern: ExtJS has tones of parameters, with more and more 
being added at each version.
Some of this parameters require special treatment in the viewhelper code 
(i.e. columns parameter), while most(like 90%) of the others just dump 
some js code like(autoLoad, paramNames etc).

My proposal is to do it more generally, I see two basic aproaches:
1)See if the parameter is registred in fluid, if yes the treat it 
accordingly, is not the just do ->setRaw('paramName', $paramValue). But 
I don't know if it's possible in fluid to pass unregistered parameters.
2)For every view helper introduce an array() property which would 
consist of 'paramName'=>'paramValue' pairs. As far as I can see, this 
implementation has almost no drawbacks, because you surely know what to 
expect from this kind of property, and use it on your own risk.

The implementation two is super simple, and if you want I can write a patch.
This would allow not to spend all of the time adding more and more dumb 
setRaw parameters, while concentrating on the more important 
architecture parts, like extDirect.

I'm complete novice at programming, and don't know any modern 
programming best practices, so please tell me if my proposal has any 
serious flaws...

Regards,
Dmitri.


More information about the TYPO3-project-typo3v4mvc mailing list