Comments on: Tarski Subversion Respository http://tarskitheme.com/2007/04/15/tarski-subversion-respository/ An elegant, flexible WordPress theme Fri, 08 Aug 2008 00:08:40 +0000 http://wordpress.org/?v=2.6.1-beta1 By: Extralogical · Adding Custom WordPress Hooks http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5433 Extralogical · Adding Custom WordPress Hooks Wed, 13 Jun 2007 11:32:48 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5433 [...] Theme hooks in this mould will be a new feature in Tarski 1.5. If you want to try them out in the meantime, just check out the latest build from our Subversion repository. [...] [...] Theme hooks in this mould will be a new feature in Tarski 1.5. If you want to try them out in the meantime, just check out the latest build from our Subversion repository. [...]

]]> By: Wptr Themes http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5402 Wptr Themes Tue, 01 May 2007 22:01:43 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5402 Perfect, thanks... Perfect, thanks…

]]> By: Free Net Publishing http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5400 Free Net Publishing Sat, 28 Apr 2007 08:43:13 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5400 So far I'm using the Semiologic template on my article blog... but I found Tarski to be lean and elegant. Will give it a try. -Robert So far I’m using the Semiologic template on my article blog… but I found Tarski to be lean and elegant. Will give it a try.

-Robert

]]> By: Chris Sternal-Johnson http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5391 Chris Sternal-Johnson Tue, 17 Apr 2007 20:06:37 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5391 That's a handy tip, thanks Erik. I'd been using the command line to do it... That’s a handy tip, thanks Erik. I’d been using the command line to do it…

]]> By: Erik Scrafford http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5390 Erik Scrafford Tue, 17 Apr 2007 19:44:34 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5390 To create branches in ZigVersion, you can connect to http://tarski.googlecode.com/svn/ , create a directory named branches at the top, and then drag trunk to branches - it will ask you if you want to copy or move (you want to copy), and give it a branch name other than trunk. ;) To create branches in ZigVersion, you can connect to http://tarski.googlecode.com/svn/ , create a directory named branches at the top, and then drag trunk to branches - it will ask you if you want to copy or move (you want to copy), and give it a branch name other than trunk. ;)

]]> By: Chris Sternal-Johnson http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5386 Chris Sternal-Johnson Mon, 16 Apr 2007 04:32:13 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5386 Yeah, unfortunately, the preview isn't a live AJAX preview, so it's fairly unintelligent. It'd be great if someone coded a JavaScript live preview that obeyed the WordPress "Allowed Tags" settings without having to hit the server every two seconds via AJAX. Yeah, unfortunately, the preview isn’t a live AJAX preview, so it’s fairly unintelligent. It’d be great if someone coded a JavaScript live preview that obeyed the WordPress “Allowed Tags” settings without having to hit the server every two seconds via AJAX.

]]> By: patis http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5385 patis Mon, 16 Apr 2007 03:17:22 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5385 On a side note: comments are previewed in real time very nicely but at the end they are not displayed as originally intended. In my first comment "Subversion Book" was a link to the site, and I used bullets for my two paragraphs on tags and branches. None of this finally made it to the comment even though it was nicely displayed in the preview 8-| Lets see, this is the <a href="http://tarskitheme.com" rel="nofollow">Tarski site</a>, and this is <b>bold face</b> ... nice preview, let's see how it goes at the end. On a side note: comments are previewed in real time very nicely but at the end they are not displayed as originally intended. In my first comment “Subversion Book” was a link to the site, and I used bullets for my two paragraphs on tags and branches. None of this finally made it to the comment even though it was nicely displayed in the preview 8-|

Lets see, this is the Tarski site, and this is bold face … nice preview, let’s see how it goes at the end.

]]> By: Chris Sternal-Johnson http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5384 Chris Sternal-Johnson Mon, 16 Apr 2007 02:45:40 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5384 Cheers, Patis. I renamed tags 'releases' to be a little more self-explanatory. I'd go back and add all the versions from 1.0 onwards, but it'd be little use I'd imagine - I just put 1.2.5 and 1.4 up. Cheers, Patis. I renamed tags ‘releases’ to be a little more self-explanatory. I’d go back and add all the versions from 1.0 onwards, but it’d be little use I’d imagine - I just put 1.2.5 and 1.4 up.

]]> By: Patis http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5383 Patis Mon, 16 Apr 2007 02:36:35 +0000 http://tarskitheme.com/2007/04/15/tarski-subversion-respository/#comment-5383 Chapter 4 of the <a>Subversion Book</a> talks about branches and tags. In my opinion, for the purposes of a project like Tarski a simple way to look at these two elements is the following: Use tags to capture specific Tarski releases. For example, make a SVN copy of the subversion revision number 2 to something like <code>tags/tarski-1.3</code>. Make a SVN copy of subversion revision number 3 to <code>tags/tarski-1.4</code>. This will give you a nice history of the project and a simple way to manage releases. By the way, usually there are many subversion revisions in between tag releases; I guess you have none between Tarski 1.3 and 1.4 just because you are starting with subversion. I wouldn't worry with branches at this time. If Tarski had multiple developers you could use them to track different development streams and get into the whole business of merging branches, not necessarily a trivial exercise. For bug fixing you can adopt a simple strategy: bugs are fixed in the current release, something which I believe you have done with Tarski up until now. I see no reason to change it for now. Anyway, just my two cents. I certainly welcome the SVN repository for Tarski. Thanks for the good work. -- Patis Chapter 4 of the Subversion Book talks about branches and tags. In my opinion, for the purposes of a project like Tarski a simple way to look at these two elements is the following:

Use tags to capture specific Tarski releases. For example, make a SVN copy of the subversion revision number 2 to something like tags/tarski-1.3. Make a SVN copy of subversion revision number 3 to tags/tarski-1.4. This will give you a nice history of the project and a simple way to manage releases.

By the way, usually there are many subversion revisions in between tag releases; I guess you have none between Tarski 1.3 and 1.4 just because you are starting with subversion.

I wouldn’t worry with branches at this time. If Tarski had multiple developers you could use them to track different development streams and get into the whole business of merging branches, not necessarily a trivial exercise. For bug fixing you can adopt a simple strategy: bugs are fixed in the current release, something which I believe you have done with Tarski up until now. I see no reason to change it for now.

Anyway, just my two cents. I certainly welcome the SVN repository for Tarski. Thanks for the good work.

–
Patis

]]>