Welcome to klargodut.com, the place on the web where I try to express my artistic domains in computers and everything around.
Follow me on Twitter: @klargodut
Welcome to klargodut.com, the place on the web where I try to express my artistic domains in computers and everything around.
Follow me on Twitter: @klargodut
This is mostly valuable to us Swedes who live in Gothenburg and around, but I'll take it in English anyway.
At vasttrafik.se, Västtrafik has a great autocompletion mechanism that uses AJAX to find the stops you are interested in while planning to travel. However, they haven't included the attribute to turn off your browser's own autocompletion mechanism.
Luckily, I found a userscript that fixes this. All I've edited is the URL matching filter, so all credits to David Dahl.
Get it here:
Disable autocompletion on vasttrafik.se
Last update: 2009-03-07 22:38
After reading this entry: Browser benchmarks 2: even Wine beats Linux Firefox, I decided to test it for myself. These were my results:
All in all, Firefox on Wine on Ubuntu feels more snappy than Firefox on Ubuntu. I'm going to stick with it for a while and post any glitches I find here.
These tests were done with Firefox 3.0.7 on Wine 1.0.1 on Ubuntu 8.10 and Firefox 3.0.7 on Ubuntu 8.10, respectively.
I tried the latest Wine from here, but found that version 1.0.1 from the Ubuntu repositories worked better for me.
I have done some extensive modding of my binary clock for a more appealing look! Check in this image gallery!
Last update: 2009-03-07 22:42
This is an active list containing what extra applications and custom settings I have installed on my Ubuntu (8.10) machine in case of a computer crash and in case you are interested. Tips and comments are welcome!
This is an active list where I am listing the Firefox extensions (and Greasemonkey scripts) I am currently using, in case my computer would crash on me and I would have to find them all again. And in case you are interested, of course!
Using only nine pins for output compared to the twenty pins used in version 1.0, my binary clock 2.0 is far more advanced both were it comes to the wiring and the coding.
It could have been done using Charlieplexing and only five pins, but that would have made the code much more complicated.
I'm currently considering getting rid of the three time setting indicators at the bottom and blinking the selected column instead. This will probably be the case in version 3.0, which is to be built as a watch.
The first version of my binary clock, where each LED has a corresponding pin on the PIC. The yellow cords to the left should connect to three buttons.
The PIC is a PIC16F887, which is a slight overkill for a project that uses 20 output and 3 input pins, but I wanted to be sure that my first project would work.
The next version will be built on a PIC16F630, which is about a sixth of the 887's size.