Re: What I'd like to see gsoc achieve: plone distributions

> I think this indicates the danger of not including required plugins in the setup. If we make it easy to include custom code but hard to reuse plugins then we end up with sites that require to much knowledge to modify so aren't simple for begginers.
> So any ideas on the best way to solve having required plugins inside GS in a diazo theme?
> 

Of course it's "possible". We just didn't get it for free with the current GS API.

But which one would be better:

a) adding support for metadata.xml, where you need to know about GS profile naming syntax
b) adding support for defining dependencies in manifest.cfg

[theme:quickinstaller]
install = 
    foo
    bar

I'd prefer b), because a) has a few issues:

- you cannot "export" metadata.xml; all the other steps you can export and just clean up the export instead requiring to remember the GS xml syntax

- even with metadata.xml, the actual installing should probably be done using quickinstaller, so just making installation its own "theme plugin" would be simplier and more "honest" (p.a.theming plugins have dependency order, which takes care that quickinstaller-plugin is called before genericsetup-plugins)

Regards
Asko

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers