My +1 for moving them to Extras. Reason is, if we need to keep it for best practice guide or for training then no doubt its a extra work. We can give good documentation with details about how to use /extras/example component to learn and keep it as best practice guide. Also we can promote this in user mailing lists .
Thanks -- Divesh On Mar 21, 2012, at 4:14 AM, Jacques Le Roux wrote: > From: "Mansour Al Akeel" <mansour.alak...@gmail.com> >> Everyone has different preference about how would the basic component >> skeleton looks like (ie, with ajax, without, exta functionality .... >> ). >> Even if a basic example included with ofbiz distribution, in the >> future it will grow again with extra unneeded functionality, or it >> will be an on going discussion about what should go there. >> >> It's much easier to provide a very basic skeleton as a separate >> download, to serve as an example and a reference. There could be more >> than one example provided, each showing different capabilities and >> different techniques. This is better than creating one huge example to >> show everything, and better than showing only the basics without any >> additional tips (ie, ajax). >> >> Those who are not satisfied with the examples as a skeleton, can >> maintain their own copy that will make him/her start a component >> quickly. >> >> Examples are not needed to run ofbiz. > > So they (examples and examplesext) could be in specialpurpose (+1) of even > Extras (0) > > Jacques > >> >> On Tue, Mar 20, 2012 at 4:33 PM, Erwan de FERRIERES >> <erwan.de-ferrie...@nereide.fr> wrote: >>> Le 20/03/2012 12:47, Jacopo Cappellato a écrit : >>>>> >>>>> Q) framework/example and framework/exampleext: move to specialpurpose >>>> >>>> >>>> Adrian would like to keep Example in the framework but slim it down a lot >>>> to the essential (no form widgets examples, no Ajax examples, no content >>>> examples etc...). Adrian would you please confirm if in your vision the >>>> "example" application should document the layout of a typical OFBiz >>>> component only? If yes, we could use the output of the "ant >>>> create-component" task to document the best practice layout. >>>> Jacques, Olivier would like to keep also the examples for the various >>>> higher level features available to OFBiz applications. >>>> >>>> I think that from the discussion it could emerge the following solution to >>>> please everyone: >>>> >>>> * keep the "example" component in the framework but slim it down to the >>>> bare essential >>>> * move the "exampleext" component to specialpurpose and migrate to it all >>>> the extra features: this could also be used as a best practice guide on how >>>> to extend a component from hot-deploy/specialpurpose >>>> >>>> I still think that it would be nicer to not bundle the "example" component >>>> ootb to keep the framework cleaner: the example should be downloaded >>>> separately (when we will have clear separation between framework and the >>>> rest); this approach is similar to tomcat and its example applications. But >>>> I don't have a strong opinion on this. >>>> >>>> Jacopo >>>> >>>> >>> create 2 components, one basic with simple CRUD and no ajax or whatever, and >>> another one with more eye candy stuff (ajax, modal forms, etc...). Both >>> components should be in specialpurpose/ >>> I'm not in favor of moving them to extras, as when delivering an official >>> release there should be a showcase included. And as Adrian said, when >>> teaching people how to create apps with OFBiz, this could be really useful. >>> And with JSR-223, there's a lot to add ! >>> >>> -- >>> Erwan de FERRIERES >>> www.nereide.biz
