Hi,

ext Cornelius Hald wrote:
> I don't know it either, but I expect it
> to be basically non-existent and probably for a good reason. I don't
> think it makes sense to work at Harmattan's Hildon before we know how
> the Harmattan UI will look and (more important) work. That's probably
> not really a technical problem, but more a motivational problem.

(...)

> What I think will happen is this: At some point people with big
> Maemo5/Hildon applications will get a Harmattan device or SDK and then
> they will try to get their applications running. Therefore they will
> compile a recent version of GTk, try to apply Hildon patches, etc.

I see your point. However, your motivational path is simpler if you
focus on the public MeeGo Handset UX and compatible devices (coming
soon) instead of waiting for the mysterious Harmattan device from Nokia.


> At that point we will see whether or not it is feasible to bring Hildon
> to Harmattan. Well, at least if it is a _real_ community effort. If
> however Nokia did sponsor some Gtk developers and provided them with
> some Harmattan UI material it might look differently.

At least from a theoretical point of view it made sense to work out the
support for GTK+ and Hildon related activities with the GNOME
Foundation, since it's an organization able to invoice that has the
overall responsibility of the GNOME and GNOME Mobile projects. The fund
given to them should be enough to kickstart the work and more.


>> There has been some discussion about this at GNOME's mobile-devel-list
>> but honestly I had expected a more concrete or articulated answer by
>> now. See the whole "What would you do to encourage application
>> developers on GNOME Mobile?" discussion starting at
>> http://mail.gnome.org/archives/mobile-devel-list/2010-April/msg00003.html
>> and even my own post back in February that got basically no traction
>> from anybody involved in GTK+ development -
>> http://mail.gnome.org/archives/mobile-devel-list/2010-February/msg00010.html
> 
> It would have been nice to inform people on the maemo-devel list about
> those posts.

True, my fault. Maybe I was too optimistic at that time about
Hildon/GTK+ maintainers taking the ball and moving forward, or at least
showing interest and asking the right questions to proceed.

There was also http://talk.maemo.org/showthread.php?t=36687 and this was
discussed elsewhere in the Maemo community as well (can't remember now
exactly where). But no post to maemo-developers, true.

Then again, the GNOME project is where the GTK+/Hildon hackers are
supposed to be found. I'm sure the maintainers and related developers
that actually have the skills and potentially the interest of doing
something like the topic discussed here were aware of these posts.


> That might now be the job of the Gnome Foundation and not of Nokia. But
> this is what I think should happen.
> 
> 1.) Provide people with some time and/or money to bring all Gtk changes
> that are needed for Hildon upstream into the real Gtk.
> 2.) Let them make sure that the current Maemo5-Hildon compiles against
> that new Gtk.
> 3.) Give them insight into the Harmattan UI spec, to make it possible to
> adapt the look and feel.

The bal is now in the GNOME Foundation's field. Our fund went there with
 a proposal/recommendation of the types of activities to do, but it is
now their budget and their decision.

> Personally, I really really want to have Hildon on MeeGo. Not because I
> think it's the future or that it is superior to Qt. No, simply because
> it would be so frustrating to see my volunteering work of over a year go
> into oblivion. If I had the time (3-4 month full time), I would rewrite
> my application using Qt. Unfortunately this is completely unrealistic.
> 
> Still hoping for Hildon on Meego!

Having an evolutionary path for GTK+ & Maemo 5 apps into MeeGo Handset
(and touch friendly UXs in general) makes total sense, and this is why
we are here (and in gnome.org) discussing in these terms.

-- 
Quim Gil
open source advocate
MeeGo Devices @ Nokia

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to