bi**********@gmail.com a écrit :
On Apr 10, 10:18 pm, "Peter Michaux" <petermich...@gmail.comwrote:
>On 10 abr, 13:36, biggio.cr...@gmail.com wrote:
>>Hi,
I've used the MM_SwapImage function from Dreamweaver to make a roll
over gallery for a photography website. The only problem is when I use
safari it changes the aspect ratio of the images.
Here's the link:http://www.lizethsantos.com/fineart/.../abstract.html
Broken link.
>>Any solutions? Any idea on modifying the function so I can pass it at
width variable?
Thanks
Peter
thanks
http://www.lizethsantos.com/fineart/.../abstract.html
Lizeth,
I went to your webpage and your webpage took forever to load. That's
unacceptable.
You've got more important issues to fix.
First, just stop slicing images.
MainSide.jpg
MainTopL.jpg
MainTopM.jpg
MainTopR.jpg
abstracttitle.jpg
etc, etc,etc
1- It's not unneeded, not necessary and
2- it increases the number of http requests, so, in the end, it slows
down the rendering in the browser and that, for the same amount of file
size (one image without being sliced)
3- by slicing images unneededlessly, you need more markup code to
position the sliced images: so, with a table, table rows, table cells,
the DOM tree increases also unneededlessly.
4- your table (table, table rows, table cells) are coded to be
overconstrained (width, height, colspan, rowspan attributes defined and
specified in many places or everywhere) too: that too slows down the
rendering because the parsing is more complex. Unneededlessly. Unnecessary.
5- By having coded more sliced images, more coded, more
over-constrained, increased DOM tree, you make the maintenance of your
webpage more complex, longer, more difficult to review/understand/figure
out by others, etc.
Just stop slicing images unless *_you know what you're doing_* and *_you
know you have to slice images_*.
Second, just stop using javascript functions that you do not understand.
Simple as that. I've never used any DW functions and I know they are not
efficient, not well written, not made to make the ordinary web author
understand how to best use it. I am absolutely convinced that a wide
majority of expert scripters in this discussion forum would not
recommend those DW functions.
Start from scratch. Ask for help on creating, doing *your* rollover
functions. Define your own functions instead of being dependent on DW.
Again, understand what you're doing.
Third,
at the very least, make your secondary windows all accessible.
function openWindow(x) {
popupWin = window.open(x, 'imagepop', 'width=380,height=560')
}
function openWindowWide(x) {
popupWin = window.open(x, 'imagepopwide', 'width=560,height=380')
}
I don't have a viewing area long enough to render a 560px high window as
I am forcing all of the toolbars on secondary windows. Your code makes
the secondary windows all non-resizable and without scrollbar(s) when I
will need a vertical one. Stop doing that and visit
Mozilla Developer Center: DOM:window.open
http://developer.mozilla.org/en/docs/DOM:window.open
for recommendable examples.
Gérard
--
Using Web Standards in your Web Pages (Updated Dec. 2006)
http://developer.mozilla.org/en/docs...your_Web_Pages 
