Menu
▾
▴
[Plone-cvs] CMFPlone/interfaces interface.py,NONE,1.1 CustomizationPolicy.py,1.1,1.2 FormTool.py,1.1,1.2 NavigationController.py,1.1,1.2
|
From: <dre...@us...> - 2003-04-23 16:13:21
|
Update of /cvsroot/plone/CMFPlone/interfaces
In directory sc8-pr-cvs1:/tmp/cvs-serv25426/interfaces
Modified Files:
CustomizationPolicy.py FormTool.py NavigationController.py
Added Files:
interface.py
Log Message:
Fixed Plone-HEAD with CMF-HEAD. *REQUIRES* CMF-HEAD
--- NEW FILE: interface.py ---
try:
from Interface import Base as Interface
from Interface.Attr import Attribute
except:
from Interface import Interface
from Interface.Attribute import Attribute
Index: CustomizationPolicy.py
===================================================================
RCS file: /cvsroot/plone/CMFPlone/interfaces/CustomizationPolicy.py,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** CustomizationPolicy.py 2 Jul 2002 19:40:52 -0000 1.1
--- CustomizationPolicy.py 23 Apr 2003 16:13:17 -0000 1.2
***************
*** 1,13 ****
! from Interface import Base
! class ICustomizationPolicy(Base):
! """ A Customization Policy is responsible for setting up a raw Plone instance according to the
! instruction provided for the Policy. The Policy must register via Products.CMFPlone.Portal.addPolicy
"""
def customize(portal):
! """ the customize method takes the portal object and massages it. the only thing that really needs
! to be understood is that the Policy itself is not persisted. most likely a CustomizationPolicy
! would be derived from the DefaultCustomizationPolicy, you would call its customize() method and tehn
! continue on customization the portal
"""
--- 1,21 ----
! from interface import Interface
! class ICustomizationPolicy(Interface):
! """
! A Customization Policy is responsible for setting up a raw
! Plone instance according to the instruction provided for the
! Policy. The Policy must register via
! Products.CMFPlone.Portal.addPolicy
"""
def customize(portal):
! """
! the customize method takes the portal object and massages
! it. the only thing that really needs to be understood is that
! the Policy itself is not persisted.
!
! Most likely a
! CustomizationPolicy would be derived from the
! DefaultCustomizationPolicy, you would call its customize()
! method and then continue on customization the portal.
"""
Index: FormTool.py
===================================================================
RCS file: /cvsroot/plone/CMFPlone/interfaces/FormTool.py,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** FormTool.py 9 Sep 2002 02:41:06 -0000 1.1
--- FormTool.py 23 Apr 2003 16:13:17 -0000 1.2
***************
*** 1,5 ****
! from Interface import Base
! class ICMFForm(Base):
""" Wraps a Formulator BasicForm and provides convience methods to ease validation """
--- 1,5 ----
! from interface import Interface
! class ICMFForm(Interface):
""" Wraps a Formulator BasicForm and provides convience methods to ease validation """
***************
*** 17,21 ****
"""
! class IFormTool(Base):
""" FormTool handles Form validation, caching of Form validators and serves as a factory for portal_form objects.
"""
--- 17,21 ----
"""
! class IFormTool(Interface):
""" FormTool handles Form validation, caching of Form validators and serves as a factory for portal_form objects.
"""
Index: NavigationController.py
===================================================================
RCS file: /cvsroot/plone/CMFPlone/interfaces/NavigationController.py,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** NavigationController.py 9 Sep 2002 01:17:14 -0000 1.1
--- NavigationController.py 23 Apr 2003 16:13:17 -0000 1.2
***************
*** 1,5 ****
! from Interface import Base
! class INavigationController(Base):
""" The NavigationController acts as a controller that controls complex states of the system.
--- 1,5 ----
! from interface import Interface
! class INavigationController(Interface):
""" The NavigationController acts as a controller that controls complex states of the system.
***************
*** 33,47 ****
status - SUCCESS or FAILURE strings used in calculating destination
! destination - is an action registed on the TypeInfo or a free-form script
! that would be appended to the url of the content
! Destinations are specified as follows:
! action:ACTION_NAME invokes the action ACTION_NAME on the current context
! script:SCRIPT_NAME invokes the python script SCRIPT_NAME on the current context.
! The script should return a tuple containing a status code (either 'success'
! or 'failure') and optional kwargs. getNext() will be called using the return code to determine the next page
! to load.
! url:URL redirects to the url specified by URL. URL may be absolute or relative
! PAGE invokes the page PAGE on the current context
! """
def removeTransitionFrom(content, script=None, status=None):
--- 33,52 ----
status - SUCCESS or FAILURE strings used in calculating destination
! destination - is an action registed on the TypeInfo or a
! free-form script that would be appended to
! the url of the content Destinations are
! specified as follows: action:ACTION_NAME
! invokes the action ACTION_NAME on the
! current context script:SCRIPT_NAME invokes
! the python script SCRIPT_NAME on the current
! context. The script should return a tuple
! containing a status code (either 'success'
! or 'failure') and optional kwargs.
! getNext() will be called using the return
! code to determine the next page to load.
! url:URL redirects to the url specified by
! URL. URL may be absolute or relative PAGE
! invokes the page PAGE on the current context
! """
def removeTransitionFrom(content, script=None, status=None):
|