Alexei, Dmitriy showed you one solution. Alternatively, for simple signal-slot connections, you can use a mechanism that we call 'stateless signal/slot learning'. With stateless signal/slot learning, you write the slot in C++, and Wt will learn the JavaScript upfront and send it to the client, so that the action happens immediately there. Read about it here: http://www.webtoolkit.eu/wt/doc/reference/html/overview.html#eventhandling
Regards, Wim. 2010/4/18 Dmitriy Igrishin <[email protected]>: > Hey, Alexei > > 2010/4/18 Alexei Vinidiktov <[email protected]> >> >> 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". >> > Normally, Wt handle each event on the server side inside the event loop. But > if you > want to handle client side events in you own JavaScript code you may want to > use Wt::JSlot. Carefully consider the use of this as Wt gives you > abstraction > from JavaScript and highly optimized to handle events on the server side. > If you want to optimize the latency of the visual effects consider using > stateless slot > implementations instead of Wt::JSlot. > >> >> Is it really necessary to make a server call in such instances? >> >> Doing everying server-side makes the interface a bit sluggish. >> > Its classical (and great) behavior of any Wt application, because Wt > provides > to developer a widget-centric API and offers complete abstraction of any > web-specific implementation details, including event handling. > >> >> 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? >> > If you need extra optimization consider to use Wt::JSlot or stateless slots. >> >> 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 > > Regards, > Dmitriy Igrishin > > ------------------------------------------------------------------------------ > 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 > > ------------------------------------------------------------------------------ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
