Introducing WP Trainer

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]

Going Gold

Finally, (almost) a week later than anticipated, RPC Heir (build 114) and RPC Rub (build 86) are good-to-go. RPC Heir’s (testable) bugs have been eliminated, which took a bit of work fixing up lastRSS to test and eliminate. However, RPC Rub behaved as expected easing that testing process. Note that there is still a ‘bug’ involved with RPC Rub’s JavaScript. This however is a “GUI” bug that won’t be noticed by most users. The long-awaited zip files should be available shortly on the WP RPC Utilities page. Have fun and enjoy.

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.

-John Havlik

[end of transmission, stay tuned]

Moo.WP Renamed

Beginning next week (hopefully), moo.wp will be archived and a new release will present itself. As of this new release moo.wp will now be known and WP-JStoolkit. This coincides with the restructuring of the moo.fx family into mootools. New features other than containing the modular mootools, will include a wp-jstoolkit.js which is editable from the admin panel. What mootools brings to the table now is a completely modular, and lightweight javascript toolkit. In previous versions of moo.fx and family, there was a dependency on prototype or prototype.lite, now mootools is completely independent of prototype, but can accept prototype style commands to retain backward compatibility. Previously when moo.wp was released, mootools was still having some compatibility issues, now it seems to be fully functional, and therefore warrants inclusion.

-John Havlik

[end of transmission, stay tuned]

moo.wp 1.0 arrives

Moo.wp, the mootoolkit manager plug-in for WordPress is now considered stable and acceptable for mass distribution. Build 30, also know as 1.0, now includes moo.dom for DOM support if the prototype.lite library is used. More updates may come with time, but as for now development for moo.wp is completed. Grab 1.0 from the moo.wp page.

-John Havlik

[end of transmission, stay tuned]

moo.wp-r2 is here

Come and get it while it’s hot. The mootoolkit manager for WordPress is available now for per-release testing. Just go on the side bar to Moo.wp to arrive at the plug-in’s page. This release is fully functional and ready for developer integration. For plug-in writers, just check for the moowp_display() function to verify that moowp is installed and working. Release 2, or rather per-release 2 contains moo.fx 1.2.3, moo.fx.pack 1.2.4, moo.AJAX 1.0, prototype.lite, and prototype 1.4.0. On the backend there are idiot-resistant checks that keep dependencies fulfilled to reduce errors. Hopefully this will be helpful for some one out there.

-John Havlik

[end of transmission, stay tuned]