Here 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]
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]
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.
-John Havlik
[end of transmission, stay tuned]
Today, the birthday present from my parents arrived, a Garmin Forerunner 305. Someone on the track team, during my senior year, had one of the old 101s that weighed three times as much and are twice as big. But, despite its size it worked well. In fact, it worked well enough for the cross country coaches to purchase two 201s for the use of the team for keeping track of distances ran, instead of those running wheels. That’s where the idea to get it for me came from.
The 305 includes a heart rate monitor and records it along with time and other various stats during a workout. I have yet to try it out but tomorrow I’ll take it for a test run. Tonight, I charged it and installed the Garmin software, which defiantly feels lacking. What is good about it though is data exporting, and with that a WordPress plug-in will be made for keeping track of runs. Naturally, this won’t be available for some time, but it will be a free and powerful alternative to MotionBased.
WP Trainer will first work with the Forerunner series training GPS, but eventually support for the iPod + Nike setup, which is a really neat setup and defiantly less expensive as well. iPod + Nike has one drawback however, as it is not a GPS system, route tracking will have to be manually done by the user. With the Forerunner units, uploading the exported data should allow an auto generation of a path overlay on top of Google maps. Since I do not own a iPod or the Nike + iPod Sport Kit this setup will not be the emphasis of this plug-in (initially that is, I’m sure I’ll have access to the needed equipment when the time comes). More details will be revealed as I begin to implement things. This blog will be the test bed for this plug-in so if things get flaky that probably is the plug-in.
-John Havlik
[end of transmission, stay tuned]
After a brief absence due a hardware failure, Weblogs.us is back. A slue of new hardware accompanies the return. From this time forward service outages should be rare (unless someone gets Dugg).
JD installed a new 8 core Woodcrest server with 8GiB ram for the new Apache/PHP/file server, and the SQL server was replaced as well. Since some nasty traffic was making it to the old Apache server, a dedicated hardware firewall was installed a good thing all around as the bad traffic was at times taking up to half of the network activity. Look forward to some more interesting updates here as some projects wrap up and the semester winds down.
One final thing, Happy Birthday James (jmweirick)! (This may be off by a day or so)
-John Havlik
[end of transmission, stay tuned]