Thanks to those of you that viewed my themes today. I should really set
up Trac using something other than plain old CGI so it doesn’t take such
a long time to load the pages.
I’m not sure what versions of Typo my themes work with, but it sounds
like we’ll find out soon.
I like the idea of one subversion repository for multiple themes, and I
think we can easily manage having one repository for multiple versions
of Typo as well. We can set up the theme repository just like the
actual Typo repository, and then themes will show up where they behave
As an example:
So in the above example, a_theme and b_theme work with Typo trunk and
the 2.6.0 release. We see that b_theme is pretty new, and there is no
version of it that works in Typo 1.6.7.
And that’s where I can learn about twill to do some automated theme
testing. Each night that a commit is made to Typo we can have a process
that updates to Typo trunk and automatically cycles through each of the
themes in the theme repository trunk checking to make sure that there
are no horribly obvious errors.
We can then use the repository, each theme’s about.markdown file, and an
automatically captured screen shot as the basis for a self sustaining
I’ll be happy to shift the focus of my existing subversion/Trac instance
from my own personal themes to being more oriented as a central
subversion repository for anyone who wants to use subversion for their
themes without going through the hassle of setting up subversion
How does that sound to you, Uzair? Is this what you had in mind when
you mentioned an SVN repository for themes?
Is there anything glaring that we haven’t covered? If there is no
disagreement then I’ll get the Trac sped up and create the appropriate
tags/branches in my repository to support the various Typo versions.
Other next steps?
I’m running 5 Typo instances on my server now, so I’m certainly eager to
see it flourish.
I have mirrored all of the themes from the contest site (that weren’t dead links) and am putting together a crude navigation once I weed out all the lost themes then I’ll share them here, and if it’s cool, move them to your svn server. I just didn’t want to do much until they Typo Theme folks did, I neither want to reinvent the wheel or step on toes, but I see a need and want to give back, plus after 5 months I think the time to move is upon us. Let’s get svn up with either sep repositories for 2.6.0 / trunk / 4.0.0 or paths, this way the ones working in trunk should migrate to 4.0.0 right when or after it comes out, giving folks trying out typo a simple way to get new themes. Heck, if they weren’t distributed with Typo we could have a script with 4.0.0 (within the admin GUI would be sweet) that says, “Update all themes” which would issue a svn checkout command with a tag just for 4.0.0 themes and checkout new themes and update the ‘old’ ones in one fell swoop! Now th
- Constant Integration server notices
up-to-date. In the case of themes that are no longer being actively
chasing authors about approvals.
Subject: Re: [typo] Themes site
has put together a theme directory.
Typo-list mailing list