[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gnue common/setup.py designer/setup.py forms/se...
|
From: |
James Thompson |
|
Subject: |
gnue common/setup.py designer/setup.py forms/se... |
|
Date: |
Sat, 19 Jan 2002 00:34:26 -0500 |
CVSROOT: /cvsroot/gnue
Module name: gnue
Changes by: James Thompson <address@hidden> 02/01/19 00:34:26
Modified files:
common : setup.py
designer : setup.py
forms : setup.py
forms/doc : techref.lyx techref.txt user_guide.lyx
Log message:
Doc updates
setup.py sdist now creates docs
setup.py now pulls VERSION info from src dir
(Have we mentioned we need a good setup system)
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/common/setup.py.diff?tr1=1.32&tr2=1.33&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/designer/setup.py.diff?tr1=1.20&tr2=1.21&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/forms/setup.py.diff?tr1=1.56&tr2=1.57&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/forms/doc/techref.lyx.diff?tr1=1.11&tr2=1.12&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/forms/doc/techref.txt.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/forms/doc/user_guide.lyx.diff?tr1=1.5&tr2=1.6&r1=text&r2=text
Patches:
Index: gnue/common/setup.py
diff -c gnue/common/setup.py:1.32 gnue/common/setup.py:1.33
*** gnue/common/setup.py:1.32 Fri Jan 18 20:19:50 2002
--- gnue/common/setup.py Sat Jan 19 00:34:25 2002
***************
*** 24,29 ****
--- 24,31 ----
import string
import os
+ from src import VERSION
+
# First of all, make sure this is a current enough Python release.
try:
if sys.hexversion < 0x02000000:
***************
*** 156,162 ****
distutils.core.setup (name = "GNUe-Common",
! version = "0.1.1",
description = "Base files of a GNU Enterprise Tools install",
long_description = "",
author = "GNUe Project",
--- 158,164 ----
distutils.core.setup (name = "GNUe-Common",
! version = VERSION,
description = "Base files of a GNU Enterprise Tools install",
long_description = "",
author = "GNUe Project",
***************
*** 174,179 ****
--- 176,183 ----
"gnue.common.dbdrivers",
"gnue.common.dbdrivers._dbsig",
"gnue.common.dbdrivers._empty",
+ "gnue.common.dbdrivers._oracle",
+ "gnue.common.dbdrivers._pgsql",
"gnue.common.dbdrivers._static",
"gnue.common.dbdrivers.geas",
"gnue.common.dbdrivers.mysql",
***************
*** 184,190 ****
"gnue.common.dbdrivers.psycopg",
"gnue.common.dbdrivers.popy",
"gnue.common.dbdrivers.pypgsql",
- "gnue.common.dbdrivers.psycopg",
"gnue.common.dbdrivers.cxoracle",
"gnue.common.dbdrivers.informix",
"gnue.common.dbdrivers.ingres",
--- 188,193 ----
***************
*** 199,221 ****
"gnue.common.installer" : "installer"},
)
-
- if not 'sdist' in sys.argv:
- if sys.platform != 'win32':
- os.remove ("setup.cfg")
-
- # This is a nasty hack to get gnue_sys (and only gnue_sys.py)
- # to install to site_packages
- file = open ("setup.cfg","w")
- file.write ("[build]\n"
- "build_base=build.1\n"
- "[install_lib]\n"
- "build_dir=build.1\n")
- file.close()
-
-
distutils.core.setup (name = "GNUe-Common",
! version = "0.1.1",
description = "Base files of a GNU Enterprise Tools install",
long_description = "",
author = "GNUe Project",
--- 202,209 ----
"gnue.common.installer" : "installer"},
)
distutils.core.setup (name = "GNUe-Common",
! version = VERSION,
description = "Base files of a GNU Enterprise Tools install",
long_description = "",
author = "GNUe Project",
Index: gnue/designer/setup.py
diff -c gnue/designer/setup.py:1.20 gnue/designer/setup.py:1.21
*** gnue/designer/setup.py:1.20 Tue Jan 15 12:04:56 2002
--- gnue/designer/setup.py Sat Jan 19 00:34:26 2002
***************
*** 24,29 ****
--- 24,31 ----
import string
import os
import os.path
+
+ from src import VERSION
#
# hack to deal w/ fact distutils won't
# allow us to set absolute path prefix
***************
*** 94,106 ****
if 'sdist' in sys.argv:
print """
! *** Notes for creating source disto ***
!
! Make sure and create update the html and text docs
! prior to creating the source distribution.
"""
! raw_input ("Press Control-D to abort or any other key to continue")
!
if 'build' in sys.argv:
# Verify that PyXML is installed
try:
--- 96,111 ----
if 'sdist' in sys.argv:
print """
! We are going to create the docs needed for the
! source distro. You'll need lyx installed.
"""
! raw_input ("Press Control-D to abort or any other key to continue")
! os.system ("""
! cd doc
! lyx --export text DevelopersGuide-Forms.lyx
! lyx --export pdf DevelopersGuide-Forms.lyx
! """)
!
if 'build' in sys.argv:
# Verify that PyXML is installed
try:
***************
*** 207,213 ****
#
# Maybe later :)
setup (name = "GNUe-Designer",
! version = "0.1.0",
description = "GNU Enterprise Designer",
long_description = "",
author = "GNUe Forms Team",
--- 212,218 ----
#
# Maybe later :)
setup (name = "GNUe-Designer",
! version = "0.1.1",
description = "GNU Enterprise Designer",
long_description = "",
author = "GNUe Forms Team",
Index: gnue/forms/doc/techref.lyx
diff -c gnue/forms/doc/techref.lyx:1.11 gnue/forms/doc/techref.lyx:1.12
*** gnue/forms/doc/techref.lyx:1.11 Thu Dec 20 22:20:28 2001
--- gnue/forms/doc/techref.lyx Sat Jan 19 00:34:26 2002
***************
*** 27,42 ****
GNU Entrprise - GNUe Forms
\newline
Technical Reference
! \layout Abstract
! This is version 0.1.4 of the Technical Reference it covers GNUe Forms 0.1.0
! \layout Abstract
The current copy is maintained as a LyX 1.1.6 file.
If anyone knows of ways to get LyX to play nicer with regard to code samples
please let us know.
! \layout Abstract
This document is covered by the GNU Free Documentation License Version 1.1
\layout Author
--- 27,42 ----
GNU Entrprise - GNUe Forms
\newline
Technical Reference
! \layout Standard
! This is version 0.1.5 of the Technical Reference it covers GNUe Forms 0.1.0
! \layout Standard
The current copy is maintained as a LyX 1.1.6 file.
If anyone knows of ways to get LyX to play nicer with regard to code samples
please let us know.
! \layout Standard
This document is covered by the GNU Free Documentation License Version 1.1
\layout Author
***************
*** 48,57 ****
GNUE Forms aims to be the primary user interface to the GNU Enterprise system.
It is comprised of two systems.
! GNUe Forms: Client is responsible for displaying output and accepting user
! input.
! GNUe Forms: Designer allows a developer to produce the XML based form
definitio
! n files utilized by GNUe Forms: Client.
\layout Standard
During development this document will serve as both a guide to the design
--- 48,56 ----
GNUE Forms aims to be the primary user interface to the GNU Enterprise system.
It is comprised of two systems.
! GNUe Forms is responsible for displaying output and accepting user input.
! GNUe Designer allows a developer to produce the XML based form definition
! files utilized by GNUe Forms: Client.
\layout Standard
During development this document will serve as both a guide to the design
***************
*** 221,261 ****
Thus if focus currently resides in Block1.Field1 of an application and the
user presses the Next Field key the focus of the application changes as
follows assuming all triggers return successfully.
! \layout Code
Block1.Field1 Pre-Focus-Out Trigger fires if defined
! \layout Code
Block1.Field1 loses focus
! \layout Code
Block1.Field1 Post-Focus-Out Trigger fires if defined
! \layout Code
Block1 Pre-Focus-In Trigger fires if defined
! \layout Code
Block1 receives focus
! \layout Code
Block1 Post-Focus-In Trigger fires if defined
! \layout Code
Block1 Pre-Focus-Out Trigger fires if defined
! \layout Code
Block1 Post-Focus-Out Trigger fires if defined
! \layout Code
Block1.Field2 Pre-Focus-In Trigger fires if defined
! \layout Code
Block1.Field2 receives focus.
! \layout Code
Block1.Field2 Post-Focus-In Trigger fires if defined
- \layout Code
-
\layout Chapter
Virtual Form
--- 220,258 ----
Thus if focus currently resides in Block1.Field1 of an application and the
user presses the Next Field key the focus of the application changes as
follows assuming all triggers return successfully.
! \layout Standard
Block1.Field1 Pre-Focus-Out Trigger fires if defined
! \layout Standard
Block1.Field1 loses focus
! \layout Standard
Block1.Field1 Post-Focus-Out Trigger fires if defined
! \layout Standard
Block1 Pre-Focus-In Trigger fires if defined
! \layout Standard
Block1 receives focus
! \layout Standard
Block1 Post-Focus-In Trigger fires if defined
! \layout Standard
Block1 Pre-Focus-Out Trigger fires if defined
! \layout Standard
Block1 Post-Focus-Out Trigger fires if defined
! \layout Standard
Block1.Field2 Pre-Focus-In Trigger fires if defined
! \layout Standard
Block1.Field2 receives focus.
! \layout Standard
Block1.Field2 Post-Focus-In Trigger fires if defined
\layout Chapter
Virtual Form
***************
*** 290,310 ****
file have a non-persistent datasource created for them automatically.
If information within such blocks requires saving it is up to the application
developer to implement persistence via the Trigger system.
- \layout Subsection
-
- Master/Detail Relationships
- \layout Standard
-
- Blocks can also be associated with other blocks in what we call a
Master/Detail
- relationship.
- A master block has one or more detail blocks associated with itself.
- These detail blocks contain a foreign key which points back to a specific
- master block/field key.
- When navigation to a different record in the master block takes place all
- detail blocks auto navigate to the matching records within themselves to
- maintain integrity of the data being displayed.
- It's worth noting that a block can be both a detail and master block
simultaneo
- usly.
\layout Section
Label
--- 287,292 ----
***************
*** 369,381 ****
stored within themself.
\layout Subsection
! Record Caching
\layout Standard
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.
\layout Section
--- 351,386 ----
stored within themself.
\layout Subsection
! Master/Detail Relationships
! \layout Standard
!
! Datasources can also be associated with other datasoure in what we call
! a Master/Detail relationship.
! A master datasource has one or more detail datasources associated with
! itself.
! These detail datasources contain a foreign key which points back to a
specific
! master datasource/field key.
! When navigation to a different record in the master datasource takes place
! all detail datasources auto navigate to the matching records within
themselves
! to maintain integrity of the data being displayed.
! It's worth noting that a datasource can be both a detail and master
datasource
! simultaneously.
! \layout Subsection
!
! Record Caching/Prefetch
\layout Standard
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.
\layout Section
***************
*** 470,545 ****
\layout Standard
Here is a simple data entry form:
! \layout Code
Form
! \layout Code
!
! Database1
! \layout Code
!
! DataSource 1
! \layout Code
! Linked to Database1's foo table
! \layout Code
! DataSource 2
! \layout Code
! Linked to Database1's bar table
! \layout Code
! \layout Code
! Trigger1
! \layout Code
! Performs
! \layout Code
! Block1.Entry4 = Block2.Entry2 + Block2.Entry3
! \layout Code
! \layout Code
! Block1
! \layout Code
! Link to DataSource1
! \layout Code
! Entry1 -> DataSource1.Field1
! \layout Code
! Entry2 -> DataSource1.Field2
! \layout Code
! Entry3 -> DataSource1.Field3
! \layout Code
! Entry4 Dummy field
! \layout Code
! Block2
! \layout Code
! Link to DataSource2
! \layout Code
! Entry1 -> DataSource2.Field3
! \layout Code
! Entry2 -> DataSource2.Field4
! \layout Code
! Post-Change Trigger link to Trigger1
! \layout Code
! Entry3 -> DataSource2.Field7
! \layout Code
! Post-Change Trigger link to Trigger1
\layout Chapter
UI System
--- 475,546 ----
\layout Standard
Here is a simple data entry form:
! \layout Standard
Form
! \layout Standard
! Database1
! \layout Standard
! DataSource 1
! \layout Standard
! Linked to Database1's foo table
! \layout Standard
! DataSource 2
! \layout Standard
! Linked to Database1's bar table
! \layout Standard
! Trigger1
! \layout Standard
! Performs
! \layout Standard
! Block1.Entry4 = Block2.Entry2 + Block2.Entry3
! \layout Standard
! Block1
! \layout Standard
! Link to DataSource1
! \layout Standard
! Entry1 -> DataSource1.Field1
! \layout Standard
! Entry2 -> DataSource1.Field2
! \layout Standard
! Entry3 -> DataSource1.Field3
! \layout Standard
! Entry4 Dummy field
! \layout Standard
! Block2
! \layout Standard
! Link to DataSource2
! \layout Standard
! Entry1 -> DataSource2.Field3
! \layout Standard
! Entry2 -> DataSource2.Field4
! \layout Standard
! Post-Change Trigger link to Trigger1
! \layout Standard
! Entry3 -> DataSource2.Field7
! \layout Standard
! Post-Change Trigger link to Trigger1
\layout Chapter
UI System
***************
*** 770,851 ****
The form /usr/local/gnue/forms/contacts.gfd will now be displayed
\layout Chapter
- GNUE Designer
- \layout Standard
-
-
- \series bold
- Development of GNUe Forms: Designer has not yet started.
-
- \series default
-
- \series bold
- However there is a script located in the gnuef/designer directory of the
- source distribution that will make creating forms a little easier until
- the real Designer is developed.
- \layout Standard
-
- The GNUe Forms: Designer allows a person to easily create data entry screens
- to be used with the GNUE Forms client.
- With it the devleoper can simply paint the form and have the .gfd file
generated
- for them.
- \layout Standard
-
- Some things that should be supported in the designer are:
- \layout Itemize
-
- Optionally store form definitions in the database system.
- Forms can be downloaded as needed instead of installed locally on each
- client platform.
- \layout Itemize
-
- Produce form diffs from an original form.
- Allowing programmers to store local alterations separate from the basic
- form.
- \layout Section
-
- Designing with GNUe Objects
- \layout Standard
-
- When working with the GNUe Forms: Designer to develop screens, the developer
- is actually working with GEAS objects.
- GEAS objects are self-aware and make this information available to programs
- for browsing.
- \layout Standard
-
- The GNUe Forms: Designer program queries all defined objects and generates
- a list containing object information.\SpecialChar ~
- The information about objects available
- to the GNUe Forms: Designer includes
- \layout Itemize
-
- Object Fields
- \layout Itemize
-
- Object Field Attributes
- \layout Itemize
-
- Object Functions
- \layout Itemize
-
- Object Triggers
- \layout Itemize
-
- Object Associations
- \layout Itemize
-
- Global Functions
- \layout Itemize
-
- Global Triggers
- \layout Standard
-
- The GNUe Form: Designer compiles this information and presents it to the
- developer via a graphical user interface.
- This allows the screen developers to build forms via simple drag and drop
- operations.
- \layout Chapter
-
GFD Structure
\layout Standard
--- 771,776 ----
***************
*** 5015,5021 ****
\end_inset
:
! \layout Code
<import library=
\begin_inset Quotes erd
--- 4940,4946 ----
\end_inset
:
! \layout Standard
<import library=
\begin_inset Quotes erd
***************
*** 5081,5087 ****
\layout Standard
Import a datasource:
! \layout Code
<import-datasource location=
\begin_inset Quotes erd
--- 5006,5012 ----
\layout Standard
Import a datasource:
! \layout Standard
<import-datasource location=
\begin_inset Quotes erd
***************
*** 5103,5109 ****
\layout Standard
Import an entry, overriding the bounded field:
! \layout Code
<import-entry location=
\begin_inset Quotes erd
--- 5028,5034 ----
\layout Standard
Import an entry, overriding the bounded field:
! \layout Standard
<import-entry location=
\begin_inset Quotes erd
Index: gnue/forms/doc/techref.txt
diff -c gnue/forms/doc/techref.txt:1.2 gnue/forms/doc/techref.txt:1.3
*** gnue/forms/doc/techref.txt:1.2 Tue Nov 20 21:12:53 2001
--- gnue/forms/doc/techref.txt Sat Jan 19 00:34:26 2002
***************
*** 3,21 ****
GNU Entrprise - GNUe Forms
Technical Reference
! Abstract
!
! This is version 0.1.4 of the Technical Reference it covers
GNUe Forms 0.1.0
- Abstract
-
The current copy is maintained as a LyX 1.1.6 file. If anyone
knows of ways to get LyX to play nicer with regard to code
samples please let us know.
- Abstract
-
This document is covered by the GNU Free Documentation License
Version 1.1
--- 3,15 ----
GNU Entrprise - GNUe Forms
Technical Reference
! This is version 0.1.5 of the Technical Reference it covers
GNUe Forms 0.1.0
The current copy is maintained as a LyX 1.1.6 file. If anyone
knows of ways to get LyX to play nicer with regard to code
samples please let us know.
This document is covered by the GNU Free Documentation License
Version 1.1
***************
*** 23,37 ****
GNUE Forms aims to be the primary user interface to the GNU
Enterprise system. It is comprised of two systems. GNUe
! Forms: Client is responsible for displaying output and accepting
! user input. GNUe Forms: Designer allows a developer to produce
the XML based form definition files utilized by GNUe Forms:
Client.
During development this document will serve as both a guide
to the design of the GNUE Forms system and as a users guide.
! 1 Features
To facilitate the development of data entry screens GNUE
Forms supports the following features
--- 17,31 ----
GNUE Forms aims to be the primary user interface to the GNU
Enterprise system. It is comprised of two systems. GNUe
! Forms is responsible for displaying output and accepting
! user input. GNUe Designer allows a developer to produce
the XML based form definition files utilized by GNUe Forms:
Client.
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
***************
*** 47,53 ****
+----------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 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
***************
*** 61,74 ****
to hide most of this separation of logic and UI from the
application user and developer during typical usage.
! 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.
! 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,
***************
*** 79,85 ****
and instead must pass requests back to the virtual form
for processing.
! 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
***************
*** 116,126 ****
Virtual Form
! 1 Form
The topmost object in a form hierarchy.
! 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
***************
*** 129,135 ****
into actual pages. However nothing prevents the driver from
using a notebook widget for separation or ignoring it altogether.
! 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
***************
*** 140,162 ****
within such blocks requires saving it is up to the application
developer to implement persistence via the Trigger system.
! 3.1 Master/Detail Relationships
!
! Blocks can also be associated with other blocks in what we
! call a Master/Detail relationship. A master block has one
! or more detail blocks associated with itself. These detail
! blocks contain a foreign key which points back to a specific
! master block/field key. When navigation to a different record
! in the master block takes place all detail blocks auto navigate
! to the matching records within themselves to maintain integrity
! of the data being displayed. It's worth noting that a block
! can be both a detail and master block simultaneously.
!
! 4 Label
Labels are the readonly visual elements in a form.
! 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
***************
*** 168,185 ****
information that is computed at run time. However this information
will not be saved upon application exit.
! 6 Button
The button object allows you to place interactive spots on
your form that when activated will fire a named trigger.
! 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.
! 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
***************
*** 190,196 ****
the provider presents its information in a record/field
format.
! 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
***************
*** 200,214 ****
types of datasources cannot provide persistance to the information
stored within themself.
! 9.1 Record Caching
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.
! 10 Triggers
Triggers contain scripts of code that execute during specific
events which "fire" the triggers. They can be attached to
--- 182,216 ----
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
! has one or more detail datasources associated with itself.
! These detail datasources contain a foreign key which points
! back to a specific master datasource/field key. When navigation
! to a different record in the master datasource takes place
! all detail datasources auto navigate to the matching records
! within themselves to maintain integrity of the data being
! 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 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.
! Triggers
Triggers contain scripts of code that execute during specific
events which "fire" the triggers. They can be attached to
***************
*** 221,233 ****
script to return True or False values to influence the applications
behaviour.
! 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.
! 10.2 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.
! 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
***************
*** 237,243 ****
Note: The ability to return true false values is not yet
implemented in GNUE Forms.
! 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
--- 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
***************
*** 264,272 ****
On-newrecord Fires whenever a new record is created.
! 10.2.2 Not Implemented
! 11 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.
! Not Implemented
! Example of Logical Hierarchy
A visual representation of how these items fit together is
in order.
***************
*** 275,321 ****
Form
! Database1
! DataSource 1
! Linked to Database1's foo table
! DataSource 2
! Linked to Database1's bar table
! Trigger1
! Performs
! Block1.Entry4 = Block2.Entry2 + Block2.Entry3
! Block1
! Link to DataSource1
! Entry1 -> DataSource1.Field1
! Entry2 -> DataSource1.Field2
! Entry3 -> DataSource1.Field3
! Entry4 Dummy field
! Block2
! Link to DataSource2
! Entry1 -> DataSource2.Field3
! Entry2 -> DataSource2.Field4
! Post-Change Trigger link to Trigger1
! Entry3 -> DataSource2.Field7
! Post-Change Trigger link to Trigger1
UI System
--- 277,323 ----
Form
! Database1
! DataSource 1
! Linked to Database1's foo table
! DataSource 2
! Linked to Database1's bar table
! Trigger1
! Performs
! Block1.Entry4 = Block2.Entry2 + Block2.Entry3
! Block1
! Link to DataSource1
! Entry1 -> DataSource1.Field1
! Entry2 -> DataSource1.Field2
! Entry3 -> DataSource1.Field3
! Entry4 Dummy field
! Block2
! Link to DataSource2
! Entry1 -> DataSource2.Field3
! Entry2 -> DataSource2.Field4
! Post-Change Trigger link to Trigger1
! Entry3 -> DataSource2.Field7
! Post-Change Trigger link to Trigger1
UI System
***************
*** 328,334 ****
mean that the form designer has no control over how their
form looks.
! 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
--- 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
***************
*** 341,347 ****
GNUE Forms: Client
! 1 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
! Basic Concepts
GNUE Forms clients read form definitions from XML based .gfd
files. The client reads in a form definition file which
***************
*** 372,378 ****
The remainder of this chapter covers the reference implementation
of the GNUe Forms client which has been written in python.
! 2 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.
! UI Drivers
UI drivers are responsible for interacting with the user
and passing user input back as requests to the virtual form.
***************
*** 391,399 ****
+----------+---------------------------------------------------------------------------------------------+
! 3 Running the client
! 3.1 Basics
Running the client is rather simple. In it's most basic form
--- 393,401 ----
+----------+---------------------------------------------------------------------------------------------+
! Running the client
! Basics
Running the client is rather simple. In it's most basic form
***************
*** 406,412 ****
gfclient --help
! 3.2 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
! Symlinks
gfclient also supports the use of symlinks to simplify execution
of forms. The easiest way to describe this is by example.
***************
*** 421,500 ****
bash-2.03$ contacts
The form /usr/local/gnue/forms/contacts.gfd will now be displayed
- GNUE Designer
-
- Development of GNUe Forms: Designer has not yet started.
- However there is a script located in the gnuef/designer
- directory of the source distribution that will make creating
- forms a little easier until the real Designer is developed.
-
- The GNUe Forms: Designer allows a person to easily create
- data entry screens to be used with the GNUE Forms client.
- With it the devleoper can simply paint the form and have
- the .gfd file generated for them.
-
- Some things that should be supported in the designer are:
-
- * Optionally store form definitions in the database system.
- Forms can be downloaded as needed instead of installed
- locally on each client platform.
-
- * Produce form diffs from an original form. Allowing programmers
- to store local alterations separate from the basic form.
-
- 1 Designing with GNUe Objects
-
- When working with the GNUe Forms: Designer to develop screens,
- the developer is actually working with GEAS objects. GEAS
- objects are self-aware and make this information available
- to programs for browsing.
-
- The GNUe Forms: Designer program queries all defined objects
- and generates a list containing object information.
- The information about objects available to the GNUe Forms:
- Designer includes
-
- * Object Fields
-
- * Object Field Attributes
-
- * Object Functions
-
- * Object Triggers
-
- * Object Associations
-
- * Global Functions
-
- * Global Triggers
-
- The GNUe Form: Designer compiles this information and presents
- it to the developer via a graphical user interface. This
- allows the screen developers to build forms via simple drag
- and drop operations.
-
GFD Structure
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
! 1 Tags
! 1.1 <form>
! 1.1.1 Attributes
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 423,450 ----
bash-2.03$ contacts
The form /usr/local/gnue/forms/contacts.gfd will now be displayed
GFD Structure
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
|
***************
*** 520,526 ****
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
! 1.1.2 Example
<form title="My Form" width="40"
height="40">
--- 470,476 ----
+--------------------+-----------+----------+-------------------------------------------------------------------------------------------------------------+
! Example
<form title="My Form" width="40"
height="40">
***************
*** 529,537 ****
</form>
! 1.2 <page>
! 1.2.1 Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 479,487 ----
</form>
! <page>
! Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 540,546 ****
| name | string | none | A unique ID for the widget. This is
only useful when importing pages from a library. |
! 1.2.2 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. |
! Example
<page name="page1">
***************
*** 554,562 ****
</page>
! 1.3 <block>
! 1.3.1 Attributes
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 504,512 ----
</page>
! <block>
! Attributes
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 576,582 ****
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 1.3.2 Example
<block name="cities" datasource="city" master="state.st_code"
detail="state">
--- 526,532 ----
+-------------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! Example
<block name="cities" datasource="city" master="state.st_code"
detail="state">
***************
*** 593,601 ****
the entry within itself named state to match the value stored
in st_code as querying data from the datasource.
! 1.4 <label>
! 1.4.1 Attributes
+------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 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
|
***************
*** 619,631 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
! 1.4.2 Example
<label text="City" x="2" y="9"/>
! 1.5 <entry>
! 1.5.1 Attributes
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default |
Description
|
--- 569,581 ----
+------------+-----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
! Example
<label text="City" x="2" y="9"/>
! <entry>
! Attributes
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default |
Description
|
***************
*** 661,667 ****
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| foreign_key_descritpion | string | none | The
description used if a style of dropdown is selected. This fields value is
displayed in the dropdown but the foreign_key value is actually stored in the
field. This allows you to display something like the full name of a US state
but only store it's 2 character abrievation. |
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! | style | string | text | The style
of entry widget requested. Currently either text, checkbox, or dropdown. To use
dropdown you are required to use both the foreign_key and
foreign_key_descriptions attributes.
|
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| default | string | none | The
default value for any new records created. If the field is visible the user can
override the value.
|
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
--- 611,617 ----
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| foreign_key_descritpion | string | none | The
description used if a style of dropdown is selected. This fields value is
displayed in the dropdown but the foreign_key value is actually stored in the
field. This allows you to display something like the full name of a US state
but only store it's 2 character abrievation. |
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! | style | string | text | The style
of entry widget requested. Currently either text, label, checkbox, or dropdown.
To use dropdown you are required to use both the foreign_key and
foreign_key_descriptions attributes. The "label" style implies the readonly
attribute. |
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| default | string | none | The
default value for any new records created. If the field is visible the user can
override the value.
|
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
***************
*** 679,685 ****
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! 1.5.2 Example
A simple example
--- 629,635 ----
+--------------------------+-----------+--------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
! Example
A simple example
***************
*** 693,701 ****
foreign_key="validator.state" foreign_key_description="description"
style="dropdown">
! 1.6 <button>
! 1.6.1 Attributes
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 643,651 ----
foreign_key="validator.state" foreign_key_description="description"
style="dropdown">
! <button>
! Attributes
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 717,730 ****
+------------+-----------+----------+-------------------------------------------------------------------------------------------------+
! 1.6.2 Example
<button label="Press Me" x="1" y="1" width="10" height="1"
trigger="HelloWorld"/>
! 1.7 <box>
! 1.7.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
|
***************
*** 742,757 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! 1.7.2 Example
<box x="1" y="8" width="37" height="8" label="State Cities"/>
! 1.8 <scrollbar>
Only partially implemented at this time. Will show on form
but do nothing.
! 1.8.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
|
***************
*** 767,779 ****
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! 1.8.2 Example
<scrollbar x="40" y="2" width="1" height="15"/>
! 1.9 <datasource>
! 1.9.1 Attributes
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
--- 717,729 ----
+------------+-----------+----------+--------------------------------------------------------------------------------------------------+
! Example
<scrollbar x="40" y="2" width="1" height="15"/>
! <datasource>
! Attributes
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
| Attribute | Datatype | Default | Description
|
***************
*** 793,806 ****
+------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
! 1.9.2 Example
<datasource name="customers" database="gnue" table="customer"
order_by="name_last,name_first" prequery="" />
! 1.10 <trigger>
! 1.10.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
|
***************
*** 816,822 ****
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
! 1.10.2 Example
Simple Embedded
--- 766,772 ----
+------------+-----------+----------+---------------------------------------------------------------------------------------------------------------+
! Example
Simple Embedded
***************
*** 860,868 ****
</form>
! 2 Form Libraries
! 2.1 Overview
Forms supports libraries of common objects. There are two
approaches to importing data in forms: 1) importing form-wide
--- 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
***************
*** 883,891 ****
For example, when importing a page, all blocks, labels,
etc. belowing to that page are imported as well.
! 2.2 Importing Form-Level Objects
! 2.2.1 Summary
The first method of importing uses the <import> tag. The
import tag takes four attributes:
--- 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:
***************
*** 904,910 ****
+--------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------+
! 2.2.2 Example
Import all datasources and the pages identified as "page1"
and "page2":
--- 854,860 ----
+--------------+-----------+----------+----------------------------------------------------------------------------------------------------------------------------------------------+
! Example
Import all datasources and the pages identified as "page1"
and "page2":
***************
*** 912,920 ****
<import library="mylibrary.gfl"
datasources="*" pages="page1,page2"/>
! 2.3 Importing Individual Objects
! 2.3.1 Summary
The second method of importing involves importing named objects.
The currently importable objects are: datasource, page,
--- 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,
***************
*** 938,944 ****
as a common detail block can be defined in a library, but
the master datasource may be different in each form.
! 2.3.2 Example
Import a datasource:
--- 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:
***************
*** 950,956 ****
<import-entry location="mylibrary.gfl"
name="zipentry" field="zipfield2"/>
! 3 Complete Example
This is the country maintenance form from the location samples
<?xml version="1.0" ?>
--- 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" ?>
***************
*** 1014,1020 ****
We deal with this in following ways
! 1 Best Judgment
Client developers are given a lot of flexibility in implementing
GNUE Forms clients. A client developer can decide that implementing
--- 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
***************
*** 1040,1046 ****
on his personal information screen, a text based client
could simply choose to ignore the picture.
! 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
--- 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
***************
*** 1052,1059 ****
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
--- 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
Index: gnue/forms/doc/user_guide.lyx
diff -c gnue/forms/doc/user_guide.lyx:1.5 gnue/forms/doc/user_guide.lyx:1.6
*** gnue/forms/doc/user_guide.lyx:1.5 Thu Nov 15 01:42:25 2001
--- gnue/forms/doc/user_guide.lyx Sat Jan 19 00:34:26 2002
***************
*** 1,6 ****
#LyX 1.1 created this file. For more info see http://www.lyx.org/
\lyxformat 218
! \textclass book
\language american
\inputencoding auto
\fontscheme default
--- 1,6 ----
#LyX 1.1 created this file. For more info see http://www.lyx.org/
\lyxformat 218
! \textclass docbook-book
\language american
\inputencoding auto
\fontscheme default
***************
*** 12,25 ****
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
! \secnumdepth 2
! \tocdepth 2
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
! \papersides 2
\paperpagestyle default
\layout Title
--- 12,25 ----
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
! \secnumdepth 3
! \tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
! \papersides 1
\paperpagestyle default
\layout Title
***************
*** 29,35 ****
User Guide
\layout Standard
! This is version 0.0.1 of the User Guide; it covers GNUe Forms 0.1.0
\layout Standard
This document is covered by the GNU Free Documentation License Version 1.1
--- 29,35 ----
User Guide
\layout Standard
! This is version 0.0.2 of the User Guide; it covers GNUe Forms 0.1.0
\layout Standard
This document is covered by the GNU Free Documentation License Version 1.1
***************
*** 159,167 ****
\layout Subsubsection
Overview
- \layout Standard
-
- Sdsfdf
\layout Subsubsection
File Syntax
--- 159,164 ----
***************
*** 464,476 ****
\layout Itemize
A gfd file stored on a web server and accessed via a command similar to:
! \layout LyX-Code
gfclient http://www.example.org/sales/customer.gfd
\layout Itemize
A gfd file stored on the local hard drive:
! \layout LyX-Code
gfclient C:
\backslash
--- 461,473 ----
\layout Itemize
A gfd file stored on a web server and accessed via a command similar to:
! \layout Standard
gfclient http://www.example.org/sales/customer.gfd
\layout Itemize
A gfd file stored on the local hard drive:
! \layout Standard
gfclient C:
\backslash
***************
*** 508,517 ****
and have it run the contacts.gfd form.
Or, put more simply, the following:
! \layout LyX-Code
bash-2.03$ ln -s /usr/local/bin/gfclient /usr/local/bin/contacts
! \layout LyX-Code
bash-2.03$ contacts
\layout Standard
--- 505,514 ----
and have it run the contacts.gfd form.
Or, put more simply, the following:
! \layout Standard
bash-2.03$ ln -s /usr/local/bin/gfclient /usr/local/bin/contacts
! \layout Standard
bash-2.03$ contacts
\layout Standard
***************
*** 4089,4095 ****
GNUe Form's gfclient accepts a variety of command line options.
These options can always be viewed by typing:
! \layout LyX-Code
gfclient --help
\layout Standard
--- 4086,4092 ----
GNUe Form's gfclient accepts a variety of command line options.
These options can always be viewed by typing:
! \layout Standard
gfclient --help
\layout Standard
***************
*** 4290,4296 ****
\end_inset
without the opening splash screen:
! \layout LyX-Code
gfclient --no_spash samples.gfd
\layout Standard
--- 4287,4293 ----
\end_inset
without the opening splash screen:
! \layout Standard
gfclient --no_spash samples.gfd
\layout Standard
***************
*** 4305,4311 ****
\end_inset
located on the company's web server in debugging level 10:
! \layout LyX-Code
gfclient -d 10 http://my.company.com/forms/samples.gf
\the_end
--- 4302,4308 ----
\end_inset
located on the company's web server in debugging level 10:
! \layout Standard
gfclient -d 10 http://my.company.com/forms/samples.gf
\the_end
Index: gnue/forms/setup.py
diff -c gnue/forms/setup.py:1.56 gnue/forms/setup.py:1.57
*** gnue/forms/setup.py:1.56 Fri Jan 18 20:19:50 2002
--- gnue/forms/setup.py Sat Jan 19 00:34:26 2002
***************
*** 26,31 ****
--- 26,33 ----
import os.path
import copy
+ from src import VERSION
+
#
# Leftover from initial attempt to create a .exe setup file for windows
#
***************
*** 122,134 ****
if 'sdist' in sys.argv:
print """
! *** Notes for creating source disto ***
!
! Make sure and create update the html and text docs
! prior to creating the source distribution.
"""
raw_input ("Press Control-D to abort or any other key to continue")
!
if ('build' in sys.argv) or ('install' in sys.argv):
# Verify that gnue-common is installed
# try:
--- 124,140 ----
if 'sdist' in sys.argv:
print """
! We are going to create the docs needed for the
! source distro. You'll need lyx installed.
"""
raw_input ("Press Control-D to abort or any other key to continue")
! os.system ("""
! cd doc
! lyx --export text techref.lyx
! lyx --export pdf techref.lyx
! lyx --export text user_guide.lyx
! lyx --export pdf user_guide.lyx
! """)
if ('build' in sys.argv) or ('install' in sys.argv):
# Verify that gnue-common is installed
# try:
***************
*** 271,277 ****
print "OK"
setup (name = "GNUe-Forms",
! version = "0.1.1",
description = "GNU Enterprise Forms",
long_description = "",
author = "GNUe Forms Team",
--- 277,283 ----
print "OK"
setup (name = "GNUe-Forms",
! version = VERSION,
description = "GNU Enterprise Forms",
long_description = "",
author = "GNUe Forms Team",
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- gnue common/setup.py designer/setup.py forms/se...,
James Thompson <=