<br><br><div class="gmail_quote">On Mon, Sep 28, 2009 at 1:17 PM, Cornelius Hald <span dir="ltr"><<a href="mailto:hald@icandy.de">hald@icandy.de</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 Mon, 2009-09-28 at 13:00 +0200, Thomas Perl wrote:<br>
> 2009/9/28 Cornelius Hald <<a href="mailto:hald@icandy.de">hald@icandy.de</a>>:<br>
> > On Mon, 2009-09-28 at 12:18 +0200, Thomas Perl wrote:<br>
> >> Yes, we can probably add whatever we want in the "Advanced" color<br>
> >> dialog. One thing that I would find nice (and that I have not found on<br>
> >> any platform yet) is that customized colors are saved per-user and not<br>
> >> per-application (so that when I for example have a great "green" color<br>
> >> that I want to use for my Uni stuff in GPE, I can have the same color<br>
> >> as background color of Uni-specific notes in Conboy and as background<br>
> >> color for Uni events in the countdown widget, etc..).<br>
> ><br>
> > Yes, I totally agree with that. We could just save custom colors to<br>
> > gconf. That should do the trick :)<br>
><br>
> Here's an updated mock-up:<br>
><br>
> <a href="http://thpinfo.com/2009/maemo/colorchooser2.png" target="_blank">http://thpinfo.com/2009/maemo/colorchooser2.png</a><br>
<br>
</div>I like the pallet selection!<br>
<div class="im"><br>
> Some remarks:<br>
><br>
> * Added pure black and white as suggested by Graham<br>
> * One slot is free (when the current setting is a custom color that is<br>
> not in the palette, the slot will be taken by that color and pre-selected)<br>
<br>
</div>Do you think that one custom color is enough? How about having a<br>
complete column or row for custom colors? I didn't try it, but it looks<br>
like there could be enough room for a fourth row of colors.<br></blockquote><div><br>full row should fit and in my experience people have a few most recent selections<br></div><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"><br>
> * HildonPickerButton for selecting a pre-set (or application-set)<br>
> palette - this would change the displayed colors except the last<br>
> column, so we always have black, white and the "custom" color<br>
><br>
> Anyone wants to do a mock-up for the advanced color chooser dialog?<br>
> Or propose "default" color palettes? (If we are going to use something<br>
> like the current mock-ups, we have 3x6 = 18 colors per palette and then<br>
> black and white and the custom color that appears in every palette...)<br>
><br>
> Also, do we want to have the dialog relayout itself for portrait mode?<br>
<br>
</div>I think not in the first version. ATM I know not a single application<br>
that allows editing in portrait mode. Also settings dialogs (where you<br>
often have color selection) are usually landscape only.<br>
If at some point this dialog should support portrait mode, we surely<br>
have to do something about the "Done" and "Advanced" buttons as they<br>
already take almost half of the screen width. Also if the pallet-mode<br>
supports portrait, then the advanced-mode should support it too, which<br>
might be even more difficult.<br></blockquote><div><br>the standalone dialogs you are used to seeing are normally from desktops and they have enough space that it doesnt matter<br><br>recall however, portrait color selection has been used in paint programs all the way back to 8bit days - it just wasnt a popup dialog, remember deluxe paint...<br>
<br>i agree we need to find a really neat way to handle those done/advanced dialog buttons<br>the amount of wasted space is silly<br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
To make it short, I vote for landscape only :)<br></blockquote><div><br><br>for now, sure its the only practical way we are going to advance<br>since we have a good idea what this may look like, how about we get down to sorting out where its going to live.<br>
<br>do we attempt to make sure the api/options for a gtk/hildon/sexy lib replacement exist, or do we aim for a maemo_community library for these kinds of dialogs?<br><br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Conny<br>
<div><div></div><div class="h5"><br>
<br>
_______________________________________________<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>