¡Acebo ideomas diversos Batman! Si mi Espanol es un poco malo ahora, lo siento. With this new version many of the problems involving languages other than English should be resolved. A new filter at the end of the plug-in should hook into the WordPress Polyglot plug-in. Full support of the gettext localization standards used in WordPress has been added for the Administration interface. The documentation was not very clear on how to implement it, so it may or may not work, if someone can let me know if it works or not, or has worked with this system before and can help get it working that would be appreciated. Improvements over the old 1.x branch of Breadcrumb Navigation XT include hierarchical category support, rewritten core that should be easier to maintain, and total removal of custom wpdb queries. Keep in mind that this release is very much like the KDE 4.0 release. Some features may still be broken, and I’m planning subsequent bug-fix releases as bugs are reported.
There is a new, and separate page for Breadcrumb NavXT, file all bug reports in the comments of that page. The documentation is not ready yet, however the old Breadcrumb Navigation XT documentation should cover the bulk of the features in Breadcrumb NavXT.
It seems when I was playing around with Compiz, Compiz-Fusion, Emerald, and Avant Window Navigator, something in Gnome broke, now nautilus won’t load. I did however get some work done on Breadcrumb NavXT. Nautilus was not the only thing broken, poEdit broke as well. With poEdit broken I could not produce the .po file needed for the localization of the administration interface. Thus, I had planed on releasing something last night, which will be pushed off until tonight. I can’t say if it will be 2.0.0 or RC 1, right now I’ll refer to it as RC 1. I’ll do an actual release tag in the SVN for this release, and hopefully it will work nicely with the plug-in update notification built into WordPress 2.3.
One last word on RC 1, I know some documents may have stated that there will be uninstallation support for it. Since I in particularly do not like the current plug-in for doing that, I’ve decided to wait until WordPress decided to include it into their API (where it belongs I believe). What I don’t like about the current method is that it adds more work on the part of plug-in developers. The developer should not have to register with a separate entity the wp_options that it sets. Any of the values set using the set_option method should automatically register to the generating plug-in, as should any new entries created by update_option. Then the uninstallation part would be occur after the plug-in is deactivated, an uninstall button should pop-up, which will remove all of the DB entries used solely by the plug-in. The only entities that should have to be registered is any custom db tables created by the plug-in. Thus, 2.0 will not support this, and I will wait until things mature a bit before adding support in a future version of Breadcrumb NavXT which will correspond to the release of WordPress 2.5.
Beginning at approximately 6:00PM CST this blog will be undergoing maintenance and may be down, broken, or some combination of the previous two states while maintenance work is done. Normal operation should resume by 8:00PM CST.
Break has been busy, That “little” project from before the semester began is consuming most of my time now. Grades finally came in, made the Dean’s List, third semester in a row. With that semester behind me, things should be getting better from here on out.
My ZEN gets much better battery life than my Zen Micro does now, it about a 3:1 battery life ratio. In the office I’m getting about 2 to 3 days worth of continuous music play, which equates to about 20 hours, add in the hour of Family Guy videos that I watched, I’d say the 30 hour estimated life for audio is achievable. The Micro was giving me fits while on campus, not even lasting the full day on the longer days near the end of the semester (cold weather was partially to blame).
Speaking about that “little” project, coming soon will be a list (yeah I know lists suck) of bad programming practices and why you should never follow them. Let’s just say words can not describe my hatred for global variables in C/C++ that has been aroused by this project’s old code. If you excessively use global variables you should be shot, plain and simple. I hesitantly give thanks for Visual Studio every time I come across one of these globals (the find all references command is very useful when it works), without it things would be taking much longer than they already are.
Originally the concept was to be highly modular, allowing for flashy yet quickly loading design. This concept still has yet to be met, mainly due to a lack of time. Blu-Berry, a rather bastardized version of the vision for Berry, remains the incomplete theme powering this blog. Its introduction was a stop gate measure as WordPress 2.1 had some changes that broke the blog with the theme it replaced. Some have inquired on the link to download the theme. When the time comes Berry will be released to the masses.
Despite the incomplete implementation of the vision, I admire Berry (sounds awkward doesn’t it?). When messing around with a few of the images for the holiday season, with the transparencies and such, the thought crossed my mind about the future of this blog and what it will look like for the majority of next year. Nothing new will surface until the end of April, but a three column layout may not be out of the question. Those ugly “date badges” will receive much needed tweaking.
The crib will undergo some much needed organization in the meantime in preparation for changes present in the next Berry. Its a big task, and between other projects time for doing such things is scarce at best.