FreeLists / openbeosnetteam / [openbeosnetteam] Re: Network preflet, the future?

["Niels Reedijk" <n.reedijk@xxxxxxxxx>]

> I try to apply your suggestions, so here another layout sample
> screenshot:
> http://philippe.houdoin.free.fr/phil/beos/openbeos/network_kit/
> network_gui-06.png

Nice.

> BeOS way, for preferences, is that they're applied in *live* as much
as
> possible, plus saved.
> For Network, I don't know if it's good idea to let a user modifiying
> setup in *live*.

It's not, and we shouldn't enforce it upon the users. 

> Until the "Apply Now" button is press, all changes made are only
stored
> in memory by each add-ons.
> However, this forbid to modify an unactive setup profile without
> activating it.

Good point. I don't think that many people need to change a profile
without actually using it, though some people in the world might need it
anyway.

> Should I split the "Apply Now" into "Save" and "Apply Now" ?

I think that Apply automatically implies saving the settings (it doesn't
make much sense). 

I recall having fixed this in my design by using a 'Set as Active
Profile'
button (though I didn't yet think of a more useful caption). Perhaps
'Activate profile' is a bit nicer. Anyway, this means that you can
change all the settings (and when you do apply, it just saves them, even
the changes you made in the inactive profiles). This would mean that
there would be a settings class (with one object per profile), that has
the ability to save and revert changes made to settings (so there would
be a Commit() and a Revert() method).

Niels