Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [e4-dev] Does that mean SWT only exist in desktop ?

Hi Zhou,

Thank a lot for your feedback. I have seen j2s project and demo are impressive. Documentation is very good too. Congratulation! Is it a project is again active?

So if I understand today there is 2 solutions SWT to _javascript_ :

* j2s
* RAP
* other???

Is it possible to compare RAP and j2s (pro/cons). I don't have studied j2s and RAP but I like the idea of j2s which use SWT widget. RAP use RWT so if I understand you cannot use RAP code into desktop application?

My second question is about performance. I have tested for instance GMail managed with j2s at http://demo.java2script.org/mail/ and I find it's a little slow compare to GMail. Sorry for my critic, I don't want have disturb with you. I know that performance with _javascript_ is very difficult to manage.

Thank a lot for your feedback.

Regards Angelo

2010/2/9 Zhou Renjian <zhourenjian@xxxxxxxxx>
FYI:

Java2Script ( http://j2s.sourceforge.net/ ) also has ported SWT library for web browser. You can convert SWT standalone application into web application using Java2Script plugin.

SWT Control Example: http://demo.java2script.org/controls/
Online web IM services: http://webuzz.im/

Regards,
Zhou Renjian

--
http://j2s.sourceforge.net/ Java2Script
http://webuzz.im/ Web IMs (Gtalk/MSN/Yahoo!/AIM/ICQ/Jabber)



On Tue, Feb 9, 2010 at 7:37 AM, Ivan Ooi <olibralo@xxxxxxxxx> 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... 

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 <bmuskalla@xxxxxxxxxxxxxxxxx> 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 ). 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, <yves.yang@xxxxxxxxxxx <mailto:yves.yang@xxxxxxxxxxx>> wrote:

    > On Thu, Jan 28, 2010 at 2:16 PM, Tom Schindl
    > <tom.schindl@xxxxxxxxxxxxxxx
   <mailto:tom.schindl@xxxxxxxxxxxxxxx>>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
   e4-dev@xxxxxxxxxxx <mailto:e4-dev@xxxxxxxxxxx> ------------------------------------------------------------------------


_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev


_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev



_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev



Back to the top