A while back I thought it would be cool to set up a theme repository
that allowed themes to be tested and maintained against multiple
versions of Typo. It took longer than expected due to a sudden flurry
of house buying and selling activity, but a rough first attempt is up.
The biggest flaw right now is that only my own themes are are in the
system. A more inclusive list of flaws and action items can be found in
the Trac.
The theme repository:
http://proofread.digital-achievement.com/catalog/
I have Trac set up to collect bugs/requests/patches:
http://proofread.digital-achievement.com/project/wiki
There’s still a long list of things to do, and if you’d like to help
please send me a message.
Thanks,
Tim
–
Timothy F.
http://digital-achievement.com
On Mon, 2006-07-10 at 00:57 -0500, Timothy F. wrote:
The theme repository:
http://proofread.digital-achievement.com/catalog/
Er… It’s just a photo gallery? Or am I missing something?
Personally, I’m not real fond of the slow JavaScript effects. Why not
just display the picture when I click on it?
- Scott
On 7/11/06, Scott B. [email protected] wrote:
On Mon, 2006-07-10 at 00:57 -0500, Timothy F. wrote:
The theme repository:
http://proofread.digital-achievement.com/catalog/
Er… It’s just a photo gallery? Or am I missing something?
Click on the name of the theme under the image which takes you to a page
for
that particular theme with SVN and tarball links. It’s a front-end for a
SVN-backed theme repository.
On 7/11/06, Timothy F. [email protected] wrote:
Scott B. wrote:
Personally, I’m not real fond of the slow JavaScript effects. Why not
just display the picture when I click on it?
Two reasons: I liked the way it looked in John Wang’s Themes Viewer[1],
and I wanted to see what Lightbox JS v2.0 was all about first hand.
I’ll admit, not the most sound technical reasons to add a “feature”, and
it will slow down browsing full size images in rapid succession.
Lightbox 2.0 has a (super easy to implement) group feature that lets you
cycle through images without leaving the lightbox. I’ve played with it
but
haven’t deployed it on the themes viewer yet b/c I may want to tweak how
it
works.
That really was easy.
I added a number of themes into the theme repository this evening,
bringing the total up to 52. Phil C. bundled them all up for me,
and then I turned my attention to scripting the screenshot capture
process. Between ruby, twill, and webkit2png.py, all of the screenshots
in the catalog were snapped automatically.
I did notice that Lightbox doesn’t behave very well when an image is
missing. For instance, the Scribbish screenshots didn’t get captured
for some reason, so if you click on that image link you will get the
Lightbox spinner, and you won’t have the opportunity to close the box.
Most of my programming time in the last few days has been back end
stuff, but it’s still nice to see a larger number of themes in the
system.
If you’d like to see Lightbox’s group feature on 52 themes, have at it:
http://proofread.digital-achievement.com/catalog/
Tim
John Wang wrote:
and I wanted to see what Lightbox JS v2.0 was all about first hand.
John Wang
Dev411 Blog
Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list
–
Timothy F.
http://digital-achievement.com
Scott B. wrote:
On Mon, 2006-07-10 at 00:57 -0500, Timothy F. wrote:
The theme repository:
http://proofread.digital-achievement.com/catalog/
Er… It’s just a photo gallery? Or am I missing something?
It seems I have a bit of work left to do in the “intuitive interface”
department. 
I made some changes to the theme summary boxes,
hopefully that helps to clear up the intention. I’m interested to see
if anyone else agrees.
Personally, I’m not real fond of the slow JavaScript effects. Why not
just display the picture when I click on it?
Two reasons: I liked the way it looked in John Wang’s Themes Viewer[1],
and I wanted to see what Lightbox JS v2.0 was all about first hand.
I’ll admit, not the most sound technical reasons to add a “feature”, and
it will slow down browsing full size images in rapid succession.
Perhaps we can turn that into a user preference in the future.
[1] Dev411 Blog
Thanks for the input – I appreciate it. I should have many more of the
themes included in the next few days, and a few days after that I may
just have the automated testing working.
Best regards,
Tim
–
Timothy F.
http://digital-achievement.com
http://tim.freunds.net/thoughts