Hi Christophe, 2010/6/18 Christophe Meessen <[email protected]>: > Hello, > > I'm considering writing a web service application and I compared WT with > GWT. I recently discovered the existence of WT by reading a tutorial > article in the french Linux journal n° 127 p78 - 84. >
Good article, nice introduction to Wt! (although you need far less threads than that article suggests) > I tried the wt examples on my iPad and Android HTC desire phone. Here is > a modest feedback contribution. > > Touch screen driven browser behave differently from mouse driven > browsers. I saw two problems. > In the git explorer example, when displaying the INSTALL content, the > window scroll bar doesn't show up. So it is not possible to read text > not displayed in the window frame. Tilting the screen from horizontal to > vertical allows to see more of the hidden text. Multi line editable text > fields are however scrollable without problem. The problem appears on > the iPad and the Android browser. > Confirmed on android, I filed a bug. > The second problem is that the split window bars can't be dragged. They > can be selected on the Android, but probably only as an image, and can't > be dragged. > We'd have to see if we can solve this. Filed a bug report to follow-up on it. > Another problem I saw with the treeview example but only on the iPad is > that the text of the pies charts is displayed in a wrong location in > vertical and horizontal mirroed orientation (upside down). > Can you send a screenshot? > A last problem to report is that the rich text editor is not working on > iPad and Android. The text insertion caret doesn't show up and the > keyboard as well. > We use TinyMCE as rich text editor, which apparently doesn't work well on android/ipad. We should consider to fallback to a plain textedit within the toolkit. > The comparison of GWT and WT is clearly in favor of WT which appears 2x > faster ! GWT menus borders are not properly rendered and everything > seems sluggish. Even text edition. The GWT rich text editor doesn't work > too on the iPad and Android. > > The conclusion is that user developing web apps targeting touch screen > browsers must avoid some widgets (split panes, rich text) and some usage > patterns (i.e. scrollable read only text). > Interesting. I did not realize Wt still behaves so much better than GWT on modern mobile browsers. Regards, Wim. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
