Chris did all the hard work on this release, so credit for the new features goes to him. Widget support is probably the most exciting addition, but there are some less glamorous ones that ought to be just as useful.
As always, let us know if you run into any problems using the theme.
Image classes
Image classes should allow you to include images in a reasonably elegant fashion, without having to write your own additional styling code. Admittedly using image classes does require adding a smidgen of code when you post an image, but it’s very minor, and should make your pictures look as good as your words.
Widgets
Widgets are basically drag-and-drop code blocks that let you include various things like text, blogrolls, feeds and so on in areas of blog pages set up to allow them. There’s some documentation on using them with Tarski here.
Currently you can only add them to your sidebar, but we plan to overhaul various bits of the rest of the theme to allow them to be added (or removed) in other places, such as the footer. Chris didn’t think much of the default links widget, so he made a new one.
Miscellany
A rudimentary print stylesheet has been added, so if you print out a page from a blog using Tarski, it should be a bit more readable than previously. The print stylesheet eliminates all the redundant page data like the header, the sidebar and the footer, leaving just the important bit—the content. Additionally, per a user request, you can now enable comments for pages should you wish.

27 comments
May 18, 2006 at 2:21 am
Pingback from ceejayoz.com · Tarski 1.1.2
May 18, 2006 at 9:53 pm
Pingback from Rumore · Tarski 1.1.2 is widgetable
May 19, 2006 at 3:45 am
Pingback from La Biblioteca E(c)léct(r)ica » Fancy Tooltips, Tarski Theme y King Links
May 20, 2006 at 2:34 pm
Pingback from Jesper.thusgaard.com · New theme, with Widgets
May 23, 2006 at 5:24 pm
Pingback from WordPress Widgets » Blog Archive » Tarski
May 23, 2006 at 9:32 pm
Pingback from Tarski · Now Previewing 1.1.3
May 18, 2006 at 3:21 am
ceejayoz
Enjoy!
May 18, 2006 at 6:11 am
Philip
hey guys thanks! in the next release is there able to have sidebar asides as an option?
May 18, 2006 at 8:30 am
Michael Camilleri
Great theme. I’ve been messing around with Taski a bit since first installing it. A change I just made today was changing the doctype to XHTML Transitional rather than Strict. The reason for this is not the fault of you guys. It’s that Wordpress still uses tags such as <strike> that have since been deprecated and will allow such tags in comments, etc. I’m not sure what you think about it (since all your code does validate just fine) but thought I’d pass it along.
May 18, 2006 at 10:28 am
ionfish
To be honest Michael, anyone who’s bothered enough about it validating with deprecated elements like
strikeis, like yourself, probably savvy enough to change the DOCTYPE without too much hassle.I don’t suppose you happen to know why WP uses
strikerather thandel, do you? I never use the WYSIWYG editor, or even the little element-inclusion shortcut buttons, so I tend not to notice things like that.May 18, 2006 at 11:35 am
NK
Downloading
May 18, 2006 at 11:38 am
monkeypup
wahoo!
May 18, 2006 at 12:49 pm
ceejayoz
Philip, probably not - I believe there’s a widget for that.
May 18, 2006 at 12:52 pm
Philip
ok, i’ve been using K2 up to a few days ago and it would be nice if i had a choice, but whatever. I really like the new color on the hovering that is used here.
May 18, 2006 at 12:54 pm
ceejayoz
Philip, like I said, you do have a choice - there’s a Widget for it.
A bit of Googling turned up Sideblog.
May 18, 2006 at 12:55 pm
soop
Fanks guys, I appreciate the time you spend on this :)
May 19, 2006 at 7:38 am
monkeypup
Finished customizing the latest version. Take a look and let me know what you think.
http://monkeypup.com/
I love the new functions. I’ve added the img classes to my quicktags buttons, so it’ll never be an issue of remembering code.
This time around, I made sure to use constants.php and a new style sheet, so I will never have an issue with upgrades to the theme. This is a pretty innovative idea, and I love it.
Great work, as always.
Thanks!
May 19, 2006 at 11:43 am
wuti
great!!
May 19, 2006 at 1:35 pm
ceejayoz
Looks good, monkeypup.
Any chance you could post how you added the image classes to the quicktags?
May 19, 2006 at 2:19 pm
monkeypup
Anything for you, C-Joz!
The file that controls the quicktags in the posting screen can be found in /wp-includes/js/quicktags.js/
In that file, you’ll see all sorts of code, followed by a long section that has blocks of instructions that look like this:
edButtons[edButtons.length] =
new edButton(’ed_em’
,’i’
,’‘
,’‘
,’i’
);
That one, for example, produces the “i” button that makes text italicized. To add a quicktag, just add a new block between two others. Here are the ones for the image alignments:
Align Left
edButtons[edButtons.length] =
new edButton(’ed_imgleft’
,’imglft’
,”
,”
);
Align Right
edButtons[edButtons.length] =
new edButton(’ed_imgright’
,’imgrt’
,”
,”
);
Image Block
edButtons[edButtons.length] =
new edButton(’ed_imgblock’
,’imgbl’
,”
,”
);
Image Link
edButtons[edButtons.length] =
new edButton(’ed_imglink’
,’imglnk’
,”
,”
);
The above will add buttons labeled the following (abbreviated to make room for the other qtags) into your posting quicktags:
imglnk, imgbl, imgrt, imglt
When you have an image to post, put the link in the post body. Highlight it, click the appropriate button, and voila!
May 19, 2006 at 2:33 pm
ceejayoz
Hoping WordPress didn’t rip out some text there… looking at the e-mail, it doesn’t seem to have.
I’ll give it a shot. Cheers!
May 19, 2006 at 2:34 pm
monkeypup
crud. the comment edited some things out..
Here’s a copy you can have to replace your own file with. If you like.
http://monkeyverse.org/quicktags.js
May 19, 2006 at 3:37 pm
Anthony
Thanks for the updated version, Quick Question is there a way to add the site Tagline to the header without jumping into the Header file? I want it to appear below the Page links but above the content.
May 19, 2006 at 3:48 pm
ceejayoz
There isn’t a way to do that in the current version, no. Might add that to the next version…
May 19, 2006 at 4:44 pm
ionfish
It’s on my to-do list for the next version already, forgot to do it this time round.
You can see roughly what we’re planning to add or change in the Roadmap.
May 23, 2006 at 12:40 am
Michael Camilleri
I think they aim to fix it for the 2.1 release but I’m not sure why it’s still there. I had a quick look at the code to see if it was something simple to fix but analysing the WYSIWYG editor looked like it required a little more than the 5 minutes I was prepared to give it. I guess it’ll be fixed soon :)
May 23, 2006 at 1:40 pm
ionfish
Hrm, ok. Thanks for looking into it Michael, much appreciated.