> > - Is using a single PlaceController with multiple 'identifiers' really a > best practice? >
I'm not sure of the proper implementation of this. In other implementations of this type of system, I have always used what GWT calls a "place" as something which encapsulates numerous "activities" which have a common similarity. For example, I would have thought you would have a single AdminPlace which managed activities such as AdminUserActivity, AdminPageActivity, AdminForumActivity, etc. Is what you are suggesting closer to a 1:1 mapping of places to activities? With an AdminUserPlace taking you to AdminUserActivity and AdminPagePlace to AdminPageActivity? Then each place only stores information relevant to the activity to which it maps to? > - I would prefer using ApplicationRequestFactory instead of > MyRequestFactory, etc... > - I would move the files in client.application to client > Done. Much more logical. > Moreover, I would love to see a more advanced domain object and related > Editor (maybe even > an object graph Editor). > I definitely agree. The current implementation is more of a proof-on-concept than anything useful. I have a GitHub issue to expand editors already created: https://github.com/JakeWharton/GwtBase/issues/issue/11 Also, thanks for the pull request! It has been merged. -- 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.
