> 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");
>> }
>> });
