[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gnue designer/doc/installer/README designer/doc...
|
From: |
Jason Cater |
|
Subject: |
gnue designer/doc/installer/README designer/doc... |
|
Date: |
Fri, 31 May 2002 21:27:45 -0400 |
CVSROOT: /home/cvs
Module name: gnue
Changes by: Jason Cater <address@hidden> 02/05/31 21:27:45
Modified files:
designer/doc/installer: README gfdesigner.iss
forms/doc : techref.txt
forms/doc/installer: gfclient.iss
Log message:
fixes for win32 binary creation
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/designer/doc/installer/README.diff?cvsroot=OldCVS&tr1=1.6&tr2=1.7&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/designer/doc/installer/gfdesigner.iss.diff?cvsroot=OldCVS&tr1=1.8&tr2=1.9&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/forms/doc/techref.txt.diff?cvsroot=OldCVS&tr1=1.4&tr2=1.5&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/forms/doc/installer/gfclient.iss.diff?cvsroot=OldCVS&tr1=1.10&tr2=1.11&r1=text&r2=text
Patches:
Index: gnue/designer/doc/installer/README
diff -c gnue/designer/doc/installer/README:1.6
gnue/designer/doc/installer/README:1.7
*** gnue/designer/doc/installer/README:1.6 Sat Jan 19 15:57:38 2002
--- gnue/designer/doc/installer/README Fri May 31 21:27:44 2002
***************
*** 13,19 ****
from the c:\installer\designer do a
! python ..\installer\builder h:\cvs\gnue\designer\doc\installer\gfdesigner.cfg
You'll get a c:\installer\designer\dist_gfdesigner dir that will contain the
self
contained designer
--- 13,19 ----
from the c:\installer\designer do a
! python ..\installer\builder.py
h:\cvs\gnue\designer\doc\installer\gfdesigner.cfg
You'll get a c:\installer\designer\dist_gfdesigner dir that will contain the
self
contained designer
Index: gnue/designer/doc/installer/gfdesigner.iss
diff -c gnue/designer/doc/installer/gfdesigner.iss:1.8
gnue/designer/doc/installer/gfdesigner.iss:1.9
*** gnue/designer/doc/installer/gfdesigner.iss:1.8 Fri May 31 19:01:34 2002
--- gnue/designer/doc/installer/gfdesigner.iss Fri May 31 21:27:44 2002
***************
*** 28,36 ****
Source: "C:\installer\designer\dist_gfdesigner\gfdesigner.exe"; DestDir:
"{app}"; CopyMode: alwaysoverwrite; Components: main
Source: "C:\installer\designer\dist_gfdesigner\*.*"; DestDir: "{app}";
CopyMode: alwaysoverwrite; Components: main
Source: "C:\python21\shared\images\*.ico"; DestDir: "{app}\..\shared\images";
Components: main
Source: "h:\cvs\gnue\designer\Copying"; DestDir: "{app}"; DestName:
"LICENSE.txt"; Components: main
! Source: "c:\python21\doc\DevelopersGuide-Forms.txt"; DestDir: "{app}\..\doc";
DestName: "Forms Developers Reference.txt"; Components: doc
! Source: "c:\python21\doc\DevelopersGuide-Forms.pdf"; DestDir: "{app}\..\doc";
DestName: "Forms Developers Reference.pdf"; Components: doc
[INI]
Filename: "{app}\gfdesigner.url"; Section: "InternetShortcut"; Key: "URL";
String: "http://www.gnuenterprise.org";
--- 28,39 ----
Source: "C:\installer\designer\dist_gfdesigner\gfdesigner.exe"; DestDir:
"{app}"; CopyMode: alwaysoverwrite; Components: main
Source: "C:\installer\designer\dist_gfdesigner\*.*"; DestDir: "{app}";
CopyMode: alwaysoverwrite; Components: main
Source: "C:\python21\shared\images\*.ico"; DestDir: "{app}\..\shared\images";
Components: main
+ Source: "C:\python21\shared\images\*.png"; DestDir: "{app}\..\shared\images";
Components: main
+ Source: "C:\python21\etc\gnue.conf"; DestDir: "{app}\..\etc"; CopyMode:
onlyifdoesntexist; Components: main
+ Source: "C:\python21\etc\connections.conf"; DestDir: "{app}\..\etc";
CopyMode: onlyifdoesntexist; Components: main
Source: "h:\cvs\gnue\designer\Copying"; DestDir: "{app}"; DestName:
"LICENSE.txt"; Components: main
! Source: "c:\python21\doc\designer\DevelopersGuide-Forms.txt"; DestDir:
"{app}\..\doc"; DestName: "Forms Developers Reference.txt"; Components: doc
! Source: "c:\python21\doc\designer\DevelopersGuide-Forms.pdf"; DestDir:
"{app}\..\doc"; DestName: "Forms Developers Reference.pdf"; Components: doc
[INI]
Filename: "{app}\gfdesigner.url"; Section: "InternetShortcut"; Key: "URL";
String: "http://www.gnuenterprise.org";
Index: gnue/forms/doc/installer/gfclient.iss
diff -c gnue/forms/doc/installer/gfclient.iss:1.10
gnue/forms/doc/installer/gfclient.iss:1.11
*** gnue/forms/doc/installer/gfclient.iss:1.10 Fri May 31 19:01:34 2002
--- gnue/forms/doc/installer/gfclient.iss Fri May 31 21:27:45 2002
***************
*** 37,44 ****
Source: "H:\cvs\gnue\forms\samples\*.*"; DestDir: "{app}\..\Samples\forms";
Components: samples
Source: "H:\cvs\gnue\forms\README"; DestDir: "{app}\doc"; DestName:
"README.txt"; Components: doc
Source: "H:\cvs\gnue\common\README.databases"; DestDir: "{app}\doc";
DestName: "README-databases.txt"; Components: doc
! Source: "c:\python21\doc\techref.txt"; DestDir: "{app}\..\doc"; DestName:
"Forms Technical Reference.txt"; Components: doc
! Source: "c:\python21\doc\techref.pdf"; DestDir: "{app}\..\doc"; DestName:
"Forms Technical Reference.pdf"; Components: doc
Source: "h:\cvs\gnue\forms\samples\*.gfd"; DestDir:
"{app}\..\Samples\forms\"; Flags: recursesubdirs; Components: samples
Source: "h:\cvs\gnue\forms\samples\*.sql"; DestDir:
"{app}\..\Samples\forms\"; Flags: recursesubdirs; Components: samples
Source: "h:\cvs\gnue\forms\samples\README.*"; DestDir:
"{app}\..\Samples\forms\"; Flags: recursesubdirs; Components: samples
--- 37,44 ----
Source: "H:\cvs\gnue\forms\samples\*.*"; DestDir: "{app}\..\Samples\forms";
Components: samples
Source: "H:\cvs\gnue\forms\README"; DestDir: "{app}\doc"; DestName:
"README.txt"; Components: doc
Source: "H:\cvs\gnue\common\README.databases"; DestDir: "{app}\doc";
DestName: "README-databases.txt"; Components: doc
! Source: "c:\python21\doc\forms\techref.txt"; DestDir: "{app}\..\doc";
DestName: "Forms Technical Reference.txt"; Components: doc
! Source: "c:\python21\doc\forms\techref.pdf"; DestDir: "{app}\..\doc";
DestName: "Forms Technical Reference.pdf"; Components: doc
Source: "h:\cvs\gnue\forms\samples\*.gfd"; DestDir:
"{app}\..\Samples\forms\"; Flags: recursesubdirs; Components: samples
Source: "h:\cvs\gnue\forms\samples\*.sql"; DestDir:
"{app}\..\Samples\forms\"; Flags: recursesubdirs; Components: samples
Source: "h:\cvs\gnue\forms\samples\README.*"; DestDir:
"{app}\..\Samples\forms\"; Flags: recursesubdirs; Components: samples
Index: gnue/forms/doc/techref.txt
diff -c gnue/forms/doc/techref.txt:1.4 gnue/forms/doc/techref.txt:1.5
*** gnue/forms/doc/techref.txt:1.4 Fri Feb 22 22:00:18 2002
--- gnue/forms/doc/techref.txt Fri May 31 21:27:44 2002
***************
*** 25,31 ****
During development this document will serve as both a guide
to the design of the GNUE Forms system and as a users guide.
! 1.1 Features
To facilitate the development of data entry screens GNUE
Forms supports the following features
--- 25,31 ----
During development this document will serve as both a guide
to the design of the GNUE Forms system and as a users guide.
! Features
To facilitate the development of data entry screens GNUE
Forms supports the following features
***************
*** 41,47 ****
+----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 1.2 Design Overview
GNUE Forms approaches the user interface differently than
many applications. In GNUE Forms the user interface exists
--- 41,47 ----
+----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! Design Overview
GNUE Forms approaches the user interface differently than
many applications. In GNUE Forms the user interface exists
***************
*** 55,68 ****
to hide most of this separation of logic and UI from the
application user and developer during typical usage.
! 1.2.1 Virtual Form
All the actual logic of the form is carried out in the virtual
form and reflected by the UI driver. The UI driver passes
requests back to the virtual form when the user requests
that something be changed.
! 1.2.2 UI System
The widget hierarchy is the visible portion of an GNUE Forms
application. Basically it's comprised of the various buttons,
--- 55,68 ----
to hide most of this separation of logic and UI from the
application user and developer during typical usage.
! Virtual Form
All the actual logic of the form is carried out in the virtual
form and reflected by the UI driver. The UI driver passes
requests back to the virtual form when the user requests
that something be changed.
! UI System
The widget hierarchy is the visible portion of an GNUE Forms
application. Basically it's comprised of the various buttons,
***************
*** 73,79 ****
and instead must pass requests back to the virtual form
for processing.
! 1.2.3 Logical Focus
One major difference in GNUE Forms applications vs typical
widget based applications is in regard to focus. Focus in
--- 73,79 ----
and instead must pass requests back to the virtual form
for processing.
! Logical Focus
One major difference in GNUE Forms applications vs typical
widget based applications is in regard to focus. Focus in
***************
*** 110,120 ****
Virtual Form
! 2.1 Form
The topmost object in a form hierarchy.
! 2.2 Page
The page object, when seen by a UI driver, suggests a visual
separation of the UI is needed. However it is up the the
--- 110,120 ----
Virtual Form
! Form
The topmost object in a form hierarchy.
! Page
The page object, when seen by a UI driver, suggests a visual
separation of the UI is needed. However it is up the the
***************
*** 123,129 ****
into actual pages. However nothing prevents the driver from
using a notebook widget for separation or ignoring it altogether.
! 2.3 Block
Blocks provide a way to logically group form objects in memory
and provide navigation logic to the form. It is always linked
--- 123,129 ----
into actual pages. However nothing prevents the driver from
using a notebook widget for separation or ignoring it altogether.
! Block
Blocks provide a way to logically group form objects in memory
and provide navigation logic to the form. It is always linked
***************
*** 134,144 ****
within such blocks requires saving it is up to the application
developer to implement persistence via the Trigger system.
! 2.4 Label
Labels are the readonly visual elements in a form.
! 2.5 Entry
Entry objects are the point at which information enters the
system. They are mapped on a one-to-one basis with the fields
--- 134,144 ----
within such blocks requires saving it is up to the application
developer to implement persistence via the Trigger system.
! Label
Labels are the readonly visual elements in a form.
! Entry
Entry objects are the point at which information enters the
system. They are mapped on a one-to-one basis with the fields
***************
*** 150,167 ****
information that is computed at run time. However this information
will not be saved upon application exit.
! 2.6 Button
The button object allows you to place interactive spots on
your form that when activated will fire a named trigger.
! 2.7 Box
The box object, when seen by a UI driver, suggests a border
of some type is needed on the UI. However it is up the the
UI driver to determine what, if any, type of border is provided.
! 2.8 Database
Database objects provide the authenticated link to a specific
data storage system. Various providers have been written
--- 150,167 ----
information that is computed at run time. However this information
will not be saved upon application exit.
! Button
The button object allows you to place interactive spots on
your form that when activated will fire a named trigger.
! Box
The box object, when seen by a UI driver, suggests a border
of some type is needed on the UI. However it is up the the
UI driver to determine what, if any, type of border is provided.
! Database
Database objects provide the authenticated link to a specific
data storage system. Various providers have been written
***************
*** 172,178 ****
the provider presents its information in a record/field
format.
! 2.9 Datasource
A datasource contains records and fields of information currently
loaded into an active form. Typically it is linked to a
--- 172,178 ----
the provider presents its information in a record/field
format.
! Datasource
A datasource contains records and fields of information currently
loaded into an active form. Typically it is linked to a
***************
*** 182,188 ****
types of datasources cannot provide persistance to the information
stored within themself.
! 2.9.1 Master/Detail Relationships
Datasources can also be associated with other datasoure in
what we call a Master/Detail relationship. A master datasource
--- 182,188 ----
types of datasources cannot provide persistance to the information
stored within themself.
! Master/Detail Relationships
Datasources can also be associated with other datasoure in
what we call a Master/Detail relationship. A master datasource
***************
*** 195,235 ****
displayed. It's worth noting that a datasource can be both
a detail and master datasource simultaneously.
! 2.9.2 Record Caching/Prefetch
In an effort to improve system performance datasources will
eventually be able to be configured to cache records in
memory. The application developer will have control over
the number of records cached to allow them to balance memory
usage vs system responsiveness. Currently the cache system
! in GNUe is in reallity a pre-fetch system. When large numbers
of records are requested from the database the system will
! fetch only the user specified cache amout at a time. When
! the user moves beyond the number of records in memory the
! system will automatically fetch another group of records.
! This allows the system to respond rapidly to user requests
! involving large number of records.
! 2.10 Triggers
Triggers contain scripts of code that execute during specific
events which "fire" the triggers. They can be attached to
any of the components of the virtual form though some trigger
! events may not pertain to the compontent and thus will never
! fire.
Not implemented yet: Triggers normally return a True value
upon sucessful completion. It is possible for the trigger
script to return True or False values to influence the applications
behaviour.
! 2.10.1 Trigger Languages
Currently, trigger scripts must be written in python. We
would like to increase the number of supported languages
as time permits.
! 2.10.2 Trigger Events
The following triggers are either implemented or planned
for implementation in the GNUe Forms system. Unless specifically
--- 195,236 ----
displayed. It's worth noting that a datasource can be both
a detail and master datasource simultaneously.
! Record Caching/Prefetch
In an effort to improve system performance datasources will
eventually be able to be configured to cache records in
memory. The application developer will have control over
the number of records cached to allow them to balance memory
usage vs system responsiveness. Currently the cache system
! in GNUe is, in reality, a pre-fetch system. When large numbers
of records are requested from the database the system will
! fetch only the user-specified "cache
! amount" at a time. When the user moves beyond the
! number of records in memory, the system will automatically
! fetch another group of records. This allows the system to
! respond rapidly to user requests involving large number
! of records.
! Triggers
Triggers contain scripts of code that execute during specific
events which "fire" the triggers. They can be attached to
any of the components of the virtual form though some trigger
! events may not pertain to the component and, as such, will
! never fire.
Not implemented yet: Triggers normally return a True value
upon sucessful completion. It is possible for the trigger
script to return True or False values to influence the applications
behaviour.
! Trigger Languages
Currently, trigger scripts must be written in python. We
would like to increase the number of supported languages
as time permits.
! Trigger Events
The following triggers are either implemented or planned
for implementation in the GNUe Forms system. Unless specifically
***************
*** 239,274 ****
Note: The ability to return true false values is not yet
implemented in GNUE Forms.
! 2.10.2.1 Implemented
! Pre-FocusOut Fires prior to a component losing focus. If
! the return value of the script is False then the focus
will not be switched.
! Post-FocusOut Fires after focus leaves a component but
prior to new component taking focus.
! Pre-FocusIn Fires prior to a component recieving focus.
! Post-FocusIn Fires after a component recieves focus.
! Pre-Change Fires prior to a change to an component.
! If the return value of the script is False then the change
! will be aborted.
! Post-Change Fires after a change to an component.
! Pre-Commit Fires prior to commiting data into persistant
storage. If the return value of the script is False then
! the commit will be aborted.
! Post-Commit Fires after data has been commited.
! On-newrecord Fires whenever a new record is created.
! 2.10.2.2 Not Implemented
! 2.11 Example of Logical Hierarchy
A visual representation of how these items fit together is
in order.
--- 240,334 ----
Note: The ability to return true false values is not yet
implemented in GNUE Forms.
! Implemented
! Entry
!
! Pre-FocusOut - Fires prior to a component losing focus.
! If the return value of the script is False then the focus
will not be switched.
! Post-FocusOut - Fires after focus leaves a component but
prior to new component taking focus.
! Pre-FocusIn - Fires prior to a component recieving focus.
! Post-FocusIn - Fires after a component recieves focus.
! Block
! Pre-FocusOut - Fires prior to a component losing focus.
! If the return value of the script is False then the focus
! will not be switched.
!
! Post-FocusOut - Fires after focus leaves a component but
! prior to new component taking focus.
!
! Pre-FocusIn - Fires prior to a component recieving focus.
!
! Post-FocusIn - Fires after a component recieves focus.
!
! Pre-Commit - Fires once, for each record in the block marked
! as either "new", "updated",
! or "deleted", prior to commiting the
! record into persistant storage. In the future, if the
! return value of the script is False then the commit will
! be aborted.
!
! Pre-Insert - Fires once, for each record in the block marked
! as "new", and commiting the record into
! persistant storage. In the future, if the return value
! of the script is False then the commit will be aborted.
! This event is called prior to the pre-commit event.
!
! Pre-Update - Fires once, for each record in the block marked
! as "updated", prior to updating and
! commiting the record into persistant storage. In the future,
! if the return value of the script is False then the commit
! will be aborted. This event is called prior to the pre-commit
! event.
!
! Pre-Delete - Fires once, for each record in the block marked
! as "deleted", prior to deleting and
! commiting the record into persistant storage. In the future,
! if the return value of the script is False then the commit
! will be aborted. This event is called prior to the pre-commit
! event.
!
! Post-Commit - Fires after data has been commited.
!
! Page
!
! Pre-FocusOut - Fires prior to a component losing focus.
! If the return value of the script is False then the focus
! will not be switched.
!
! Post-FocusOut - Fires after focus leaves a component but
! prior to new component taking focus.
!
! Pre-FocusIn - Fires prior to a component recieving focus.
! Post-FocusIn - Fires after a component recieves focus.
!
! Form
!
! Pre-Commit- Fires prior to commiting data into persistant
storage. If the return value of the script is False then
! the commit will be aborted.
! Post-Commit - Fires after data has been commited.
! Not Implemented
! Pre-Change - Fires prior to a change to an component.
! If the return value of the script is False then the change
! will be aborted.
! Post-Change Fires after a change to an component.
!
! On-newrecord Fires whenever a new record is created.
!
! Example of Logical Hierarchy
A visual representation of how these items fit together is
in order.
***************
*** 330,336 ****
mean that the form designer has no control over how their
form looks.
! 3.1 Widget Coordinates
The coordinate/layout system for widget in GNUE Forms needs
to be able to deal with text based displays as well as GUI
--- 390,396 ----
mean that the form designer has no control over how their
form looks.
! Widget Coordinates
The coordinate/layout system for widget in GNUE Forms needs
to be able to deal with text based displays as well as GUI
***************
*** 343,349 ****
GNUE Forms: Client
! 4.1 Basic Concepts
GNUE Forms clients read form definitions from XML based .gfd
files. The client reads in a form definition file which
--- 403,409 ----
GNUE Forms: Client
! Basic Concepts
GNUE Forms clients read form definitions from XML based .gfd
files. The client reads in a form definition file which
***************
*** 374,380 ****
The remainder of this chapter covers the reference implementation
of the GNUe Forms client which has been written in python.
! 4.2 UI Drivers
UI drivers are responsible for interacting with the user
and passing user input back as requests to the virtual form.
--- 434,440 ----
The remainder of this chapter covers the reference implementation
of the GNUe Forms client which has been written in python.
! UI Drivers
UI drivers are responsible for interacting with the user
and passing user input back as requests to the virtual form.
***************
*** 393,401 ****
+----------+---------------------------------------------------------------------------------------------+
! 4.3 Running the client
! 4.3.1 Basics
Running the client is rather simple. In it's most basic form
--- 453,461 ----
+----------+---------------------------------------------------------------------------------------------+
! Running the client
! Basics
Running the client is rather simple. In it's most basic form
***************
*** 408,414 ****
gfclient --help
! 4.3.2 Symlinks
gfclient also supports the use of symlinks to simplify execution
of forms. The easiest way to describe this is by example.
--- 468,474 ----
gfclient --help
! Symlinks
gfclient also supports the use of symlinks to simplify execution
of forms. The easiest way to describe this is by example.
***************
*** 428,450 ****
Forms are described via a .gfd file. A GFD file always contains
the following structure
! * XML version
! * Document root element - GNUE-Form
! * Form options.
! * Form Logic
! * Widget hierarchy
! * End of document - GNUE-Form
! 5.1 Tags
! 5.1.1 <form>
! 5.1.1.1 Attributes
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 488,510 ----
Forms are described via a .gfd file. A GFD file always contains
the following structure
! XML version
! Document root element - GNUE-Form
! Form options.
! Form Logic
! Widget hierarchy
! End of document - GNUE-Form
! Tags
! <form>
! Attributes
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 470,476 ****
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
! 5.1.1.2 Example
<form title="My Form" width="40"
height="40">
--- 530,536 ----
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
! Example
<form title="My Form" width="40"
height="40">
***************
*** 479,487 ****
</form>
! 5.1.2 <page>
! 5.1.2.1 Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 539,547 ----
</form>
! <page>
! Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 490,496 ****
| name | string | none | A unique ID for the widget. This is
only useful when importing pages from a library. |
! 5.1.2.2 Example
<page name="page1">
--- 550,556 ----
| name | string | none | A unique ID for the widget. This is
only useful when importing pages from a library. |
! Example
<page name="page1">
***************
*** 504,512 ****
</page>
! 5.1.3 <block>
! 5.1.3.1 Attributes
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 564,572 ----
</page>
! <block>
! Attributes
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 528,534 ****
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 5.1.3.2 Example
<block name="cities" datasource="city" master="state.st_code"
detail="state">
--- 588,594 ----
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! Example
<block name="cities" datasource="city" master="state.st_code"
detail="state">
***************
*** 545,553 ****
the entry within itself named state to match the value stored
in st_code as querying data from the datasource.
! 5.1.4 <label>
! 5.1.4.1 Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 605,613 ----
the entry within itself named state to match the value stored
in st_code as querying data from the datasource.
! <label>
! Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 571,583 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
! 5.1.4.2 Example
<label text="City" x="2" y="9"/>
! 5.1.5 <entry>
! 5.1.5.1 Attributes
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default |
Description
|
--- 631,643 ----
+------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
! Example
<label text="City" x="2" y="9"/>
! <entry>
! Attributes
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default |
Description
|
***************
*** 595,600 ****
--- 655,662 ----
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| field | string | Matches name attribute. | The name
of the field in the datasource to which this widget is tied.
|
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | max_length | int | none | The
maximum number of characters the user is allowed to enter into the entry.
|
+
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| case | string | mixed | The entry
widget converts all input based upon this setting. Possible values are lower,
upper, or mixed
|
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| typecase | string | text | The type
of data the entry widget will accept. Possible values are text, number, date
|
***************
*** 631,637 ****
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 5.1.5.2 Example
A simple example
--- 693,699 ----
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! Example
A simple example
***************
*** 645,653 ****
foreign_key="validator.state" foreign_key_description="description"
style="dropdown">
! 5.1.6 <button>
! 5.1.6.1 Attributes
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 707,715 ----
foreign_key="validator.state" foreign_key_description="description"
style="dropdown">
! <button>
! Attributes
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 669,682 ****
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
! 5.1.6.2 Example
<button label="Press Me" x="1" y="1" width="10" height="1"
trigger="HelloWorld"/>
! 5.1.7 <box>
! 5.1.7.1 Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 731,744 ----
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
! Example
<button label="Press Me" x="1" y="1" width="10" height="1"
trigger="HelloWorld"/>
! <box>
! Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 694,709 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! 5.1.7.2 Example
<box x="1" y="8" width="37" height="8" label="State Cities"/>
! 5.1.8 <scrollbar>
Only partially implemented at this time. Will show on form
but do nothing.
! 5.1.8.1 Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 756,771 ----
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! Example
<box x="1" y="8" width="37" height="8" label="State Cities"/>
! <scrollbar>
Only partially implemented at this time. Will show on form
but do nothing.
! Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 719,758 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! 5.1.8.2 Example
<scrollbar x="40" y="2" width="1" height="15"/>
! 5.1.9 <datasource>
! 5.1.9.1 Attributes
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! | Attribute | Datatype | Default | Description
|
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! | name | string | none | A unique ID for the widget.The name of
the widget.
|
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! | database | string | none | The name of the database object the
datasource will utilize.
|
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! | table | string | none | The name of the table the datasource to
which the datasourse must attach.
|
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! | order_by | string | none | A comma seperated list of fields within
the table. The datasource will present the information sorted by this list of
fields. |
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! | prequery | string | none | Causes the datasource to load all data
from the table into memory. Usefull for validation purposes and obtaining
values to dropdown style entry objects. |
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! | sql | string | none | No longer active. A way of overriding
the internal sql generation functions of the datasource with hard coded sql.
|
!
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! 5.1.9.2 Example
<datasource name="customers" database="gnue" table="customer"
order_by="name_last,name_first" prequery="" />
! 5.1.10 <trigger>
! 5.1.10.1 Attributes
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 781,820 ----
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! Example
<scrollbar x="40" y="2" width="1" height="15"/>
! <datasource>
! Attributes
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
! | Attribute | Datatype | Default | Description
|
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
! | name | string | none | A unique ID for the widget.The name of
the widget.
|
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
! | database | string | none | The name of the database object the
datasource will utilize.
|
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
! | table | string | none | The name of the table the datasource to
which the datasourse must attach.
|
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
! | order_by | string | none | A comma seperated list of fields within
the table. The datasource will present the information sorted by this list of
fields. |
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
! | prequery | string | none | Causes the datasource to load all data
from the table into memory. Useful for validation purposes and obtaining values
to dropdown style entry objects. |
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
! | sql | string | none | No longer active. A way of overriding
the internal sql generation functions of the datasource with hard coded sql.
|
!
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
! Example
<datasource name="customers" database="gnue" table="customer"
order_by="name_last,name_first" prequery="" />
! <trigger>
! Attributes
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 768,774 ****
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
! 5.1.10.2 Example
Simple Embedded
--- 830,836 ----
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
! Example
Simple Embedded
***************
*** 812,820 ****
</form>
! 5.2 Form Libraries
! 5.2.1 Overview
Forms supports libraries of common objects. There are two
approaches to importing data in forms: 1) importing form-wide
--- 874,882 ----
</form>
! Form Libraries
! Overview
Forms supports libraries of common objects. There are two
approaches to importing data in forms: 1) importing form-wide
***************
*** 835,843 ****
For example, when importing a page, all blocks, labels,
etc. belowing to that page are imported as well.
! 5.2.2 Importing Form-Level Objects
! 5.2.2.1 Summary
The first method of importing uses the <import> tag. The
import tag takes four attributes:
--- 897,905 ----
For example, when importing a page, all blocks, labels,
etc. belowing to that page are imported as well.
! Importing Form-Level Objects
! Summary
The first method of importing uses the <import> tag. The
import tag takes four attributes:
***************
*** 856,862 ****
+--------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------+
! 5.2.2.2 Example
Import all datasources and the pages identified as "page1"
and "page2":
--- 918,924 ----
+--------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------+
! Example
Import all datasources and the pages identified as "page1"
and "page2":
***************
*** 864,872 ****
<import library="mylibrary.gfl"
datasources="*" pages="page1,page2"/>
! 5.2.3 Importing Individual Objects
! 5.2.3.1 Summary
The second method of importing involves importing named objects.
The currently importable objects are: datasource, page,
--- 926,934 ----
<import library="mylibrary.gfl"
datasources="*" pages="page1,page2"/>
! Importing Individual Objects
! Summary
The second method of importing involves importing named objects.
The currently importable objects are: datasource, page,
***************
*** 890,896 ****
as a common detail block can be defined in a library, but
the master datasource may be different in each form.
! 5.2.3.2 Example
Import a datasource:
--- 952,958 ----
as a common detail block can be defined in a library, but
the master datasource may be different in each form.
! Example
Import a datasource:
***************
*** 902,908 ****
<import-entry location="mylibrary.gfl"
name="zipentry" field="zipfield2"/>
! 5.3 Complete Example
This is the country maintenance form from the location samples
<?xml version="1.0" ?>
--- 964,970 ----
<import-entry location="mylibrary.gfl"
name="zipentry" field="zipfield2"/>
! Complete Example
This is the country maintenance form from the location samples
<?xml version="1.0" ?>
***************
*** 966,972 ****
We deal with this in following ways
! 6.1 Best Judgment
Client developers are given a lot of flexibility in implementing
GNUE Forms clients. A client developer can decide that implementing
--- 1028,1034 ----
We deal with this in following ways
! Best Judgment
Client developers are given a lot of flexibility in implementing
GNUE Forms clients. A client developer can decide that implementing
***************
*** 992,998 ****
on his personal information screen, a text based client
could simply choose to ignore the picture.
! 6.2 Form Requirements
Sometimes the omission of the data in the form might render
a form useless. The loss of the ability to display the employee's
--- 1054,1060 ----
on his personal information screen, a text based client
could simply choose to ignore the picture.
! Form Requirements
Sometimes the omission of the data in the form might render
a form useless. The loss of the ability to display the employee's
***************
*** 1004,1011 ****
critical to the forms ability to operate. When a client
is unable to provide a feature it must
! * Notify the user of the missing feature
! * Notify the application (if applicable) of the missing feature
! * Shut down
--- 1066,1073 ----
critical to the forms ability to operate. When a client
is unable to provide a feature it must
! Notify the user of the missing feature
! Notify the application (if applicable) of the missing feature
! Shut down
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- gnue designer/doc/installer/README designer/doc...,
Jason Cater <=