> im trying to use css instead of tables with photoshop's slicing tool.

Signature
To email a reply, remove (dash)un(dash). Mail sent to the un
address is considered spam and automatically deleted.
sorry i don't have a free url to post to at the moment.
the page that i'm working on is completely graphic and all the links will be
rasterized text. i'm also using photoshop as an interactive way to 'design'
the page. slicing seems to be a simple way to make linking areas on the
page. i am new to html, but what i've heard is that tables are being
replaced by css positioning techniques. am i wrong?
> > im trying to use css instead of tables with photoshop's slicing tool.
>
> There seems to be something contradictory here. If you are positioning
> with CSS rather than tables, why oh why are you using image slices at all?
>
> Post a url, rather than code.
Owen Jacobson - 30 Oct 2003 00:55 GMT
> sorry i don't have a free url to post to at the moment.
>
[quoted text clipped - 4 lines]
> that tables are being replaced by css positioning techniques. am i
> wrong?
You're not wrong, but you are going about it a rather non-optimal way.
One approach is to think in layers, rather than in blocks of space: you
can have one background image that contains all your decorative fluff,
and then place text (or even other images) overtop of that with CSS
positioning, without slicing up either the background or the overlaid
images.
salty_dogs - 30 Oct 2003 03:12 GMT
hey thanks owen:
that makes a lot of sense. i'll keep visualizing the layout in photoshop,
use a separate background and grab link/changeable sections and layers via
slice, (noting their 'left' and 'top' values for css positioning.)
do you incorporate nested <div> tags? is there a limit to the depth?
essentially what im trying to do is locate a block within a block relative
to the block's content edge. i gave the childDiv and parentDiv a color
background property, so they actually are empty of content (just a block of
color.)
<body id="none">
<div id="parentDiv">
<div id="childDiv">
<div id="babyDiv">
<p id="none"><img src="temp.jpg"/></p>
</div>
<div id="babyDiv2">
<p></p>
</div>
</div>
</div>
</body>
does this look right?
> > sorry i don't have a free url to post to at the moment.
> >
[quoted text clipped - 12 lines]
> positioning, without slicing up either the background or the overlaid
> images.
PeterMcC - 30 Oct 2003 09:24 GMT
>>> im trying to use css instead of tables with photoshop's slicing
>>> tool.
[quoted text clipped - 12 lines]
> that tables are being replaced by css positioning techniques. am i
> wrong?
A little aside from your principal issue - hope it's OK to wander a little -
but that method is going to create serious problems if you're hoping to get
decent search engine listings.

Signature
PeterMcC
If you feel that any of the above is incorrect,
inappropriate or offensive in any way,
please ignore it and accept my apologies.
kchayka - 30 Oct 2003 16:52 GMT
> sorry i don't have a free url to post to at the moment.
You really should find some place to upload test pages. It will make
things easier for everyone. Does your ISP give you any web space?
> the page that i'm working on is completely graphic and all the links will be
> rasterized text. i'm also using photoshop as an interactive way to 'design'
> the page. slicing seems to be a simple way to make linking areas on the
> page. i am new to html, but what i've heard is that tables are being
> replaced by css positioning techniques. am i wrong?
No you are not wrong about using CSS instead of layout tables, but I
think you are wrong about using slices at all, at least if your plan is
to use this as the final product. I've seen enough sites "designed"
from just image slices to know they are pretty ghastly from both a user
and developer standpoint.
The images are never properly optimized so these pages are generally
very slow to load. Each image is an added server call, which makes
loading even slower. The text will not be resizable, so some portion of
your visitors won't be able to read it. Image slices rarely have
appropriate ALT text, so the site probably won't be usable with image
loading off. The slicing process makes a complex table layout that not
only creates a pile of bloated tag soup for code (adding to load time),
but likely does not linearize well so the page won't make any sense in
some browsing situations. I imagine you plan to add JavaScript
rollovers, too, which add other twists to the mess. And I haven't even
gotten to maintenance yet.
I can't tell from your code snippets what you are really trying to
accomplish, but I'm pretty sure image slices are not the best way to do
it. And using graphics for text is often a bad idea, anyway.

Signature
To email a reply, remove (dash)un(dash). Mail sent to the un
address is considered spam and automatically deleted.