grodog wrote:Hey Scott, in Firefox 1.5.0.1 the front page links for the site don't work fully: for example, the Front Desk link appears to be mapped to the area just below the "w?" of "What's New?" right to the "u" of "Dungeons in the subtitle, rather than at the "Front Desk" button.It looks like the image map is mapped incorrectly. I'll check in IE in a minute.edit: nevermind, everything was fine after I cleared my cache, in both browsers.
FoulFoot wrote:Thanks for the comments. One thing I'm not real happy with is the dual-index-page thing. When you click the "Subwebs" button, it loads an (identical) index page with the subwebs now replacing the indexes. I was hoping it would be more seamless than it is -- unfortunately, at least on my browser, it wants to load the whole page again, which sort of ruins the effect. Perhaps those of you with more active caches are seeing it as I intended....Anyone have any ideas on how to do this better? My main goal is to keep the front page small in filesize -- no more than maybe 75k. Right now it's about 40k. I'm afraid that most DHTML or Java-type scripts would quickly push the filesize up, and make it impractical for those on a slow connection.Foul
grodog wrote:Looks good to me too, now, Scott (in both Firefox and IE). Short of making the indices section a separate include/image/whatever that would load once and then be cached again, I don't know of another way to make the transition between the main site index page and the subwebs index page cleaner.But then, I'm not an .html guru either. I'm sure someone else will be able to chime in with other ideas.
deimos3428 wrote:grodog wrote:Looks good to me too, now, Scott (in both Firefox and IE). Short of making the indices section a separate include/image/whatever that would load once and then be cached again, I don't know of another way to make the transition between the main site index page and the subwebs index page cleaner.But then, I'm not an .html guru either. I'm sure someone else will be able to chime in with other ideas.I'd pull the background image out of the css and put it in the body tag, but that's just me. Don't think it would matter, performance-wise. Once it's cached, that's as fast as it's going to get, unless I put my cache on a ram disk or something crazy like that.
guerret wrote:Visualization should be separated from the content.
deimos3428 wrote:I'm not (primarily) a web developer, so I don't know where people make these arbitrary rules.
guerret wrote:deimos3428 wrote:I'm not (primarily) a web developer, so I don't know where people make these arbitrary rules.Around the World Wide Web Consortium (http://www.w3.org). I happen to know the director of the Italian division, Laforenza, because I work in the same institute as he.
