I've already submitted a theme (albeit, not a very good one). It's not up yet, so there are definitely more than the four showing currently.
Regarding versions, I agree with those that have suggested better theme code makes for better themes. There is nothing preventing themes already created from adding or revising with the new code. P.S. My blog (http://akau.homeip.net) is not currently running on my theme. It's an implementation of a Wordpress theme. > Date: Mon, 7 Nov 2005 18:38:36 -0800 > From: Scott Laird <scott at sigkill.org> > Subject: Re: [typo] THEME CONTEST !! - How many people are entering > To: typo-list at rubyforge.org > Message-ID: <EAF209F7-EE19-42CA-BFA6-A367EA165DCA at sigkill.org> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > I don't really care what the rules are for the theme contest, as long > as there *are* rules and everyone plays by the same ones :-). > > Right now, *none* of the theme view code is in 2.5.6, which is the > current stable release. So you're safe on that front, at least right > now. > > Unfortunately, 2.5.6 doesn't entirely work right with Rails 0.14.x, > so I need to release 2.5.7 soon; it'd be best for me if it's out > before Wednesday night. Now, since I'm doing a new release, I *can* > include the view code--it's really self-contained and easy to drop > into place. It's won't break any existing themes, but it'll add new > abilities that give newer themes an advantage. Which probably isn't > fair. So I'm leaning against including the new view code, unless > there's an overwhelming show of support, ideally including people who > already have themes submitted. So far, I've heard one person who's > against the new code. Is anyone *for* it? > > > Scott -- Arron Kau kau at lifetime.oregonstate.edu blog: http://akau.homeip.net Most modern freedom is at root fear. It is not so much that we are too bold to endure rules; it is rather that we are too timid to endure responsibilities. --G. K. Chesterton
