Vista, Ha! No, Thanks.

Currently Windows only serves one purpose that Linux cannot. Think about it for a while. The only thing Windows does better is gaming. For the past 5 days, I lived without Windows.

There was a method to the ‘madness’, though something crapped out on me (ATI’s display driver) that just set me back a week. Luckily, I now work off of a 20GiB USB hard drive for anything important (work), which is good for when a system goes bonkers. In the process I realized two things:

  1. I really need a wide screen monitor.
  2. Having a laptop or some other powerful computer combined with my current setup would be nice.

Honestly, the realization of needing a wide screen monitor came earlier, but with the multiple desktops Gnome and KDE have, switching between them was fine, but it would be nice to fit Aptana and Firefox side-by-side for the benefit of testing. I’m just waiting for the ones that can fit 1080p HD video plus the taskbars to drop in price—one step down in resolution saves 300 USD. As for having an additional powerful computer (ideally a much more powerful one) so that I can have two separate computers, one that only runs Gentoo for work and daily use. Leaving the other open for playing games, and probably running distcc to aid in compiling for the other.

-John Havlik

[end of transmission, stay tuned]

Bug Squashing

A certain reboot day rapidly approaches, and for the first time I am ready. In reality there are dozens of little bugs to fix and tuning to do, but for the most part things are falling into place for the new theme, berry. Right now nothing should be horribly broken, but there are no guarantees. Things happen, and when a theme is built from scratch (or nearly from scratch, currently the comments file is K2’s with modifications) bugs may exist.

Not much will change in appearance on the 1st of May except the application of the official mtekk ‘branding’ (read as the m logo appearing in the header). However, depending on how things go, and open beta may begin for blu-berry. Should the beta not become public on May first do not expect it until the middle of the month as the are a few more pressing projects that need attention.

-John Havlik

[end of transmission, stay tuned]

Welcome to the party

Mtekk - Welcome to the partyHere comes the fun part: Berry is going Alpha. Rather, the completed parts are now running this blog. The primary reason for this steams from the old theme’s incompatibilities with WordPress 2.1. Hopefully by the end of the weekend things will not be broken anymore.

edit: I never finished the theme yet so comments are broken among other things (e.g., IE6 and its padding issues).

-John Havlik

[end of transmission, stay tuned]

Not Again

Sorry I blew it this year, due to the school work load I 100% forgot that today is the second annual CSS Naked Day. It took browsing a blog and seeing that its CSS was missing but it was not facing the effects of Digg, and it dawned on me. The other too bad thing is that this blog has had the same skin for over a year now, it is time for change. But change takes time, especially when you are building a theme platform (inspired by K2, but it is not K2) from the ground up. That is all I’ll leak about one of my many projects, and I’ll leave you with a verbatim copy of my CSS Naked Day post from last year:

For a full 48 hours, while somewhere on earth it’s April 5th this blog will be separated from its lovely CSS file. This is about standards, not retarded Digg users, along with some ignorant Newsvine users. This day is to educate those web developers that don’t write code to conform to standards, which is a bad thing. Don’t even think about starting an AJAX/Web 2.0 project if you don’t plan on using web standards, otherwise bad things will happen.

Here is the link: CSS Naked Day

-John Havlik

[end of transmission, stay tuned]

Forerunner

Never trust the weather forecast, very rarely is it correct. Today, day number 5 or 6 in the rain-a-thon that we Minnesotans have experienced turned up fairly dry. The sun even managed to peak out from behind the clouds a few times today. Thus, at 47 degrees and mostly cloudy, today was the best day for running in the past several days. Seizing the opportunity to try out the birthday gift from my parents, I went for a quick 20 minute run.

It turns out, if I had done an out-and-back of my route, I would have covered 3 miles. I did not realize that the start lap button must be pressed before the Forerunner will record the run, I ran over a mile before figuring that out. Hence, the GPS recorded 1.72 miles but the actual route was more on the lines of 2.72 miles according to walkjogrun.net (a very cool site by the way).

The GPS is not sensitive to running under power lines, which is good, but I can not say the same for the heart rate monitor. From the get-go it said I was at 100BPM or higher (not even close to resting heart rate). Most of the time it though I had a heart rate near 190BPM, and for a good stretch of time it was at 204BPM. Doing quick math, 204BPM is near to what my max heart rate should be. This high of a heart rate is not possible to sustain for extended periods of time with out heart failure. According to this, I should have collapsed during my run. After the run I did a little pulse vs. heart rate monitor and found it off by nearly 40BPM. For one moment I was able to get it measure an accurate heart rate of 74BPM at rest, it then spontaneously jumped to double that. The heart rate monitor will need to be figured out eventually, but for now every thing else works.

When just looking at the Forerunner, it looks a bit awkward due to the L shape of the body that wraps partially around the arm. When running that oddity makes sense, as the GPS antenna is located in this part and the way human arms move when running this part of the GPS is always facing the sky. The weight of the Forerunner, which is not that high to begin with, is transparent while running. Design wise, Garmin did their homework with this GPS and created a very nice product.

The feature lacking Garmin Training Center (GTC), which allows the transferring of data to and from the GPS, is basic but useful. GTC creates nice graphs and has data/lap view and statistics. Its mapping is practically useless as at anything under 1 mile = 1 inch scale is considered over zoom and has literally no local roads, what it does do though is plot your course on the map accurately. Hands down, the best feature of GTC is the import/export data options. Data output is in a nice XML formatted document, which will make life easy for me when writing WP Trainer. With this one run and the data from it I will be able to begin writing WP Trainer as no “hacking” of the export files will be necessary, and my experience with RSS will really help here as both are XML documents.

The Good:

  • Fits well
  • GTC software exports a XML formatted document
  • GPS locks in quickly after initial region discovery, even locks in when indoors in some cases
  • Accurate even in non-ideal conditions
  • Software and firmware updates are easy
  • Not-evil software, easy to disable windows tray icon

The Bad:

  • Had to install a firmware update for the new day light savings time
  • Heart rate monitor is inaccurate

The Ugly:

  • GTC software maps leave much to be desired, Garmin could learn a lot from Google Earth

-John Havlik

[end of transmission, stay tuned]