Complete.Org: Mailing Lists: Archives: freeciv-dev: April 2004:
[Freeciv-Dev] Re: Failing to link with a QPE client -- any hints?
Home

[Freeciv-Dev] Re: Failing to link with a QPE client -- any hints?

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Failing to link with a QPE client -- any hints?
From: Frederic Briere <fbriere@xxxxxxxxxxx>
Date: Tue, 20 Apr 2004 23:04:56 -0400

On Tue, Apr 20, 2004 at 07:33:55PM +0200, Raimar Falke wrote:
> How large is the difference between Qt/Embedded and classic Qt?

From which point of view?  To the programmer, they share the same API;
although it's common to leave some bloat out of Qt/E, so you obviously
can't use any compiled-out functions.  Aside from that, any Qt app
should be compilable under Qt/E (and vice-versa), although many of them
would be unusable at the low resolution of the Zaurus SL-5x00.

(Obviously, under the hood, they're two different beasts.)

So, if you're asking whether a Qt/E port would immediately lead to a Qt
port, I would say no.  Rob's goal was not only to port to Qt, but to
redesign the interface for the Zaurus (240x320, mouse-only if possible,
no middle/right-click).  Such a client would be a great thing for the
Zaurus (and the iPaq, I imagine) but would suck on a destop.

Which is not to say that some significant chunks of code couldn't be
reused from one to the other.  But it wouldn't be trivial either.

Assuming that was the intent of your question. :)

> > Both Qtopia and OPIE are GPL.
> 
> And Qt/Embedded?

Yes, that too.


-- 
             Frederic Briere    <*>    fbriere@xxxxxxxxxxx

 =>  <fbriere@xxxxxxxxxx> IS NO MORE:  <http://www.abacomsucks.com>  <=


[Prev in Thread] Current Thread [Next in Thread]