Re: Request for ergonomy feature

["Jeroen van de Nieuwenhof" <lists vandenieuwenhof nl>]

Op donderdag 11-10-2007 om 11:19 uur [tijdzone -0400], schreef Dan Williams:
> On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
> > Ok, but it is just a pain in the *ss this bug, and everybody
complains.
> >
> > Please, rather than saying "I disagree", maybe propose an alternative,

> > because it is really annoying bug.
>
> We already discussed alternatives on this list.  First, NM should scan
quite quickly after dropping the menu down, as long as NM has not
scanned within the last 20 seconds.  Currently that may not be the case,
it might push off the scan for 20 seconds.  This is a case of a bug that
should be fixed (if it exists).
>
> Furthermore, I don't believe that it's that much of a burden to check
the menu twice.  Can you refresh my memory as to what situations
explicitly scanning for networks is necessary?  The applet should be
kept simple, additional functionality that doesn't fit in the applet can
certainly be farmed out to other tools that are not the applet or NM.
The applet should cover 90% of all users needs 90% of the time.  It
should _not_ cover 100% of all users needs 100% of the time.  There are
some features that just won't be implemented.  I believe explicitly scan
requests fit in that last 10%.  I may be able to be convinced otherwise.
>
> Dan
>

I think the main problem is that new users of NM don't KNOW that NM scans
for new networks after a click or some time. So if a new user runs NM and
sees no networks while he knows there are networks in the area he gets
annoyed that they aren't available in the applet.

Jeroen





Op donderdag 11-10-2007 om 11:19 uur [tijdzone -0400], schreef Dan Williams:
> On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
> > Ok, but it is just a pain in the *ss this bug, and everybody complains.
> > 
> > Please, rather than saying "I disagree", maybe propose an alternative, 
> > because it is really annoying bug.
>
> We already discussed alternatives on this list.  First, NM should scan
> quite quickly after dropping the menu down, as long as NM has not
> scanned within the last 20 seconds.  Currently that may not be the case,
> it might push off the scan for 20 seconds.  This is a case of a bug that
> should be fixed (if it exists).
>
> Furthermore, I don't believe that it's that much of a burden to check
> the menu twice.  Can you refresh my memory as to what situations
> explicitly scanning for networks is necessary?  The applet should be
> kept simple, additional functionality that doesn't fit in the applet can
> certainly be farmed out to other tools that are not the applet or NM.
> The applet should cover 90% of all users needs 90% of the time.  It
> should _not_ cover 100% of all users needs 100% of the time.  There are
> some features that just won't be implemented.  I believe explicitly scan
> requests fit in that last 10%.  I may be able to be convinced otherwise.
>
> Dan

I think the main problem is that new users of NM don't KNOW that NM scans for new networks after a click or some time. So if a new user runs NM and sees no networks while he knows there are networks in the area he gets annoyed that they aren't available in the applet.

Jeroen