unity-design team mailing list archive

["frederik.nnaji@xxxxxxxxx" <frederik.nnaji@xxxxxxxxx>]

about the attachment..
i'd already like to correct the syntax:

* chat settings
* broadcast settings
* about me

    CONTINUE >




On Mon, Feb 28, 2011 at 22:35, frederik.nnaji@xxxxxxxxx <
frederik.nnaji@xxxxxxxxx> wrote:

> On Mon, Feb 28, 2011 at 13:57, Matthew Paul Thomas <mpt@xxxxxxxxxxxxx>wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> frederik.nnaji@xxxxxxxxx wrote on 15/02/11 13:39:
>> >...
>> > On Tue, Feb 15, 2011 at 11:36, Matthew Paul Thomas <mpt@xxxxxxxxxxxxx
>> >...
>> >> The items in the status menus are shortcuts. Sometimes someone will go
>> >> into the clock menu to change something about the time, or the sound
>> >> menu to change something about the sound, etc, before realizing that
>> >> the menu itself doesn't contain the setting they want. But that's
>> >> okay, because at the end of the menu there's a shortcut to the
>> >> relevant settings pane.
>> >...
>> > As i understand your explanation, it would make sense to have 1
>> > "configure XYZ" entry in each status menu!?
>> > I would like that and i would find it quite consistent, compared to
>> > having several configuration links in one menu, 2 in an other status
>> > menu and only 1 on the bottom of yet another, while the Session Menu
>> > e.g. has not a single configuration item on the bottom of its menu.
>> >...
>>
>> There's no real benefit from trying to have exactly one settings item
>> per menu.
>>
>
> except for the point of consistency perhaps?
> derived thereof, learnability, simplicity ...
>
> > For the Me/Messaging Menu, that would then mean there would be an item
>> > such as "configure messaging" on the bottom.
>> > This again would lead to a unified messaging configuration wizard or
>> > page, where i can pick out the part or type of messaging i intend to
>> > configure.
>> >
>> > Is that too far off?
>>
>> Yes, first you would need to implement either a unified messaging
>> client, or an API for multiple clients to share the same settings window.
>
>
> or something like the attached mockup perhaps?
>
> OTOH i'd love to see an About Me view, with an EDIT button somewhere.
> I don't see the point of having a settings window for Empathy, for example,
> i'd only use it to enter account details.
> This i can do on an About Me page, too, and Empathy can fetch its data from
> there. AIUI, it's all about storing the information to accessible variables,
> which will be used by whatever connection manager is authorized to use them
> in the end.
>
> Also, i don't believe that multiple clients need to be considered here,
> only the ones delivered by default, imo.
> That's why i'm not yet understanding the problem..
>