Re: [Wifiadmin-users] Wireless Settings UI

[Thanos P. <pan...@ce...>]

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.
>>
>>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
>_______________________________________________
>Wifiadmin-users mailing list
>Wif...@li...
>https://lists.sourceforge.net/lists/listinfo/wifiadmin-users
>
>
>  
>