At 02:24 PM 7/25/2005, you wrote:
I really think that this place isn't the right place for asking your question.
It's the perfect place as evidenced by your well thought out response below:
The difficulty involved in porting Qt based apps to Gtk can vary a lot. Personally, If I were you and I _really_ wanted to do it. I'd try to get libqt to work under the scratchbox environment. Then package it as statically linked to your application executables. Hang on, isn't that against Trolltechs UA? Anyhow.
Remember there is a difference between the open source version and the commercial version, we have a commercial license, which might still be a problem, I'm in the research phase right now.
You're part of a business that has chosen to specialise in writing apps for embedded devices (I'm guessing here). You chose Qt as your platform, which was shipped with the zaurus. Now, tell me if I'm wrong. I'm guessing you plan on trying to sell applications to users of the N770 when it gets shipped. Cool, nothing wrong with that. It isn't however a good idea, in my opinion, to write apps that: a) Will look crap on stock devices. (Unless Qt can be hildonised) b) Do not look like other apps on the device. c) Don't interface with the core platform.
well, we don't know that any of those items will be true yet do we? That is the point of researching it. First we find out if it is a viable short term option technically, then we do a proof of concept to see how it works in reality. If it doesn't look and work naturally on the device (like most Java apps on the Zaurus) then it won't make sense to do it that way.
So, personally. Even though the wording by koen may have sounded hard. Unless you plan on helping/starting/doing some Qt modifications to make it interface, at least a little, with hildon/libosso.
who knows, we might - like I said, this is all research right now
You should really get your development team to read some docs at 'http://www.gtk.org/'. It took me less than a week to get good enough to write apps in Gtk + Hildon + libosso.
oh, we know all about Gtk, but take a look at www.thekompany.com/embedded and you tell me what is going to be faster, rewriting all those apps or have a way to make them run 'as is' and react naturally on the device. From the user experience perspective they don't care what OS is on it, or the toolkit used to get there, they want apps that do what they want, are easy to use and typically attractive. That is what my focus is. Maybe in a week we'll find that there is no reasonable way to have our apps run 'as is' and we will have to start porting. Like I said, our presentation layer is nicely partitioned from the transaction layer for the most part, so we would typically just be rewriting the UI, which might be relatively trivial, but we won't know till we get in to it deeper.
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Regards, Shawn Gordon President theKompany.com www.thekompany.com www.mindawn.com 949-713-3276 _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
