Since the original author of Breadcrumb Navigation XT ran out of time for further development of the WordPress plug-in, I have picked it up. After a few days of coding and working on setting up the code section of this blog, the new version is ready for release. This new version, 1.8.0, includes support for author pages, and limiting the number of categories displayed in the breadcrumb.
Note that beginning with this release the version numbering scheme is to follow the same as WordPress uses, the first digit changes for major changes and as the second runs past 9. The second digit changes with the addition of features, internal structure of the class will not change in with a change in this digit. Finally, the third digit signifies a bugfix to features previously introduced without any added features. The next version, 1.9, is planned for the release of WordPress 2.3 due to the addition of tags into WordPress.
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.
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).
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.
What this means for the progress of the Weblogs.us website is that we could launch Monday. lCards won’t make the launch, and it’s better that way as more data is needed to implement it correctly.