unity-design team mailing list archive
-
unity-design team
-
Mailing list archive
-
Message #00612
Re: Message Indicator: Listing apps in menu even if they are not on
On Sat, 2009-09-05 at 06:56 -0400, Scott Kitterman wrote:
> On Sat, 05 Sep 2009 12:58:37 +0530 mac_v <drkvi-a@xxxxxxxxx> wrote:
> >Anyone subscribed to the wiki page would realize that the messaging menu
> >specs are changed almost every other day[in the past couple of weeks].
> >They seem to be testing it and trying to find a proper solution! I think
> >if we are a *little patient* the plans would become clear,eventually.
> >
>
> If we are just supposed to sit back and wait and accept what we are given,
> then there is no need for a public list. Please don't attempt to shout
> down people who have questions.
>
> Scott K
>
err... i didnt mean to shout anyone down... :(
But rather wanted to say, the product is still in development cycle.
When a product is in *development cycle* it is reasonable to find
several changes in the apps almost every day.
We cant keep constantly banding the doors for an answer which might
change at anytime during testing!
Rather we need to offer solutions about what seems wrong.
Its just we are not used to such changes in specs , since only recently
has Ubuntu been doing upstream development.
take for example: gnome3 had changes in several aspects and even now we
dont know what it is going to end up as...
Well,these were just my impressions from all the work going on, i maybe
wrong. But none is to shout anyone down :)
On Sat, 2009-09-05 at 12:40 +0200, Steve Dodier wrote:
>
> Excuse, but that seems like a perfect exemple of design flaw Celeste
> is warning against. Her point of view is entirely valid when she says
> that you need to make sure the design fits with the goals now that you
> (even slightly) changed the goal.
>
I agree . The questions raised are valid,*to devs* who want to keep up.
But in no way at all do the arguments bare any weight on having the
feature implemented or not. Regarding the design of the product this is
not a valid argument. I was commenting only on that. ;)
--
Cheers,
mac_v
Follow ups
References