Commits

Ed Crewe  committed e725cf3

add skins config for plone4 default skins

  • Participants
  • Parent commits 2e8a55b

Comments (0)

Files changed (3)

File ilrt.formalworkflow.egg-info/PKG-INFO

         <http://www.ilrt.bris.ac.uk/>`_ at University of Bristol, September 10th 2009
         
         Formal workflow is designed for sites where there may be many editors
-        for whom unmoderated access to change live published content on the
-        web site is not desired. A typical scenario may be an organistaion's
+        for whom unmoderated access to change live published content on the 
+        web site is not desired. A typical scenario may be an organistaion's 
         public website which has to comply with certain legal restrictions or
         editorial style for example. To ensure this compliance only a limited
         subset of editors are trusted to review and publish content.
         Whilst content in the private state is available to all editors.
         
-        This package applies a workflow definition based on simple publication
+        This package applies a workflow definition based on simple publication 
         workflow ... but it ensures that editors cannot modify public content.
-        Instead it enables `plone.app.iterate`_  with which users can check out a
+        Instead it enables `plone.app.iterate`_  with which users can check out a 
         working copy of a published item to work on and resubmit for review.
         
         .. _`plone.app.iterate`: http://pypi.python.org/pypi/plone.app.iterate
         
-        Editors and owners are also restricted from deleting published items or
-        reverting them to past versions, essentially anything that could change
+        Editors and owners are also restricted from deleting published items or 
+        reverting them to past versions, essentially anything that could change 
         published content, without review.
         
         Workflow
         --------
         
-        A diagram of the workflow is available in /docs folder
+        A diagram of the workflow is available in /docs folder   
         
         .. image:: http://mail.ilrt.bris.ac.uk/~cmetc/images/formalworkflow.png
         
         The following walks through a user story::
         
-        Editor
-        - An editor creates a document
-        - They edit and then submit it for review
-        - It is now in the pending state
+          Editor
+          - An editor creates a document
+          - They edit and then submit it for review
+          - It is now in the pending state
         
-        Reviewer
-        - The document appears for review in their review list so they click on it
-        - They make a few minor ammendments and publish it
+          Reviewer
+          - The document appears for review in their review list so they click on it
+          - They make a few minor ammendments and publish it
         
-        Editor
-        - A week later some more information needs to be added to the document
-        - The editor goes to it, but it there is no workflow menu just
-        State:Published so they cannot retract it. The edit and history tabs
-        are also gone. So instead they must click on 'Make changes' from the actions menu.
-        - This locks the item and marks it as being edited in a working copy.
-        - The editor does their edits then clicks on submit to bring their changes to the
-        attention of the reviewer
+          Editor
+          - A week later some more information needs to be added to the document
+          - The editor goes to it, but it there is no workflow menu just 
+            State:Published so they cannot retract it. The edit and history tabs
+            are also gone. So instead they must click on 'Make changes' from the actions menu.
+          - This locks the item and marks it as being edited in a working copy.
+          - The editor does their edits then clicks on submit to bring their changes to the
+            attention of the reviewer
         
-        Reviewer
-        - The reviewer sees the page pop up in their review list
-        - They click on it and look at the changes the editor has made.
-        They like the changes but decide they want some modifications made to them
-        by the editor. They dont want to 'Cancel changes' since the editor has done a
-        lot of changes, so they just add a note of the further changes needed and make
-        the working copy private again.
+          Reviewer
+          - The reviewer sees the page pop up in their review list
+          - They click on it and look at the changes the editor has made. 
+            They like the changes but decide they want some modifications made to them
+            by the editor. They dont want to 'Cancel changes' since the editor has done a
+            lot of changes, so they just add a note of the further changes needed and make
+            the working copy private again.
         
-        Editor
-        - The editor reads the comment and re-edits the working copy, once these final changes
-        are complete is it resubmitted to the pending state.
+          Editor
+          - The editor reads the comment and re-edits the working copy, once these final changes
+            are complete is it resubmitted to the pending state. 
         
-        Reviewer
-        - The reviewer notices the item is back again in their review list, so realises
-        it has been re-edited.
-        They click on it ... see that it is ready and so do the 'Accept changes' to replace
-        the current published version, at which point the working copy is removed.
+          Reviewer
+          - The reviewer notices the item is back again in their review list, so realises 
+            it has been re-edited.
+            They click on it ... see that it is ready and so do the 'Accept changes' to replace 
+            the current published version, at which point the working copy is removed.
         
         Notes
         -----
         
         This package is really all just xml config data and reworking skin copy, paste
         and delete security to be object specific rather than folder based.
-        However though it contains little python aside from the functional tests,
-        it is a commonly required workflow which does require some time consuming
+        However though it contains little python aside from the functional tests, 
+        it is a commonly required workflow which does require some time consuming 
         configuration tweaks.
         
         If this workflow is applied in conjunction with a theme egg then the formalworkflow
-        skin should be added near the top of the editing layer's skins listing in the
+        skin should be added near the top of the editing layer's skins listing in the 
         portal_skins tool.
         
-        If this workflow is applied to an existing site you may require the
-        `ilrt.migrationtool
-        <http://pypi.python.org/pypi/ilrt.migrationtool>`_ to use its utility for mapping
-        existing content states from one workflow to another. Otherwise changing
+        If this workflow is applied to an existing site you may require the 
+        `ilrt.migrationtool 
+        <http://pypi.python.org/pypi/ilrt.migrationtool>`_ to use its utility for mapping  
+        existing content states from one workflow to another. Otherwise changing 
         workflow reverts objects to the new workflow's default state.
         
-        If you wish to use custom types with this workflow you will need to make them versionable
-        via the
+        If you wish to use custom types with this workflow you will need to make them versionable 
+        via the 
         `portal_repository tool
-        <http://plone.org/documentation/how-to/enabling-versioning-on-your-custom-content-types>`_ or
-        plone.app.iterate will not be available for them.
+        <http://plone.org/documentation/how-to/enabling-versioning-on-your-custom-content-types>`_ or 
+        plone.app.iterate will not be available for them. 
         
-        If formal workflow is applied to folders (as is the default profile setting) then types
-        without workflow such as images and files cannot be added or deleted by editors.
-        To fix this a slightly adapted version of one_state_workflow is also included for these
-        content types that allows for editors to modify this content unrestricted.
+        If formal workflow is applied to folders (as is the default profile setting) then types 
+        without workflow such as images and files cannot be added or deleted by editors.  
+        To fix this a slightly adapted version of one_state_workflow is also included for these 
+        content types that allows for editors to modify this content unrestricted. 
         
-        You can customize which types use formal_worflow, and hence enforce a review process,
-        via the the portal_workflow tool. You could also choose to only apply formal workflow
+        You can customize which types use formal_worflow, and hence enforce a review process, 
+        via the the portal_workflow tool. You could also choose to only apply formal workflow 
         to the high profile parts of your site, via `placeful workflow
         <http://pypi.python.org/pypi/Products.CMFPlacefulWorkflow>`_.
         
         Changelog for ilrt.formalworkflow
         ---------------------------------
         
-        (name of developer listed in brackets)
+            (name of developer listed in brackets)
         
         ilrt.formalworkflow - 0.6 Released - 10th September 2009
         
-        - Tested against plone 3.3 - fixed tests
-        - Added option to globally set check out location in site properties.
+            - Tested against plone 3.3 - fixed tests
+            - Added option to globally set check out location in site properties.
         
-        [Ed Crewe, ILRT - University of Bristol]
+            [Ed Crewe, ILRT - University of Bristol]
         
         ilrt.formalworkflow - 0.5 Released - 10th June 2009
         
-        - Added a subclass of the iterate info viewlet to redeclare the security so that
-        editors can see it and find existing checkouts.
+            - Added a subclass of the iterate info viewlet to redeclare the security so that 
+              editors can see it and find existing checkouts.
         
-        [Dave Mote, Washtenaw County Government]
+            [Dave Mote, Washtenaw County Government]
         
         ilrt.formalworkflow - 0.4 Released - 20th May 2009
         
-        - Added an adapted version of one_state_workflow to allow editors to add
-        and delete images and files. Since the default formalworkflow profile adds
-        formal_workflow to folders - blocking editor modification of unworkflowed types.
+            - Added an adapted version of one_state_workflow to allow editors to add 
+              and delete images and files. Since the default formalworkflow profile adds 
+              formal_workflow to folders - blocking editor modification of unworkflowed types.
         
-        [Ed Crewe, ILRT - University of Bristol]
+            [Ed Crewe, ILRT - University of Bristol]
         
         ilrt.formalworkflow - 0.3 Released - 5th April 2009
         
-        - Changed action names and templates to be less versioning orientated
-        Now uses Make changes, Accept changes and Cancel changes
-        - Fixed folder permissions checks blocking delete, copy and paste of objects
-        in published folders for editors
-        - Cleaned up permissions
-        - Removed unnecessary formalworkflow layer
+            - Changed action names and templates to be less versioning orientated
+              Now uses Make changes, Accept changes and Cancel changes
+            - Fixed folder permissions checks blocking delete, copy and paste of objects
+              in published folders for editors
+            - Cleaned up permissions
+            - Removed unnecessary formalworkflow layer
         
-        [Ed Crewe, ILRT - University of Bristol]
+            [Ed Crewe, ILRT - University of Bristol]
         
         ilrt.formalworkflow - 0.2 Released - 20th Jan 2009
         
-        - Released to pypi with some documentation
+            - Released to pypi with some documentation
         
-        [Ed Crewe, ILRT - University of Bristol]
+            [Ed Crewe, ILRT - University of Bristol]
         
         ilrt.formalworkflow - 0.1 Unreleased
         
-        - Initial package structure.
+            - Initial package structure.
         
-        [zopeskel]
+            [zopeskel]
         
         
         To Do list
         ----------
         
-        #. Find a better way to allow permissions of objects to be used rather
-        than those of their containers for delete, copy and paste.
-        Currently it uses a workaround that needs proxy manager then does a
-        manual permission check, within the skins.
+        #. Find a better way to allow permissions of objects to be used rather 
+           than those of their containers for delete, copy and paste.
+           Currently it uses a workaround that needs proxy manager then does a
+           manual permission check, within the skins.
         
         
         

File ilrt.formalworkflow.egg-info/SOURCES.txt

 MANIFEST.in
+README.txt
 ilrt.formalworkflow-configure.zcml
 setup.cfg
 setup.py

File ilrt/formalworkflow/profiles/default/skins.xml

       folder permission being different if it is published.
       -->
 
-<object name="portal_skins" allow_any="False" cookie_persistence="False"
-   default_skin="formalworkflow">
+<object name="portal_skins" allow_any="False" cookie_persistence="False">
 
  <object name="formalworkflow"
     meta_type="Filesystem Directory View"
     directory="ilrt.formalworkflow:skins/formalworkflow"/>
 
- <skin-path name="formalworkflow" based-on="Plone Default">
-  <layer name="formalworkflow"
-     insert-after="custom"/>
+ <skin-path name="Sunburst Theme">
+  <layer name="formalworkflow" insert-after="custom"/>
+ </skin-path>
+
+ <skin-path name="Plone Classic Theme">
+  <layer name="formalworkflow" insert-after="custom"/>
  </skin-path>
 
 </object>