On Tue, 06 Mar 2007 15:38:30 +0000
Darren Kenny <Darren.Kenny at Sun.COM> wrote:
> Hi Michael,
>
> Michael Hunter wrote:
> ----8< SNIP 8< --------
> >
> > Additionally for most users NWAM is suppose to just work. They
> > shouldn't have to touch the config GUI. In many ways having to touch
> > the config GUI is indicitive of NWAM not working well enough. That
> > said VPNs are common and not something we can just detect. Providing a
> > mechanism where people can make them work is a requirement as far as
> > I'm concerned as is providing defaults in known cases.
> >
>
> There is one main issue here - wireless - it is unlikely to ever "just work"
> out
> of the box - most people (I would hope) have some level of authentication on
> their wireless networks, this in turn then requires interaction with the user
> -
> even if it's as simple as "wireless net <insert name here> - would you like to
> connect to it".
That is correct. That is why I said "config GUI" ;)
>
> From this perspective, I think that a "fully fledged UI" isn't really what is
> needed initially - infact the most likely wired/wireless combo interaction
> requires little more than :
> - default IP being DHCP (but possibly allow user to enter a static IP)
> - select the name services (Environment)
> - if using wireless,
> - configure the preferred networks
> - or add one based on the visible networks (including the WEP key here).
> - or supply a new WEP key for a preferred network we seem to be having
> problems connecting to.
>
> To me, for PHASE 1 at least, using a GNOME based desktop (it is expected that
> CDE will go away eventually[1]) we really want the GNOME Panel Applet type
> functionality - not the full (or even currently proposed for phase 1) UI. I
> know
> I've mentioned Network Manager before here, but I'm starting to think it's
> *too*
> simple for our needs and maybe a Solaris specific version might be better,
> but I
> still think that something along these lines is what's needed first for the
> target market of SDX.
I think the typical task flow for NWAM should be to almost entirely
interact with a runtime GUI (panel applet driver kind of thing). As
you drift between different environments you might be prompted for new
information (WEP keys being a primary example) the first time but then
in the future the right thing happens.
Thus my comment that the "config GUI" shouldn't have to be touched in
the normal course of the day.
That said I think I'm in the minority when I think of the thing you use
to build a more complex configuration and the thing you interact with
for basic decision making and status as being different.
mph
>
> Darren.
>
>
> [1] - Even if we wanted to handle non-GNOME environments we could simply have
> things run in "application mode" - i.e. don't use the panel if it's not there,
> it can be done AFAIK..
>
>
