[haiku-3rdparty-dev] Re: Development context
- From: pete.goodeve@xxxxxxxxxxxx
- To: haiku-3rdparty-dev@xxxxxxxxxxxxx
- Date: Mon, 12 Nov 2018 23:51:31 -0800
On Mon, Nov 12, 2018 at 06:51:43PM -0700, Leonard Sitongia wrote:
I'd like to get a better idea of the big picture of developing apps for
Haiku. I've looked over documentation, and I don't know the answer to the
following questions. Can you help me, please?
Others will be able to give more complete answers, but in the meantime...
What is the relationship between Haiku and Qt? Is Qt the
recommended/required graphical toolkit?
Qt has been ported to run in Haiku, but is *not* native. Haiku has its own GUI
which one would normally use if writing a new app -- or even porting one that
doesn't already depend on Qt.
What's the relation to KDE? I see HaikuDepot has a lot of KDE apps (and
has/uses the latest Qt). Is it a good idea to develop KDE apps to run on
Haiku?
KDE is basically Linux, and is related directly to neither Haihu nor Qt.
I didn't know there were any 'KDE' apps on Haiku. Someone else will have
to explain the relation.
What's the relation to FreeBSD? I've seen a compatibility library
mentioned. Is that still the case? Does this apply to device drivers on up
to application?
Again, FreeBSD and Haiku are quite separate entities, but it turns out that
the standard FreeBSD Driver API can be ported over to Haiku fairly easily
(There's an interface layer for that, I believe.) As FreeBSD has a lot more
resources to develop drivers, this has been very useful.
HTH
-- Pete --
Other related posts:
