On Dec 13, 2007 10:03 AM, Balazs Ree <[EMAIL PROTECTED]> wrote: > http://plone.org/products/plone/roadmap/215
Having already talked with Balazs about what's in 1.4 in Napels, I'll give this my +1 as well. > About this last issue I have a particular question. If I do all this, > still two things will be separate from the plone.app.kss package: > > - GS profiles that set up the js, kss - still in Products.CMFPlone > > - the *.kss that are in skins in Products.CMFPlone. > > Do you have any suggestion on how these could best be moved inside > plone.app.kss? Maybe a GS profile in the product would be a good solution > for both resources and skins? I think that with PLIP #195 accepted and nearly ready, we should use profile dependencies for this and move kss files back to the products to which they pertain. I find that moving all the kss files away from their dependencies and into a central package hampers maintenance somewhat. Unless the goal is to be able to disable kss cleanly by removing the *.kss packages, at which point the kss profile should live there too and the Products.CMFPlone profile should depend on that. -- Martijn Pieters _______________________________________________ Framework-Team mailing list [email protected] http://lists.plone.org/mailman/listinfo/framework-team
