Louis, you'll definitely want to look at Quirksmode:
http://www.quirksmode.org/js/
On Feb 3, 2006, at 3:01 PM, Louis Walch wrote:
im not a javascript programmer... so be nice.
scriptaclous uses a differnt format for writing functions and code
then i
am used to. are there books or tutorial
I'm using scriptaculous' SlideUp and SlideDown effects to animate a menu. Specifically, I SlideUp, make some CSS changes, and SlideDown. All works well, except that for a split second in between, the element's display becomes 'none' and the other menu item jump into the space. I haven't been able t
You could do:
new Effect.SlideUp(element, { to: 0.01 });
That way it’ll only slide up until
there is 1% showing, and not completely remove it.
Then, on the reverse do:
new Effect.SlideDown(element, { from: 0.01 });
Or at least that *should* work.
Good luck.
Greg
I need a way to pass parameters to an event handler function other than just the e.I'm declaring the handler as such: Event.observe('regmenu', 'mouseover', togglein, false);I need a way to pass parameters to the togglein function. I'm getting tripped up by the fact that the event object is getting
Using to: x doesn't work. The element still disappears after it reaches its desired destination.On 2/6/06, Gregory Hill <
[EMAIL PROTECTED]> wrote:
You could do:
new Effect.SlideUp(element, { to: 0.01 });
That way it'll only slide up until
there is 1% showing, and not completely
On Monday 06 February 2006 13:05, Yehuda Katz wrote:
> I need a way to pass parameters to an event handler function other than
> just the e.
> I'm declaring the handler as such: Event.observe('regmenu', 'mouseover',
> togglein, false);
What you're looking for is a closure :)
Event.observe('regmen
It seems to be a side-effect of the makeClipping commend in Effect.BlindDown. When I comment it out, I no longer have the problem, but I do need the clipping behavior. Any thoughts?On 2/6/06,
Yehuda Katz <[EMAIL PROTECTED]> wrote:
Using to: x doesn't work. The element still disappears after it rea
After further experimentation, it seems I needed to have the parameter: {to: 0.99}, not {to: 0.01}On 2/6/06, Yehuda Katz <
[EMAIL PROTECTED]> wrote:It seems to be a side-effect of the makeClipping commend in
Effect.BlindDown. When I comment it out, I no longer have the problem, but I do need the c
That’s interesting. I just assumed
it would be the reverse for effects that make an element disappear. I believe
Effect.Fade works that way, but maybe I’m just smoking something.
Anyhoo, good to know.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Yehuda Kat
One more question for today: How do I trigger a function after an effect has completed?On 2/6/06, Gregory Hill <
[EMAIL PROTECTED]> wrote:
That's interesting. I just assumed
it would be the reverse for effects that make an element disappear. I believe
Effect.Fade works that way, but
http://wiki.script.aculo.us/scriptaculous/show/CoreEffects
The documentation has a list of callback
functions available to all effects.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Yehuda Katz
Sent: Monday, February 06, 2006
3:07 PM
To: rails-spinoffs@lis
I've been able to do it with: the option afterFinishInternal.On 2/6/06, Yehuda Katz <[EMAIL PROTECTED]> wrote:
One more question for today: How do I trigger a function
after an effect has completed?On 2/6/06, Gregory Hill <
[EMAIL PROTECTED]> wrote:
That's interesting. I just assum
Um, afterFinishInternal or anything else
marked ‘internal’ is something you generally don’t want to
mess with, as it means it’s internal to the class.
afterFinish is the proper option you are
looking for, which is listed on the page I sent.
From:
[EMAIL PROTECTED]
[mail
Hey all,
I just wanted to let you guys know that I updated my notify script.
I still need to package it for easy download (next on my task list)
but it does what I need it to do. Any thoughts, comments?
http://thinkof.net/notify/index.html
Also thanks to those of you who helped previous
Yup. I noticed that after I sent it. The internal version worked, but you're right.On 2/6/06, Gregory Hill <[EMAIL PROTECTED]
> wrote:
Um, afterFinishInternal or anything else
marked 'internal' is something you generally don't want to
mess with, as it means it's internal to the class.
In Sortables, we have a function onHover:
onHover: function(element, dropon, overlap) {
if(overlap>0.5) {
Sortable.mark(dropon, 'before');
if(dropon.previousSibling != element) {
var oldParentNode = element.parentNode;
element.style.visibility =
"
16 matches
Mail list logo
