[Closed] Should we have a separate category or sub category for Qt on Symbian
Page |
1 |
Since there are some things like signing and native capabilities which are specific to Qt for Symbian
22 replies
I don’t like the idea of creating too many categories.
Yes, there are things specific for Symbian and for Maemo / MeeGo, but ideally the quantity of specific stuff should decrease (e.g. code using avkon stuff must disappear!). The signing process for the most use cases nowadays is way simpler than it was in the past.
EDIT: This is just my opinion, I’d like to read yours ;)
I don’t like the idea of creating too many categories.Yes, there are things specific for Symbian and for Maemo / MeeGo, but ideally the quantity of specific stuff should decrease (e.g. code using avkon stuff must disappear!). The signing process for the most use cases nowadays is way simpler than it was in the past.
Why? Given the sorry state of Mobility and Phonon, doing native is life essential in many cases.
Hi Ansel, unfortunately, you are too optimistic IMHO.
Indeed, the last part of my post was very optimistic, as I said :-P.
Regarding the category, for me it would be equivalent to create a category for Qt on Linux, Qt on Mac, Qt on Windows and so on. Keeping the larger groups (Desktop, mobile, embedded) makes more sense for me, but maybe I’m wrong…
I don’t like the idea of creating too many categories.Yes, there are things specific for Symbian and for Maemo / MeeGo, but ideally the quantity of specific stuff should decrease (e.g. code using avkon stuff must disappear!). The signing process for the most use cases nowadays is way simpler than it was in the past.
EDIT: This is just my opinion, I’d like to read yours ;)
The avkon stuff can disappear only when Qt becomes much more stronger and blends in to the system. Say one cannot apply any sort of themes to cba or status pane using Qt. So a full screen app looks better in Qt for Symbian now.
You must log in to post a reply. Not a member yet? Register here!





