Quote for the day:
"It sounds like a Nostradamus Prophecy-'A team from the south will win a hockey championship' "--Andrew Turnier
Quote for the day:
"It sounds like a Nostradamus Prophecy-'A team from the south will win a hockey championship' "--Andrew Turnier
I have serious suspicions that many of the complaints over the font rendering in OS X are the result of two things:
The longest part of the secadic eye movements that are used in the visual searches done on text is dwell duration, which is partially governed by the ease of information extraction, ``which is often influenced by stimulus quality(e.g. in target search, longer dwells on a degraded target).'' (Wickens, Gordon, & Liu, 1998).
I'm actually getting the information in the above paragraph from the textbook from my human factors course this semester. (I like it a lot. Who thought studying could be so much fun? One should follow their passions and do what they love to do. Preferably for a large sum of money, if possible.)
My point--ridiculously anti-aliased text is a ``degraded target'' and thus takes longer to perform a visual search. And this would especially suck for older adults like Doc whose visual search capability is already fairly degraded.
When the brain sees text with a reduced contrast and the appearance of blur, visual accomodation (the eye's lens moving to accomodate for distance) kicks in automatically. In other words, ridiculously anti-aliased font tricks the brain into thinking the font is at a different distance than it really is, and the muscles in the eye are constantly trying to adjust the lens very so slightly in the futile attempt to bring the blurry text into focus (which of course never happens). Given that some people feel okay with the extreme anti-aliasing, it might be possible that the brain eventually adapts and quits trying to bring the text into focus. It would also be fascinating to see whether screwing around with the perspective to make the ridiculously anti-aliased text appear to actually be a different distance than the rest of the screen would eliminate the eye strain. Making a menu selection look farther/nearer than it actually is would be a less than adequate solution. But it would be interesting to see if it could be done.
Some of this (mostly #2) is somewhat conjecture right now. But I suspect that if I could get my hands on an oculometer and a bunch of guinea pi...er..subjects and sit them down in front of such environments, I could easily prove both of these conditions to be true.
Got the PyQt zaurus diet program a little more properly laid out last night (at least something got laid last night). Finally got around to learning how to create a Qtopia desktop entry for it, and I hope to learn ipkg shortly. I'm now using DietMaster to record what I eat on a regular basis and it works quite well, though there are still a few minor things I need to add but haven't due to time constraints, such as deleting an entry(although maybe this is not the best idea for a program that records your eating habits. Too much temptation to erase history). One of the things that I think would be neat to add would be something that makes use of the SOAP python module to display values from DietMaster in a graph on my desktop via RPC. It would probably be a fluff feature that really wouldn't add to the user experience and probably shouldn't be in the program. But it would be kind of neat to try it in a prototype.
I have to curb working on stuff right now. I have to devote every waking minute I have to learn everything I can in my Cognitive Processes and Ergonomics classes. These classes will be far more useful to me in the long run for creating usable interfaces than any code I write over the next several weeks.
Have gotten an extremely crude PyQt diet program for my Zaurus up and running. I finally polished up the XML handling a little more and tied that into the PyQt interface. The biggest problem now is that too much screen real-estate is being taken up and not everything can fit. And this is not because I have a whole lotta crud on the screen. It's because TrollTech/Qtopia has fallen into the trap of copying Microsoft/Windows CE who fell into the trap of designing the PDA UI as if it was a desktop UI. Widgets and layouts and styles of navigation that work on a 17" monitor will not necessarily work on something 20 times as small. The text fields and buttons in particular take up too much space for what they are supposed to do. I suppose if I want something well designed, I should shut up and make my own Qtopia. The things we go through for a 206Mhz StrongArm and 64MB...sigh..
It's amazing how PalmOS is close to 5 years old, yet in many ways the design of its user interface (and it's form factor, for that matter) is far more ahead of its time and more well thought-out than much of the crud that came out in the last year.
I've started the habit of keeping a log of everything I eat. I've heard from several people that doing this really helped them lose weight, so I figured what the hell. I've even started to work on a silly little PyQt program for my Zaurus that will help me keep this log in a nice, orderly, XML-ized fashion.
After seeing "Attack of the Clones" a few days ago, I am left with a few puzzlements:
First summer session at NCSU has begun. I'm taking Cognitive Processes and Ergonomics. Finally I get to take classes in stuff I'm really interested in and that can I can use to advance my work further.
Insight for the day: Time spent talking to a wall is time better spent demolishing it.
I actually consider Tk's crap important for what I'm doing. I need to practice receiving lot's of uninformed criticism from immature newbies. I think that that people who have very successful software projects have to cultivate this ability. Keep it coming. You're only making me stronger.
Some people think the UI theories backed up by user testing and findings in cognitive psychology are BS. I have no problem with this and I could really care less. Just as I'm sure all the people working on the Manhattan project didn't care whether many people in Japan or Germany thought that Einstein's theory of relativity was BS. By 1946, it really didn't matter what some people thought.
As long as we're quoting excellent postings of mine (Kudos to Tk for linking to it. That was one of my best to the gnome-gui list, and I heartily stand by it), I thought I might post a something I wrote to Slashdot recently about the leaked letter of Microsoft's urging it's supporters to engage in an underground campaign of sabotage against linux. I consider this a necessary public service announcement for those who read advogato diary entries.
How to spot a Microsoft Mole
Microsoft moles can be identified by their unwavering committment to preventing windows users from installing linux. A microsoft mole might be identified by one or more of the following activities:
If you see your friend, spouse, employer, LUG members, or poster to on-line forums such as Slashdot or Advogato engaging in one or more of these counter-revolutionary activities, there is a very good chance that they are an agent of microsoft committed to making sure that linux will never be installed on the machines of existing windows users.
- Tells a newbie who is having a problem to shut up and RTFM
- Claims that a user-hostile program that lacks any kind of usability is "perfectly ready for the desktop"
- Tells said developer of program to "keep up the good work".
- Tells people who criticize a badly designed free software UI to "quit whining" or "you get what you pay for".
- Uses the word "Idiot","Simpleton" or "Moron" in the same sentance as "GUI". An example would be the sentance "GUI's are for morons who can't think".
- Runs around screaming "Don't standardize linux GUI's. It's a matter of choice--don't promote facism."
- Assaults the credibility and necessity of UI designers, chasing them off and therefore insuring that linux will be as user-hostile as possible.
The point to my silly piece is the same one I made two or more odd weeks ago: Bill Gates doesn't have to lift a finger to sabotage linux on the desktop because so many people in the linux community and Free Software development community do his job for him.
Long time since last update....
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!