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