"Gour D." <gour@atmarama.net> wrote in message news:20101007055846.597a5b6e@atmarama.noip.me...
>Although I'm still hankering to see QtD, I'm just curious (not having
>experience with) how does SWT (DWT) can compare in regards?

SWT/DWT uses the native GUI, at least on windows. I have no idea what it uses on Linux, my guess would be GTK-only, but that's only a guess. But I think DWT is D1-only right now (so is wxD).

On Wednesday 06 October 2010 22:00:02 Nick Sabalausky wrote:
> "Gour D." <gour@atmarama.net> wrote in message news:20101007055846.597a5b6e@atmarama.noip.me...
> 
> >Although I'm still hankering to see QtD, I'm just curious (not having
> >experience with) how does SWT (DWT) can compare in regards?
> 
> SWT/DWT uses the native GUI, at least on windows. I have no idea what it uses on Linux, my guess would be GTK-only, but that's only a guess. But I think DWT is D1-only right now (so is wxD).

SWT uses GTK on Linux (unfortunately), so presumably DWT does as well. It's what Eclipse uses. However, I do believe that you're right and that it's currently only D1 compatible.

On 2010-10-07 07:00, Nick Sabalausky wrote:
> "Gour D."<gour@atmarama.net>  wrote in message
> news:20101007055846.597a5b6e@atmarama.noip.me...
>> Although I'm still hankering to see QtD, I'm just curious (not having
>> experience with) how does SWT (DWT) can compare in regards?
>
> SWT/DWT uses the native GUI, at least on windows. I have no idea what it
> uses on Linux, my guess would be GTK-only, but that's only a guess. But I
> think DWT is D1-only right now (so is wxD).

It uses native controls on all supported platforms. If there isn't a native control available it will emulate it. On Linux GTK and Motif is supported, I think they're working on a Qt port as well.

-- 
/Jacob Carlborg

On 2010-10-07 00:26, Robert Clipsham wrote:
> On 06/10/10 23:03, Nick Sabalausky wrote:
>>> Ok, for me GTK is native because I use Linux and a GTK based desktop.
>>> I know that there's a native GTK port for OSX/Quartz and I thought
>>> GTK had
>>> themes to look native on Windows?
>>>
>>
>> It does make a vague attempt to look native on Windows, and is FAR
>> better in
>> that regard than, say, Swing, Winamp, Iron/Chrome, or pretty much
>> anything
>> from Apple. But there's still rather noticable differences in both
>> look (the
>> chunkiness I mentioned, just as one example) and in feel (particulary if
>> you're using GIMP). It's kinda like gluing a picture of some wings
>> overtop
>> the logo on a Ferrari and saying "See, it's an Aston Martin!"
>
> Platform wise, GTK looks appalling on OS X, acceptable, if non-native on
> Windows (I think there's a GTK theme that fixes this, not sure), and,
> well, you use it on linux. As for Qt, it uses the native GUI for all the
> platforms it works on (and if you don't like that there's a config tool
> to make it look as ugly as you like :)).

I haven't seen any native looking Qt application on Mac.

>  From a developers standpoint, GTK is a lot more awkward to work with
> (whether you're using the C interface or the GtkD wrapper), and is
> generally not as nice to work with (based on a few hundred lines of code
> that did very little, I switched to Qt at that point). Qt on the other
> hand I've found a pleasure to work with from day 1, everything seems to
> work as expected, and typically needs far less code.
>


-- 
/Jacob Carlborg

On 2010-10-07 08:37, Jonathan M Davis wrote:
> On Wednesday 06 October 2010 22:00:02 Nick Sabalausky wrote:
>> "Gour D."<gour@atmarama.net>  wrote in message
>> news:20101007055846.597a5b6e@atmarama.noip.me...
>>
>>> Although I'm still hankering to see QtD, I'm just curious (not having
>>> experience with) how does SWT (DWT) can compare in regards?
>>
>> SWT/DWT uses the native GUI, at least on windows. I have no idea what it
>> uses on Linux, my guess would be GTK-only, but that's only a guess. But I
>> think DWT is D1-only right now (so is wxD).
>
> SWT uses GTK on Linux (unfortunately), so presumably DWT does as well. It's what
> Eclipse uses. However, I do believe that you're right and that it's currently
> only D1 compatible.

Correct, though I think they're working on Qt port. I'll try to do my best to make DWT work with D2.

-- 
/Jacob Carlborg

On 07/10/10 00:28, Nick Sabalausky wrote:
> Unless you're a KDE (or Xfce) user. Which actually brings up another thing:
> It's my understanding that wxWidgets can use other things than just GTK on
> Linux. And AIUI, Qt and KDE are tied togther in the same way as GTK and
> GNOME, so does that mean Qt won't use GTK for Linux users running GNOME?

Dunno about GTK, you can set Qt to use your GTK theme though, thus keeping your theme in sync across both Qt and GTK apps.

-- 
Robert
http://octarineparrot.com/

On 07/10/10 09:46, Jacob Carlborg wrote:
> I haven't seen any native looking Qt application on Mac.

When did you last use a Qt application on a Mac? The cocoa backend for OS X is fairly new - Qt apps I've written look native on a Mac (admittedly the spacing's a bit off in places, that's not a huge issue though).

-- 
Robert
http://octarineparrot.com/

On 10/6/10, Nick Sabalausky <a@a.a> wrote:
> "sybrandy" <sybrandy@gmail.com> wrote in message news:i8g8oi$1hv6$1@digitalmars.com...
>> Just asking out of curiosity.  With all the great language features, I'm sure that many of you have thought about this.
>>
>> For me, I figured a good start would be your basic Unix/Linux/BSD utilities, like cat and grep.  I figure it may make the code easier to read and maintain as well as potentially improve the quality of the software.  Of course, most of these are so old they're probably quite bug free, but some probably could use a rewrite.  Some may even benefit for threading.
>>
>
> Not that I would want to do it myself, but I'd like to see LLMV and Scintilla moved to D.
>
> But really, just about anything in C/C++ that I might ever want to modify. If I never have to touch another line of C/C++ it'll be too soon.
>
>
>

FYI, there's a DFL Scintilla component you can use in D2, which is downloaded separately from DFL. I've made a small update to it in the DFL forums although you would also need to add one more method in the scintilla class to get messages back from Scintilla itself (I'll  post an update to the DFL forums some time later for that).

So basically the DFL component loads the scintilla DLL, and you can use message passing or optionally get a function pointer for direct access. It's really easy to use the editor from D in this way. In fact, you can port *Scite* source code to a D equivalent that uses the Scintilla DLL with ease. It only took me a minute to port the automatic indentation functionality from Scite to a fresh project that uses the DFLs Scintilla class.

I wouldn't know if there are any bottlenecks in the Scintilla codebase, so I can't judge if it's worth porting to D. But it already works and you can use it from D already, so why go through all the trouble of rewriting it? :-)

An operating system written in D would be really interesting.

On Thu, Oct 14, 2010 at 11:05 AM, Andrej Mitrovic < andrej.mitrovich@gmail.com> wrote:

> On 10/6/10, Nick Sabalausky <a@a.a> wrote:
> > "sybrandy" <sybrandy@gmail.com> wrote in message news:i8g8oi$1hv6$1@digitalmars.com...
> >> Just asking out of curiosity.  With all the great language features, I'm sure that many of you have thought about this.
> >>
> >> For me, I figured a good start would be your basic Unix/Linux/BSD utilities, like cat and grep.  I figure it may make the code easier to read and maintain as well as potentially improve the quality of the software.  Of course, most of these are so old they're probably quite
> bug
> >> free, but some probably could use a rewrite.  Some may even benefit for threading.
> >>
> >
> > Not that I would want to do it myself, but I'd like to see LLMV and Scintilla moved to D.
> >
> > But really, just about anything in C/C++ that I might ever want to
> modify.
> > If I never have to touch another line of C/C++ it'll be too soon.
> >
> >
> >
>
> FYI, there's a DFL Scintilla component you can use in D2, which is downloaded separately from DFL. I've made a small update to it in the DFL forums although you would also need to add one more method in the scintilla class to get messages back from Scintilla itself (I'll  post an update to the DFL forums some time later for that).
>
> So basically the DFL component loads the scintilla DLL, and you can use message passing or optionally get a function pointer for direct access. It's really easy to use the editor from D in this way. In fact, you can port *Scite* source code to a D equivalent that uses the Scintilla DLL with ease. It only took me a minute to port the automatic indentation functionality from Scite to a fresh project that uses the DFLs Scintilla class.
>
> I wouldn't know if there are any bottlenecks in the Scintilla codebase, so I can't judge if it's worth porting to D. But it already works and you can use it from D already, so why go through all the trouble of rewriting it? :-)
>

On Thu, 14 Oct 2010 21:32:44 +0400, Michael Stover <michael.r.stover@gmail.com> wrote:

> An operating system written in D would be really interesting.

http://wiki.xomb.org/index.php?title=Main_Page