Worth to mention their debug mode where you can find design problems. Try to click on the "analyse layouts" button: http://demo.vaadin.com/sampler/?debug=true
so +1 for Vaadin Marcelo Magno On Wed, Aug 11, 2010 at 1:17 PM, Steve Wart <steve.w...@gmail.com> wrote: > Vaadin looks good, and it makes sense to keep the client-side load > light, especially with touch devices becoming prevalent. > > But it doesn't seem great (so far) for touch UI work, and I think the > "everything in Java" mantra is sub-optimal. While Vaadin has hooks for > CSS and hand-crafted JavaScript, my ideal toolset would better support > the developers who can make these technologies sing. > > On Wed, Aug 11, 2010 at 7:42 AM, Kevin Qiu <kevin.jing....@gmail.com> > wrote: > > +1 for Vaadin. > > Their widgets are very polished and professional. GXT and SmartGWT are > fine > > but they're too desktop-looky, not Web2.0 looky... > > > > > > On Mon, Aug 9, 2010 at 4:03 PM, marius.andreiana > > <marius.andrei...@gmail.com> wrote: > >> > >> Hi Chi, > >> > >> On Aug 9, 10:23 pm, Chi H <c...@chi.ca> wrote: > >> > * Pagination is the standard solution to the 'large number of > >> > entities' problem. However, there is a usability cost to pagination. > >> > It would be really nice to get rid of the pagination and just use a > >> > scrollbar. If you used the approach of SlickGrid (http:// > >> > wiki.github.com/mleibman/SlickGrid/), where you only rendered what > was > >> > visible on the screen, you can render large numbers entities without > >> > the need for pagination. > >> > >> How will search engines index all the content in this case? > >> > >> The SlickGrid widget doesn't work at all if JS is not enabled. > >> > >> Thanks > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Google Web Toolkit" group. > >> To post to this group, send email to > google-web-tool...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > >> For more options, visit this group at > >> http://groups.google.com/group/google-web-toolkit?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Web Toolkit" group. > > To post to this group, send email to google-web-toolkit@googlegroups.com > . > > To unsubscribe from this group, send email to > > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > > For more options, visit this group at > > http://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
