Posted by dorayme on 02/26/07 00:52

In article
<1172449857.616506.167700@a75g2000cwd.googlegroups.com>,
"windandwaves" <nfrancken@gmail.com> wrote:

> Hi Folk
>
> If you have a large image does it make sense to slice it to make it
> load faster? If so, what would be the best way?
>
> Please dont ask me why to have a large image in the first place - that
> is a given...
>
> TIA
>
> > Nicolaas

The idea of slicing to save is dependent on you preparing the
different slices differently. In other words, there is no point
at all simply slicing and having the overhead of a "display"
table to boot. If you have parts of an image that can be heavily
compressed without affecting the look you want, and other parts
not so amenable, there might be an argument if bandwidth is
really at such a premium and the pic is so large as to warrant
it. But I'd say not to bother, it is a small k gain at best and
there are many downfalls, namely getting the bits to render well
cross browser. The way to do it is usually to use a generator in
prgms like Fireworks and these work best when there are lots of
filler clear gifs to pad the table out right! It is not a nice
road to travel. It is sometimes done where you want to have
ordinary html text in the midst of it all (which generates
problems too).

--
dorayme

[Back to original message]