[maemo-developers] Community widgets for Fremantle

[From: Andrew Olmsted]

Hi all,

I have released countdown-home 0.5-8 to extras-testing for Fremantle.  I 
have gotten some initial positive feedback for the colour and font 
selection I use.

I have made the font selection and colour selection widgets as 
self-contained as possible - they are not integrated in any way in the 
countdown-home code.  In my case, I decided to try to parallel past 
hildon colour and font dialogs as much as possible.

To this end I now have six different widgets, each prefaced with "he" 
for hildon-extras (but much shorter).  They are:

he-color-button, he-color-dialog, he-color-selector
he-font-button, he-font-dialog, he-font-selector

As for developing with these widgets, the developer need only put a 
font/color button in his/her application and he/she can set and retrieve 
the font/colour through that.  For example, the he-color-button 
automatically creates a he-color-dialog for user input containing an 
he-color-selector.  The developer can use the dialog and selector 
widgets as well, but it is just easier to put a button in and have 
everything controlled.

I would welcome any thoughts on my particular implementation.  The 
source can be obtained at:  
http://repository.maemo.org/extras-testing/pool/fremantle/free/source/c/countdown-home/countdown-home_0.5-8.tar.gz

Thanks,
Andrew (fiferboy)

gary liquid wrote:
>
> can i have a recap
>
> from what i know now,
> there are 2 sortof nearly good finger friendly color selection dialog 
> tests in use
> in two different apps and some python test code
>
> all of which is better than the not very finger friendly but standard 
> implementations.
>
> we now seem to have stopped dead with with good stuff and worrying 
> about the specific implementation.
>
> fiferboy, conny, thomas - excellent bits of code and usable dialogs 
> seem to be appearing!
>
> fifer, conny - please try to ensure your dialogs are as self contained 
> as possible and documented to some degree so if someone wants to lift 
> them from your projects its as easy as possible.
>
> should we put up a wiki page with links to the in use projects along 
> with screenshots and howto include in your project and stuff - leaving 
> the code basically where they are now and try to work on getting 
> decent implementations together?
>
> that seems like minimal fuss next step until we can haggle a library 
> or project etc
>
> we are mostly developers and like to show off screenies
> not worry about these niggly bits - if someone with determination to 
> build it as a library comes along and pulls those examples in - great
>
> gary
>
>
>
>
> On Tue, Sep 29, 2009 at 1:23 PM, Graham Cobb <g+770 at cobb.uk.net 
> <mailto:g%2B770 at cobb.uk.net>> wrote:
>
>     On Tuesday 29 September 2009 13:49:10 Marius Vollmer wrote:
>     > ext Claudio Saavedra <csaavedra at igalia.com
>     <mailto:csaavedra at igalia.com>> writes:
>     > > To be realistic, I don't think you'll have your library ready
>     by the
>     > > time Fremantle ships either, so I don't see that as a real
>     problem.
>     >
>     > The problem is that after Fremantle ships, libhildon is frozen for a
>     > long time.  It is prudent to assume that there will be no updates to
>     > libhildon that applications could rely on for, I dunno, 6 months
>     or so.
>
>     Exactly.   Hildon releases will not under the control of even the
>     Hildon team
>     (let alone the community): they will be tied to Nokia platform
>     releases and
>     Nokia QA schedules.   Due to the signing stuff the community
>     cannot replace
>     Hildon even if we wanted to.
>
>     > Ok, can't be done in any sane way.  So my best proposal now is
>     to create
>     > a separate library for the community widgets, without any hope
>     of ever
>     > moving the widgets into libhildon.
>
>     I am missing something.  Why do you (and Claudio) believe that if
>     we start off
>     by implementing the widgets in a community library it will be hard
>     to later
>     move them into Hildon?  I realise why it will be hard to get
>     people to stop
>     using the community versions but is there some reason it will be
>     hard to add
>     the community-developed widgets to Hildon?
>
>     If there really is a problem then there is only one other
>     alternative I see:
>     work in Hildon (or a fork) and allow the community to release an
>     alternative
>     to the standard hildon libraries (under a different library name but
>     containing the whole hildon library) on our own schedule.  Any
>     apps which
>     wanted to use the new features would have to link against the
>     community
>     library names instead of the standard library names but the Nokia
>     apps would
>     be unchanged.
>
>     Graham
>     _______________________________________________
>     maemo-developers mailing list
>     maemo-developers at maemo.org <mailto:maemo-developers at maemo.org>
>     https://lists.maemo.org/mailman/listinfo/maemo-developers
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>