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

Asko Soukka wrote:
> Now it's possible to create selective exports into themes and
> continue from that TTW

TL;DR; next release of collective.themesitesetup provides support for 
exporting and importing templates and scripts from portal_skins/custom

Well, to get the original idea of "heavy TTW themes" really to work, it 
should be possible to populate e.g. portal_skins/custom with custom 
portlet templates to be able to configure portlet assignments with 
custom TTW portlets in portlets.xml:

I duck a bit deeper into, how GS content export/import works.

The default GS import/export support all DAV-aware content objects, but 
CMFCore selects to properly export and import only CMF-objects.

But I could do the following:

- add a marker interface for theme developer to enable exporting of 
portal_skins/custom (by tagging first portal_skins and then custom)

- enable export/import of page templates and zope scripts by
   tagging their classes with a required interface (they are DAV-aware,
   but they are just too old to provide the interface)

- register a custom GS exporter for Plone site root to support
   the previous

https://github.com/collective/collective.themesitesetup/commit/332ea1a1c0e4955d98b2ca70575c23af0efd66db

The only "ugly" part is that I have to override the default GS content 
exporter for Plone site root, the new one should actually be a bit 
better, because the default one exports stuff it doesn't import (e.g. 
acl_users' plugin configurations).

Regards,
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/