gnue/designer/doc/technotes 00001.txt

[Jason Cater]

CVSROOT:        /cvsroot/gnue
Module name:    gnue
Changes by:     Jason Cater <address@hidden>    02/07/22 11:57:02

Modified files:
        designer/doc/technotes: 00001.txt 

Log message:
        modified wizard notes to reflect that wizards can now work at the 
object level, and not just at the 'create a new form' level

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/designer/doc/technotes/00001.txt.diff?tr1=1.2&tr2=1.3&r1=text&r2=text

Patches:
Index: gnue/designer/doc/technotes/00001.txt
diff -c gnue/designer/doc/technotes/00001.txt:1.2 
gnue/designer/doc/technotes/00001.txt:1.3
*** gnue/designer/doc/technotes/00001.txt:1.2   Mon Jul 22 11:47:31 2002
--- gnue/designer/doc/technotes/00001.txt       Mon Jul 22 11:57:02 2002
***************
*** 13,27 ****
  
  A valid package must contain at least three elements:
  
!   1) The package must import the TemplateBase package. All of the base
!      classes and convenience methods are defined in TemplateBase.
  
          from gnue.designer.TemplateBase import *
  
  
    2) A single class must be exposed that inherits a TemplateBase class.
!      Two convenience classes, FormTemplate and ReportTemplate, implement
!      the TemplateBase class for forms and reports, respectively.
  
          class SimpleFormTemplate(FormTemplate):
  
--- 13,41 ----
  
  A valid package must contain at least three elements:
  
!   1) The package must import the TemplateBase package, or a proper derivative.
!      All of the base classes and convenience methods are defined in 
TemplateBase.
  
          from gnue.designer.TemplateBase import *
  
+      Note: Individual tools override TemplateBase, so you should import:
+ 
+         from gnue.designer.<PACKAGE>.TemplateSupport import *
+ 
+      So, if you are writing a forms template/wizard, the line would be:
+ 
+         from gnue.designer.forms.TemplateSupport import *
+ 
+      Or, for reports:
+ 
+         from gnue.designer.reports.TemplateSupport import *
+ 
+ 
  
    2) A single class must be exposed that inherits a TemplateBase class.
!      Each product defines its own TemplateBase.  The class is usually named
!      as <Package>Template (e.g., FormTemplate, ReportTemplate, etc), although
!      this is not a hard rule.
  
          class SimpleFormTemplate(FormTemplate):
  
***************
*** 44,51 ****
  
  The basic difference, from an end-user's viewpoint, between a wizard and a
  template is that a wizard interacts with the user (to get data or to at least
! provide feedback) whereas a template simply creates a new Form or Report
! without any sort of user intervention.
  
  From the developer's viewpoint, a template only implements the Start() and
  Finalize() methods, whereas the wizard also implements the GetStep() and
--- 58,65 ----
  
  The basic difference, from an end-user's viewpoint, between a wizard and a
  template is that a wizard interacts with the user (to get data or to at least
! provide feedback) whereas a template simply performs an action without any
! sort of user intervention.
  
  From the developer's viewpoint, a template only implements the Start() and
  Finalize() methods, whereas the wizard also implements the GetStep() and