Gord
Forum Replies Created
-
https://www.saratogahosting.com/aol/
Any AOL surfers who do not turn off the compression will see a bad image.However, presumably they are used this and expect to see poor quality.
The only other thing I can suggest is to test the site with a .PNG image instead of a JPEG.
The AOL compression guide makes no mention of this format . It may work??
https://webmaster.info.aol.com/compgraphics.htmlGord
-
Somewhere in the aol preferences there is a “Always compress graphics” setting which defaults to on when using dial up.I think its under:
Settings > Preferences > Graphics ? or Images? or something.
Reset this to off.Gord
-
< body >
< div class="container" >
< div class="logo">< /div >
< div class="flash">< /div >
< div class="espanol" >< /div >
< /div >
< /body >???? works fine on explorer 5.5 PC . could be an issue with the MAC version ?
maybe try adding { border:0px;margin:0px;padding:0px; } to each div container.
One of these could be forcing the div down ?Gord
-
Hi
The new version is not as good.In my opinion the blue areas in the original work well with the image, the web pages & the blue text links.
I didn’t mean to suggest that you take colours out , just that you take a bit of care when slicing to minimise the file size.
My best advice to get rid of the white spaces and reduce the file size is still to re-slice the original, look for areas of duplication & use a single gif for these, tile the outside pattern and try tweaking the quality of the web page samples.Also, if you change the central web page samples to .jpeg rather than .gif , you can sigificantly reduce the size without loosing toooo much quality. They look ok to me at about 1/3 file size (10KB rather than 30KB).Thats a huge saving per image.
Gord
-
Whats your point ??
-
Afterthought.
This may or may not be the best way to do things.
But for a complex graphic, I get my finished image in Photoshop & drag guides in to work out my slicing.It has to be pixel perfect.Once done I write in all the ()widths across the top & (
)heights down the left.
Works for me.
Gord -
Hello MiLiNd.
I had a quick look at your layout & I can’t remember seeing so many random? slices in an image.
It’s too complex for me to try & work out why the browser creates a few gaps.
Personally i’d slice it up again from scratch. These are the rules I follow.
1/ Keep it simple enough to be able to manage any browser problems.ie: if ,when troubleshooting ,you add a border tag to your table cells,will you be able to work out whats going wrong?
2/ Before you start slicing, look for obvious areas of duplication.
For example, the magnifying glass and ‘view’ comment at the bottom of each web sample page is the same graphic. So providing you slice this area consistently each time,you can repeat the same graphic 14 times rather than having 14 graphics (1x2KB rather than 14X2KB).
The ‘featured links’ menu is another area.
3/ Look for logical slice borders.Consider the fact that the more colours in an individual gif, the larger the gif will be. So try not to split say a blue part across several slices.
4/ Like I said before, use a small ’tile’ gif to create the external pattern.Hope this helps a bit.
Gord
-
Hello MiLInd.
It is a bit slow to download on a 56k modem.
First thing I’d try is to remove the pattern graphic on the left/right side & replace it with a small tile ( currently 25KB & 14KB ) as a background (The same graphic, just a tiny “tiled” version).
The bulk of your site (KB) is contained within the 14 central web page images (104KB). All you can do is either tweak the quality down or accept the slower download time.(Are your clients likely to be on dial up modems? Are your clients likely to find you via a search or are they specifically looking for you?) .
As for the white spaces.If you look at a vertical line down the center of the image (where shree is) the graphics fit the whole page.To the left and right sides there are some white spaces , and spaces at the top and bottom. This suggests to me that the vertical height of the slices do not add up to the middle section total, causing the browser to ‘guess’ where you want the graphic & creating 1 or 2px whitespaces.Gord
-
Hello Rob.
Firstly, the version of Javascript could be different (1.1 or 1.5 etc..).
Secondly, and more likely, Javascript code manipulates the browsers document object model(DOM).Whilst very similar, no two browsers DOM are exactly the same, meaning that some browsers may not recognise the ‘element’ your code refers to .eg: code refering to document.layers will be ok on Netscape 4 browsers but will mean nothing to IE.
Thirdly, browser versions for Windows are different from browser versions for the Mac & each will have a few quirks & strange behaviors.If you really want to write & understand the code rather than search for good cross-browser compatible drop down menus already written, you need to do a search for “Javascript browser compatibility ‘strategy’ ‘techniques’ ‘help’ …etc”
A common approach is to test for the feature before executing code and if the feature is not detected , supply alternative options using the if syntax.
if(document layers){ .. do this code… document.layers is supported
}
else if(document.getElementById){.. do this code… document.getElementById is supported
}
else { .. some simple static code
}
If you can post your code up on the web I’ll have a look.Hope this helps
Gord -
Hello Rob.
Firstly, the version of Javascript could be different (1.1 or 1.5 etc..).
Secondly, and more likely, Javascript code manipulates the browsers document object model(DOM).Whilst very similar, no two browsers DOM are exactly the same, meaning that some browsers may not recognise the ‘element’ your code refers to .eg: code refering to document.layers will be ok on Netscape 4 browsers but will mean nothing to IE.
Thirdly, browser versions for Windows are different from browser versions for the Mac & each will have a few quirks & strange behaviors.If you really want to write & understand the code rather than search for good cross-browser compatible drop down menus already written, you need to do a search for “Javascript browser compatibility ‘strategy’ ‘techniques’ ‘help’ …etc”
A common approach is to test for the feature before executing code and if the feature is not detected , supply alternative options using the if syntax.
if(document layers){ .. do this code… document.layers is supported
}
else if(document.getElementById){.. do this code… document.getElementById is supported
}
else { .. some simple static code
}
If you can post your code up on the web I’ll have a look.Hope this helps
Gord