The reason I've added the night background with Javascript is so that those without JS enabled don't have it cover everything permanently. I can the put script to make the backdrop inline, up at the top of the body, and it'll come up before anything loads. (why I didn't do that in the first place I don't know) My current working model has this done, and I've tweaked the animation a little (the floor fades in, then the text, then a little pause, then the sunrise) - i'll upload it this afternoon. (it's 9:00 am ATM)
And, yeah, It's pretty clear it doesn't need to work in IE5.5 (your stats surprised me a little - I was expecting it to about as popular as opera), but the issues are the same as in IE6 - which is at 13% - enough to be worthwhile (unfortunately). I think that all I need to do to make it work in IE6 is:add some proprietary code so IE understands the transparent PNG for the 'wicket' text. http://www.alistapart.com/articles/pngopacity/ add a conditional comment that give #information a specific width. and remove the underlines from the tabs - IE6 requires that they are links to use the :hover selector. I should be able to test this when I have computers at school (1.5hr) Hopefully it's ok with you that the CSS won't validate - otherwise you're stuck having it work <90% of the time. It's also surprising that so many people have 1280x1024 monitors — it's not the standard ratio or the widescreen one. - 1280x960 is. Do you have stats on the browser window sizes? It's mostly a curiousity, but it could also be useful for this… Martijn Dashorst wrote: > > Total and utter Coolness. > I think you can delay the start of the animation a tad, say ~.5 or 1 > second. > Let the folks get accustomed to what they are seeing. Perhaps make sure > the > background and such of the 'night' are the starting point (i.e. not > setting > them with js, but directly in the css), this will mitigate the > transitions, > and add extra time to the animation. > > Stats for the site: > > firefox: 67% (2.0.0.11 : 35%, 2.0.0.9: 32%, 2.0.0.10 : 15%, 2.0.0.8 : 6%, > 2.0.0.6 : 3%, etc.) > ie: 23% (6.0 : 57%, 7.0: 43%, 5.5: 0.18%, 4.01 : 0.04%) > opera: 4% (9.23 : 33%, 9.24: 31%, 9.50 9%, 9.22: 8%, 9.21: 4%) > Safari : 4% (523.10 : 53%, 523.12: 26%, 419.3: 9%, 523.12.9: 6.8%) > Mozilla: 1% > Camino: 0.3% > Konqueror: 0.3% > > So I think you can safely skip IE 5.5 compatibility. > > Screen resolutions: > 1280x1024 : 33% > 1024x768: 19% > 1280x800: 11% > 1680x1050: 10% > 1440x900 7% > 1600x1200 5% > 1400x1050 5% > 1920x1200 4% > 1152x864 2% > 1280x768 1% > 1280x960 1% > 800x600 0.59% > > Martijn > > On Dec 16, 2007 2:47 PM, WalkerP <[EMAIL PROTECTED]> wrote: > >> I've currently got a mostly working version of the page that I've tested >> on: >> Safari 3 (which is where it looks best due to support of the >> 'text-shadow' >> CSS property & rounded corners) >> Firefox 2.0.0.11 & IE7 (both look the same) >> IE6 & IE 5.5 (It failed these tests, as neither browers supports >> 'max-width' >> or alpha transparent PNGs - but both issues should be easily fixable with >> a >> little JS.) >> >> As yet, I haven't been able to see what it looks like in Firefox 1.5, >> Opera, >> or Safari 2, so if anyone has access to these apps, please take a screen >> shot… >> >> The site is useable with or without javascript enabled (the only >> difference >> is that there's no animation without JS), and at resolutions from 800x600 >> up >> (though it looks better on 1024x768+ - more white space) >> >> I've uploaded the page here: http://wicket.awardspace.com/ (the hosting's >> pretty bad, but hey, it's free) and I've attached a zip of screenshots of >> the page with different browsers >> http://www.nabble.com/file/p14361677/Wicket%2BScreenshots.zip >> Wicket+Screenshots.zip As you may notice, Safari's menu looks markedly >> better than other browsers' (esp. IE). Currently, I'm not entirely sure >> how >> the menus should be organised (help?) - but once the menu structure >> itself >> finalised, I'll be able to make them look just as good on the other >> browsers. For now, it's using scarcely-supported CSS3 to do the rounded >> borders and drop shadows. >> >> And, just now - after uploading the site I realised something I hadn't >> remembered to consider before - currently the page loads & displays in >> its >> entirety, then it animates. Not particularly appealing. That's easily >> fixable (I just need to move the JS that draws the navy cover over the >> page >> higher up in the code, and have it run before the DOM is fully >> downloaded, >> - >> then have the animation run when the download's finished.) >> >> To-Do: >> Make Page work with IE 6 (and maybe 5.5) >> Shrink page & resources size >> Improve & finalise Menu Structure >> Re-style menus so they look better cross-browser >> Various Minor Tweaks >> Whenever >> >> http://code.google.com/p/google-highly-open-participation-asf/issues/detail?id=51 >> Issue 51 is resolved, put it's result into the page >> Anything I've forgotten? >> >> >> >> >> >> Martijn Dashorst wrote: >> > >> > Again, I'm not going to maintain the swf file: I don't know the format, >> > nor >> > have I any intention to learn it. So for me the format is off limits. I >> > also >> > think that in the advent of adblock and other plugin blockers the >> format >> > is >> > flawed for a entry point of any website. >> > >> > I really do like the rising sun idea. This has to stay :) >> > But the coffee cup is way off: got to get that thing out of your head. >> > >> >> -- >> View this message in context: >> http://www.nabble.com/-GHOP--Issue-14---Created-an-Animated-Launch-Page-for-Site-tp14237894p14361677.html >> Sent from the Wicket - Dev mailing list archive at Nabble.com. >> >> > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-rc1 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/ > > -- View this message in context: http://www.nabble.com/-GHOP--Issue-14---Created-an-Animated-Launch-Page-for-Site-tp14237894p14366998.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
