You might want to look into Sitebricks which is a Google developed web app framework built on top of Guice. It is a simple request response processor with no fancy "component" abstractions like Wicket or Tapestry. This model fits in very well with GWT (or other client frameworks) which request data via RPC or small snippets of rendered html to assemble on the client.
It is still very much in active development so you have to be prepared to dig into the code and figure out the plumbing yourself. The author, Dhanji, has built a fantastic API here - simple, powerful and clever. http://code.google.com/p/google-sitebricks/ John On 10 September 2010 05:35, tempy <fay...@gmail.com> wrote: > Thanks for the explanation Chris! > > Guess I'm learning jquery, golly, I'll be a real web programmer yet. > =) > > On Sep 9, 7:58 pm, "Chris (Google Employee)" <api.ch...@google.com> > wrote: > > Hi Mike, > > > > I think the reason we don't explicitly publish a list of "frontend > > frameworks that play well with App Engine" is because there really is > > no technical barrier between front end frameworks that work in the > > browser such as JQuery, etc and the backend (App Engine). Many App > > Engine users make full use of a myriad of front end technologies/ > > frameworks for UI creation ranging from HTML5/JS/CSS to flash etc. > > > > JQuery is especially popular for a variety of Web app usages, so if > > that works for you, I'd definitely continue trying it out. > > > > Hope this helps, > > -Chris > > > > On Sep 9, 10:43 am, tempy <fay...@gmail.com> wrote: > > > > > > > > > Hello all, > > > > > A little background... I'm mostly new to web frontend development, I > > > come from a mostly backend and desktop background. I have a GAEj app > > > that provides the backend for a rather sophisticated desktop/mobile > > > app. This backend will also drive a website in addition to the > > > desktop/mobile app. > > > > > The website will show a small subset of the data in the system. I > > > started with GWT, but it doesn't seem to be quite right. The website > > > is for presentation of a small subset of the system's data only, and > > > users do not interact with the data in any way other than searching > > > for it. As the data is mostly unstructured text and some images, I > > > feel most comfortable formatting it with plain old html/css. In fact, > > > the layout of the site will be minimal and look a lot like a blog. As > > > such, the website should certainly not feel like a single-page "web > > > application" a la gmail. With GWT, I have little use for widgets and > > > find myself constantly fighting with it to get a non-application look- > > > and-feel. > > > > > The only functionality that I thus really need from GWT is the RPC > > > component, the page should be AJAX, I don't want to do round trips to > > > the server for every navigation event. > > > > > So, I'm not quite sure which framework to use with the GAEj backend. > > > At first GWT seemed like a natural fit, but now seems like overkill. > > > I'm doing some research on jquery, but I haven't seen a list of > > > "frontend frameworks that play well on GAEj" anywhere. > > > > > Thanks for any advice, > > > Mike > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-j...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
