Re: [e4-dev] Does that mean SWT only exist in desktop ?

[yves.yang@xxxxxxxxxxx]

>
>    But.... we can't port our existing code over :-( at least in certain
> percentage or degree .. :-(

Agree! But for new applications or new components, there is a lot of
benefices to use XWT comparing to programming approach.

yves
>
> Thanks
>
> On Sat, Feb 6, 2010 at 7:33 AM, <yves.yang@xxxxxxxxxxx> wrote:
>
>> > On Thu, Jan 28, 2010 at 2:16 PM, Tom Schindl
>> > <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
>> https://dev.eclipse.org/mailman/listinfo/e4-dev
>>
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>