www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - DUI

reply bobef <bobef_member pathlink.com> writes:
Is DUI dead? Should use it or better use plain GTK?
Sep 09 2005
next sibling parent John Reimer <John_member pathlink.com> writes:
In article <dfsrqi$2o97$1 digitaldaemon.com>, bobef says...

Is DUI dead? Should use it or better use plain GTK?


I think it's still active.  Ant adds/fixes features in the library every once
and awhile and brings it up to date with new compiler releases.  I cleaned up
some minor things recently also.  There were some bugs with tree views if I
recall that still needed fixing, though.  (LEDS is the main source of testing
for the library.  There are still a number of problems with it.)  That said, I
haven't heard much from Ant (DUI's author) in the last little while.

Hopefully, DUI sticks around for awhile.  At least, I hope it does because it's
provides a fairly comprehensive GUI toolkit; it's also one of the oldest GUI
toolkits out there for D.

You might get more feedback if you ask the same question on the dsource.org
forum.

-JJR
Sep 09 2005
prev sibling parent reply Ant <duitoolkit yahoo.ca> writes:
bobef wrote:

 Is DUI dead?


nah. DUI is here to stay.
I'm using it for private projects.
I have new ideas for it.
My latest project will have a windows version soon
so the windows version will have to be working soon.

for the latests DUI version grab the dsource svn repositories
for DUI use  http://svn.dsource.org/projects/dui/trunk/dyndui
not the main trunk.
(don't forget dool, DUI depends on dool)

The main problem is that I'm desapointed with DMD state,
I'm always designing around DMD bugs.


 Should use it or better use plain GTK?


there is a project on dsource that contains vanilla GTK+ bindings.

Ant
Sep 10 2005
parent reply bobef <bobef lessequal.com> writes:
Ant wrote:

 
 for the latests DUI version grab the dsource svn repositories
 for DUI use  http://svn.dsource.org/projects/dui/trunk/dyndui
 not the main trunk.
 (don't forget dool, DUI depends on dool)
 


It would be nice if you update dui.sourceforge.net with the latest 
bugfixes etc. Me personaly don't like dsource very much because it does 
not contain (almost) any information about the projects. In other words 
it would be nice to provide some more info. Maybe the GTK version of dui?
Sep 12 2005
next sibling parent reply Ant <Ant_member pathlink.com> writes:
In article <dg3dar$15p0$1 digitaldaemon.com>, bobef says...

Ant wrote:

 
 for the latests DUI version grab the dsource svn repositories
 for DUI use  http://svn.dsource.org/projects/dui/trunk/dyndui
 not the main trunk.
 (don't forget dool, DUI depends on dool)
 


It would be nice if you update dui.sourceforge.net with the latest 
bugfixes etc.


You're right, I'll try to do it.


 Maybe the GTK version of dui?


both 2.6 and 2.8 are good for now (dmd 0.131).

Ant

(leds on windows is almost here - thanks jjr)
Sep 12 2005
parent reply John Reimer <terminal.node gmail.com> writes:
Ant wrote:

 In article <dg3dar$15p0$1 digitaldaemon.com>, bobef says...
 

Ant wrote:


for the latests DUI version grab the dsource svn repositories
for DUI use  http://svn.dsource.org/projects/dui/trunk/dyndui
not the main trunk.
(don't forget dool, DUI depends on dool)


It would be nice if you update dui.sourceforge.net with the latest 
bugfixes etc.


 
 
 You're right, I'll try to do it.
 
 

Maybe the GTK version of dui?


 
 
 both 2.6 and 2.8 are good for now (dmd 0.131).
 
 Ant
 
 (leds on windows is almost here - thanks jjr)
 
 


Great!  I noticed you committed a number of updates.  I'll start testing 
things again soon too.

Thanks much, Ant.

-JJR
Sep 12 2005
parent reply Ant <duitoolkit yahoo.ca> writes:
John Reimer wrote:

 I'll start testing 



don't bother.
I messed up something and now it won't compile on Linux.
it was working on windows.

Ant
Sep 12 2005
next sibling parent reply Def <Def_member pathlink.com> writes:
Another question, I don't feel like registering to DScource, so I thought
I might ask here as well. Have you decided now to stick to the LGPL for
DUI or is there any chance you might change over to something less
restrictive like MIT/X11/zlib license?

Def
Sep 13 2005
parent reply Ant <duitoolkit yahoo.ca> writes:
Def wrote:

 Another question, I don't feel like registering to DScource, so I thought
 I might ask here as well. Have you decided now to stick to the LGPL for
 DUI or is there any chance you might change over to something less
 restrictive like MIT/X11/zlib license?
 
 Def
 
 


I want to go with something less restrictive.
but it's very confusing.
I want to include the documentation from GTK into the code comments
and I don't know if I can do it.
I guess it will be simple to strip the comments out if necessary.
I also have code copied from phobos (on dool) so I'll probably have to go
with he same license as phobos (GPL + Artistic - as I remember)

BTW
as far as updating the sourceforge pages I'll wait until I can compile it again
on linux.
(the problem might be with the templates - but no changes there for many months
dmd is out to get me!)

Ant
Sep 13 2005
next sibling parent Def <Def_member pathlink.com> writes:
In article <dg82f4$2o6n$1 digitaldaemon.com>, Ant says...


with he same license as phobos (GPL + Artistic - as I remember)


You're confusing things here. It's the DMD front end that is released under GPL
and Artistic license. Phobos is released under a permissive MIT/ZLIB type
license. (I don't know which one exactly, and if it's always the same, but it
doesn't matter since I believe they say almost the same.)

Def
Sep 14 2005
prev sibling parent reply Def <Def_member pathlink.com> writes:
In article <dg82f4$2o6n$1 digitaldaemon.com>, Ant says...


I want to go with something less restrictive.
but it's very confusing.
I want to include the documentation from GTK into the code comments
and I don't know if I can do it.
I guess it will be simple to strip the comments out if necessary.


BTW, have you confirmed that the license of the GTK documentation that you
want to use in your comments is actually under the LGPL? Or is there
another license for the docs? Or is it simple copyright, similar to what
Walter uses for his D documentation?

Def
Sep 14 2005
parent Ant <Ant_member pathlink.com> writes:
In article <dg9stv$1s0l$1 digitaldaemon.com>, Def says...

In article <dg82f4$2o6n$1 digitaldaemon.com>, Ant says...


I want to go with something less restrictive.
but it's very confusing.
I want to include the documentation from GTK into the code comments
and I don't know if I can do it.
I guess it will be simple to strip the comments out if necessary.


BTW, have you confirmed that the license of the GTK documentation that you
want to use in your comments is actually under the LGPL? Or is there
another license for the docs? Or is it simple copyright, similar to what
Walter uses for his D documentation?

Def


I'll have to review that.
I asked on the GTK group once.
what I remember is that I couldn't do it
but also the all thing wasn't too clear.

Ant
Sep 14 2005
prev sibling parent reply John Reimer <brk_6502 yahoo.com> writes:
Ant wrote:

 John Reimer wrote:
 

 I'll start testing 


 
 
 
 don't bother.
 I messed up something and now it won't compile on Linux.
 it was working on windows.
 
 Ant


Strange.  I got it compiling on linux with the build utility just last 
night.  It builds leds too.  Leds will run without a segfault.  Yet I 
can only build everything properly if I use build to build all objects 
at once, that is by letting build collect and compile all required 
source files for DUI and leds.

Where I have complete failure is where I try to use build to create libs 
for libdool.a, libdui.a, and libdantfw.a separately.  It creates the 
libraries just fine... but when I try to build any project like the 
HelloWorld example or Leds, and then link with the build-created 
libraries... the link fails miserably.  I solved this by tacking on 
-L-lphobos (which is already included on the command line from dmd.conf, 
so I shouldn't have to do this);  when I do that, it cleans up all link 
errors and builds the projects and links with the libs.  Unfortunately 
the programs don't run.  They immediately segfault.

So the only way to use build successfully (sadly) with DUI is to avoid 
creating a library.  Let build do what it does best and collect the 
necessary objects from DUI, itself.  I don't like that it doesn't work, 
but I'm at a loss to figure out why. I think this is the same problem I 
was having before, though.  At the very least, I know it's not DUI's 
fault, since it does build and run fine with the other method.

-JJR
Sep 13 2005
next sibling parent Ant <duitoolkit yahoo.ca> writes:
John Reimer wrote:

 Ant wrote:

 John Reimer wrote:


 I'll start testing 




 don't bother.
 I messed up something and now it won't compile on Linux.
 it was working on windows.

 Ant


 
 [...]  At the very least, I know it's not DUI's
 fault, since it does build and run fine with the other method.
 


got a workaround:
moved the template aliases to the module where the templates are declared.

tomorrow I'll try to update the sourceforge pages.

Ant
Sep 13 2005
prev sibling next sibling parent reply =?ISO-8859-1?Q?Jari-Matti_M=E4kel=E4?= <jmjmak invalid_utu.fi> writes:
John Reimer wrote:

 Ant wrote:
 

 John Reimer wrote:


 I'll start testing 





 don't bother.
 I messed up something and now it won't compile on Linux.
 it was working on windows.

 Ant


 
 
 Strange.  I got it compiling on linux with the build utility just last 
 night.  It builds leds too.  Leds will run without a segfault.  Yet I 
 can only build everything properly if I use build to build all objects 
 at once, that is by letting build collect and compile all required 
 source files for DUI and leds.
 
 Where I have complete failure is where I try to use build to create libs 
 for libdool.a, libdui.a, and libdantfw.a separately.  It creates the 
 libraries just fine... but when I try to build any project like the 
 HelloWorld example or Leds, and then link with the build-created 
 libraries... the link fails miserably.  I solved this by tacking on 
 -L-lphobos (which is already included on the command line from dmd.conf, 
 so I shouldn't have to do this);  when I do that, it cleans up all link 
 errors and builds the projects and links with the libs.  Unfortunately 
 the programs don't run.  They immediately segfault.
 
 So the only way to use build successfully (sadly) with DUI is to avoid 
 creating a library.  Let build do what it does best and collect the 
 necessary objects from DUI, itself.  I don't like that it doesn't work, 
 but I'm at a loss to figure out why. I think this is the same problem I 
 was having before, though.  At the very least, I know it's not DUI's 
 fault, since it does build and run fine with the other method.
 
 -JJR


I tried to use the sourceforge version a few months ago. There was some 
linking issues, but eventually I got it working. BTW, how is it possible 
that DUI links properly only when the compiler include-paths are set in 
a specific order.
Sep 13 2005
parent reply John Reimer <terminal.node gmail.com> writes:
Jari-Matti Mäkelä wrote:


 
 
 I tried to use the sourceforge version a few months ago. There was some 
 linking issues, but eventually I got it working. BTW, how is it possible 
 that DUI links properly only when the compiler include-paths are set in 
 a specific order.


Were you using the dyndui version of dui?  Were you using build?  If it 
was a few months ago, you may have been using a version that did work. 
Now I can't seem to get it to work as I described.

What do you mean about the include-path order?  Is that what you were 
doing to get it working?  That would be strange;  I can't see how 
include-path order on the command line would have any effect on success 
or failure. Library order, on the other hand...

-JJR
Sep 14 2005
parent reply =?ISO-8859-1?Q?Jari-Matti_M=E4kel=E4?= <jmjmak invalid_utu.fi> writes:
John Reimer wrote:

 Jari-Matti Mäkelä wrote:
 

 I tried to use the sourceforge version a few months ago. There was 
 some linking issues, but eventually I got it working. BTW, how is it 
 possible that DUI links properly only when the compiler include-paths 
 are set in a specific order.


 
 
 Were you using the dyndui version of dui?  Were you using build?  If it 
 was a few months ago, you may have been using a version that did work. 
 Now I can't seem to get it to work as I described.
 
 What do you mean about the include-path order?  Is that what you were 
 doing to get it working?  That would be strange;  I can't see how 
 include-path order on the command line would have any effect on success 
 or failure. Library order, on the other hand...
 
 -JJR


I tried the old sourceforge version on Linux. I didn't use Build so I 
needed to modify the include path order manually in the makefile. I 
haven't used DUI for a while, but if a new "stable" version is coming, 
it might be worth testing. Does it already support GTK+ 2.8?
Sep 14 2005
parent Ant <Ant_member pathlink.com> writes:
In article <dg9tun$1tj6$1 digitaldaemon.com>,
=?ISO-8859-1?Q?Jari-Matti_M=E4kel=E4?= says...

I tried the old sourceforge version on Linux. I didn't use Build so I 
needed to modify the include path order manually in the makefile. I 
haven't used DUI for a while, but if a new "stable" version is coming, 
it might be worth testing. Does it already support GTK+ 2.8?


stable :)

I do run leds for days (on linux) with no problems,
but DUI is still a work in progress.

There are improvements but DUI is basically at 2.4 + comboBox and fileChooser
from 2.6.
GTK+ 2.8 works fine but 2.8 features don't have a binding/wrap on DUI.

DUI on linux is still better than on window.
Meanwhile GTK+ for windows is much better than a year ago,
one can notice it immidiatly on the DUITests.

I'll try to update the sourceforce pages
(well, I'm taking work home today... :( )

Ant
Sep 14 2005
prev sibling parent reply Ant <duitoolkit yahoo.ca> writes:
John Reimer wrote:

 Ant wrote:

 John Reimer wrote:


 I'll start testing 




 don't bother.
 I messed up something and now it won't compile on Linux.
 it was working on windows.

 Ant


 
 Strange.  I got it compiling on linux with the build utility just last 
 night.  It builds leds too.  Leds will run without a segfault.


Is this linux?

can you turn on the outline, open a source file,
go to the outline browser and back to the project browser?
that will segfault leds for me on linux.

(color bug workaround - after turning on the outline the window
background will became black:
go to Edit/preferences/D/Editor/Color to reset the background)


Ant
Sep 16 2005
parent John Reimer <brk_6502 yahoo.com> writes:
Ant wrote:

 John Reimer wrote:
 

 Ant wrote:


 John Reimer wrote:


 I'll start testing 





 don't bother.
 I messed up something and now it won't compile on Linux.
 it was working on windows.

 Ant



 Strange.  I got it compiling on linux with the build utility just last 
 night.  It builds leds too.  Leds will run without a segfault.


 
 
 Is this linux?
 
 can you turn on the outline, open a source file,
 go to the outline browser and back to the project browser?
 that will segfault leds for me on linux.
 
 (color bug workaround - after turning on the outline the window
 background will became black:
 go to Edit/preferences/D/Editor/Color to reset the background)
 
 
 Ant


Yes... window was going ugly black. :-(

Didn't get it to segfault, though.  I'll try what you were doing and 
see.  I imagine you are right, though. :-p

-JJR
Sep 16 2005
prev sibling parent John Reimer <terminal.node gmail.com> writes:
bobef wrote:

 Ant wrote:
 

 for the latests DUI version grab the dsource svn repositories
 for DUI use  http://svn.dsource.org/projects/dui/trunk/dyndui
 not the main trunk.
 (don't forget dool, DUI depends on dool)


 
 It would be nice if you update dui.sourceforge.net with the latest 
 bugfixes etc. Me personaly don't like dsource very much because it does 
 not contain (almost) any information about the projects. In other words 
 it would be nice to provide some more info. Maybe the GTK version of dui?


You're right. Such information should be added.  Like Ant said, it's 
been tested with the most recent versions 2.6+ on both linux and 
windows.  I realize also that there's not much documentation for the 
dynamic gtk loader.  That might be useful since other projects may like 
to make use of the tool from it.

The gtk loader is easy enough to update for new versions of gtk as well.

-JJR
Sep 12 2005