headers
Christopher Ness | 20 Jun 23:51

Wireless Settings UI

Which is the prefered UI for editing settings in a text box form?

The method used by iwsettings.php where the current value is printed
beside the header and the text box is left blank

 - or -

The method used by ifsettings.php where the current value is
pre-populated into the text box for the user.  I think I'd be leaning to
this method myself.

Cheers,
Chris
--

-- 
Wireless Group,
McMaster University

finger.localdomain
17:46:49 up 6:49, 1 user, load average: 0.11, 0.07, 0.02

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Permalink | Reply |
headers
Thimios Dimopulos | 21 Jun 01:21
Picon
Favicon

Re: Wireless Settings UI

I also think the second option looks better.

On Tuesday 21 June 2005 00:51, Christopher Ness wrote:
> Which is the prefered UI for editing settings in a text box form?
>
> The method used by iwsettings.php where the current value is printed
> beside the header and the text box is left blank
>
>  - or -
>
> The method used by ifsettings.php where the current value is
> pre-populated into the text box for the user.  I think I'd be leaning to
> this method myself.
>
> Cheers,
> Chris

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Permalink | Reply |
headers
Thanos Panousis | 21 Jun 09:01
Picon
Favicon

Re: Wireless Settings UI


Yes, thimios likes the second option because he implemented that one :).

The thing is that if you pre-populate the text-boxes, which looks nicer 
indeeed, you have no way of knowing which textbox was altered by the 
user. So in iwsettings, where I must parse the textboxes to issue a 
`iwconfig bla blah`, I want to shorten the last command to just the 
needed directives, since prism drivers tend to be a little buggy with 
too many iwconfig arguements.

I'm sure there is a way to actually post only the user-changed 
values(JS?), but I didn't decide to use one.

Thimios Dimopulos wrote:

>I also think the second option looks better.
>
>On Tuesday 21 June 2005 00:51, Christopher Ness wrote:
>  
>
>>Which is the prefered UI for editing settings in a text box form?
>>
>>The method used by iwsettings.php where the current value is printed
>>beside the header and the text box is left blank
>>
>> - or -
>>
>>The method used by ifsettings.php where the current value is
>>pre-populated into the text box for the user.  I think I'd be leaning to
>>this method myself.
(Continue reading)

Permalink | Reply |
headers
Christopher Ness | 21 Jun 17:22

Re: Wireless Settings UI

On Tue, 2005-06-21 at 10:01 +0300, Thanos Panousis wrote:
> The thing is that if you pre-populate the text-boxes, which looks nicer 
> indeeed, you have no way of knowing which textbox was altered by the 
> user. So in iwsettings, where I must parse the textboxes to issue a 
> `iwconfig bla blah`, I want to shorten the last command to just the 
> needed directives, since prism drivers tend to be a little buggy with 
> too many iwconfig arguements.
> 
> I'm sure there is a way to actually post only the user-changed 
> values(JS?), but I didn't decide to use one.

Why not get the data again using `get_wireless_status()` before building
the iwconfig argument list.  Now you know the current state of the
system and have the values entered by the user in the form.

Then compare what the system settings are to the user input fields
building an argument list for only the ones that changed?

Cheers,
Chris
--

-- 
Wireless Group,
McMaster University

finger.localdomain
11:16:57 up 1 day, 20 min, 1 user, load average: 0.01, 0.01, 0.00

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
(Continue reading)

Permalink | Reply |

Gmane