The first (and hopefully only) release candidate for the latest K2 is up and about, and it’s a milestone.
Tag Archive for 'k2'
While WordPress ships with jQuery, it’s often a few updates behind the latest version. Since jQuery 1.4 is just out, I wanted to use it with K2. That in and of itself is fairly easy, and a simply matter of deregistering the ‘jquery’ script and registering a new one. While looking for a proper solution I came across this rather crude way of going about it quite a lot, and it’s a horribly way of going about this, and will (and has probably) undoubtedly result in old plugins and themes blindly overwriting newer version of jQuery with their own, once new hotness, now old and busted version of jQuery.
Ugh.
This PHP code snippet checks to see if the passed version is later than the one currently registered, and makes sure we’re not in the admin (just to be sure).
If our version is indeed newer than the one currently registered, we go ahead and grab the idol… eh, swap jQuery’s.
/**
* Register a later version of jQuery if it’s later than the one currently in WordPress
*
* @param {String} our_version The version of jQuery we want to upgrade to if needed.
*/
function upgrade_jquery( our_version ) {
// We want to use the latest version of jQuery, but it may break something in
// the admin, so we only load it on the actual site.
global $wp_scripts;
if ( ( version_compare(our_version, $wp_scripts -> registered[jquery] -> ver) == 1 ) && !is_admin() ) :
wp_deregister_script(‘jquery’);
wp_register_script(‘jquery’,
get_bloginfo(‘template_directory’) . ‘/js/jquery.js’,
false, our_version);
endif;
}
add_action( ‘wp_head’, upgrade_jquery( ’1.4.1’ ) );
It sure would be neat if this was built straight into WordPress’ wp_register_script.
I’m lucky enough to have force-fed myself enough roleplaying games and science fiction comics to have picked up English to a level where I’m often more fluent in it, than I am in my mothertongue. And for the purposes of of blogging about those two particular subjects, whatever grammar, puntuation and structure snafus that happen to find their way onto this blog are less a real worry than they merely distracting (and at times embarrassing).
But if one were to take writing more seriously, be it for personal, academic or straight-up professional reasons, a friend of a friend of mine recently started a site that’ll do just that, hassle-free.
I don’t generally plug things on this site unless I truly like them. And until I tried Wordy, I honestly didn’t know what use I could have for it. But listen, Wordy gets it.
It’s on-demand copy-editing, and it’s ultra slick. No hassles, no clutter, no crap. I took it for a test-run on a chapter from a book another friend of mine is writing, and the experience couldn’t have been better. If for nothing else, you should check it out just to marvel at the elegance of how they’ve set up the site and how clear their process and goal is.
Particularly interesting to some of us, is that they’re working specifically on a WordPress plugin, which should make it even easier to use. They’ve also got a blog (in Danish).
Now if you’ll excuse me, I’ve got some K2 code to clean up.
Even though I intended to blog some more over the holidays, I instead spent most of the time glued to the computer working in various capacities on K2.
I feel I squandered the trust of the community, by having been too casual about K2 in the past. K2 has been first with a whole bunch of features and functionality, we had a rather large and very active community and a solid codebase, yet mostly due to me having other priorities it’s atrophied somewhat.
The good news is that we put out our 1.0 and subsequently our 1.0.2 over the holidays.
And the great news is we’re already up to having nine languages1 in our new localization repository which puts us well on our way towards the 1.1 release which is of course geared towards localization. We’ve got some pretty cool ideas in the pipeline for the roadmap after that, but more on that later.
Meanwhile, it’s been a while since I did any web design of significance, and I think I’d forgotten a little bit how fun it is (as long as Internet Explorer isn’t invited to the party that is). This has also meant getting reacquainted with the tools of the trade, old and new, and where I used to use TextMate for pretty much everything, I tried switching to Coda (I had a license, even though I’d hardly ever used it), and I’m now a full convert. Those Panic guys know a thing or two about software.
Cinch is another little app that’s been making my life a lot easier, especially since Chrome for OS X still doesn’t have the same functionality that the Windows version has had for a year or more, and since Apple refuses to acknowledge the need for a maximize button.
Now if only I could find a great app for resizing windows in a sane manner.
It took long enough, but K2 just went 1.0. Oh what a feeling. Now to get the localization effort in a row and ready for 1.1.
K2 has been a fun project for a number of reasons, but most of all I’ve been happily surprised at how the entirely lax and cell-like development process has worked out. I recently picked up the reins again and started going through our bugs, weeding out where I could and organizing what was left, in an effort to get to a 1.0 release as soon as possible. So now’s the time to tell us if something’s broken or missing.
Read more over at the K2 site.
I’m sorry for this past week’s permission-problem-outage, but despite having vacation, it’s been everything but quiet around here. And before we get on to other business, let me just take one more opportunity to congratulate Rasmus and Anna-Vera on their wedding this weekend, it was fantastic!
New K2 release, updating this and that, here and there. I recommend getting it if you’re a K2ian.
Yeah, so I’m still at home, eating oat meal and yoghurt very slowly. Very carefully. Which by the way, for those of you keeping track, means I missed out on the burgers at work today. Which sucks, because they are legendary burgers. And free.
Anyway, it does give me an opportunity to mindlessly check my feeds when I’m not feeding myself with painkillers. And as luck would have it, Prototype 1.5 was released today, complete with a new site and brand-spanking new documentation! Shiny!
I’ve already updated our K2 SVN repository, which by the way is as near as I can tell ready for the imminent release of WordPress 2.1.
Fixing the broken AJAX (file-name mismatch) and a batch of other bugs from the bug tracker, r157 is now available from the usual place.
And on a related note, Dave has updated his FlickrRSS plugin to v3.0, which K2 of course supports.
And let me again chime in with a plea: If you encounter any bugs or if you’re planning on doing something with our code and there’s some way we can help you by making changes to the core, then please, let us know. The easiest way is to file a bug report, which you can be certain we look at, and then we’ll take it from there. I’ve already helped several people who’ve requested minor changes to the code, to make it easier for them to create their custom styles. And now is the time, before we get too close to the final release.
As usual, support questions, tips and tricks, general shenanigans and the talk of fairies go in the support forum.
Update: Fixed the missing authors on entries in r157.
We won’t be able to deliver to you a 1.0 before the new year, as I had promised. But that’s okay, because I’m pretty proud of this Beta Two to be quite honest. It has seen some significant strides lately, and by and large I consider it a very stable product.
For Beta Two, there’s a new button in the options panel, which lets you quickly and easily set the options of Arnaud’s Extended Live Archives, try it out. Also, you’ll notice the inclusion of several Fam Fam Fam Silk Icons, which I personally love.
Chris went into some of the javascript files and bled them down to the bare essentials, and I finally got around to putting the ShowUtils and HideUtils functions into their own file (k2/js/k2functions.js). You may have noticed those two functions showing up in pingbacks and trackbacks all over the place; well that was my fault, and I’m really sorry. I hope Matt and the guys do something about it in Kubrick for 2.1.
There’s lots of other stuff as well, most of which you probably won’t notice, but trust us, it’s better.
If your favorite bug remains unfixed, head on over to the bug tracker and submit or resubmit a bug report, and you can be sure we’ll check it out. As usual, many tips and tricks can be found in the support forums, where you can also share your customizations and check out other people struttin’ their stuff. For a little taster, check out “Tauquil’s offering”:http://tauquil.com/.
So from Chris and I, a happy new year.
Download K2 Beta Two (for WordPress 2.0)
Revision 156
So I’m looking at Symphony, a new CMS of sorts, and I almost choke on my own spit as I read their header. I’m sorry guys, but I’m going to have to call you on your hyperbole:
Bull. Shit.
Were it up to me, K2 would’ve been out of my hands a long time ago. And of course, in a sense it is (or were) up to me; but I just haven’t had the time / motivation to get it done.
Until now.
Please welcome ‘Vader’, a K2-based ‘design’ (not that I want to inflate the word ‘design’, but ‘color palette’ is a bit weak, yes?), which will help me bring Binary Bonsai up to speed as well as test among other things the pages functionality in WordPress. Should you wish to see Freya, you can visit her in the detention area.
The fundamentally largest change from Kubrick to K2 is in how the template deals with plugins. For a while Kubrick shipped with a few plugins and some scruffy code, which people could uncomment if they wanted plugin support. Bad mojo.
K2 automatically detects a range of my favorite plugins out of the box, and will upon detecting set them up for you, no hassles. I try to keep an eye on the whole plugin market, but feel free to mail me about your favorite plugins so that I might give them a spin.
Also, K2 will have a configuration file in which you can toggle between two-column or single-column layout, as per popular request.
Other than that it’s getting some nips and tugs here and there and all around; oh, and it is now entirely CSS driven. No more images needed