May 04, 2014
Le 04/05/2014 11:21, "Marc Schütz" <schuetzm@gmx.net>" a écrit :
> A "meta" question, not related to your specific implementation:
>
> While Qt is certainly the most powerful and comprehensive portable GUI
> framework, it also contains lots of code that's not related to user
> interfaces: strings, multi-threading support, file abstractions,
> containers, databases interfaces, etc. In short: Things which properly
> should be part of the standard library, but aren't (widely) available,
> or not working well enough in C++.
>
> Now, Qt depends on those, and if you want to interact with it, you need
> to use them in your own code. Doesn't that cause a lot of friction? Just
> as a random example, QListView can take its elements from a data source
> ("model"). But in D, that data source might be idiomatically implemented
> as a range, so it has to be adapted first. Or, a more frequent thing:
> char[] vs. QString.
>
> Could it be a better strategy to only re-use low-level functionality of
> Qt internally, but provide more idiomatic public D interfaces for it?

With a friend we created the DQuick project cause of our major interest of the QtQuick (also called QML) part of Qt framework and also for the reason you invoke. For us phobos already aim to implement same things than QtCore, and wrapping primitive types of Qt seems hard and will introduce design constraint and poor performances. It's certainly bad for a longterm vision.

IMO DQt will be interesting for those looking for a stable GUI library based on widget essentially.
DQuick have no chance to be usable in production before years if we continue to develop it.
We are back after a long break, it's really hard to stay motivated cause we have some difficulties with points aren't fixed in D, mainly GC issues, signals,... My friend just find get the property binding working in D code, but he doesn't like his code :-).

I see DQt/gtkD and DQuick as complementary projects. I hope we will capable to provide good enough GUI libraries to D community shortly.
May 04, 2014
On Sunday, 4 May 2014 at 13:32:13 UTC, Xavier Bigand wrote:
> With a friend we created the DQuick project cause of our major interest of the QtQuick (also called QML) part of Qt framework and also for the reason you invoke. For us phobos already aim to implement same things than QtCore, and wrapping primitive types of Qt seems hard and will introduce design constraint and poor performances. It's certainly bad for a longterm vision.
>
> IMO DQt will be interesting for those looking for a stable GUI library based on widget essentially.
> DQuick have no chance to be usable in production before years if we continue to develop it.
> We are back after a long break, it's really hard to stay motivated cause we have some difficulties with points aren't fixed in D, mainly GC issues, signals,... My friend just find get the property binding working in D code, but he doesn't like his code :-).
>
> I see DQt/gtkD and DQuick as complementary projects. I hope we will capable to provide good enough GUI libraries to D community shortly.

Best of luck to you guys. I encourage as many people as possible to give writing D GUI libraries a go, and perhaps we can all learn from each other.
May 04, 2014
On Sunday, 4 May 2014 at 14:09:38 UTC, w0rp wrote:
> Best of luck to you guys. I encourage as many people as possible to give writing D GUI libraries a go, and perhaps we can all learn from each other.

Done ;)

http://forum.dlang.org/thread/wdddgiowaidcojbrklsg@forum.dlang.org
May 04, 2014
On 5/4/14, 9:19 AM, Gary Willoughby wrote:
> On Sunday, 4 May 2014 at 14:09:38 UTC, w0rp wrote:
>> Best of luck to you guys. I encourage as many people as possible to
>> give writing D GUI libraries a go, and perhaps we can all learn from
>> each other.
>
> Done ;)
>
> http://forum.dlang.org/thread/wdddgiowaidcojbrklsg@forum.dlang.org

Worth a reddit announcement tomorrow morning? -- Andrei
May 04, 2014
On Sunday, 4 May 2014 at 16:19:32 UTC, Gary Willoughby wrote:
> On Sunday, 4 May 2014 at 14:09:38 UTC, w0rp wrote:
>> Best of luck to you guys. I encourage as many people as possible to give writing D GUI libraries a go, and perhaps we can all learn from each other.
>
> Done ;)
>
> http://forum.dlang.org/thread/wdddgiowaidcojbrklsg@forum.dlang.org

I just read your announcement and this is very good.
May 04, 2014
Le 04/05/2014 18:19, Gary Willoughby a écrit :
> On Sunday, 4 May 2014 at 14:09:38 UTC, w0rp wrote:
>> Best of luck to you guys. I encourage as many people as possible to
>> give writing D GUI libraries a go, and perhaps we can all learn from
>> each other.
>
> Done ;)
>
> http://forum.dlang.org/thread/wdddgiowaidcojbrklsg@forum.dlang.org

It's a great news.

May 05, 2014
>> http://forum.dlang.org/thread/wdddgiowaidcojbrklsg@forum.dlang.org
>
> Worth a reddit announcement tomorrow morning? -- Andrei

TkD is nice,but the exe's Memory usage is 6.8~7M,but DFL's only 2.8~3M,and only a single file on windows 7.

https://github.com/Rayerd/dfl,
https://github.com/FrankLIKE/dfl
May 05, 2014
On 2014-05-04 09:26, w0rp wrote:
>
> Qt 4 support basically arises from what is easy to do right now.
> Supporting Qt 5 doesn't seem that far off. I went with Qt 4 for now
> because it's easier, and at this stage it's more important to work with
> something that can actually work and learn from that, than to try and
> work with something which might not actually work at all.

Nice work, I think Qt 4 is a very nice start and can help bring a lot more interest in D from the C++ crowd if it's successfully implemented, I think these people worry mostly about using the same data types and interface in a new programming language.
May 06, 2014
On 2014-05-05 7:00 PM, FrankLike wrote:
>
>>> http://forum.dlang.org/thread/wdddgiowaidcojbrklsg@forum.dlang.org
>>
>> Worth a reddit announcement tomorrow morning? -- Andrei
>
> TkD is nice,but the exe's Memory usage is 6.8~7M,but DFL's only
> 2.8~3M,and only a single file on windows 7.
>
> https://github.com/Rayerd/dfl,
> https://github.com/FrankLIKE/dfl

I've just started using tkd and the memory usage is 3.4MB on windows for a Hello World.

It requires a lot of tcl/tk source files (900 files) and 2 dlls, but I think a workaround can be found for them to be packed in an in-place unpacker app by compiling on top of it (I'm looking into this right now). It would be good to have an application that know what to trim out too. The zipped size of a tkd application is 3 MB.

It's very simple to use, it implements a lot of the D idioms and, most of all, it's stable. I appreciate the effort very much!
May 07, 2014
On 07/05/14 01:05, Etienne wrote:

> I've just started using tkd and the memory usage is 3.4MB on windows for
> a Hello World.
>
> It requires a lot of tcl/tk source files (900 files) and 2 dlls, but I
> think a workaround can be found for them to be packed in an in-place
> unpacker app by compiling on top of it (I'm looking into this right
> now). It would be good to have an application that know what to trim out
> too. The zipped size of a tkd application is 3 MB.
>
> It's very simple to use, it implements a lot of the D idioms and, most
> of all, it's stable. I appreciate the effort very much!

Have you tried DWT [1]? It has no dependencies except for the system libraries. Although, it will generate quite large binaries. But I don't think they'll grow that much when adding new functionality.

[1] https://github.com/d-widget-toolkit/dwt

-- 
/Jacob Carlborg