Slow to load
i think you are right. What I noticed was a lot of image layers loading all of the different backgrounds and effects, which -true this is not a code issue. Ordinarily you would do all of that layering in something like photoshop image ready, or fireworks, flatten it, slice all that up into smaller pieces and it would make it load much faster. If iweb were really smart it would have some sort of utility that would optimize images for the web... Make sure all the images were sized to crop at 72 ppi, for example... but that could be dicey, because if iweb started making too many decisions for you, the end result might not look as good. I think with all the special effect features iweb must just be adding image on top of image without doing any flattening. Just curious- are there any user defined web publishing features to optimize the file size?
At macworld the guy doing the demo made this cool looking page and then had to suffer the embarrassment of have a status bar showing the crowd exactly how slowly this was uploading to .mac. I think he was dragging and dropping all these photos and never checking to see what there resolution and size were and then had to upload these huge files. I suspect this is the problem wih iweb.
Diatribe said:Yeah, your problem is a different one. iWeb creates insanely large .pngs. I don't think it is the code that is the problem here. I am no expert, so if I am wrong about that somebody correct me here.
They have to make the image size/format smaller but .mac servers just add to that problem.
i think you are right. What I noticed was a lot of image layers loading all of the different backgrounds and effects, which -true this is not a code issue. Ordinarily you would do all of that layering in something like photoshop image ready, or fireworks, flatten it, slice all that up into smaller pieces and it would make it load much faster. If iweb were really smart it would have some sort of utility that would optimize images for the web... Make sure all the images were sized to crop at 72 ppi, for example... but that could be dicey, because if iweb started making too many decisions for you, the end result might not look as good. I think with all the special effect features iweb must just be adding image on top of image without doing any flattening. Just curious- are there any user defined web publishing features to optimize the file size?
At macworld the guy doing the demo made this cool looking page and then had to suffer the embarrassment of have a status bar showing the crowd exactly how slowly this was uploading to .mac. I think he was dragging and dropping all these photos and never checking to see what there resolution and size were and then had to upload these huge files. I suspect this is the problem wih iweb.