Tuesday, November 4, 2008

system input methods

this is a temporary blogging mania caused by 1. sjw and 2. having two days off in a row and 3. immersing my identity into another person's identity. it will wear off and i will go back to my normal style soon.

i went to another weis to shop today, and talked to a cashier there who recognized me. (i avoid shopping at my own store, partly because people there now know that i have some kind of horrible scandal going on, and every time i look at them i can't forget that they know, and that the scandal hasn't been resolved yet. but that's not the only reason. it's mainly just to avoid social pressure, that i have to say hello to everybody when i might not feel like talking.)

the cashier complained about our new touchscreen monitors. i agreed right away. i only saw them briefly the other day but i felt immediately that this was a mistake. in my opinion, you should NEVER have to drag a scrollbar up and down on a touchscreen. it should be designed to avoid that. it makes the tip of your fingernail scrape the screen, or your finger is leaving a smear that will have to be washed off. the screens will need to be wiped all the time.

he said that he didn't like the monitors because when it was originally typed on keys, his fingers could type without looking. i don't remember if the keys had a 'braille' bump on the 5 or not, but i understand that it's possible to type without looking. that can't be done on a touchscreen, and it slows you down. i didn't have to use the register much, but when i did, i could just go bam-bam-bam-bam-bam-bam on the keys extremely fast and it took only a couple of seconds. but now you have to look at what you're doing.

i spent a couple minutes opening each of the menus to find out whether it was possible to get lost and not be able to find your way back. i figured it was better to do this during an idle moment when i wasn't waiting on a customer, instead of getting lost and screwing something up in the middle of a transaction. i familiarized myself with everything so that if somebody went in there and changed the settings of something and said 'nicole!!! help! how do i change this back?' i would know what to do. i'm sure i will eventually have to train somebody to use that register. it turns out that the settings seem to be relatively foolproof and that you can't screw something up by pushing the wrong button.

the only bizarre thing that i found was a menu that said 'system input methods: bengali input method, devanagari input method, gujarati input method, gurmukhi input method...' i copied it down on a piece of paper because i wanted to google it. this menu looked scary, so i didn't touch anything. if there was something i didn't understand, and if it got changed, and if it seemed weird, then i would guess that somebody had probably pushed a button in that menu. i'm going to google it...

okay, i know nothing about java. i have a feeling this is probably a bad thing, and i should leave it alone. but i wonder what happens if you change it.

the challenge is to see whether anybody else can locate that menu. it didn't require typing any secret passwords or anything. it was just in the 'touch everything' foolproofness testing that i did.

No comments: