Re: tkui users please comments

Eugene wrote:
> On Sat, 31 Dec 2005 19:22:37 -0500
>  Eliezer Flores <[email protected]> wrote:
>> I've been working on some patches to the tkui to make it a bit easier 
>> to hack various parameters. I just noticed if you turn off mudecho in 
>> the TKUI the entry field becomes a password field (i.e. instead of 
>> seeing the text you type in, you see a corresponding numbers of *s).
>>
>> Is there any reason why this is desired/expected behavior? My idea is 
>> to turn it off by default
>
> Sorry, I'm not quite getting what it is all about. What are you trying 
> to do?
>
> -- 
> Eugene
> ---
> Professional hosting for everyone - http://www.host.ru
>
Well I refactored tkui.py a bit so that it's easier to modify some of 
the basic parameters of the interface. Next my plan is to implement a 
couple of commands to allow the end-user to change those same 
parameters. Kinda like a more formalized tkconf.py. At the end of the 
day, i'd like to submit these changes to be a part of the official 
codebase.

In the process of this, somewhat unrelatedly, I noticed this bizarre 
behavior where if you turn the mudecho config option off, the entry 
field becomes a password field (i.e. obscures what you type with *s). 
Honestly, I find this behavior rather bizarre and I plan to implement a 
way where turning the echo off doesn't obscure what you type (heh i have 
a distinct difference in mudding philosophy from the author of tkui. I 
like black on white and hate having a local echo)

My inclination is just to delete the code that obscures what you type 
but seeing how I'd like my changes to be added to the official codebase, 
I don't want to step on any toes as it were. If there's someone who 
thinks it's really necessary to not being able to see what they type 
while mudding, i'll go through the extra trouble of coding another 
config option to toggle obscuring what you type.

Also, I'm vaguely curious why someone would want to not be able to see 
what they type. The obscuring isn't a side-effect of some other code. 
Someone spent a bit of time coding it to behave that way so it makes me 
a bit more cautious about getting rid of it. That being said, I just 
have a hard time imagining its utility unless it was some sort of 
whacky, half-implemented Boss feature.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click