WILL NOT COMPILE - org\jcon\_ReadMe.txt - 2/14/99 - JH - How to use this software.

Developed with Swing 1.1.1 Beta3, JDK 1.1.7.
Put the javax.swing SwingAll.jar in your classpath.
There are bugs and little doc. The BA is still immature. Help it grow!

---------------------------------------------------
To run the client/server system, which uses the Data Framework, which uses the Bean Assembler:
- Set up the Access database with your 32bit ODBC. See gov\cdc\atsdr\ReadMe.txt for details.
- java gov.cdc.atsdr.server.DataServer  (this starts the local server)
- java gov.cdc.atsdr.client.DataClient  (this starts the client)
- Enter "J" and "J" for UserID and Password

Note the server and client can also be started from the BeanAssembler. To do this:
  - java org.jcon.ba.Assembler
  - Choose Tree, gov.cdc.atsdr.server.DataServer
  - Wait while the first tree opened loads
  - Right click on the root node, choose Start    (this starts the server)
  - Choose Tree, gov.cdc.atsdr.client.DataClient
  - Right click on the root node, choose Start    (this starts the client)    

---------------------------------------------------
The most useful BA tool besides the tree is the Parameter Editor. Choose Tools, Auto Edit Param. This opens the automatic Parameter Editor. Select any node on a tree. If the node has a parameter text file it will be automatically displayed, and can be edited. All containers and those beans with "X" haveparameters. To observed the ability to edit parameters in a running system, in the DataClient tree select the SystemMenu. In the ParamEditor change "Title is: System Menu - ATSDR" to "Title is: xxxxxSystem Menu - ATSDR". Then click on the Apply button. Notice the instantly modified menu window. Next change "WindowTop is: 0" to "WindowTop is: 50" and "Text is: System" to "Text is: xxxSystem". Click on Apply.Click on the Undo button to backout your changes one change at a time. Click on Redo to redo them. Click on Apply anytime to see the current effect. When done with experimenting, click on Revert and Apply. The System Menu is now restored to the state in the parex file.

---------------------------------------------------
If you want to close the client, don't choose System, Exit. Instead close the DataClient tree window. This forces a clean close on all components in that system. The DataServer can be closed in the same manner, but do this after closing the client.

---------------------------------------------------
In the BA choose Tree, org.jcon.test.app3.Client3. This is a small, understandable system Jack is evolving totest various components for a new client. It does not use a relational database. Instead it used server APIs, which are not included as of 8/21/98. We are simulating this instead. This system illustrates:
- How the Data Framework can use relational or other data.
- How various components are used in a small system.
- How fast parameter driven windows can be loaded.
- The minimum components needed for a visual system, which are SystemMenu and SystemCloser.

--------------------------------------------------
We have class models created with Rational Rose Solo. These can be opened with any Rose Modeler. The most important models are:
- org\jcon\df\doc\Data7.mdl, the 7th interation Data Framework.
     Note the Request and DatabaseFactory subsystem pages.
- org\jcon\df\doc\Edit1.mdl, the Data Editor subsystem.
- org\jcon\ba\doc\BA2.mdl, the 2nd interation of the BA system engine.

---------------------------------------------------
As of 2/24/99 we have 2 new example systems. Run them this way, in this order:
java -nojit org.jcon.test.screen.StartSystem
java -nojit org.jcon.test.screen.autotest.StartSystem

You can also run them from the visual BA Editor. Try using the Inspector to set the menuNavigation test isRepeated to true, and then do start(). The test will then run forever, or until you set isRepeated back to false.
