Changes between Initial Version and Version 1 of Ticket #2041, comment 18
- Timestamp:
- 11/29/18 18:08:26 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2041, comment 18
initial v1 5 5 In the UI what I've done is mostly similar. Even though I require that the field be filled in, the the field *starts out* filled in with the output from xpra.platform.info.get_username() (so the user would have to decided to clear it to get a blank field). I think that this behavior is almost equivalent to the command line behavior that I just mentioned. 6 6 7 The slight difference is (in my opinion) desirable: On windows my username doesn't match my username on the server that I am logging into. My windows username has a space in it, and I think that that is pretty typical. When, due to a bad username, my attempt to login fails my IP gets blocked (my server runs OSSEC). I would bet that lots of people have similarly configured server and would appreciate having the UI thusly steer them away from such mistakes. I think as I've done things the UI protects the user while providing the benefits of sensible defaults.7 The slight difference is (in my opinion) desirable: On windows my username doesn't match my username on the server that I am logging into. My windows username has a space in it, and I think that that is pretty typical. When, due to a bad username, my attempt to login fails my IP gets blocked (my server runs OSSEC). I would bet that lots of people have similarly configured server and would appreciate having the UI thusly steer them away from such mistakes. I think as I've done things the UI protects the user by *displaying* the default value while providing the benefits of sensible defaults. 8 8 9 9 If you want me to allow for the launcher entry fields to be blank, I *will* change it to do whatever you prefer. Just say the word!
copyleft 2010 - 2021
