On Fri, Oct 8, 2010 at 12:41 AM, Quim Gil <[email protected]> wrote:
> Still, it feels like too wide for a task that could be committed to 1.2.
> Looking at your list, there are some items that look like more immediate
> and could be completed during the 1.2 release cycle:
I was not aiming for a specific release at the first go, as I noted
the first few items seems closer, and I am going to choose a few of
them to target for the 1.2 release cycle.
>
> - Document comparing Qt in MeeGo 1.1 with Qt in Symbian3: what is the
> same and what differs.
This is I think the most important so far for the 1.2 release to
provide some point of view for development efforts that want to plan
for cross platform support.
>
> - Examples of apps running in MeeGo 1.1 Handset+Netbook and in Symbian3.
> Document explaining the steps made for platform / UX compatibility and
> optimizations.
You mean documenting coding practice? or everything needed ?
>
> - Plus: closer to 1.2 release update the docs and examples with Symbian4
> & MeeGo 1.2. What has improved, what is the same (hopefully nothing
> worse).
I think that could well be done even a bit after the release, so see
where the future takes us.
>
> - Big plus: document the experience of publishing a Qt app in
> Ovi/Symbian and AppUp/MeeGo + meego.com Extras.
I consider this even more important than the former, as this is a
crucial part in code, publish, profit (and not only in monetary terms
;))
Thanks for mentioning it! I had completely forgotten about it.
>
>
> Just an idea. These are tasks that are somehow needed to address well
> the rest of tasks listed in your page. You could have these (or the ones
> you prefer) committed for 1.2 with the team that will work on them, and
> leave the rest as Nice To Have. Perhaps food for the next release?
>
Noted, however given Kate's response I guess I better co-ordinated
with her to not step on FN's toes.
>
> And a detail: note that "Qt" is a wide umbrella these days with ol' good
> Qt, Qt Quick and Qt WebRuntime. These pieces are moving through MeeGo
> and Symbian. Maybe you find volunteers to cover of all them, but
> otherwise perhaps the best is to focus on the best path now. As you see
> it.
According to Kate, Qt Components which as I understand it is building
specialized reusable components through QML, is the most probably
cross platform way, maybe because they are built in runtime through
generic ECMAScript like language, where you make it run on a different
platform (namely, Symbian) you just need to replace the runtime with
runtime for S{3,4} that uses the underlying look and feel of the
native widgets.
My feeling is that QWRT is somewhat similar, so going with
"Components" seem wise, given QML's promises in tems of UX and
designer incorporation. What would ol' Qt mean in this context?
-Sivan
_______________________________________________
MeeGo-community mailing list
[email protected]
http://lists.meego.com/listinfo/meego-community
