Difference between revisions of "JGuiGen Demo"

Revision as of 18:50, 12 April 2006

Back to Main Page

• Screencast ... dry run for rev 82 ... recorded 2006/04/12

• notes made during creation of demo script
• notes made during moves of files on 20060410
• notes made attempting to compile with java 1.5 on 20060411 (not as bad as i expected)
• notes made 20060411 evening

1. Assumed to have installed: subversion, java sdk, maybe eclipse 3.1.2
2. (ghp) On one of my Fedora boxes I had to install subversion yum install subversion worked fine
3. svn checkout https://svn.sourceforge.net/svnroot/jguigen/JGuiGen/trunk/ jguigen
4. (ghp) I had to chmod the jguigen folder to give permissions before I could use elcipse. I had to do the same for the files - especially .classpath and .project which did not have write access.
5. (ghp) When running from Eclipse - I had to 1) Create a new Project (JGuiGen) in the folder where I installed JGuiGen (this found the existing project) 2) Right click on the project (in the Java Perspective window) --> Properties --> Build Class Path There are two external jars jce.jar and jsse.jar that are sun security files. The current class path points to their location on my Windows box. You need to change this path to point to the <java install path>/jre/lib/ext folder on your box.

1. cd jguigen
2. unzip JGuiGenMisc.zip
3. ./build.sh
4. classpath=".:"`echo lib/*.jar | tr " " ":"`
5. java -cp $classpath JGuiGen
6. Users
7. UserDemo
8. change the social security number
9. change the start date
10. change to a different row in the table and show off the validation catch
11. sort by clicking on a column
12. right click and drop your jaw
13. click back in the main window and change the ssn
14. right click ... choose next
15. watch validation work again
16. mention the 10 or so actions which are already coded for me, and I dont have to write code for that correctly validate and make sure the users of my gui do not loose data in irritating ways
    1. changing rows in the table
    2. next in the right click pop-up
    3. previous in the right click pop-up
    4. "Refresh table" in the right click pop-up
    5. Find in the richt click pop-up and in the top menu
    6. Extra in the right click pop-up and the top menu
    7. "Dup" in the right click which means duplicate the current row with a new id number
    8. "Add" in the right click and in the main menu
    9. the exit button in the upper left
    10. and the window close X button in the upper right ... web developers eat your heart out
    11. we may have missed 1 or 2 ... isn't that rediculous
17. Notice that the font chooser has octothorpes around the text
    1. the code still runs, which anyone whose ever had to do i18n should appreciate, and we can also go in and regenerate the resource bundles for the internationalization of that menu option
18. Notice that "ExtRa" button ... i should be able to easily find the code for this button in the java and rename it and add my own functionalty to it ... maybe runing a custom report
19. Look and feel (placeholder)
    1. right click again ... choose inverse mono look and feel
    2. right click ... choose Native
20. Print the screen (placeholder)
21. Find
    1. First name "is equal to" Hale
    2. OR
    3. last name "is like" Sing%
    4. Execute
    5. Find ... note it saved our most recent find critereon
    6. note the "Show inactive" button which toggles and ... guess what allows the user to find rows that they or someone else deleted last week, but were not really deleted of course ... just flagged that way so that you did not have to write that code again ... just use JGuiGen
    7. Reports (place holder)
22. click Help in upper right
    1. When we have generated our own gui the help will be our own help
23. Exit out of User Demo
24. The help that is "here" is for JGuiGen eating it's own dog food
    1. 1. this pop-up help
       2. manual
       3. readme
25. So there is plenty of documentation about JGuiGen for those of you who like to RTFM
26. such as this read me which shows you all of the databases suppoerted by JGuiGen ... cuddle up with this in bed some evening ... rediculous quantities of docs
27. Now let generate our own gui
28. Exit JGuiGen
30. vi JGuiGenIni.xml, add table name "Lead", add class name "Lead", add table model name "LeadTm"
31. sh ./runUtil.sh DatabaseManager ...
    1. type: "... Standalone"
    2. driver: JGuiGenDb
    3. Ok
32. cut and paste new table "Lead"
33. cut and paste new columns: id, date, address
34. run JGuiGen from the command line java -cp $classpath JGuiGen
35. Basic flow ... run JGuiGen and start in the Data Dictionary Menu
    1. Mark Tables - place a check mark on the "Process Table" field for your new Lead Table
    2. Check Data Dictionary, Leave Flags, Run Now
    3. Edit Data Dict ...Select the Lead table, Do a bunch of stuff for each column
    4. Generate Application (Model, Order, Create Java)
    5. Exit from the Internationalization causes a write
    6. Generate HTML (optional)
36. Compile and run the new gui
    1. show out-of-the-box features of the gui
    2. View, Add, Edit, Delete ... right click duplicate
    3. Search for some rows
    4. Oh ... what's this? ... Reports!
    5. try closing a window after a change
    6. try changing the row to edit after a change
37. wash, rinse, repeat ?, ?, ?, and ? showing features
    1. Quickly adding a column, such as: ssn, phone, address
    2. Internationalization
    3. Hot keys
    4. Change validation error message and Test
    5. blast the coffee cup
    6. run test scripts against the gui
    7. show test script output
38. launch eclipse

• shameless plug - 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.

3. To update the SourceForge web site I used Winscp and logged into shell.sourceforge.net using my sourceforge username and password. That placed me in /home/users/h/ha/halepringle. I navigated to /home/groups/j/jg/jguigen/htdocs and uploaded the web pages. Hale 4/10/2006