gnue/common/doc common-techref.lyx

[James Thompson]

CVSROOT:        /cvsroot/gnue
Module name:    gnue
Changes by:     James Thompson <address@hidden> 02/05/03 16:01:44

Modified files:
        common/doc     : common-techref.lyx 

Log message:
        Checking in mess so Reinhard has something to read

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/common/doc/common-techref.lyx.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: gnue/common/doc/common-techref.lyx
diff -c gnue/common/doc/common-techref.lyx:1.1 
gnue/common/doc/common-techref.lyx:1.2
*** gnue/common/doc/common-techref.lyx:1.1      Thu Apr 11 16:19:18 2002
--- gnue/common/doc/common-techref.lyx  Fri May  3 16:01:44 2002
***************
*** 186,192 ****
  
  
  \begin_inset  Tabular
! <lyxtabular version="2" rows="7" columns="2">
  <features rotate="false" islongtable="false" endhead="0" endfirsthead="0" 
endfoot="0" endlastfoot="0">
  <column alignment="left" valignment="top" leftline="true" rightline="false" 
width="" special="">
  <column alignment="left" valignment="top" leftline="true" rightline="true" 
width="" special="">
--- 186,192 ----
  
  
  \begin_inset  Tabular
! <lyxtabular version="2" rows="8" columns="2">
  <features rotate="false" islongtable="false" endhead="0" endfirsthead="0" 
endfoot="0" endlastfoot="0">
  <column alignment="left" valignment="top" leftline="true" rightline="false" 
width="" special="">
  <column alignment="left" valignment="top" leftline="true" rightline="true" 
width="" special="">
***************
*** 291,296 ****
--- 291,314 ----
  
  \layout Standard
  
+ --interactive-debugger
+ \end_inset 
+ </cell>
+ <cell multicolumn="0" alignment="center" valignment="top" topline="true" 
bottomline="false" leftline="true" rightline="true" rotate="false" 
usebox="none" width="" special="">
+ \begin_inset Text
+ 
+ \layout Standard
+ 
+ Run application inside python's built-in debugger
+ \end_inset 
+ </cell>
+ </row>
+ <row topline="true" bottomline="false" newpage="false">
+ <cell multicolumn="0" alignment="center" valignment="top" topline="true" 
bottomline="false" leftline="true" rightline="false" rotate="false" 
usebox="none" width="" special="">
+ \begin_inset Text
+ 
+ \layout Standard
+ 
  --connections <loc>
  \end_inset 
  </cell>
***************
*** 679,705 ****
  Using the Data Access System
  \layout Standard
  
! The user interface in GNUe Forms is generated from the defined virutal form.
!  Thus the form designer doesn't need to concern themself with the features
!  of a specific widget set.
!  Instead the form designer describes the form's function and a UI driver
!  chooses the appropriate method of displaying that form based on the client's
!  capabilities.
!  However, this doesn't mean that the form designer has no control over how
!  their form looks.
  \layout Section
  
! Widget Coordinates
  \layout Standard
  
! The coordinate/layout system for widget in GNUE Forms needs to be able to
!  deal with text based displays as well as GUI systems.
!  Thus sizes and coordinates for widgets will need to be specified in character
!  coordinates.
!  Exceptions to this will include widgets that display pictures.
!  Support for grid style coordinates will be first then we will look at layout
!  managers that provide relative positioning similar to X/Java as well as
!  character coordinates like curses.
  \layout Chapter
  
  Using the XML<->Object System
--- 697,784 ----
  Using the Data Access System
  \layout Standard
  
! GNUe Common provides access to various types of data storage via it data
!  system.
!  The system is comprised of datasources, dataobjects, resultsets, recordsets,
!  and the connection manager.
!  
! \layout Section
! 
! The DataSource
! \layout Standard
! 
! A DataSource corresponds to the <datasource> tag in client files (GFD and
!  GRD for forms and reports, respectively).
!  The DataSource object acts as a implementation buffer between vendor-specific
!  DataObjects and vendor-neutral datasource tags (explained further in the
!  DataObject discussion).
!  In other words, a vendor-specific DataObject will be bound to the DataSource
!  after the DataSource is initialized.
!  Programs alway use the DataSource instances to access the DataObject, they
!  never reference the DataObject itself.
! \layout Standard
! 
! During initialization, a DataSource queries the GConnection manager for
!  a handle to a DataObject.
!  If necessary the GConnection manager will prompt the user for any required
!  authentication information.
!  If authentication is sucessfull then the end result is that the DataSource
!  is bound to a specifc database driver.
  \layout Section
  
! The DataObject
  \layout Standard
  
! A DataObject is the highest level object in the Database Driver hierarchy.
!  It basically maintains state information such as the database connection,
!  parent/child relationships, etc.
!  It contains/generates ResultSets, but not actual data.
!  An application DataSource will ask its DataObject for a ResultSet using
!  supplied conditions.
! \layout Standard
! 
! Note that the implementation of DataObject is vendor-specific as well as
!  DataSource-type dependent; e.g., there will be a PostgreSQL DataObject for
!  "Object" type datasources (base tables, etc) and a separate PostgreSQL
!  DataObject for "Raw SQL Queries" or for "XML-Queries" (once implemented).
!  The DataObject *interface*, however, remains constant across the various
!  implementations.
!  It is because of the number of implementations of DataObjects that a separate
!  DataSource had to be created.
! \layout Standard
! 
! A DataObject may hold several ResultSets (i.e., detail resultsets in a 
master/deta
! il relationship).
! \layout Standard
! 
! A DataObject contains link to ResultSet.
!  
! \layout Section
! 
! ResultSet
! \layout Standard
! 
! A ResultSet is a traversable set of RecordSets.
!  It has no GFD equivalent, although most of GFBlock's functionality may
!  consist of calls to DataSets.
!  It contains methods to load records, go to next/prev/first/last records,
!  deleting/insert records, etc.
! \layout Standard
! 
! A ResultSet holds RecordSets.
! \layout Section
! 
! RecordSet
! \layout Standard
! 
! A RecordSet is a set of the fields contained in a record.
!  A RecordSet knows the current state of itself and all its fields.
! \layout Standard
! 
! A master RecordSet contains a reference to its detail ResultSets.
! \layout Section
! 
! Connection Manager
  \layout Chapter
  
  Using the XML<->Object System