|
|
| (107 intermediate revisions by 8 users not shown) |
| Line 1: |
Line 1: |
| | Back to [[Main Page]] | | Back to [[Main Page]] |
| | | | |
| − | * [http://vernon.is-a-geek.org/JGuiGen/JGuiGen.html Screencast] ... just a placeholder for now
| |
| | | | |
| − | * [[notes made during creation of demo script]]
| + | ==== Our Objectives: ==== |
| | | | |
| − | # Assumed to have installed: sdk, eclipse 3.1.2 | + | # [http://lightcloud.verns.net/JGuiGen/JGuiGenDemo.html JGuiGen Demo Screencast] 13 minutes |
| − | # svn checkout https://svn.sourceforge.net/svnroot/jguigen/JGuiGen/trunk/ jguigen
| + | ## This screencast shows some of the features your users will get if you generate a GUI using JGuiGen |
| − | ## JGuiGenCode | + | ## created on 20060510 using revision 235 |
| − | ## JGuiGenJars | + | ## [[JGuiGenDemo Script]] |
| − | ## JGuiGenMisc - hsql text files, containing JGuiGenDB: Data_Dict, JGuiGen_i18n, UserLogData, CodesBank | + | # [http://lightcloud.verns.net/JGuiGen/JGuiGen.html JGuiGen Screencast] 14 minutes |
| − | # tar xf JGuiGen.tar; cd JGuiGen; unzip JGuiGenMisc.zip | + | ## This is a demonstration showing how to quickly generate a powerful GUI using JGuiGen |
| − | # classpath=".:"`echo *.jar | tr " " ":"`
| + | ## created on 20060512 using revision 235 |
| − | # javac -classpath $classpath com/*/standard/*.java com/*/standard/XML/*.java com/*/src/*.java JGuiGen.java
| + | ## [[JGuiGen Lead Script]] |
| − | # vi JGuiGenIni.xml, add table name "Lead", add class name "Lead", add table model name "LeadTm"
| + | |
| − | # launch db admin. sh ./runUtil.sh DatabaseManager ... type: "... Standalone", driver: JGuiGenDb ... Ok
| + | |
| − | # cut and paste new table "Lead"
| + | |
| − | # cut and paste new columns: id, date, address
| + | |
| − | # run JGuiGen from the command line java -cp $classpath JGuiGen
| + | |
| − | # Basic flow ... start in the Data Dictionary | + | |
| − | ## Check Data Dictionary, Leave Flags, Run Now | + | |
| − | ## Edit Data Dict ... Do a bunch of stuff for each column
| + | |
| − | ## Generate Application
| + | |
| − | ## Exit from the Internationalization causes a write
| + | |
| − | ## Generate HTML (optional)
| + | |
| − | # Compile and run the new gui
| + | |
| − | ## show out-of-the-box features of the gui
| + | |
| − | ## View, Add, Edit, Delete ... right click duplicate
| + | |
| − | ## Search for some rows
| + | |
| − | ## Oh ... what's this? ... Reports!
| + | |
| − | ## try closing a window after a change
| + | |
| − | ## try changing the row to edit after a change
| + | |
| − | # wash, rinse, repeat ?, ?, ?, and ? showing features | + | |
| − | ## Quickly adding a column, such as: ssn, phone, address | + | |
| − | ## Internationalization | + | |
| − | ## Hot keys
| + | |
| − | ## Change validation error message and Test
| + | |
| − | ## blast the coffee cup
| + | |
| − | ## run test scripts against the gui
| + | |
| − | ## show test script output
| + | |
| − | # launch eclipse
| + | |
| | | | |
| | + | * Assumptions: subversion, java sdk, maybe eclipse 3.1.2 |
| | * shameless plug - [http://hale.homeip.net/ Hale Pringle's web site] | | * shameless plug - [http://hale.homeip.net/ Hale Pringle's web site] |
| − |
| |
| − |
| |
| − | ***************
| |
| − | Notea about getting JGuiGen installed on SourceForge.
| |
| − | I ran into two "issues" while moving a new project to SourceForge as a Subversion version control project.
| |
| − | 1. SourceForce wants a Subversion dump file to start with which menat I needed to place JGuiGen into
| |
| − | subversion locally. I created a repository using the Tortisesvn client. I imported the files into the
| |
| − | repository and checked them out again. Then it was time to create the dump. TortiseSvn doesn't create
| |
| − | dump files so I needed to use the command line. No problem. The instructions said use the svnadmin tool to
| |
| − | create the dump file. The issue came with figuring out what folder to be in when I ran svnadmin. I finally
| |
| − | found out that being in the main repository folder worked. That seems like a strange place to work from
| |
| − | but it worked.
| |
| − |
| |
| − | 2. The instructions on uploading a new project said to use scp and copy the file to
| |
| − | scp FILENAME.ZIP
| |
| − | USERNAME@shell.sourceforge.net:/home/groups/P/PR/PROJECTNAME/FILENAME.ZIP
| |
| − |
| |
| − | I tried this and it didn't work
| |
| − | scp jguigen.zip Halepringle@shell.sourceforge.net:/home/groups/P/PR/jguigen.zip.
| |
| − |
| |
| − | What they don't mention in these instructions is that the "P/PR" are the first letter and first two letters
| |
| − | of our project name. This worked
| |
| − | scp jguigen.zip Halepringle@shell.sourceforge.net:/home/groups/J/JG/jguigen.zip.
| |
| − |
| |
| − | Hale 4/10/2006
| |
| − | *********************************************************************
| |
