January 12, 2017
On Wednesday, 11 January 2017 at 15:56:46 UTC, Chris Wright wrote:
> On Wed, 11 Jan 2017 07:21:22 +0000, thedeemon wrote:
>> If you need some GUI, DLangUI is just a "dub build" away.
>
> How does DLangUI do with screen readers and magnifiers?

Very poorly, I guess. It does not use native controls and I don't remember seeing any special support for accessibility there.

It's not necessarily tied to OpenGL, when compiled with proper flags it does not use OpenGL at all and relies on WinAPI or SDL, there are different backends available, including even text mode. For example, I'm shipping a Windows product where DLangUI is used with WinAPI backend, so no OpenGL libraries or drivers need to be shipped or installed in the user's system.


January 12, 2017
On Wednesday, 11 January 2017 at 15:33:36 UTC, Sai wrote:
> On Wednesday, 11 January 2017 at 09:17:45 UTC, aberba wrote:
>> On Wednesday, 11 January 2017 at 07:21:22 UTC, thedeemon wrote:
>>> On Monday, 9 January 2017 at 21:41:37 UTC, aberba wrote:
>>>> [...]
>>>
>>> No drag, DLangUI is quite fine and usable (and already being used in industry).
>>> Or are you talking about including it into Phobos? That's not the best idea, it would make Phobos unnecessary fat and involve some dependencies complicating things, besides there is never a consensus regarding a GUI library, trying to include any GUI library is a recipe for eternal flamewar about all the different aspects of what GUI library should be and do.
>>> If you need some GUI, DLangUI is just a "dub build" away.
>>
>> I'm worried about it not becoming abandoned.
>
> I guess this is a risk with any free SW, the risk of it getting abandoned. Unless someone is willing to pay money for support contracts, which is not possible for hobbyists like me. Nor can I support it myself as I am not an expert in that field.
>
> After suffering from this couple of times, I now tend to prefer SW from big corporations which hopefully will be supported for few years or SW from communities which are large enough to pick things up when things are abandoned.
>
> Didn't mean to offend anyone, just thinking out loud.

D Foundation could help ensure the project keeps running by providing some kind of recognition and backing.

After all, when someone wants a cross platform D GUI library, the ONLY current usable choice is DLangUI.

Is there any technical or legal issues to this? We could go with it now or wait till nothing comes. Every modern/mainstream/widely used software has some kin of GUI frontend.
January 12, 2017
On Thursday, 12 January 2017 at 07:24:43 UTC, aberba wrote:
> On Wednesday, 11 January 2017 at 15:33:36 UTC, Sai wrote:

> After all, when someone wants a cross platform D GUI library, the ONLY current usable choice is DLangUI.
>

I disagree. There is no need for a pure D GUI library. It is a lot of work for little value and we'd be better off with improved C++ interop first.

I have several cross platform projects in industry now running on GtkD. It works out of the box on Linux and was trivial to get going on Windows and Mac. It is built on a stable base and has a D api that is easy to use.

GtkD could use some more hands to really improve the D experience so I'd argue that project would be better suited to immediate D foundation support (after C++ interop of course).

bye,
lobo
January 12, 2017
On Thursday, 12 January 2017 at 07:43:18 UTC, lobo wrote:
> On Thursday, 12 January 2017 at 07:24:43 UTC, aberba wrote:
>> On Wednesday, 11 January 2017 at 15:33:36 UTC, Sai wrote:
>
>> After all, when someone wants a cross platform D GUI library, the ONLY current usable choice is DLangUI.
>>
>
> I disagree. There is no need for a pure D GUI library. It is a lot of work for little value and we'd be better off with improved C++ interop first.
>
> I have several cross platform projects in industry now running on GtkD. It works out of the box on Linux and was trivial to get going on Windows and Mac. It is built on a stable base and has a D api that is easy to use.
>
> GtkD could use some more hands to really improve the D experience so I'd argue that project would be better suited to immediate D foundation support (after C++ interop of course).
>
> bye,
> lobo

Gtk doesn't focus much in cross platform support. Its written in C so no c++.

DlangUI is Pure D so future prof when gtk makes hard decisions. DlangUI is the closest you can get ATM. Its architecture is quite powerful and flexible with multiple backends. Its will work on Android. Plus its ready.

It could use more hands on deck to improve.
January 13, 2017
On Wednesday, 11 January 2017 at 15:56:46 UTC, Chris Wright wrote:
> On Wed, 11 Jan 2017 07:21:22 +0000, thedeemon wrote:
>> If you need some GUI, DLangUI is just a "dub build" away.
>
> How does DLangUI do with screen readers and magnifiers?
>
> From what I'm seeing, neither GTK+ nor Qt work with screen readers anad other assistive technologies. wxWidgets has some accessibility bugs (wxGrid is invisible to screen readers). DLangUI uses OpenGL, so it's less likely to support screen magnifiers (and equally unlikely to support screen readers).

Checked magnifier under Windows. Works ok for DlangUI apps built with OpenGL support as well as software renderer (configuration="minimal").
If OpenGL is stopper for magnifier on other platforms, it's possible to try minimal configuration.

Currently DlangUI does not support screen readers.
I'm not sure what is API to support screen readers.
If there should be ability to get control text from window by X,Y - it can be added easy.

January 13, 2017
On 13/01/2017 9:04 PM, Vadim Lopatin wrote:
> On Wednesday, 11 January 2017 at 15:56:46 UTC, Chris Wright wrote:
>> On Wed, 11 Jan 2017 07:21:22 +0000, thedeemon wrote:
>>> If you need some GUI, DLangUI is just a "dub build" away.
>>
>> How does DLangUI do with screen readers and magnifiers?
>>
>> From what I'm seeing, neither GTK+ nor Qt work with screen readers
>> anad other assistive technologies. wxWidgets has some accessibility
>> bugs (wxGrid is invisible to screen readers). DLangUI uses OpenGL, so
>> it's less likely to support screen magnifiers (and equally unlikely to
>> support screen readers).
>
> Checked magnifier under Windows. Works ok for DlangUI apps built with
> OpenGL support as well as software renderer (configuration="minimal").
> If OpenGL is stopper for magnifier on other platforms, it's possible to
> try minimal configuration.
>
> Currently DlangUI does not support screen readers.
> I'm not sure what is API to support screen readers.
> If there should be ability to get control text from window by X,Y - it
> can be added easy.

A bit older reference for Win32[0].
But this means COM.

[0] https://msdn.microsoft.com/en-us/windows/desktop/gg712214.aspx

January 13, 2017
On Wednesday, 11 January 2017 at 15:56:46 UTC, Chris Wright wrote:
> On Wed, 11 Jan 2017 07:21:22 +0000, thedeemon wrote:
>> If you need some GUI, DLangUI is just a "dub build" away.
>
> How does DLangUI do with screen readers and magnifiers?
>
> From what I'm seeing, neither GTK+ nor Qt work with screen readers anad other assistive technologies. wxWidgets has some accessibility bugs (wxGrid is invisible to screen readers). DLangUI uses OpenGL, so it's less likely to support screen magnifiers (and equally unlikely to support screen readers).

GTK3 on Linux works with Orca the screen reader and other assistive technologies including a magnifier.

https://opensource.com/life/15/5/accessibility-linux
January 13, 2017
On Thursday, 12 January 2017 at 07:24:43 UTC, aberba wrote:
> After all, when someone wants a cross platform D GUI library, the ONLY current usable choice is DLangUI.
>

Arsd-official:simpledisplay is also natively D and cross-platform, plus it's native and VERY simple to use. Does not work on as many platforms as DlangUI, trough. It should really be added to that wiki listing of graphical frameworks.


January 13, 2017
On Friday, 13 January 2017 at 20:11:08 UTC, Dukc wrote:
> Arsd-official:simpledisplay is also natively D and cross-platform, plus it's native and VERY simple to use. Does not work on as many platforms as DlangUI, trough. It should really be added to that wiki listing of graphical frameworks.

Oops, just realized you said GUI library, not a graphics library. Arsd has a GUI interfacce too but it is, I think, Windows only.


January 13, 2017
On Friday, 13 January 2017 at 20:16:02 UTC, Dukc wrote:
> Oops, just realized you said GUI library, not a graphics library. Arsd has a GUI interfacce too but it is, I think, Windows only.

Well, it has some support for Linux too, but it is a custom job there and not complete. (I write things as I need them, and since I do more simple games or web stuff, the nicer gui widgets are low on my todo list.)