We’re now running WordPress 2.5 here, so as you can see, Tarski seems to get along with it fine. If you run into any issues with 2.5 and Tarski, let me know. Tarski 2.1 should be out in the next week or so, I still need to iron out some upgrade issues but it’s basically done.
You are currently browsing articles tagged roadmap.
Just published an article over on Extralogical about adding custom hooks to WordPress themes, which might be of interest to the theme authors amongst you. It also offers a little preview of how the new hooks system in Tarski 1.5 will work.
I’ve updated the roadmap with some more information on the changes that will appear in the next version of Tarski.
Bugs bother us, so when they’re brought to our attention, we do our best to fix them. Tarski 1.2.3 is mostly a bug-fixing release, but I’m happy to say it comes with some new features too, albeit not of our making: two new translations, into French by Matthieu Mauduit and into Danish by Henrik Buchwald. Many thanks to both of them for their hard work.
The changelog is briefer than usual, but I like to think this is a good thing: there were fewer things to fix. A couple of them could have been classified as ‘tweaks’, specifically the Internet Explorer issues, but since they broke the proper display of some elements in that browser it seemed more accurate to call them bugs.
If we receive more translations before the next major version comes out, we’d be happy to release another iteration of the 1.2.x branch. All the details, as ever, are on the localisation page. It’s great that Tarski is now available in five languages (other than English), but we’d very much like to add to that. Various feature additions and amendments are planned to improve matters still further on this front, but if you have any suggestions don’t hesitate to post them on the forum.
Thanks again to everyone who’s helped us out with Tarski, particularly those who’ve contributed translations and brought bugs to our attention, and I hope you enjoy using Tarski 1.2.3.
Bugs and suggestions should be posted on the forum.
Tags: 1.2.3, bugs, changelog, community, compatibility, download, features, localisation, release, roadmap, translations, WordPress
As part of our continued efforts to make Tarski completely amenable to localisation, we’ve just fixed a few lingering issues such as the comment number text and the edit links, which until now couldn’t be translated without altering the core Tarski code.
An updated POT is now up. I know this has been frustrating our translators so it’s cheering to finally have a fix. If there are any other bits of text that aren’t yet localisable, please let us know in the forum or in the comments on this post.
In addition to this, we’re still looking for more translations for 1.2.3, so if you’re able to translate Tarski into another language (that hasn’t already been covered by someone else) please get in touch.
Tags: 1.2.3, bugs, community, localisation, roadmap, translations
As I mentioned in my previous post, my website’s theme broke the WP admin panel, so until Chris and I figure out what’s going on, I’ll be running Tarski. Since 1.2 is not a million miles away from finished, I thought I’d upload that and use my site as a sort of field test to iron out bugs—I’ve already caught a couple. Hopefully we’ll iron out the biggest issues over the weekend and get a Beta copy out to our testers. We’ll keep you posted.
Honestly. Real life (and paid work) just took the reins for a bit; you know how it is.
Chris and I hope to get back to working on 1.2 shortly—the frontend code is all there, we just need to finish up the new options page, tie it into the new loop code, and test it. We’ll keep you abrest of our progress.
We’re still dealing with support queries on the forum, so if you have a Tarski mod or custom style you’d like to show off, or just need some help sorting something out, drop by and give us a shout.
The roadmap has been updated to give a more accurate and complete picture of what’s going to be in 1.2, but I thought I’d write up a brief summary of where things stand and where we go from here.
Firstly, I’ve rewritten a fair amount of the CSS, to make it more flexible and extensible. Content areas (such as entries, comments and so on) are now denoted by the content class, while the two columns are referred to by primary and secondary classes. This replaces a large and disparate set of classes and ids, making the code cleaner and easier to extend and modify. Additional stylesheets, for example, should now be much easier to write.
Secondly, Chris has been working on the Tarski Options page, cleaning it up and improving it substantially. We hope that the new version will be easier and more intuitive to use.
There are also the usual raft of tweaks and improvements, including the much-requested pagination and next/previous links, better trackback and language support, and a new and improved loop.php file which should make modifications based on the Tarski code much easier to implement.
1.2 beta test
Because there are such substantial alterations to the code, we want to run a small test before releasing it publicly. Sign up for the 1.2 beta on this forum thread.
Beta applications are now closed.
Tags: 1.2, beta test, customisability, features, forum, modifications, roadmap, theme hooks, themes, tweaks
We only released 1.1.2 last week, but 1.1.3 is almost ready now—this blog is running a preview version. As you can see, the Asides look a little different, and the site’s tagline is being displayed below the title.
The roadmap gives a fairly good idea of what else will be included in the new release when it comes out, later this week.