| |
|
| |
|
| |
Preliminaries |
 |
|
|
|
Working with zeroCode
|
|
Designers
pay an annual subscription fee for access to the zeroCode
Design Environment. Build-time costs, however,
are drastically reduced from traditional methods of
creating business web applications because
of the reduced coding labor. There is no charge for
the deployment of the finished web applications, subject
to zeroCode standard terms and conditions. Each Designer
is given his own Apache server instance for each application
under development, assuring security.
|
|
Downloading
applications is a one-step process. Once downloaded,
you may run them on your own servers, or re-distribute
to other servers at no charge. When you want
to make changes to the application, you come back to
the zeroCode site, where the original work is preserved
for your use as long as you have paid subscription
to zeroCode (after which we will still have it available
in off-line back-up). You also have the option
of buying the source-code for site, including your custom
objects (but not including zeroCode-proprietary objects
that are delivered in JAR form), although most of our
customers elect to return to the zDE for modifications.
|
| |
|
Getting into zeroCode
|
To begin
with, register online at the zeroCode website, using
your company's ID. If your company does not have such
an ID, send us an email to techsupport@zerocode.com
and request one. We will generate a password for you
and mail it to you. Once you receive your own user
name and password, enter the site and you will be brought
to the zeroCode Design Environment (the zDE). Click
here to read details of navigation within the zDE.
Once
you're registered and comfortable with the zDE, you
will be ready to build your own site. Typically, there
are a couple of things you need to do before you build
an application, as described below. Once that's done,
you're all set to build your application - in five clicks!
|
| |
|
Preparing to build an application |
|
The preliminary steps for using zeroCode are: |
|
|
A
business analyst outlines the business functions needed
and the facets of the Web application that accomplish
these functions. You can do this on your own or involve
us at this stage. |
|
|
At
the end of systems analysis, a database schema (i.e.,
SQL script for creating the tables and their relationships
) is created. In the schema, the data elements and the
relationships among them are defined clearly and unambiguously.
|
| |
|
| |
For
more details on Site creation click
here. |
| |
|
|
|
|
|
|
