On 18/01/17 05:27, rikki cattermole wrote:
> On 18/01/2017 3:56 AM, Shachar Shemesh wrote:
>> On 17/01/17 15:58, Adam D. Ruppe wrote:
>>> On Tuesday, 17 January 2017 at 13:46:21 UTC, Vadim Lopatin wrote:
>>>> There is a workaround: it's possible to create DlangUI theme which
>>>> looks like native OSX app.
>>>
>>> It usually isn't the theme, it is the little details of user interaction
>>> that the native ones get (though the theme is really hard to get right
>>> too, especially given user color customization, etc.).
>>
>> https://www.wxwidgets.org/docs/faq/osx/
>>
>> Like I said.
>
> Don't look at wxWidgets too closely for how to do windowing correctly.
> They have like 5 event loops for OSX with only one actually ever used.

IIRC, QT also uses native widgets when they are available (i.e. - on anything other than Linux).

Shachar

On 2017-01-18 08:22, Shachar Shemesh wrote:

> IIRC, QT also uses native widgets when they are available (i.e. - on
> anything other than Linux).

"As with Cocoa and Carbon, Qt provides widgets that look like those described in the Human Interface Descriptions. Qt's widgets use HIThemes to implement the look and feel" [1]

Doesn't sound like they're native.

[1] http://doc.qt.io/qt-5/osx-issues.html

-- 
/Jacob Carlborg

On Monday, 16 January 2017 at 07:38:31 UTC, Jacob Carlborg wrote:
> On 2017-01-16 07:28, Vadim Lopatin wrote:
>
>> Windows support in DlangUI is not native since it does not use native
>> controls.
>> DlangUI draws widgets itself on all platforms. But on Win32 it's
>> possible to build app which uses Win32 API only, and no additional DLLs
>> will be required to run it. On Linux and Mac, there is extra dependency
>> - libSDL2.
>
> For most application on macOS, a non-native GUI library is not interesting.

What about Photoshop? Is it native? No.

On 2017-01-18 10:24, aberba wrote:

> What about Photoshop? Is it native? No.

Last time I used it it didn't look very native.

-- 
/Jacob Carlborg

On Wednesday, 18 January 2017 at 17:51:18 UTC, Jacob Carlborg wrote:
> On 2017-01-18 10:24, aberba wrote:
>
>> What about Photoshop? Is it native? No.
>
> Last time I used it it didn't look very native.

So it will be incorrect to say native gui is a requirement to fain higher adoption.

On 19/01/2017 10:00 AM, aberba wrote:
> On Wednesday, 18 January 2017 at 17:51:18 UTC, Jacob Carlborg wrote:
>> On 2017-01-18 10:24, aberba wrote:
>>
>>> What about Photoshop? Is it native? No.
>>
>> Last time I used it it didn't look very native.
>
> So it will be incorrect to say native gui is a requirement to fain
> higher adoption.

Photoshop is one of the oldest programs still in use today commercially.
It has more holes in its licensing then a sieve. I wouldn't look towards it for best practices.

On 2017-01-18 22:00, aberba wrote:

> So it will be incorrect to say native gui is a requirement to fain
> higher adoption.

Of course there will be applications that does not look native but still is popular.

If I'm looking for a new type of application I'll dismiss those that don't look native very quickly. Unless I know beforehand that the application is very good, then I'll give it some more time.

Example, I'm using Eclipse for Scala related coding. Although Eclipse is written using SWT, that uses native drawing, it still looks a bit alien. Non-native tabs, non-native preferences and so on. But I don't know of any other IDE for Scala that looks more native. Also I used Eclipse on other platforms before I used it on macOS.

-- 
/Jacob Carlborg

On Thursday, 19 January 2017 at 07:39:10 UTC, Jacob Carlborg wrote:
> If I'm looking for a new type of application I'll dismiss those that don't look native very quickly. Unless I know beforehand that the application is very good, then I'll give it some more time.

I think it has more to do with looking well-designed for the purpose. 3D and audio editors often use non-native custom UI toolkits. VS Code is also non-native.

But on OSX you have to use the OSX-menu and put extra effort into the design if you use non-native widgets IMO.

Also, make sure it isn't sluggish. Java apps often has that extra GC sluggishness to them, even the polished JetBrains IDEs feel a bit sluggish.

On 01/16/2017 02:39 AM, Jacob Carlborg wrote:
> On 2017-01-09 22:41, aberba wrote:
>> This seemed to be an effort (among others) to bring GUI cross platform
>> to standard D but some language/compiler/Phobos/Deimos/manpower issues
>> were the drag.
>>
>> https://github.com/Devisualization
>>
>>
>> We now have DLangUI.
>>
>> I wonder what the current drag is.
>
>
> There's DWT [1] as well. Works on Windows and Linux, uses native drawing.
>
> [1] https://github.com/d-widget-toolkit/dwt
>

There's also QtE5 https://github.com/MGWL/QtE5

Looks pretty good, from what I can see.

On Wednesday, 18 January 2017 at 09:24:09 UTC, aberba wrote:
> What about Photoshop? Is it native? No.

No, by-and-large Photoshop does not use native controls.

However, I would not hold up Photoshop as validation for not using native controls.

Games have wide latitude for ignoring their platform's native control and rolling their own user interface.

Productivity applications ignore their platform's native controls and native user-interface at their own peril.  Photoshop is an example of a successful program that treads in those dangerous waters.