Weather Indicator

Series 3.0
Bug #703815
Comment #36

Comment 36 for bug 703815

Revision history for this message

Panagiotis Skintzos (ph7) wrote on 2011-03-29: Re: [Bug 703815] Re: change layout by omgubuntu mockup

#36

> That said, I like 1), except I don't think scrolling on the indicator
> should change the display - IMO this is not a very logical behaviour. I
> think there'd be less people using this feature than there would be
> people who accidentally trigger it and get confused. Plus the
> information is only a click away.
Ok let's forget the scrolling for the moment

>
> 2) I don't think that this should be customisable. We should choose a
> sensible set in a sensible order and format, and tailor the indicator's
> design to that. Maybe, maybe if people REALLY want to alphabetise it or
> change the order then we should let them customise it with a settings
> file, but as long as we put the 'right' data in I don't think people
> will desperately want to change the order or take things out.
The info available is a big list and I really believe that many users
will not care about some things like humidex or sunset/sunrise.
The list of fields to be displayed is already a couchdb setting in the
vala port. The only thing missing is the ability to be changed by the
user. One could use the couchdb command line tool to change it, but a
simple listbox with checkboxes in the preference dialog should not be
too overwhelming.

>
> 3) and 4):
> I like Mind Bending's mockup - it's a neat way of changing location. Reading through the comments on that page, only one person wanted "to see directly the weather in other locations". Everyone else wanted a forecast or "both" (i.e. to have easy access to a forecast and to the weather in different locations). I suspect that the majority of these people would be happy with the Mind Bending approach, as long as switching between locations is sufficiently fast. So my vote would be for implementing 3) and 4) as standard, and make people go through the carousel to see other locations.
Yeah seems like these are most popular.

>
> The "Forecast" and "About" menu items could be removed. If it's
> essential that we have an "About" box (which I don't think it is), then
> it could be linked to from the Preferences window.
The Forecast should be visible if the user has not selected to see the
forecast info in the menu

+1 for the About to go to preferences.

> That said, I like 1), except I don't think scrolling on the indicator
> should change the display - IMO this is not a very logical behaviour. I
> think there'd be less people using this feature than there would be
> people who accidentally trigger it and get confused.  Plus the
> information is only a click away.
Ok let's forget the scrolling for the moment

> 
> 2) I don't think that this should be customisable.  We should choose a
> sensible set in a sensible order and format, and tailor the indicator's
> design to that.  Maybe, maybe if people REALLY want to alphabetise it or
> change the order then we should let them customise it with a settings
> file, but as long as we put the 'right' data in I don't think people
> will desperately want to change the order or take things out.
The info available is a big list and I really believe that many users
will not care about some things like humidex or sunset/sunrise.
The list of fields to be displayed is already a couchdb setting in the
vala port. The only thing missing is the ability to be changed by the
user. One could use the couchdb command line tool to change it, but a
simple listbox with checkboxes in the preference dialog should not be
too overwhelming.

> 
> 3) and 4):
> I like Mind Bending's mockup - it's a neat way of changing location.  Reading through the comments on that page, only one person wanted "to see directly the weather in other locations".  Everyone else wanted a forecast or "both" (i.e. to have easy access to a forecast and to the weather in different locations).  I suspect that the majority of these people would be happy with the Mind Bending approach, as long as switching between locations is sufficiently fast.  So my vote would be for implementing 3) and 4) as standard, and make people go through the carousel to see other locations.
Yeah seems like these are most popular.

> 
> The "Forecast" and "About" menu items could be removed.  If it's
> essential that we have an "About" box (which I don't think it is), then
> it could be linked to from the Preferences window.
The Forecast should be visible if the user has not selected to see the
forecast info in the menu

+1 for the About to go to preferences.