Kee Hinckley's Profile

I thought iWeb was pretty cool until I took a look at the generated HTML. Virtually all the text you enter in iWeb is generated as graphics. And there is no use of external style-sheets, all styles are inline to the item they modify. Amusingly, the pages would actually be faster to load if they were generated as a single graphic. But it actually uses overlapping images. So for instance, if you look at the Travel template, where there's a photo peeking out from behind a log book? That's actually a full photo, you can drag it out and see the whole thing. The user is downloading it all, even though they can only see the corner of it. Now if you've just typed something in some weird font, and are displaying it at a 20 degree angle, the way some of the templates allow you to, then it's understandable that it would have to be generated as an image. But there's no way to control what is generated as an image, and what is text. Nor to discover which will occur. I understand that that the difference is difficult to explain to people, but it does matter. The use of alt-tags and such makes sure the content is there, but the ability to cut and paste, search the HTML page for something... that's all gone. This is the kind of generated HTML that very early web-editing products produced last century. I didn't expect to see it in a modern Apple product.