Eric Suen wrote:

> Hi,
> 
>  One if my application is base on DWT, I will try to using
> your version if I got time.
> 
> this is DWT version: http://www.agpad.com/
> and this is Java one: http://www.spket.com/
> 
> Regards
> 
> Eric
> 

Nice!  You'll be using the windows port, then.  Hopefully you will need very few changes to get it working.

As mentioned earlier, one thing that might be a problem is the use of Tango (the previous version of dwt used Phobos), but perhaps we can work on a solution that makes this easier on you. Maybe Tangobos might have some application here.

-JJR

Bjoern wrote:

> 
> Just one word : Incredible.
> Thanks !
> 
> Does it make sense, to port the SWT snippets ?
> this ones : http://www.eclipse.org/swt/snippets/
> 
> I like to suggest to support /groups/ like dwt.group.layout (Tango like)
> 
> Bjoern


About SWT snippets... I didn't know they existed. :)  They look like a pretty comprehensive test of SWT functionality.  I agree that they should be ported at some point.  Right now, I think it's best to focus on porting the examples first.  But anybody that wants to tackle the snippets as well would be most welcome. :)

Concerning "groups":  as far as I know, that is still experimental in Tango.
Doing something similar for dwt is quite possible.  At this point, though,
we are concentrating on the port only, and don't want to make any
fundamental additions or changes to swt. In the future, an option
like "group" should be discussed as a possible way to reduce large import
lists. We were considering the same thing in GtkD, but it doesn't look like
the idea has gained much popularity yet.

-JJR

doob wrote:

> Frank Benoit wrote:
>> Bjoern schrieb:
>>> Does it make sense, to port the SWT snippets ?
>>> this ones : http://www.eclipse.org/swt/snippets/
>> 
>> Sure, that would be great.
>> I you want to start, please talk to me first.
>> So I can prepare the sources in the same way, i did it on the rest.
>> 
>> As said in the dwt-linux homepage, in the moment i am working on the
>> examples.
>> this ones: http://www.eclipse.org/swt/examples.php
>> 
>> Frank
> 
> This is great news and I would be happy to help. I can help testing both the linux and windows version. Any plans on an osx version?

Yes, any help would be greatly appreciated.  Testing, of course, is good... but if you have any expertise (especially on win32)... please let us know.

OS X would be great!  But it's way more than we can tackle at this point. But, if you (or somebody else) is interested in doing such a port, then Frank should be able to get you started. :)

-JJR

Frank Benoit wrote:

> Dear D community
> 
> We are happy to announce the new dsource projects
> - DWT-Win      http://www.dsource.org/projects/dwt-win
> - DWT-Linux    http://www.dsource.org/projects/dwt-linux
> 
> Both projects will be a manual port of the SWT 3.3 with tango compatibility.
> 
> Status DWT-Linux:
> Completed:
> dnd, custom, widgets, events,
> graphics, accessibitly, printing, layout
> Missing:
> browser, program
> 
> First helloworld example running
> Size with debug info/strip/upx: 4,8 MB/1,8 MB/0,5 MB
> 
> Help is welcome:
> All ported code is pretty untested. Examples are needed.
> The official SWT examples should be ported to show the functionality of
> the widgets.
> They can serve as a test and also as programming examples.
> 
> Frank


Also, for those that haven't checked the link, IRC chat on freenode is available in #DWT.  Feel free to check in there to discuss anything about either of these ports.

-JJR

John Reimer wrote:
> Bill Baxter wrote:
> 
>> Bjoern wrote:
>>> Frank Benoit schrieb:
>>>> Dear D community
>>>>
>>>> We are happy to announce the new dsource projects
>>>> - DWT-Win      http://www.dsource.org/projects/dwt-win
>>>> - DWT-Linux    http://www.dsource.org/projects/dwt-linux
>>>> The official SWT examples should be ported to show the functionality
>>>> of the widgets.
>>>> Frank
>>> Just one word : Incredible.
>>> Thanks !
>>>
>>> Does it make sense, to port the SWT snippets ?
>>> this ones : http://www.eclipse.org/swt/snippets/
>>>
>>> I like to suggest to support /groups/ like dwt.group.layout (Tango like)
>>>
>>> Bjoern
>>
>> What's the story with DWT-Win?  Is it just in planning at this stage?
>> There's not much on the web dsource page.
>>
>> Also why two projects?  Won't they share most of the same source code?
>> Just curious.
>>
>> --bb
> 
> 
> Yes, the win port has just started; I have not yet committed any ported
> source... No they don't share much source code (other than perhaps a few
> highlevel sections).  
The implementation of widgets on linux uses
> gtk+/cairo, while the implementation on win32 graphics/system calls.  It's
> quite a bit of work.  It would be a mess to integrate both projects into
> one (using version statements).

Ok.  Well I was just thinking of wxWidgets, which has subdirectories for platform-specific stuff, and other subdirectories for the common stuff.  There's a fair amount of common stuff there.  I would expect SWT/DWT to not differ too terribly much from wx in the ratio.  So, anyway, just surprising to me to see the different ports going to entirely different repositories.  But if it works for you then, great.

--bb

Bill Baxter wrote:

>> 
>> Yes, the win port has just started; I have not yet committed any ported source... No they don't share much source code (other than perhaps a few highlevel sections).
> The implementation of widgets on linux uses
>> gtk+/cairo, while the implementation on win32 graphics/system calls.
>> It's
>> quite a bit of work.  It would be a mess to integrate both projects into
>> one (using version statements).
> 
> Ok.  Well I was just thinking of wxWidgets, which has subdirectories for
> platform-specific stuff, and other subdirectories for the common stuff.
>   There's a fair amount of common stuff there.  I would expect SWT/DWT
> to not differ too terribly much from wx in the ratio.  So, anyway, just
> surprising to me to see the different ports going to entirely different
> repositories.  But if it works for you then, great.
> 
> --bb

SWT actually tries to separate platform specific stuff into internal/gtk or
internal/win32.  But then it creates a class OS, which all widgets use to
access system specific calls.

yes, a few directories do contain files that are common across platforms:
events, layout, part of accessibility, a tiny portion of internal, and
maybe some of graphics).  Otherwise... everything else is very system
specific implementation (see widgets modules).

I know some projects organize into platform directories for internal things (eg harmonia), and I agree that it's a good idea, but I still think that this would be difficult to do given the already established organization of swt.  You would litterly have to pull it apart and restructure it.

GtkD has little trouble doing one source base for both linux and win32 because it uses common gtk+ calls on both platforms.  It doesn't even have to separate win32 and linux specific calls in different directories.  This, perhaps would be a possibility for DWT also if it had a common linux and win32 gtk+ port.

Anyway, thanks for the suggestion.  If you have a look at DWT and think there's a workable solution for integrating the two, please feel free to propose a solution... But /IF/ we ever get several other OS ports done, the suggestion would have to be practical enough for multiple platforms.

One other reason we didn't put the ports together was that we wanted to keep the size of the hg (mercurial) repositories down so that people didn't have to download volumes of unrelated platform code.

-JJR

Frank Benoit wrote:
> Dear D community
> 
> We are happy to announce the new dsource projects
> - DWT-Win      http://www.dsource.org/projects/dwt-win
> - DWT-Linux    http://www.dsource.org/projects/dwt-linux
> 
> Both projects will be a manual port of the SWT 3.3 with tango compatibility.
> 
> Status DWT-Linux:
> Completed:
>     dnd, custom, widgets, events,
>     graphics, accessibitly, printing, layout
> Missing:
>     browser, program
> 
> First helloworld example running
> Size with debug info/strip/upx: 4,8 MB/1,8 MB/0,5 MB
> 
> Help is welcome:
> All ported code is pretty untested. Examples are needed.
> The official SWT examples should be ported to show the functionality of the widgets.
> They can serve as a test and also as programming examples.
> 
> Frank

Awesome. Now time to get porting the rest of Eclipse over for a pure-D Descent ;-).

Robert Fraser escribió:
> Awesome. Now time to get porting the rest of Eclipse over for a pure-D Descent ;-).

Heh. Same thought here, although without runtime reflection, hmm...

For OSX, Maybe should waiting for SWT 3.4, because SWT 3.3 is based on Carbon, and SWT 3.4 has Cocoa port

"doob"
> Frank Benoit wrote:
>> Bjoern schrieb:
>>> Does it make sense, to port the SWT snippets ?
>>> this ones : http://www.eclipse.org/swt/snippets/
>>
>> Sure, that would be great.
>> I you want to start, please talk to me first.
>> So I can prepare the sources in the same way, i did it on the rest.
>>
>> As said in the dwt-linux homepage, in the moment i am working on the
>> examples.
>> this ones: http://www.eclipse.org/swt/examples.php
>>
>> Frank
>
> This is great news and I would be happy to help. I can help testing both the linux and windows version. Any plans on an osx version?

Eric Suen wrote:
> For OSX, Maybe should waiting for SWT 3.4, because SWT 3.3
> is based on Carbon, and SWT 3.4 has Cocoa port
> 


That probably is a good idea.  Updating 3.3 to 3.4 for the other ports should be less of an effort than 3.02 to 3.3.

-JJR