Re: MeeGo

[Mike Turquette <mturquette gmail com>]

On Mon, Feb 15, 2010 at 4:08 PM, Stormy Peters <stormy gnome org> wrote:
> I think we stop waiting for people to come use GNOME Mobile technologies and
> make it really attractive to application developers. If the GTK+ toolkit is
> really attractive to application developers, the mobile platforms/devices
> will make sure that they work on the their device.

Stormy,

I disagree and I think your view is a bit too developer-oriented.
Truth is that in the land of handsets there is little freedom.  It's
*hard* to put your favorite Distro X on a handheld to enable
application development in your favorite Toolkit Y.  Winning over
application developers does little good when your foundation software
isn't directly supported and deployed by handset vendors.  Furthermore
app developers will often go to whichever platform makes the best
business sense to them, regardless of development environment, toolkit
and programming language.

Its easy to wipe WinXP off a netbook and start toying with Distro X;
that war can be won in the hearts of developers.  However the handset
world is an entirely different beast and if GNOME Mobile is going to
win it needs to win at the handset manufacturer level, not the
application developer level.

Mike

> Stormy
>
> On Mon, Feb 15, 2010 at 2:42 PM, Stefan Kost <ensonic hora-obscura de>
> wrote:
>>
>> hi,
>> Am 15.02.2010 19:02, schrieb Mike Turquette:
>> > What does this mean for GNOME Mobile?  From the Architecture page:
>> >
>> > "MeeGo UI Toolkit
>> >
>> > The MeeGo UI toolkit is the primary toolkit for developing MeeGo
>> > applications and is based on Qt with specific enhancements and
>> > additions. GTK and Clutter are also included for application
>> > compatibility."
>> >
>> > Sounds like GTK+ is taking a back seat.  More info at
>> > http://meego.com/developers/meego-architecture
>> >
>> > Mike
>>
>> yes, gtk+ takes a backseat. So what can we do? gtk+ needs to make a better
>> first
>> impression on software vendors as well. There are people working on that,
>> but
>> those are clearly not enough of them. Almost everyone can help with
>>
>> - moving the apis docs from tmpl to inline
>> - afterward improving the docs
>> - getting rid of cruft in the code
>> - writing tests
>> - review pending patches
>> - help triaging bugs
>>
>> Don't take any of those platform decisions cast in stone, in the end the
>> companies will use what they feel is better,
>>
>> Stefan
>> _______________________________________________
>> mobile-devel-list mailing list
>> mobile-devel-list gnome org
>> http://mail.gnome.org/mailman/listinfo/mobile-devel-list
>
>