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

Dylan Jay wrote:
> The default content and configuration is installed on first install maybe vs GS. You would likely have upgrades to the diazo or plugins but you would have to ship upgrade profiles to the GS if you wanted to ship a theme that included upgrades to configuration. Most likely you wouldn't.
> The idea is to help people get started quickly so they have to make so many choices on how to get a useful site for their purpose quickly.

So, I wrote a proof-of-concept skeleton for this:

https://github.com/datakurre/collective.themesitesetup/tree/master/src/collective/themesitesetup

- a view (for writable resource directory), which dumps GS export into a 
timepstamp-named directory into context resource directory.

- a p.a.theming-plugin, which imports configured "install"-profile 
during theme activation an optional "uninstall"-profile during theme 
deactivation

- current configuration in the theme manifest

       [theme:genericsetup]
       install = profile
       uninstall =

Notes:

- plone resource directories are globally configured to filter dot-files 
and therefore dotted files must be handled as special cases (e.g. 
".objects" and ".properties" are renamed to just "objects" and "properties")

- nobody has ever made a plugin for p.a.theming onEnabled-hook, because 
that was broken: 
https://github.com/plone/plone.app.theming/compare/1.1.x...datakurre-1.1.x-fix-on-enabled-pluginsupport

Cheers,
Asko

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/