How to use the Cameleon OSP
Components - an Overview
Requirements
Before you start using Cameleon OSP, you should be familiar with
runtime
configuration, writing, compiling and running java applications in
general.
If you want to develop server applications, we recommend to acquire
basic
knowledge on Unix and MySQL before you start.
Get the source
Visit https://must.de/cameleon.html
The paradigm of the Cameleon Open Source Project
Edit your application in an abstract way and let the framework realize
the concrete technical solution.
Sample:
If the user is to be informed that an entry cannot be deleted, you
could
-
fill the status label with this information by the method setText()
-
open a dialog / modal window with the information and an Ok button
Instead we should use the method setMessageToKeep and let the
framework decide in which way this is going to be realized. Maybe
tomorrow
something else is hip.
Swing / Servlet / JSP Decision
At first: No matter how you start, your work is never useless, because
many things are similar in this framework. Anyway, once you will decide
which way to go. If you decided to create a server application: The
advantage
of the pure Servlet variant are few instructions, reliability and a
great
flexibility to change behaviour and layout retrospectively. The
advantage
of Java Server Pages is individuality and creativity.
Set up your own project
What you should basically know
Concerning database
The database connection is specified in de.must.dataobj.ConnectionSpecification,
this class provides the connection via method getConnection(). It's
recommended
to make the main connection globaly available in a subclass of de.must.middle.GlobalStd
for each application.
Tables are described in Objects extending de.must.dataobj.DataObject.
If your database is already created, you need not more than defining
the
table name. If not, it is recommended to define your table as a
subclass
of DataObject and
generate
creation scripts or the database itself out of these descriptions by
sbuclasses
of de.must.dataobj.TableCreatorStd
(see samples).
The primary key is administrated by DoIdent,
a de.must.dataobj.DataObject. You need this object and the associated
table
"Identity" to insert records.
Concerning Data Modification
The concept to navigate through big amounts of data is:
-
Specifiy the entry / entries to be modified by an enquiry with one or
more
criteria to reduce the search result significantly.
-
Browse the search result and switch to modify mode by doubleclick of a
single entry.
-
Modify the entry and click Ok
For Swing UI see de.must.wuic.SimpleDataListFrame
and de.must.wuic.DataPropertyAdministration.
For HTML UI see de.must.markup.Enquiry,
de.must.markup.DataList
and de.must.markup.DataPropertyAdministration.
Check out suitable sample applications.
Resources
Icon Repository
We found a small icon repository at http://developer.java.sun.com/developer/techDocs/hi/repository.
Sun allows to redistribute it.
Further Information
Internet Information
Look at http://www.must.de/cameleon.html
for newer documentation.
API Documentation
Check out the API Documentation.
To understand the framework and its usage we recommend:
-
Check sample applications functions by running the sample application
and
compare them to your needs.
-
Check the corresponding source code.
-
Use the API Documentation
for
detailed understanding of the framework and for using other framework
functions
as used in the sample application. In the API Documentation the sample
classes are included into document the "Direct Known Subclasses".
Anyway
it's more helpful to read the sample source code itself rather than
reading
the sample API.
FAQ
The first expected questions are answered in FAQ.html.
You're welcome to join the Cameleon OSP and ask additional questions in
the Cameleon
help forum to let the FAQ grow.
© Copyright 2001-2020 Christoph
Müller, Kärntner Str. 56, D-70469 Stuttgart, Germany, http://www.must.de