Hi, As promised to Toby, this email concerns research I've made for the form component requirements.
eZ Publish team works hard on making the kernel more modular and modules easier to do with the recent developer API, but eZ is still responsible not only for the kernel but also the components. Django made it possible to develop applications that are reusable in different projects. The demand is considerably high: there are thousands of apps hosted on google. Reusing this applications should highly reduce development and maintenance costs, although their documentation did not take this in account, making 90% of the apps not over loadable. Development and maintenance costs would decrease with eZ Components if only the Framework allowed to create reusable and overloadable applications. This is the reason why i made this research/poc. Research proven needs: - a template location that allows overloading, - a persistent definition manager that loads persistent object definitions of all applications, - a shortcut method for the mvc router to import routes more easily, - result object namespacing: to know from which app to import the views, Other needs i can think of follow. Application static stuff (css, js ...) Those should be bundlable in a convenient for httpd configuration. Dependencies between applications Pear can not only do that, but also allow making a future application package manager. Inter-component communication Factories like ezcMvcRequest+ezcDbSchema->PersistentObject instance, PersistentObjectDefinition+ezcDbSchema->ezcUserInput definition, etc, etc ... Two solutions: either make the user maintain all definitions and load them all in an abstract factory class; or make an intermediary form - which i still highly recommend because it could also be used to generate HTML (be "details" of an object, an object "list" table or even a form and userinput definition). Overloadable applications Basically that's mostly solved by MvcTools, are left-over: static stuff, definitions (po, ui, etc, etc ...). Sources: http://github.com/jpic/ezc-framework-apps/tree http://blog.chocolatpistache.com/blog/tag/django/ Regards, James. -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
