[xyz]

I was just wondering since all of you are pretty good with you graphics and html and probably have more expirinece on this more than me what do you guys think is better please consider and think about this because you can do a variety of things with both.
(sorry for the misspelled words if any!)
eNd mEsAgE
xyz

[Affected]

I don't see much need fore imagemaps... Splicing up into tabless will alow for rollovers (OK, you can do rollovers with imagemaps, but the download times will be huge), and scalable content areas etc... I'd say tables/frames/layers. Of course, if you need to have small areas in an image have links, and mouseovers aren't needed, an imagemap can be a good choice, but I wouldn't just slap a big image on a page, make an imagemap and call it a site...(I've seen it done)

------------------
Affected

Knowledge is belief and belief is knowledge
http://affected.xs.mw

[Belzero]

Hehe, image maps as pagfes. That is one of the funniest yet saddest things :P This guy comes up to me and says, "Dude check out my cool new page." You go there and it takes 5 min to load and is one big image. Works good for keeping people from copy/pasting your content :P But now-a-days OCR is too common for that even :P

Hehe image map pages. Oh yeah btw splicing is the way for a few reasons, changing one little thing is easier with splicing than changing the whole image and stuff. Rollovers, very useful, are not good with image maps. Just save yourself from some grief and splice it, especially with all the programs that practically do it for you.

There's my bit -- BelZ

[[Shizo]]

Sliced up images take longer to load since it's a bunch of small images instead of one big one that continues loading without interruption.. But if you multiply location of our orbit star "Triton" by zeranogon of the height of Mexican cactus, it'll still be the same!!!!

PS: Them cable bums may shut up.. 33.6k forever!!!!!

------------------
Russia is power. You dont agree --> we nuke you!