Also noticed that once an image is in your cache and changing page it briefly displays the image before hiding it and re-fading. Is there anything I can do to stop that?
All of these effects are highly dependent on the speed and power of
the client computer. Scriptaculous effects “scale” to the local
computer, dropping frames when necessary to maintain effect timing.
(If you set an effect to take a half second to complete, it will take exactly that long to finish. Whether it takes 4 steps or 200 to do
that transition is a function of how fast your local processor is,
and how much real memory your browser can allocate to its process.)
Making the effect do less work is one way to make things run more
smoothly. If the objects you are animating are large, make them
smaller. If you are animating many elements at once, try doing fewer.
Walter
On Oct 17, 2008, at 10:26 AM, ed watt wrote:
thanks for the kind words guys,
would really appreciate if somebody can help though:)
it’s not a major thing but would be nice if it was a bit smoother…
Walter’s right. I have site that uses around 6 large images to fade in and out - at first they are a little jumpy, but once they have loaded and the sequence begins again all is well.
All of these effects are highly dependent on the speed and power of the client computer. Scriptaculous effects “scale” to the local computer, dropping frames when necessary to maintain effect timing. (If you set an effect to take a half second to complete, it will take exactly that long to finish. Whether it takes 4 steps or 200 to do that transition is a function of how fast your local processor is, and how much real memory your browser can allocate to its process.)
Making the effect do less work is one way to make things run more smoothly. If the objects you are animating are large, make them smaller. If you are animating many elements at once, try doing fewer.
Walter
On Oct 17, 2008, at 10:26 AM, ed watt wrote:
thanks for the kind words guys,
would really appreciate if somebody can help though:)
it’s not a major thing but would be nice if it was a bit smoother…
The difference is because Action-generated code (along with the HTML)
gets converted in the process of More/Less Readable, and some
portions of the JavaScript don’t take kindly to having their
whitespace removed in this fashion. So the JavaScript will fail to
run, and thus the effect is dead. There is a flag that the Action-
writer can set which “freezes” the code and keeps it from being
influenced by the end-user’s choice of whitespace, but unless this is
set, the script will be mangled.
Not all JavaScript functions are sensitive to this, but there’s
something in the FX scripts that is. Hopefully Joe can find it and
add the missing semicolon or what-have-you that is the real sticking
point here.
Walter
On Oct 20, 2008, at 11:16 AM, DeltaDave wrote:
And now it displays fine.
There has been some discussion here about certain things working
better with Code More Readable - I do not know if this is a case in
point or not!