On Thursday, 3 September 2015 at 14:24:29 UTC, Mike James wrote:
>
> Have a look at GtkD and DWT - they are the most complete. I've written small apps using both and they work :-)
> With GtkD you can use the Glade Builder to simplify design of the GUI elements.

Thanks for the reply. A graphical tool to build the GUI might come in handy :) I will remember it, in case I decide to use D. Right now I am on the fence... (I pointed this already out in an other reply to rikki, but I will like wait before using D).

On Thursday, 3 September 2015 at 14:35:44 UTC, Jacob Carlborg wrote:
> On 2015-09-03 14:19, motaito wrote:
>
>> I am looking for a cross platform (Windows, Linux, BSD) solution.
>
> Others have already mentioned DWT. It officially only support Windows and Linux. It might be easy to get it to work on BSD since the platform is similar to Linux, assuming GTK is used.

Thanks for the tip. It's always hard to find out of the box support for BSD. That request was probably a bit of a stretch :)

On Thursday, 3 September 2015 at 15:26:45 UTC, Rikki Cattermole wrote:
> On 04/09/15 3:15 AM, motaito wrote:
>> Anyway, I hope you will be successful with alphaPhobos. I think D needs
>> it, so don't abandon it! I will keep an eye out and check again in about
>> a year or so. But for now I have to rethink whether to use D or not.
>
> Thanks, this is a long term thing. I've been planning this for ~2 years. Previous was Devisualization (Github org of mine). So a bunch of code has actually originated here. Before that DOOGLE. Even some of that came from OOGL (ported it from c++ to D as D_OOGL).
>
>> Out of curiosity, why do you think that I wouldn't want a Phobos
>> solution? Wouldn't an integrated solution be better? I would not have to
>> maintain a build of an external third party project, that may or may not
>> be abandoned in the future, not knowing whether there will be updates,
>> bugfixes or missing features to be added. It seams like quite a bit
>> extra management for my project if I have to keep a third party project
>> up to date and may need to adjust my code due to an update in an
>> external project.
>
> Because, at best case the graphics could be very ugly and lacking of features in a GUI toolkit. We're just too far away from it.
>
> We need to focus on getting the core problems solved. So that people can flourish with building e.g. GUI toolkits unimpeded by what we support. Also helps interop between them.
>
> After we have a decent one, then we can consider it for Phobos.
> I know the current situation is unfortunate. We've had some pretty major changes in the last few years and that is ok. I hope we do get to a point where it is easy to get started in almost any problem domain :)

Again Thanks for the details. It's very much appreciated. From a usability stand point for alphaPhobos. Are you more going into the direction of WPF or QML, using a declaration file or more along the lines of a QWidget, building the GUI through instantiating objects inside a D-module?

On 04/09/15 3:37 AM, motaito wrote:
> On Thursday, 3 September 2015 at 15:26:45 UTC, Rikki Cattermole wrote:
>> On 04/09/15 3:15 AM, motaito wrote:
>>> Anyway, I hope you will be successful with alphaPhobos. I think D needs
>>> it, so don't abandon it! I will keep an eye out and check again in about
>>> a year or so. But for now I have to rethink whether to use D or not.
>>
>> Thanks, this is a long term thing. I've been planning this for ~2
>> years. Previous was Devisualization (Github org of mine). So a bunch
>> of code has actually originated here. Before that DOOGLE. Even some of
>> that came from OOGL (ported it from c++ to D as D_OOGL).
>>
>>> Out of curiosity, why do you think that I wouldn't want a Phobos
>>> solution? Wouldn't an integrated solution be better? I would not have to
>>> maintain a build of an external third party project, that may or may not
>>> be abandoned in the future, not knowing whether there will be updates,
>>> bugfixes or missing features to be added. It seams like quite a bit
>>> extra management for my project if I have to keep a third party project
>>> up to date and may need to adjust my code due to an update in an
>>> external project.
>>
>> Because, at best case the graphics could be very ugly and lacking of
>> features in a GUI toolkit. We're just too far away from it.
>>
>> We need to focus on getting the core problems solved. So that people
>> can flourish with building e.g. GUI toolkits unimpeded by what we
>> support. Also helps interop between them.
>>
>> After we have a decent one, then we can consider it for Phobos.
>> I know the current situation is unfortunate. We've had some pretty
>> major changes in the last few years and that is ok. I hope we do get
>> to a point where it is easy to get started in almost any problem
>> domain :)
>
> Again Thanks for the details. It's very much appreciated. From a
> usability stand point for alphaPhobos. Are you more going into the
> direction of WPF or QML, using a declaration file or more along the
> lines of a QWidget, building the GUI through instantiating objects
> inside a D-module?

Neither, I'm not touching GUI's itself. Only the creation of a window and a context.

GUI's are far too controversial and for good reason. They are next to impossible to do properly. But that is not a popular opinion :p

Here is more or less what I'm planning on supporting: https://github.com/rikkimax/alphaPhobos/blob/master/source/std/experimental/ui/window/defs.d
There is a bunch of optional features you will notice in other files. Such as a menu, notifications and even screenshots.

On Thursday, 3 September 2015 at 15:41:34 UTC, Rikki Cattermole wrote:
> Neither, I'm not touching GUI's itself. Only the creation of a window and a context.
>
> GUI's are far too controversial and for good reason. They are next to impossible to do properly. But that is not a popular opinion :p
>
> Here is more or less what I'm planning on supporting: https://github.com/rikkimax/alphaPhobos/blob/master/source/std/experimental/ui/window/defs.d
> There is a bunch of optional features you will notice in other files. Such as a menu, notifications and even screenshots.

I see, more like a unified groundwork for someone to build a GUI on top. Looks like an interesting project. Good luck with alphaPhobos! It will be interesting to see it move forward.

On Thursday, 3 September 2015 at 16:18:34 UTC, motaito wrote:
> On Thursday, 3 September 2015 at 15:41:34 UTC, Rikki Cattermole wrote:
>> Neither, I'm not touching GUI's itself. Only the creation of a window and a context.
>>
>> GUI's are far too controversial and for good reason. They are next to impossible to do properly. But that is not a popular opinion :p
>>
>> Here is more or less what I'm planning on supporting: https://github.com/rikkimax/alphaPhobos/blob/master/source/std/experimental/ui/window/defs.d
>> There is a bunch of optional features you will notice in other files. Such as a menu, notifications and even screenshots.
>
> I see, more like a unified groundwork for someone to build a GUI on top. Looks like an interesting project. Good luck with alphaPhobos! It will be interesting to see it move forward.

https://github.com/buggins/dlangui is fairly complete and contains DML - DlangUI Markup Language - similar to QML.

On Thursday, 3 September 2015 at 16:31:33 UTC, Zekereth wrote:
> https://github.com/buggins/dlangui is fairly complete and contains DML - DlangUI Markup Language - similar to QML.

+1, came here to mention dlangui. It already works and contains a lot of good stuff, including layout engine and markup language.

On 9/3/2015 5:19 AM, motaito wrote:
> Hi,
>
> I haven't used D before and wanted to take a closer look at it. However,
> there are a few things that keep me from doing so.

I'm in a similar place as you are. While D is better than C++, right now C++ plus JUCE is better for me overall than D plus <whatever GUI lib>. C# plus WPF seems attractive too except that WPF isn't cross platform. Anyway, I still always keep an eye on D.

On Thursday, 3 September 2015 at 16:40:56 UTC, Jim Hewes wrote:
> I'm in a similar place as you are. While D is better than C++, right now C++ plus JUCE is better for me overall than D plus <whatever GUI lib>. C# plus WPF seems attractive too except that WPF isn't cross platform. Anyway, I still always keep an eye on D.

Yeah, it's a shame that the mono framework does not support WPF. I think WPF and MEF are the two most powerful features from .NET (for me anyway, that may be subjective). And working in visual studio is really nice too. I wish there was a cross platform IDE like that. I don't quite like the text editor from eclipse, but I haven't used it in a while. Maybe I need to give it another try.

On Thursday, 3 September 2015 at 16:36:31 UTC, thedeemon wrote:
> On Thursday, 3 September 2015 at 16:31:33 UTC, Zekereth wrote:
>> https://github.com/buggins/dlangui is fairly complete and contains DML - DlangUI Markup Language - similar to QML.
>
> +1, came here to mention dlangui. It already works and contains a lot of good stuff, including layout engine and markup language.

@Zekereth and @thedeemon
I guess I will stick to QT for my current project, but I will build some smaller learning projects in D, to try out various GUI libraries. DlangUI seams promising. I probably will either use DlangUI or GtkD.