Hi, Thanks for your reply. It looks great. However I found out the speed of grid are a bit slow compare to SmartGWT. Can we write client logic in Java and let the compiler translate that to JavaScript ? some things like GWT.
j2s looks good as well. only the UI looks a bit Win9x. Thanks On Thu, Feb 11, 2010 at 1:34 AM, Rüdiger Herrmann < [email protected]> wrote: > On 09.02.2010 00:37, Ivan Ooi wrote: > >> Hi, >> >> Thanks for the reply. sorry about that. Ya, RAP are filling the gape >> for this area. Sorry, I forgot about RAP project. This is great.... >> About RAP, Can I simply use RWT instead of RCP ? Sorry for my stupid >> questions... >> > Put simply, you can use RWT instead of SWT and (with some limitations) let > the RCP/e4 workbench run on top of it. > See here for a more detailed introduction to RAP: > http://eclipse.org/rap/introduction.php > > >> Thanks again! Good to hear that SWT now exist in Web platform as well. >> Best is it use back Java language. >> >> Oh ya! can I use Java in RWT client side for logic ? >> >> Thanks and Best Regards, >> Ivan >> >> On Tue, Feb 9, 2010 at 2:28 AM, Benjamin Muskalla >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hi, >> >> as Lars already pointed out, the RAP project already allows you to >> single-source your existing code to bring your RCP application to >> the web (see eclipse.org/rap <http://eclipse.org/rap> ). The >> >> problems Tom mentioned are real, but only some of them. Eg. the >> event-loop is part of RAP for several releases and has proven to >> work efficiently in a server-centric environment. Operating system >> resources are available too (eg. Fonts, Cursors, etc). The only >> missing part is a proper GC implementation which heavily relies on >> the capabilities of modern browsers but depending on your task at >> hand you could use the RAP theming to customize the look and feel of >> the application (eg. roundend corners or gradients). >> >> Hope that helps, >> Ben >> >> Ivan Ooi wrote: >> >> Hi, >> >> But.... we can't port our existing code over :-( at least in >> certain percentage or degree .. :-( >> Thanks >> >> On Sat, Feb 6, 2010 at 7:33 AM, <[email protected] >> <mailto:[email protected]> <mailto:[email protected] >> >> <mailto:[email protected]>>> wrote: >> >> > On Thu, Jan 28, 2010 at 2:16 PM, Tom Schindl >> > <[email protected] <mailto: >> [email protected]> >> <mailto:[email protected] >> <mailto:[email protected]>>>wrote: >> >> > >> >> Hi, >> >> >> >> Doing a full SWT-Port for the Web is a very hard task because >> some of >> >> the concepts in SWT can't be emulated easily on the browser: >> >> >> >> * Event-Loop: Todays browser though HTML5 brings webworkers are >> still >> >> single threaded and so you can't e.g open blocking dialogs >> like you >> >> do in SWT => SWT would have to introduce API with callbacks so >> >> that one could write single-source code. >> >> >> >> An example might make this clear: >> >> >> >> Today: >> >> ----------8<---------- >> >> MessageBox msg = new MessageBox(parent,SWT.ICON_ERROR); >> >> msg.setText("I'm the message"); >> >> msg.open(); // Blocking call >> >> System.out.println("I'm running after dialog closed"); >> >> ----------8<---------- >> >> >> >> In Future: >> >> ----------8<---------- >> >> MessageBox msg = new MessageBox(parent,SWT.ICON_ERROR); >> >> msg.setText("I'm the message"); >> >> msg.open(new Runnable() { >> >> public void run() { >> >> System.out.println("I'm running after dialog closed"); >> >> } >> >> }); >> >> It is exactly one of benefice of using XWT: physical >> separation between >> event handling and UI. XWT can manage the both cases >> transparently. >> We can >> define the event handling policy (sync, async and delayed >> async) between >> declarative UI and event handling based on Java Handling, >> Bundle >> service, >> web service etc. >> >> yves >> >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> >> >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> >> >> >> >> ------------------------------------------------------------------------ >> >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] <mailto:[email protected]> >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] <mailto:[email protected]> >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> >> >> >> >> _______________________________________________ >> e4-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
