[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gnue designer/doc/installer/gfdesigner.cfg form...
|
From: |
James Thompson |
|
Subject: |
gnue designer/doc/installer/gfdesigner.cfg form... |
|
Date: |
Fri, 22 Feb 2002 22:00:18 -0500 |
CVSROOT: /cvsroot/gnue
Module name: gnue
Changes by: James Thompson <address@hidden> 02/02/22 22:00:18
Modified files:
designer/doc/installer: gfdesigner.cfg
forms/doc : techref.txt
Log message:
Change to designer mcmillian config
updated text techref
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/designer/doc/installer/gfdesigner.cfg.diff?tr1=1.5&tr2=1.6&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/forms/doc/techref.txt.diff?tr1=1.3&tr2=1.4&r1=text&r2=text
Patches:
Index: gnue/designer/doc/installer/gfdesigner.cfg
diff -c gnue/designer/doc/installer/gfdesigner.cfg:1.5
gnue/designer/doc/installer/gfdesigner.cfg:1.6
*** gnue/designer/doc/installer/gfdesigner.cfg:1.5 Wed Jan 30 13:54:45 2002
--- gnue/designer/doc/installer/gfdesigner.cfg Fri Feb 22 22:00:18 2002
***************
*** 18,25 ****
[APPZLIB]
type = PYZ
! name= gfdesigner.pyz
! dependencies= gfdesigner
excludes= dospath, macpath, wxPython.demo
includes =
packages = _xmlplus,encodings,gnue
--- 18,25 ----
[APPZLIB]
type = PYZ
! name= designer.pyz
! dependencies= designer.Designer
excludes= dospath, macpath, wxPython.demo
includes =
packages = _xmlplus,encodings,gnue
Index: gnue/forms/doc/techref.txt
diff -c gnue/forms/doc/techref.txt:1.3 gnue/forms/doc/techref.txt:1.4
*** gnue/forms/doc/techref.txt:1.3 Sat Jan 19 00:34:26 2002
--- gnue/forms/doc/techref.txt Fri Feb 22 22:00:18 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.
! 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.
! 1.1 Features
To facilitate the development of data entry screens GNUE
Forms supports the following features
***************
*** 41,47 ****
+----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! Design Overview
GNUE Forms approaches the user interface differently than
many applications. In GNUE Forms the user interface exists
--- 41,47 ----
+----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 1.2 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.
! 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,
--- 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,
***************
*** 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
--- 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
***************
*** 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
--- 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
***************
*** 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
--- 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
***************
*** 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
--- 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
***************
*** 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
--- 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
***************
*** 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
--- 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
***************
*** 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
--- 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
***************
*** 195,201 ****
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
--- 195,201 ----
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
***************
*** 210,216 ****
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
--- 210,216 ----
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
***************
*** 223,235 ****
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
--- 223,235 ----
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
***************
*** 239,245 ****
Note: The ability to return true false values is not yet
implemented in GNUE Forms.
! Implemented
Pre-FocusOut Fires prior to a component losing focus. If
the return value of the script is False then the focus
--- 239,245 ----
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
***************
*** 266,274 ****
On-newrecord Fires whenever a new record is created.
! Not Implemented
! Example of Logical Hierarchy
A visual representation of how these items fit together is
in order.
--- 266,274 ----
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.
***************
*** 330,336 ****
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
--- 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
***************
*** 343,349 ****
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
--- 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
***************
*** 374,380 ****
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.
--- 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.
***************
*** 393,401 ****
+----------+---------------------------------------------------------------------------------------------+
! Running the client
! Basics
Running the client is rather simple. In it's most basic form
--- 393,401 ----
+----------+---------------------------------------------------------------------------------------------+
! 4.3 Running the client
! 4.3.1 Basics
Running the client is rather simple. In it's most basic form
***************
*** 408,414 ****
gfclient --help
! Symlinks
gfclient also supports the use of symlinks to simplify execution
of forms. The easiest way to describe this is by example.
--- 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.
***************
*** 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
! Tags
! <form>
! Attributes
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 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
|
***************
*** 470,476 ****
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
! Example
<form title="My Form" width="40"
height="40">
--- 470,476 ----
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
! 5.1.1.2 Example
<form title="My Form" width="40"
height="40">
***************
*** 479,487 ****
</form>
! <page>
! Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 479,487 ----
</form>
! 5.1.2 <page>
! 5.1.2.1 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. |
! Example
<page name="page1">
--- 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">
***************
*** 504,512 ****
</page>
! <block>
! Attributes
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 504,512 ----
</page>
! 5.1.3 <block>
! 5.1.3.1 Attributes
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 516,522 ****
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| datasource | string | none | The name of a datasource
(defined in by a <datasource> tag.) that provides this block with it's data.
|
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! | readonly | boolean | none | If set then none of the entry
widgets inside this block can be modified via the user interface.
|
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| transparentBlock | boolean | none | If set then the you can tab out
of the block via next or previous field events. Makes navigation in mutliblock
forms easier.
|
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
--- 516,524 ----
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| datasource | string | none | The name of a datasource
(defined in by a <datasource> tag.) that provides this block with it's data.
|
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! | restrictDelete | boolean | none | If set then the user will be
unable to request that a record be deleted via the user interface.
|
!
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! | restrictInsert | boolean | none | If set then the user will be
unable to request that new records be inserted into the block
|
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| transparentBlock | boolean | none | If set then the you can tab out
of the block via next or previous field events. Makes navigation in mutliblock
forms easier.
|
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
***************
*** 526,532 ****
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! Example
<block name="cities" datasource="city" master="state.st_code"
detail="state">
--- 528,534 ----
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 5.1.3.2 Example
<block name="cities" datasource="city" master="state.st_code"
detail="state">
***************
*** 543,551 ****
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
|
--- 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
|
***************
*** 569,581 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
! Example
<label text="City" x="2" y="9"/>
! <entry>
! 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
|
***************
*** 629,635 ****
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! Example
A simple example
--- 631,637 ----
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 5.1.5.2 Example
A simple example
***************
*** 643,651 ****
foreign_key="validator.state" foreign_key_description="description"
style="dropdown">
! <button>
! Attributes
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 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
|
***************
*** 667,680 ****
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
! Example
<button label="Press Me" x="1" y="1" width="10" height="1"
trigger="HelloWorld"/>
! <box>
! 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
|
***************
*** 692,707 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! 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
|
--- 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
|
***************
*** 717,729 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! Example
<scrollbar x="40" y="2" width="1" height="15"/>
! <datasource>
! Attributes
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 719,731 ----
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! 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
|
***************
*** 743,756 ****
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! Example
<datasource name="customers" database="gnue" table="customer"
order_by="name_last,name_first" prequery="" />
! <trigger>
! Attributes
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 745,758 ----
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! 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
|
***************
*** 766,772 ****
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
! Example
Simple Embedded
--- 768,774 ----
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
! 5.1.10.2 Example
Simple Embedded
***************
*** 810,818 ****
</form>
! Form Libraries
! Overview
Forms supports libraries of common objects. There are two
approaches to importing data in forms: 1) importing form-wide
--- 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
***************
*** 833,841 ****
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:
--- 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:
***************
*** 854,860 ****
+--------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------+
! Example
Import all datasources and the pages identified as "page1"
and "page2":
--- 856,862 ----
+--------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------+
! 5.2.2.2 Example
Import all datasources and the pages identified as "page1"
and "page2":
***************
*** 862,870 ****
<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,
--- 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,
***************
*** 888,894 ****
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:
--- 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:
***************
*** 900,906 ****
<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" ?>
--- 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 ****
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
--- 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
***************
*** 990,996 ****
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
--- 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
***************
*** 1002,1009 ****
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
--- 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
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- gnue designer/doc/installer/gfdesigner.cfg form...,
James Thompson <=