[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gnue] r9303 - trunk
From: |
reinhard |
Subject: |
[gnue] r9303 - trunk |
Date: |
Sat, 13 Jan 2007 09:16:15 -0600 (CST) |
Author: reinhard
Date: 2007-01-13 09:16:06 -0600 (Sat, 13 Jan 2007)
New Revision: 9303
Modified:
trunk/README.txt
Log:
Updated global readme file.
Modified: trunk/README.txt
===================================================================
--- trunk/README.txt 2007-01-13 15:08:41 UTC (rev 9302)
+++ trunk/README.txt 2007-01-13 15:16:06 UTC (rev 9303)
@@ -30,15 +30,15 @@
backend reporting server and various reporting clients.
gnue-appserver/
- GNUe App Server is a data and business rules server. It provides
+ GNUe AppServer is a data and business rules server. It provides
an object-oriented backend to forms and reports. In an n-tier
- environment, App Serverholds all business rules/logic and provides
+ environment, AppServer holds all business rules/logic and provides
object-to-relational access to various database backends.
gnue-designer/
GNUe Designer is an graphical IDE for GNU Enterprise. Currently,
it only handles Forms Definitions, but support for Reports and
- App Server class definitions are planned. Designer requires the the
+ AppServer class definitions are planned. Designer requires the the
corresponding toolset for any definitions you plan to design. (i.e.,
GNUe Forms must be installed in order for designer to support Forms)
@@ -50,12 +50,6 @@
corresponding tools must be installed (i.e., to run forms, GNUe
Forms must be installed.)
-gnue-integrator/
- GNUe Integrator is a data migration/synchronization tool that can
- be used to move or copy data from one datasource to another in a
- batch-like mode. It is useful for pulling data from one production
- database into another.
-
gnue-common/
GNUe Common is required for any Python-based tools (GNUe Forms,
Reports, and Designer.) It defines a common code base for other
@@ -69,39 +63,18 @@
each other, but will also form a coherent system when installed
together.
-gnue-phpforms/
- GNUe Forms (PHP version) is a reimplementation of GNUe Forms in
- PHP. It tries to provide a similar look and feel as GNUe Forms
- through an web interface. See phpforms/README for more information.
-gnue-pointofsale/
- GNUe Point-of-Sale is a module-based register application. It
- is designed to be plugged into an existing architecture. For
- example, it can be customized to use your existing database
- structure. It is in a very early stage of development, but is
- used in at least two smaller retail establishments.
-
-gnue-dbtools/
- GNUe DBTools is a set of database data manipulation utilities
- based off of GNUe-Common. It provides a common set of command-
- line utilities that can be used across several database vendors.
- It includes a data loader and an interactive SQL shell.
-
-
The following directories contain no code and are basically support structures:
-docbook/ Various docbook-based documentation for GNU Enterprise. There's
- plenty of goodies in this directory.
-
gnue-samples/
- Several sample programs that use the various GNUe tools. None of
these
- are actually meant for real-world use, but show off various features
- of each tool.
+ Several sample programs that use the various GNUe tools. None of
+ these are actually meant for real-world use, but show off various
+ features of each tool.
www/ This contains the skeleton of our website.
-The various tools (Forms, Reports, App Server) can work independently of each
+The various tools (Forms, Reports, AppServer) can work independently of each
other, or can work together to provide a complete enterprise application
framework.
@@ -111,15 +84,17 @@
BACKENDS
--------
-Forms and Reports (both based on GNUe-Common) will work with or without App
Server:
+Forms and Reports (both based on GNUe-Common) will work with or without
+AppServer:
- * With App Server
+ * With AppServer
- In this mode, an n-tier setup, App Server will contain all (most) business
logic
- and will provide objects to Forms and Reports. App Server will perform
object-
- to-relational mapping between the database backends and the other tools.
+ In this mode, an n-tier setup, AppServer will contain all (most) business
+ logic and will provide objects to Forms and Reports. App Server will
+ perform object-to-relational mapping between the database backends and the
+ other tools.
- * Without App Server
+ * Without AppServer
In this mode, commonly a 2-tier setup, GNUe Forms/Reports will communicate
directly to a supported relational database or via a supported middle-ware
@@ -131,11 +106,11 @@
INSTALLATION
------------
-There are two types of installations that can be performed from the Subversion
tree:
-developer installation and production installation. Note that each tool has
-its own set of dependencies. It is recommended that you read the INSTALL file
-for each tool you plan to use to make sure your system has all the necessary
-prerequisites.
+There are two types of installations that can be performed from the Subversion
+tree: developer installation and production installation. Note that each tool
+has its own set of dependencies. It is recommended that you read the INSTALL
+file for each tool you plan to use to make sure your system has all the
+necessary prerequisites.
* Developer installation:
@@ -143,10 +118,9 @@
[ This option is only available on POSIX (Linux/Unix)
systems as it extensively makes use of symbolic links. ]
-
To install the python-based tools, type "python setup-cvs.py" from the
gnue-common directory. This will set up GNUe Common, GNUe Forms, GNUe
- Reports, GNUe Designer, GNUe Navigator, and GNUe App Server.
+ Reports, GNUe Designer, GNUe Navigator, and GNUe AppServer.
* Production Installation:
@@ -154,12 +128,3 @@
To install the python-based tools, go into each tool directory and run
'python setup.py install'. If using Reports, Forms, or Designer, first
install the GNUe-Common libraries (in gnue-common/).
-
-
- * Generating Snapshots:
-
- To generate a snapshot, go into each tool directory and run
- `GNUE_VERSION_SUFFIX=-`date +"%Y%m%d"` ./setup.py sdist'. The resulting
- file is placed in the `dist' subdirectory.
-
-
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [gnue] r9303 - trunk,
reinhard <=