Quintagroup Plone Skin Dump qPloneSkinDump allows to create Plone product (in file system) from some ZMI based skin folder (eg "custom") from portal_skins. So you can easy design new Plone skin with all customized styles, page tamplates, python scripts, ECMA-scripts, Images and other objects, located in some folder of portal_skins. Than dump it to new Plone Skin Product to file system. Features: - Support dumping objects from generated portal's root to Skin Product for adding this objects to destination portal root on iinstalling Skin Product. - Dump css and ecma-cripts resources registries from generated portal to Skin Product for right working styles and ecma-scripts. - Allow dumping sorce skin folder with subfolder tree. - Allow add aditional installation functions in config.py module generated Skin Product. - Allow customize slots for generated Skin Product. - All configuration data for Skin Procut can be easy changed in file system, cause all constants has detailed explanations and examples. Installation: 1. Install qPloneSkinDump as Zope product 2. Install qPloneSkinDump in your Plone instance with QuickInstaller (Plone Control Panel -> Add/remove Products) Usage 1. Create standart Plone Folder ( ) in portal_skins or use standard 'custom' folder and fill it with content according to your needs. You can create subfolders in . 2. Go to the Plone Control Panel, select "qPloneSkinDump Configuration" configlet and edit corresponding form fields: - is the name of the folder where all the content and styles are located in ZMI ../portal_skins/. - is name of the Plone Skin, which list of layers will be used for creating new skin. (eg "Plone Tableless"). - is checkbox for erasing folder from portal_skins after Product creating. - is the name of skin folder for new product ( Actually Products//skin/ ), that will be based on the staff. This also used as name of new Plone skin. - - the name of new Plone product. - - Check it for PROVIDING SLOTS CUSTOMIZATION in New Skin Product. - , - left and right slots lists for New Plone Product. You are responsible for leaving only those portlets, which relate to your skin product or are standard for Plone. - - slot's list forming control on New Plone Product installation. -
- decide in which column leave same slots, in case of meetings one. - - check it for export objects from your Portal root to Skin Product. Than chosed objects will be added to Portal root (where Skin Product will be installed) on installation. - - define how will be imports objects to portal root on installation Skin Product if will be meeting same named (id) objects. - multyselected list for choosing objects from generated portal, which must be imported to portal root on Skin Product's installation. - - switch on|off dumping portal_css registry resources with all properties sets. Be attentive when switch-off this checkbox. When switch-on - all css-es of your new Skin Product and other portal_css resources will be sets identically to your settings and this guarantee identical look and behavior of your skeen on other Plone site. - - switch on|off dumping portal_javascripts registry resources with all properties sets. Be attentive when switch-off this checkbox. When switch-on - all ECMA-scripts of your new Skin Product and other portal_javascripts resources will be sets identically to your settings and this guarantee identical look and behavior of your skeen on other Plone site. 5. For using new Plone product you must reload Zope, and install it in quickinstaller. In file system new product located in ../Products/. Caution If you wish distribute generated Skin Product, you must - (for Plone 2.1+) before run generation remove all non-standard (for Plone dstribution) css and jvascripts resources from plone_css and plone_javascripts registries, which aren't related to new Skin Product (not in the ) Authors * Andriy Mylenkyy License * ZPL