Difference between revisions of "JGuiGen Demo with Hale's notes"

Revision as of 01:37, 13 April 2006

Back to Main Page

The objective:

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

The demo script

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
   1. Going hardcore ...
   2. Check out of the latest JGuiGen source code
   3. In case this is your first time hearing about JGuiGen ... it is all about J for Java, Gui for Graphical User Interfaces, and the Generation thereof, hence "J" ... "Gui" ... "Gen"
   4. Some have said that they'd rather write code that writes code than just write code.
   5. So again what we are checking out here is code that compiles in order to generate code that compiles in order to render GUIs that allow users to do something I call ... View, add, edit, and delete from a table.
   6. The big picture here is that we will be able to quickly generate a screen that allows users to view, add, edit, and delete entries from a table.
   7. Another person called this "Elegant CRUD" which sounds like an oxymoron where CRUD stands for Create, review, update, and delete ... or as I translate it ... add, view, edit, delete
   8. Only the most motivated, high speed, open source development allowed ... no holding back
   9. grabbing the latest source using subversion on sourceforge.net
   10. The jars, a 3 MB sample database, help files, and of course the source ... there it is
   11. we have revision ...
   12. Let's get down to business in JGuiGen
4. cd jguigen
5. unzip JGuiGenMisc.zip - these are starter files that we usually don't want others committing back into source, such as the configuration files you need to customize for yourself when you are generating your Graphical User Interfaces ... and other files that you will need to ...
6. ./build.sh
7. classpath=".:"`echo lib/*.jar | tr " " ":"`
8. java -cp $classpath JGuiGen
9. Users
10. UserDemo
11. change the social security number
12. change the start date
13. change to a different row in the table and show off the validation catch
14. sort by clicking on a column
15. right click and drop your jaw
16. click back in the main window and change the ssn
17. right click ... choose next
18. watch validation work again
19. 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
20. Notice that the font chooser has octothorpes around the text, two points I'd like to make about this:
    1. the code still runs, which, for anyone whose ever had to do serious i18n in Java, you will appreciate
    2. we can also go in now with JGuiGen and regenerate the resource bundles for the internationalization of that menu option
21. Notice that "ExtRa" button ...
    1. This is just a simple button in the code that
    2. you will be able to easily find the code for it in the java
    3. rename it to "my custom report"
    4. add your own functionalty to it
    5. and look it has built in functionality underneath that you might like to use ... option 1, 2, 3
22. 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
23. place holder for dicussing
    1. Reports
    2. Look and feel
       1. right click again ... choose inverse mono look and feel
       2. right click ... choose Native
    3. Print the screen
24. click Help in upper right ... This is your place to put your own help for your gui
25. Exit out of User Demo
26. The help that is "here" one of the many examples of JGuiGen eating it's own dog food.
    1. Simply tonnes of documentation about JGuiGen e.g.
    2. here is a manual and for those of you who like to RTFM
    3. here is a read me which shows you, for example, all of the databases suppoerted by JGuiGen
    4. You can cuddle up with this in bed some evening
27. Now let us move on now and generate our own gui
28. Exit JGuiGen
29. vi JGuiGenIni.xml, add table name "Lead", add class name "Lead", add table model name "LeadTm"
30. sh ./runUtil.sh DatabaseManager
    1. type: "... Standalone"
    2. driver: JGuiGenDb
    3. Ok
31. cut and paste new table "Lead"
32. cut and paste the index
33. discuss the table columns
    1. lead_ID integer identity
    2. lead_DATE timestamp
    3. lead_PHONE char(20)
    4. isremoved smallint - the deleted flag
    5. lastchangedby char(20) - for sanity and multi user functionality
    6. lastchangeddate timestamp default null - for validation and multi user functionality
34. java -cp $classpath JGuiGen
35. Starting 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

Notes 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