Hello,

Do I understand correctly that Wt processes almost everyting on the server side?

Trying the examples I saw that every action triggers a call to the
server, where in most cases a client-side action (written in
Javascript) would suffice. For instance if I click a button in the
example for PushButton here
http://www.webtoolkit.eu/widgets#/form-widgets/wpushbutton I see a
"loading..." notification and after that the text in the lower part of
the window changes to "Last activated signal: WPushButton click".

Is it really necessary to make a server call in such instances?

Doing everying server-side makes the interface a bit sluggish.

I wonder what the rationale for that is.

Could actions be separated into two categories: client-side and server-side?

If it's not possible, how could the responsiveness of the interface be improved?

Thanks.

-- 
Alexei Vinidiktov

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to