Difference between revisions of "Thoughts on Google WebToolkit"
From lightwiki
Line 7: | Line 7: | ||
Connecting to SQL Backend - obviously there somewhere but I haven't seen it yet. | Connecting to SQL Backend - obviously there somewhere but I haven't seen it yet. | ||
+ | ******************* | ||
+ | Main Menu | ||
# Exit - no problem | # Exit - no problem | ||
Line 17: | Line 19: | ||
# Help - since we can use straight html - no problem | # Help - since we can use straight html - no problem | ||
− | **** | + | ************* |
+ | Popup Menu | ||
# Freq Count - probably not a problem | # Freq Count - probably not a problem |
Revision as of 18:05, 17 May 2006
The Google WebToolkit is very exciting.
I am going to listing some of the functions we currently have in JGuiGen in order to start a list of what can and can't be done easily.
Given the way I have structured the code generator (which is not finished except in my mind) - one of the hardest steps is to get a working version of a final application. I can then "mark-it-up" and use it to generate code that deals with different SQL tables and columns.
Connecting to SQL Backend - obviously there somewhere but I haven't seen it yet.
Main Menu
- Exit - no problem
- Delete - no problem
- Add - no problem
- Print - ignore - browser takes care of it.
- Extra - no problem
- Find - lots of code - Query building is probably not a problem, the report is something else again.
- Save - no problem
- Help - since we can use straight html - no problem
Popup Menu
- Freq Count - probably not a problem
- Duplicate - no problem
- next - no problem
- previous - no problem
- A11y - ignore for now (write the code with A11y, just ignore the magnifying glass and probably the debug screen)
- Switch look and feel - ignore - browser handles that
- Switch locale - probably need to do this - not sure how
- Switch font - ignore - let the browser handle
Bottom line - menu options don't seem to be a big problem
Now on to other basics