[TYPO3-core] RFC #8985: Enable USER object to become USER_INT on the fly

Dmitry Dulepov [typo3] dmitry at typo3.org
Mon Jul 21 11:54:12 CEST 2008


Hi!

Ingo Renner wrote:
> I thought about it a little more... As I'm currently also working on the 
> new functions for the templating system, here's some info from that side:
> 
> With the new system you'll be able to pass objects to the engine:
> 
> $template->addVariable('myVariable', new MyObject());
> 
> You can then use it in your template with this marker 
> ###MYVARIABLE.SOME_PROPERTY###
> 
> The engine will then take care of finding the MYVARIABLE markers and 
> translate the SOME_PROPERTY part to a 'getSomeProperty()' call on the 
> object.

Cool!

> ... so strictly and consitantly using camleCase is not only a matter of 
> style but also an issue of 'automated' method finding (let's call it 
> like that for now -  I don't know a better name ATM).
> 
> Do you agree and see the point?

I think we can close this particular topic of discussion. Let's use CGL. As Ingo said it does not follow exclusions and it exists to follow it. This is the best for all of us.

-- 
Dmitry Dulepov
TYPO3 Core team
More about TYPO3: http://typo3bloke.net/
Subscribe: http://typo3bloke.net/rss.xml
Latest article: http://typo3bloke.net/post-details/nominate_me_as_typo3_mvp/


More information about the TYPO3-team-core mailing list