www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - The Cross Plattform DWT

reply Frank Benoit <keinfarbton googlemail.com> writes:
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
Jan 19 2008
next sibling parent Marcin Kuszczak <aarti_please_no spam_interia.pl> writes:
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



Wow! I am pretty impressed! 

I was waiting for quite a long time for a good GUI toolkit for D: my
requirements were:
a. cross platform
b. native look and feel
c. native D implementation

and now I hope that this time the dream will come true... :-)

Keep up the good work!

-- 
Regards
Marcin Kuszczak (Aarti_pl)
-------------------------------------
Ask me why I believe in Jesus - http://www.zapytajmnie.com (en/pl)
Doost (port of few Boost libraries) - http://www.dsource.org/projects/doost/
-------------------------------------
Jan 19 2008
prev sibling next sibling parent reply torhu <no spam.invalid> writes:
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


Great, I've been waiting for this!


 
 Both projects will be a manual port of the SWT 3.3 with tango compatibility.


Well, let's hope tangobos can do the trick, with the help of some 
version (Tango) statements.

Do you know anything about compatibility with the original DWT?
Jan 19 2008
parent reply John Reimer <terminal.node gmail.com> writes:
torhu wrote:


 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


 
 Great, I've been waiting for this!
 

 
 Both projects will be a manual port of the SWT 3.3 with tango
 compatibility.


 
 Well, let's hope tangobos can do the trick, with the help of some
 version (Tango) statements.



This might be possible, but we haven't got that far yet. :)



 
 Do you know anything about compatibility with the original DWT?



The original dwt was based on swt 3.02 (and win32 only).  The new versions
for linux and win32 are being ported from swt 3.3.  So, as far as
compatibility is concerned, these should be as compatible as the 3.02 and
3.3 versions of swt will be.  

Strings in original dwt were char[] instead of Java "String"... this is the
same in the new dwt ports.  Furthermore, we are adding the option of a
dynamic loader system similar to Gtkd.  This may simplify some things...
but for now it will be optional.

In summary, as far as I can tell, they old and new should look and feel much
the same, but I guess proof of this will only be evident when dwt based
software is rebuilt with new the dwt.

I particularly look forward to seeing poseidon ported to both dwt-win and
dwt-linux.  Perhaps that will be the ultimate test. :)

Incidentally, the win32 port of dwt to 3.3 has just begun... the dwt-linux
port is much further along.

-JJR
Jan 19 2008
parent reply torhu <no spam.invalid> writes:
John Reimer wrote:

 torhu wrote:
 

 Frank Benoit wrote:

 Both projects will be a manual port of the SWT 3.3 with tango
 compatibility.


 
 Well, let's hope tangobos can do the trick, with the help of some
 version (Tango) statements.


 
 
 This might be possible, but we haven't got that far yet. :)


I should have said that I was thinking about my own dwt app, not 
dwt-win.  Since the original dwt uses phobos, and wouldn't work with 
tangobos because of threads etc, I can't port my app to Tango until 
dwt-win is ready.  So I'm hoping some adjustments to my app can make it 
possible to build it both with dwt+phobos, and dwt-linux+tango+tangobos.
Jan 19 2008
parent reply Lars Ivar Igesund <larsivar igesund.net> writes:
torhu wrote:


 John Reimer wrote:

 torhu wrote:
 

 Frank Benoit wrote:

 Both projects will be a manual port of the SWT 3.3 with tango
 compatibility.


 
 Well, let's hope tangobos can do the trick, with the help of some
 version (Tango) statements.


 
 
 This might be possible, but we haven't got that far yet. :)


 
 I should have said that I was thinking about my own dwt app, not
 dwt-win.  Since the original dwt uses phobos, and wouldn't work with
 tangobos because of threads etc, I can't port my app to Tango until
 dwt-win is ready.  So I'm hoping some adjustments to my app can make it
 possible to build it both with dwt+phobos, and dwt-linux+tango+tangobos.


Depending on how threads are used, you may be lucky. The latest has
std.thread wrapping tango.core.Thread and simple examples work correctly.
There are a few methods in std.thread that had to be set to no-ops though.

-- 
Lars Ivar Igesund
blog at http://larsivi.net
DSource, #d.tango & #D: larsivi
Dancing the Tango
Jan 20 2008
parent torhu <no spam.invalid> writes:
Lars Ivar Igesund wrote:

 Depending on how threads are used, you may be lucky. The latest has
 std.thread wrapping tango.core.Thread and simple examples work correctly.
 There are a few methods in std.thread that had to be set to no-ops though.
 


I've already verified that DWT wouldn't work, it uses Thread.getThis 
quite a bit.  So I'll just use tango threads directly when linking with 
dwt-linux, otherwise phobos threads.
Jan 20 2008
prev sibling next sibling parent reply "Eric Suen" <eric.suen.tech gmail.com> writes:
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

"Frank Benoit" <keinfarbton googlemail.com>

 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
Jan 19 2008
parent John Reimer <terminal.node gmail.com> writes:
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
Jan 20 2008
prev sibling next sibling parent reply Bjoern <nanali nospam-wanadoo.fr> writes:
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
Jan 20 2008
next sibling parent reply Bill Baxter <dnewsgroup billbaxter.com> writes:
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
Jan 20 2008
parent reply John Reimer <terminal.node gmail.com> writes:
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).

If anyone is interested in helping please let Frank or me know.

DWT-win was announced at the same time so that people understood our intent
to support both.  We actually both started work on the Linux port first.

-JJR
Jan 20 2008
parent reply Bill Baxter <dnewsgroup billbaxter.com> writes:
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
Jan 20 2008
parent John Reimer <terminal.node gmail.com> writes:
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
Jan 20 2008
prev sibling parent John Reimer <terminal.node gmail.com> writes:
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
Jan 20 2008
prev sibling next sibling parent reply torhu <no spam.invalid> writes:
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


A while ago, someone mentioned that he might get his company to port SWT 
to D.  Do you know what happened to that?  I guess it didn't happen, or 
you wouldn't be starting this project.
Jan 20 2008
parent Frank Benoit <keinfarbton googlemail.com> writes:
torhu schrieb:

 A while ago, someone mentioned that he might get his company to port SWT 
 to D.  Do you know what happened to that?  I guess it didn't happen, or 
 you wouldn't be starting this project.


I wrote an email to robby, and also asked in his ng thread ("A couple of 
thoughts/queries." 8th dec 07) if he received it, but i never got any 
response.
Jan 20 2008
prev sibling next sibling parent reply bobef <bobef abv-nospam.bg> writes:
Manual port?! You guys must be really determined :)

Maybe you can make the GTK port available to Windows too? It won't be that
native but I think it is not a big deal, plus it supports theming which could
be useful.
Jan 20 2008
next sibling parent Frank Benoit <keinfarbton googlemail.com> writes:
bobef schrieb:

 Maybe you can make the GTK port available to Windows too? It won't be that
native but I think it is not a big deal, plus it supports theming which could
be useful.


If you have experience with GTK and windows, would you mind to take a 
look? Perhaps it is quite easy to do that, perhaps not.
Jan 20 2008
prev sibling next sibling parent John Reimer <terminal.node gmail.com> writes:
bobef wrote:


 Manual port?! You guys must be really determined :)
 
 Maybe you can make the GTK port available to Windows too? It won't be that
 native but I think it is not a big deal, plus it supports theming which
 could be useful.


I thought about this possibility. It could work with some effort, I
suppose...but it would take reprogramming certain sections that depend on
non-windows features (X11, XRender, etc) and also working without direct
COM which the win32 SWT uses. It also would add dependencies like the gtk+
toolkit dll's and gthreads (and all the dll's they depend on), which would
meen added bloat.  The linux version of dwt also uses many gtk/gdk
functions that are linux/X11 specific also (I think).  In short, the win32
SWT seems quite closely connected to win32 (which is good for optimal
performance and interface consistancy).

So, I think it wouldn't be that easy.  But, by all means, please prove me
wrong if you like. :) Can't hurt having a third port, although I'd be
honored to have you lend your skills to the win32 port first.  If I
remember correctly, your skills are quite extroadinary in that area.

In summary, T\the advantage of doing a direct win port is probably less
bloat, more consistancy with platform, and being able to reference the
original 3.03 version of DWT as a guideline. I also think you will find
fewer people interested in a win32 gtk+ based version.  For others, it's no
big deal.

-JJR
Jan 20 2008
prev sibling parent John Reimer <terminal.node gmail.com> writes:
bobef wrote:


 Manual port?! You guys must be really determined :)
 
 Maybe you can make the GTK port available to Windows too? It won't be that
 native but I think it is not a big deal, plus it supports theming which
 could be useful.



Oh... and about theming... I'm not exactly familiar with how swt does it,
but both win32 and linux swt seem to support their own theming mechanism. 
I'm not sure how it works, but it's in swt/internal/theme. Of course, win32
version uses win32 system calls and linux uses gtk+ calls.

-JJR
Jan 20 2008
prev sibling next sibling parent John Reimer <terminal.node gmail.com> writes:
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
Jan 20 2008
prev sibling next sibling parent reply Robert Fraser <fraserofthenight gmail.com> writes:
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 ;-).
Jan 20 2008
parent reply Ary Borenszweig <ary esperanto.org.ar> writes:
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...
Jan 20 2008
parent reply Robert Fraser <fraserofthenight gmail.com> writes:
Ary Borenszweig wrote:

 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...


I was kidding mostly. According to Ohloh, Eclipse is ~10 million LOC and 
Descent is nearing 700,000. While I'd love to see a D port of Descent at 
some point, it would be a HUGE amount of work, even if we started with 
TioPorted sources & debugged from there.
Jan 21 2008
parent Ary Borenszweig <ary esperanto.org.ar> writes:
Robert Fraser escribió:

 Ary Borenszweig wrote:

 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...


 
 I was kidding mostly. According to Ohloh, Eclipse is ~10 million LOC and 
 Descent is nearing 700,000. While I'd love to see a D port of Descent at 
 some point, it would be a HUGE amount of work, even if we started with 
 TioPorted sources & debugged from there.


Yeah, I know... And I'm sure it won't make any big difference with the 
Java version, except Expression#getConstantValue would return a pure D 
object. :-P
Jan 21 2008
prev sibling next sibling parent reply bobef <bobef abv-nospam.bg> writes:
John Reimer Wrote:


 bobef wrote:
 

 Manual port?! You guys must be really determined :)
 
 Maybe you can make the GTK port available to Windows too? It won't be that
 native but I think it is not a big deal, plus it supports theming which
 could be useful.


 
 I thought about this possibility. It could work with some effort, I
 suppose...but it would take reprogramming certain sections that depend on
 non-windows features (X11, XRender, etc) and also working without direct
 COM which the win32 SWT uses. It also would add dependencies like the gtk+
 toolkit dll's and gthreads (and all the dll's they depend on), which would
 meen added bloat.  The linux version of dwt also uses many gtk/gdk
 functions that are linux/X11 specific also (I think).  In short, the win32
 SWT seems quite closely connected to win32 (which is good for optimal
 performance and interface consistancy).
 
 So, I think it wouldn't be that easy.  But, by all means, please prove me
 wrong if you like. :) Can't hurt having a third port, although I'd be
 honored to have you lend your skills to the win32 port first.  If I
 remember correctly, your skills are quite extroadinary in that area.
 
 In summary, T\the advantage of doing a direct win port is probably less
 bloat, more consistancy with platform, and being able to reference the
 original 3.03 version of DWT as a guideline. I also think you will find
 fewer people interested in a win32 gtk+ based version.  For others, it's no
 big deal.
 
 -JJR



Sorry I can't help, but am not into the DWT business anymore :) I find
HTMLayout much better now and I am using it instead of DWT for my work...
Native looking apps are like (slowly) going out of the game... Take a loop at
which direction Windows is going, MS Office, etc... And this is natural,
because it looks much better and slower :D Fortunately HTMLayot is fast.
Anyway, you did good work. Wish you luck.
Jan 21 2008
parent John Reimer <terminal.node gmail.com> writes:
bobef wrote:


 
 
 Sorry I can't help, but am not into the DWT business anymore :) I find
HTMLayout much better now and I am using it instead of DWT for my work...
Native looking apps are like (slowly) going out of the game... Take a loop at
which direction Windows is going, MS Office, etc... And this is natural,
because it looks much better and slower :D Fortunately HTMLayot is fast.
Anyway, you did good work. Wish you luck.



Okay, no problem. :)

HTMLayout is a great tool; I'm sure you'll get something out of that. 
You may be right about native tools... but I think we have a pretty big 
population that thinks native widgets are here to stay too. ;)

-JJR
Jan 21 2008
prev sibling parent reply BCS <ao pathlink.com> writes:
Reply to Frank,


 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
 


I can't seem to check it out.

http://svn.dsource.org/projects/dwt-win/ amI missing
Jan 22 2008
next sibling parent Frank Benoit <keinfarbton googlemail.com> writes:
BCS schrieb:

 http://svn.dsource.org/projects/dwt-win/ amI missing
 


yes, you missed the hg (mercurial) part :)
Jan 22 2008
prev sibling parent reply John Reimer <terminal.node gmail.com> writes:
BCS wrote:


 
 I can't seem to check it out.
 
 http://svn.dsource.org/projects/dwt-win/ amI missing
 


Well, first, you need mercurial (hg) to check out the repository.

We moved away from svn because mercurial provides excellent support for 
distributed repository maintenance.

Once you have the hg package for win32, you do:

hg clone http://hg.dsource.org/projects/dwt-win dwt-win

(where dwt-win is the name of the destination directory)

You will need to download the hg win32 port from here:

http://www.selenic.com/mercurial/wiki/index.cgi/WindowsInstall

I really don't like the confusing number of choices there are mercurial 
packages for win32.  But take your pick and get it set up by following 
the instructions on that page.

For dwt-win, I should have provided information on the project wiki 
giving instructions on how to do this.  I'll try to add that information 
soon.

Also, be aware that little of the win32 port of dwt has been done yet. 
So there's not much in the repository at this point, let alone anything 
working.  If you want to lend me a hand, I'd very much appreciate it.

-JJR
Jan 22 2008
parent reply BCS <ao pathlink.com> writes:
Reply to John,


 BCS wrote:
 

 I can't seem to check it out.
 
 http://svn.dsource.org/projects/dwt-win/ amI missing
 


 Well, first, you need mercurial (hg) to check out the repository.
 
 We moved away from svn because mercurial provides excellent support
 for distributed repository maintenance.
 


[...]

 For dwt-win, I should have provided information on the project wiki
 giving instructions on how to do this.  I'll try to add that
 information soon.


Ideally, I should be able to tell from the front page or one "oh-duh" click 
away what downloading it will take. Something like some easy to find verbiage 
along the line of "Download with /Mercurial/ from...."


 
 Also, be aware that little of the win32 port of dwt has been done yet.
 So there's not much in the repository at this point, let alone
 anything working.  If you want to lend me a hand, I'd very much
 appreciate it.
 
 -JJR
 


Is there any other way to get it? I don't think installing another source 
control system is going to happen any time soon. tarballs would work for 
me considering I'm not going to be doing dev (I have enough trouble using 
GUI API's, I don't even want to think about writing one)
Jan 22 2008
next sibling parent reply John Reimer <terminal.node gmail.com> writes:
BCS wrote:

 Reply to John,
 

 BCS wrote:


 I can't seem to check it out.

 http://svn.dsource.org/projects/dwt-win/ amI missing


 Well, first, you need mercurial (hg) to check out the repository.

 We moved away from svn because mercurial provides excellent support
 for distributed repository maintenance.


 [...]

 For dwt-win, I should have provided information on the project wiki
 giving instructions on how to do this.  I'll try to add that
 information soon.


 
 Ideally, I should be able to tell from the front page or one "oh-duh" 
 click away what downloading it will take. Something like some easy to 
 find verbiage along the line of "Download with /Mercurial/ from...."
 



Yes, I agree.  I should have done this.



 Also, be aware that little of the win32 port of dwt has been done yet.
 So there's not much in the repository at this point, let alone
 anything working.  If you want to lend me a hand, I'd very much
 appreciate it.

 -JJR


 
 Is there any other way to get it? I don't think installing another 
 source control system is going to happen any time soon. tarballs would 
 work for me considering I'm not going to be doing dev (I have enough 
 trouble using GUI API's, I don't even want to think about writing one)
 
 



At this point, since there is nothing working to "get", I don't think 
we'll provide a tarball of any sort.  But perhaps once things start 
building properly, we should consider making releases available in an 
alternative package.  This makes sense.  We'll need some storage options 
that, at this point, I don't think mercurial provides, but perhaps the 
Trac system does. I'll have to investigate the options.

-JJR
Jan 22 2008
parent reply John Reimer <terminal.node gmail.com> writes:
John Reimer wrote:


 
 
 At this point, since there is nothing working to "get", I don't think 
 we'll provide a tarball of any sort.  But perhaps once things start 
 building properly, we should consider making releases available in an 
 alternative package.  This makes sense.  We'll need some storage options 
 that, at this point, I don't think mercurial provides, but perhaps the 
 Trac system does. I'll have to investigate the options.
 



Let me just clarify here... I'm referring to the dwt-win project (since 
I know that dwt-linux is working right now).  Either way, we should 
investigate a way of packaging working releases, eventually.

-JJR
Jan 22 2008
parent reply BCS <ao pathlink.com> writes:
Reply to John,


 John Reimer wrote:
 

 At this point, since there is nothing working to "get", I don't think
 we'll provide a tarball of any sort.  But perhaps once things start
 building properly, we should consider making releases available in an
 alternative package.  This makes sense.  We'll need some storage
 options that, at this point, I don't think mercurial provides, but
 perhaps the Trac system does. I'll have to investigate the options.
 


 Let me just clarify here... I'm referring to the dwt-win project
 (since I know that dwt-linux is working right now).  Either way, we
 should investigate a way of packaging working releases, eventually.
 
 -JJR
 


is there a linux tar-ball?
Jan 22 2008
parent John Reimer <terminal.node gmail.com> writes:
BCS wrote:

 Reply to John,
 

 John Reimer wrote:


 At this point, since there is nothing working to "get", I don't think
 we'll provide a tarball of any sort.  But perhaps once things start
 building properly, we should consider making releases available in an
 alternative package.  This makes sense.  We'll need some storage
 options that, at this point, I don't think mercurial provides, but
 perhaps the Trac system does. I'll have to investigate the options.


 Let me just clarify here... I'm referring to the dwt-win project
 (since I know that dwt-linux is working right now).  Either way, we
 should investigate a way of packaging working releases, eventually.

 -JJR


 
 is there a linux tar-ball?
 
 



No, not yet. :)
Jan 22 2008
prev sibling parent John Reimer <terminal.node gmail.com> writes:
BCS wrote:


 [...]

 For dwt-win, I should have provided information on the project wiki
 giving instructions on how to do this.  I'll try to add that
 information soon.


 
 Ideally, I should be able to tell from the front page or one "oh-duh" 
 click away what downloading it will take. Something like some easy to 
 find verbiage along the line of "Download with /Mercurial/ from...."
 


I've updated the dwt-win front page.
Jan 26 2008