Daniel Pitts
1/8/2016 2:03:00 AM
On 1/7/16 12:24 PM, Dmitry A. Kazakov wrote:
> On 2016-01-07 20:37, Daniel Pitts wrote:
>> I use a Mac personally, but if my idea takes off, I'd like to make sure
>> it can be "easily" ported to Windows and Linux with native idioms.
>>
>> It is already going to be a bit of a learning curve for me to build a UI
>> on the Mac, but I think I can do it. In any case, what I'm hoping to do
>> is to build the stuff that isn't UI specific in a common code-base. I'm
>> thinking that C++ might be the language of choice for this common layer,
>> and then provide bindings for Swift and C# when it comes time to make
>> the code portable.
>>
>> I'm actually familiar with C++, but have never done anything with Swift
>> or C#. I have done Java UI programming before, but I don't think
>> that'll suit my purpose here.
>>
>> So, what I'm hoping for is either confirmation that I'm thinking about
>> this correctly, or suggestions on other technology I may be unaware of.
>
> There are basically only two major alternatives: Qt and GTK. GTK has
> plain C interface which makes it possible to use with some more decent
> language than C/C++. Qt is somewhat more difficult to use with a
> languages other than C++. Both have comparable performance and enjoy
> target platform hardware acceleration. GTK deploys native look-and-feel.
> Qt is more distant.
>
> On the other hand GTK maintainers keep on doing almost everything to
> discourage users by introducing incompatibilities with each new version.
> Qt has potential licensing problems. Qt supports a wider set of OSes,
> e.g. VxWorks. Both support Windows, Mac, Linux.
>
I feel like you misunderstood. I'm hoping to create the UI in the
language specific to the platform, but have the UI backed by common
library code written in, say, C++.
I'm not expecting to write-once-run-anywhere the UI portion.