Interesting topic.
Can't really comment on those things but I guess the CellWidgets are a
good starting point.
I also came across a good stackoverflow reply which I think might also be
useful: http://stackoverflow.com/a/7481137/356594
Yeah I have also came across this link and it
[1] http://code.google.com/p/google-web-toolkit/wiki/CellBackedWIdgets
[2] http://www.sencha.com/products/gxt/whats-new-in-sencha-gxt-3/
[3]
https://groups.google.com/d/topic/google-web-toolkit-contributors/g8WPRxkdqPA/discussion
[4]
Interesting topic.
Can't really comment on those things but I guess the CellWidgets are a good
starting point.
I also came across a good stackoverflow reply which I think might also be
useful: http://stackoverflow.com/a/7481137/356594
On Monday, February 25, 2013 3:32:08 PM UTC+1, Jens wrote:
+1
Just adding few thoughts.
Personally I think that, performance wise, cells are the best. But it is
also true that they can be tricky to work with, when defining new widgets.
Luckily CellWidget helps *a lot* this way. Using CellWidget + Appearance
pattern [1] + maybe UiRenderer, let you code
On Tuesday, February 26, 2013 5:12:34 PM UTC+1, Andrea Boscolo wrote:
As a side note, interesting are the choices made in Collide: low-level
mvp-based widgets built upon the Element object coming from the Elemental
library, with some added custom listeners, as necessary [5].
[5]
I am planing to write some new widgets that meet my personal requirements
and I would like to have some opinions how to implement them best.
First my requirements:
1.) Performance
2.) ClientBundle for styles/resources
3.) DOM/behavior should be extendable/changeable (see next point)
4.) Mobile
