Difference between revisions of "Thoughts on Google WebToolkit"

From lightwiki
Jump to: navigation, search
 
Line 5: Line 5:
 
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.
 
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.
+
Connecting to SQL Backend - obviously there somewhere but I haven't seen it yet.
 +
 
  
 
# Exit - no problem
 
# Exit - no problem
Line 15: Line 16:
 
# Save - no problem
 
# Save - no problem
 
# Help - since we can use straight html - no problem
 
# Help - since we can use straight html - no problem
 +
 
****
 
****
 
# Freq Count - probably not a problem
 
# Freq Count - probably not a problem
 
# Duplicate - no problem
 
# Duplicate - no problem
 
# next - no problem
 
# next - no problem
previous - no problem
+
# previous - no problem
 
# A11y  - ignore for now (write the code with A11y, just ignore the magnifying glass and probably the debug screen)
 
# 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 look and feel - ignore - browser handles that
 
# Switch locale - probably need to do this - not sure how
 
# Switch locale - probably need to do this - not sure how
 
# Switch font - ignore - let the browser handle
 
# Switch font - ignore - let the browser handle
 +
 
************************
 
************************
 
Bottom line - menu options don't seem to be a big problem
 
Bottom line - menu options don't seem to be a big problem

Revision as of 18:04, 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.


  1. Exit - no problem
  2. Delete - no problem
  3. Add - no problem
  4. Print - ignore - browser takes care of it.
  5. Extra - no problem
  6. Find - lots of code - Query building is probably not a problem, the report is something else again.
  7. Save - no problem
  8. Help - since we can use straight html - no problem
  1. Freq Count - probably not a problem
  2. Duplicate - no problem
  3. next - no problem
  4. previous - no problem
  5. A11y - ignore for now (write the code with A11y, just ignore the magnifying glass and probably the debug screen)
  6. Switch look and feel - ignore - browser handles that
  7. Switch locale - probably need to do this - not sure how
  8. Switch font - ignore - let the browser handle

Bottom line - menu options don't seem to be a big problem

Now on to other basics