Firstly, I agree entirely with your position on flash — if I were to make the page in flash - I myself couldn't see it, — and besides, I don't have $500 to spare to buy Flash! (though, if i can help with 15 issues…)
Secondly, the coffee cup came from http://code.google.com/p/google-highly-open-participation-asf/issues/detail?id=13 another issue in the GHOP — personally, I kind of like it, but it wasn't accepted, so I've stuck with the rising sun page with some tweaks and changes (e.g: the tabs were originally going to be just tabs, now they're pull-down menus - as per someone's suggestion. ). 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.
