Ideas for an eZModuleInterface

Monday 21 June 2010 2:58:29 am

Taking a slightly different approach to the original problem (simplifying development of new views via php classes):

• define a conventional dir where 'controller' php classes are to be put
• every new public, static method of those classes becomes a view
• those methods must return either a chunk of html code or the $results array
• for access checking, a policy limitation is available per single method of every controller class

If this sounds yummy, please join development effort on the upcoming "eZ On rails" extension!

Under the hood:

• no kernel hacks
• one single new module: ezonrails
• one new view per controller class
• the actual class methods end up as first positional parameter
• no validation (yet) of the parameters passed to php methods, but it can be done via introspection

http://projects.ez.no/ezonrails

Principal Consultant International Business
Member of the Community Project Board