Our Esteemed Judges

Posted by Geoffrey Grosenbach Thu, 24 Nov 2005 11:09:00 GMT

I thought it would only be appropriate to match the quality of our sponsors and our entries with a panel of top-notch judges.

Next week, the following individuals will be handing out glory to some and defeat to most of the rest.

Again, the general rules are here and the remainder of the judging will be up to the judges and your creativity.

Over 50 themes so far. Keep ‘em coming!

Posted in  | 21 comments

Comments

  1. Marco said about 6 hours later:

    Whoah…. that’s one hell of a jury!

    4 highly respected creative individuals. Very nice!!!

  2. victor said about 11 hours later:

    what content will the judges apply the themes to? My style is designed for programmer’s blogs, ie, for listing code (which tends to be very wide) but if there’s no such sample content, no one will notice…

  3. Marco said about 11 hours later:

    Why not setup your own demo site and have them look there?

    I have done that myself. I don’t know for sure if they’ll be willing to look at the demo site but it’s at least a good way to highlight the stuff you want to show and to make sure there’s a setup on which everything works right. I did it mainly to prevent any possible install problem that may occur when judging the theme. It would break my heart if it would be flagged down because of any problem that might occur since my theme is Trunk based.

  4. Sebastian GräßlŸl said about 14 hours later:

    I think it should be a goal for you to build a theme that works on every kind of blog and typo install, excluding trunk, because it’s not used that much. Functionality is a goal, this also includes that there are now App errors. I installed every Theme at my Test-Blog-Server to discover such App Errors and tell the Theme-creators how to solve them.

  5. Marco said about 15 hours later:

    You can’t support both Trunk AND release. My theme works like a snap-in solution on trunk based Typo installs. There’s nothing you have to configure or do. I’m running it on a live server and on a windows dev environment. There isn’t very much else one can do I guess…

  6. Nathan said about 15 hours later:

    Woah. That’s really intimidating.

  7. topfunky said about 15 hours later:

    If you have sent me a link to a live version of your theme, it will be given to the judges (just as it has been linked to during the course of the contest so far).

    If you didn’t send a link to a live version of your theme, I will save a static copy of the theme using my local install of Typo and an older copy of the data from http://nubyonrails.com.

    I’ll do everything I can to present a realistic copy of your theme, but it helps if you have put up a live, running copy of your theme on a publicly accessible site.

  8. Marco said about 15 hours later:

    Excellent!

    I spent a whole sunday on getting RoR to run on dreamhost. I’m glad that wasn’t for nothing ;)

  9. Leevi Graham said 1 day later:

    I agree with Marco …. EXCELLENT x 2 … I have also set up a sub domain for my typo entry… http://typo.leevigraham.com.. and I can tell you it was HARD YAKKA (non-australian translation = hard work)... So im willing to offer my services…. If you have a v2.6 Typo theme… i can try and install it on one of my sub domains eg: yourTheme.leevigraham.com… no garuntees tho.. but I will try… Provide me with a dump of your DB and I will upload that for you…

  10. Johnathan said 1 day later:

    http://typo.leevigraham.com/

    heh, I wish I could send you a screenshot of your test website right now – surfing in Safari every link disappeared when I moused over it. Uber cool when hovering at the top of a list and watching it melt into thin air, but made it kind of difficult to use : ) I think it happened because only some of the page/css had loaded, and presumably link onhover styling wasn’t completely loaded. Not sure why though. An interesting bug in Safari, but it might be worth trying to reproduce it and avoid doing whatever triggers it.

  11. Marco said 1 day later:

    I know something that triggers it: on the fly changing styles like:

    document.getElementById(‘some-id’).style.some-thing = ‘something’;

    I used that for the font-size chooser in my site at first. The result was a magic effect where all elements with a :hover set would disappear when hovering over them with the mouse.

    It forced me to fall back to a much less elegant way to implement the same thing.

    It’s a real shame but I figured people like Shaun or John will definitely check our stuff on a mac and I don’t want it to break on their browsers ;)

  12. Marco said 1 day later:

    I just teste Leevi’s site in Safari Version 2.0.2 (416.12) on Mac OS X 10.4.3 on my G5 and I am not experiencing the problem Jonathan describes.

    What version are you using Jonathan?

  13. Bastiaan Terhorst said 1 day later:

    I just checked it with the exact same version (2.0.2), and I do see the problem. Weird :)

  14. Sebastian Gräßl said 1 day later:

    I check the site also with Safari 2.0.2 on 10.4.3 and: First the site needs very long to load Second every Link hides whn scrolling over it.. really every link

  15. Sebastian Gräßl said 1 day later:

    Ok, tried e second time… this only happens when the site is loading..

  16. asdf said 2 days later:
  17. Kyle said 3 days later:

    Can we get a clear distinction on what version of typo we’re supporting? Release and trunk vary drastically in the way the body is retrieved for an article.

    One cannot support both backwards, current, and future compatability.

  18. topfunky said 3 days later:

    The most ideal solution is if you develop for Typo 2.5.6. If you do that, your theme will work for most any version of Typo, now or upcoming.

    If you need the features in the newer versions, you can develop against 2.6.0 or trunk…your theme will still be accepted.

  19. Marco said 4 days later:

    Last day!

    Can’t wait to see the last submissions. I hope mine was received too?

  20. PolandTypoFans said 4 days later:

    I hope they will set the new submission date to around Christmas. We got noticed too late ;-/

  21. test said 5 days later:

    test

Comments are disabled