inline...
DavidF said:
David,
Thanks, I think. Changing to the high setting does allow for layering an
image or a text frame on top of a text frame without converting it all to
a
GIF. And yes, position:absolute is in the source code, but not z-index. I
looked at the source code of
http://www.dogwoodindustries.com/ and saw
what
you meant by having both.
I say thanks, I think, because this seems to open up all kinds of
different
design options for me with Publisher 2000. I pretty much knew what I could
and could not do with the low setting, but will have to experiment a lot
to
see what I can do at the high setting.
I already realize that the high setting seems to create a lot more code.
Will the page also take longer to load?
the more code the longer the load time. but, if you have a few smaller
images versus one large one, the time might be a wash since a few smaller
images will load faster then a larger one.
a good way to check the total size of a page is to view the page in IE, go
to File, Save As, select file type .mht, and save the page. Then browse to
the .mht file and look at the size of it. The mht file contains all the code
and the images and so should be an accurate indicator of total page size.
The larger of which translates into longer download time. If you wanted to
get real creative you could browse your favorite sites and save their page
as mht and then compare their page file size to yours.
While experimenting a little, I inserted some JavaScript I use, and it
seems
to work ok, but the code for 'Top of Page' does not on the first try,
whether it is layered or not...at least not in preview. This leads to a
general question. What do you suppose that I am going to have to give up,
if
I design in the high setting? What's the downside? I can remember in the
past you recommending to folks that they change to the lowest setting to
solve some problems, but I don't remember what those problems were.
well back in the days of 2000 lots of people still used NS 4x, and in
general there were lots of complaints about browser compatibility, even in
older versions of IE. And CSS wasn't as commonplace as it is today. So
moving the default high setting to low provided for traditional html that
was more widely supported and of course is cleaner and faster to load.
But now, 2 versions later and a few years past, it's a different world. NS
has pretty much vanished, IE is more dominant, and there is a new player.
Now CSS is a must and CSS2 is more widely used to varying degrees. And
Publisher walked away from traditional html and shrugged off browser
compatibility. And also ISP connections have gotten faster and broadband has
grown rapidly. So today there isn't any real reason why a 2000 customer
shouldn't feel free to try out the higher settings for their web. I haven't
gotten into 2000 in quite awhile but if I recall correctly the target
setting would vary the amount of CSS and CSS2 used versus traditional html,
so feel free to slide it somewhere in the middle range and compare.
No rush responding as I won't have time to experiment with this until the
weekend, but I do appreciate your advice. Its great to learn a new
capacity
for Pub 2000...I think. ;-)
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com