I’m doing a bit of research for a microemulator feature request I filed. link
In short, the question is: on your cell phone’s Java ME implementation, does the ticker scroll across the top get reset and start again from the side, or does the text get updated without the ticker restarting from the side, as in this example:
On my Nokia 6121, it starts the text over each time it gets updated, which isn’t how I wanted it to work. The debate regarding microemulator is how it ought to behave – update the text, or restart from the right, like the Sun emulator and my Nokia phone. To that end, we’re looking for you to let us know what your phone does. Thanks!
Besides the nasty Ubuntu bug, which I was unable to do anything meaningful with, yesterday I also found a small bug in Ruby’s YAML package:
ArgumentError: time out of range
The problem is that the YAML implementation that Ruby is using, called “syck” interprets that kind of date as something that it should make a
else if ( strcmp( type_id, "timestamp#iso8601" ) == 0 )
obj = rb_syck_mktime( n->data.str->ptr, n->data.str->len );
So I did a little bit of hacking on the C code, and made it create a DateTime object instead. My fix works, although I’m not sure it’s the best possible way of tackling the problem. The patch is attached to the bug report here:
This matters because my Rails text fixtures had some dates in them that were quite old, and this was causing problems.