Hi, I have a sample project that solves this problem -- well, it is one particular solution to the problem. It works well for me. I am following this approach for a real app that I am building. You may find it useful: http://zenoconsulting.wikidot.com/blog:16
Regards, Davis On Sat, Oct 24, 2009 at 1:19 AM, Open eSignForms <[email protected]> wrote: > > Newbie question for GWT 1.7 is how do people tend to organize their > webapps that may have multiple distinct sets of functionality. > > That is, would people tend to create a HTML+Entry for a login page > that is streamlined only for this very specific task of authenticating > users, handling forgot passwords, etc. that are related to a non- > logged in user. > > Then perhaps have another HTML+Entry for the main "dashboard" aspect > of the application. I tend to think of this part of the application > as the run-time focus for typical users who are making use of the > system. > > Then perhaps have another HTML+Entry for specialist tasks that are > more geared towards administrators or the like that are setting up the > application and all of those tasks that can be fairly complex on their > own, but aren't user functions. > > And then would most people create one RPC interface to support each of > these Entry points, or might a non-trivial Entry point tend to support > a series of RPC interfaces to deal with myriad functions. > > Thanks for any ideas on what are considered best practices in this > area. > > > > -- Zeno Consulting, Inc. home: http://www.zenoconsulting.biz blog: http://zenoconsulting.wikidot.com p: 248.894.4922 f: 313.884.2977 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
