GUI libraries

[Chris]

On Friday, 29 November 2013 at 13:31:34 UTC, Jacob Carlborg wrote:
> On 2013-11-28 21:54, Xavier Bigand wrote:
>
>> Yep, that the goal, having applications with a real 
>> personality. I don't
>> think it's an issue especially when application is full screen 
>> and
>> respect pictographs (icons and texts) standards,...
>
> "real personality", it's more of trying to emulate the native 
> toolkit to fails.
>
>> Having custom UI can help applications to improve ergonomic 
>> with
>> dedicated behaviors when it's needed.
>>
>> D itself isn't limited to one policy, you can do objects or 
>> not,... the
>> only things that is important is to let a strong default 
>> couple of style
>> and ergonomic without adding complexity for users want do some 
>> custom
>> stuff.
>>
>>
>> What is native on windows ?
>>  - Win32
>>  - Winforms
>>  - Qt Widgets (that is near Win32)?
>>
>> And on linux ?
>>  - GTK (with gnome and KDE)
>>  - Qt QML (KDE future)
>>
>> A native UI isn't necessary considered as the standard one, 
>> maybe Qt
>> have a chance to be a real standard (on many platforms).
>
> There's one thing in creating a completely new GUI, like games 
> do, and a completely different thing in trying to emulate a 
> native toolkit and fail. The above video is an example of the 
> latter.

It's not about emulating. It's about innovating. And as for the 
features of OSes, say the Preferences dialog on OS X, you could 
always interface to that, and only that. As platforms are 
becoming more diverse (Android, Ubuntu, OS X, Windows, Blackberry 
and whatnot) companies and programmers want a 
write-once-run-everywhere toolkit more than ever. Look at Gtk, 
Textadept even delivers the libraries on OS X. Self-catering is 
becoming more and more important as different OSes are being used.