matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org
2006-Sep-14 15:37 UTC
scriptaculous Toggle Appear rate
I have the following code to toggle a basic appear of a div:
<a href="#"
onclick="Effect.toggle(''d3'',''appear'');
return
false;">Toggle appear</a>
I want to edit the rate in which the effect runs. I can''t for the life
of me figure it out. I would like to make the effect complete faster,
like .5 seconds. I''ve tried to hunt through the effects.js, but have
come up empty handed.
Anyone done this?
Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---
How about something like:
Effect.toggle(''d3'',''appear'', {duration:
0.5})
-----Original Message-----
From: matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org
[mailto:matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org]
Sent: Thursday, September 14, 2006 5:37 PM
To: Ruby on Rails: Spinoffs
Subject: [Rails-spinoffs] scriptaculous Toggle Appear rate
I have the following code to toggle a basic appear of a div:
<a href="#"
onclick="Effect.toggle(''d3'',''appear'');
return
false;">Toggle appear</a>
I want to edit the rate in which the effect runs. I can''t for the life
of me figure it out. I would like to make the effect complete faster,
like .5 seconds. I''ve tried to hunt through the effects.js, but have
come up empty handed.
Anyone done this?
Thanks
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---
Perfect! I knew it was simple, but no where could I find the syntax. Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
Effect.toggle(''d3'',''appear'', {duration:
.5});
The (optional) third parameter is a hash of effect options.
See some common options at
http://wiki.script.aculo.us/scriptaculous/show/CoreEffects
TAG
On Sep 14, 2006, at 9:37 AM, matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org
wrote:
>
> I have the following code to toggle a basic appear of a div:
>
> <a href="#"
onclick="Effect.toggle(''d3'',''appear'');
return
> false;">Toggle appear</a>
>
> I want to edit the rate in which the effect runs. I can''t for the
life
> of me figure it out. I would like to make the effect complete faster,
> like .5 seconds. I''ve tried to hunt through the effects.js, but
have
> come up empty handed.
>
> Anyone done this?
> Thanks
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---
Hey Matt, matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org a écrit :> I want to edit the rate in which the effect runs. I can''t for the lifeNote the rate, the duration.> of me figure it out. I would like to make the effect complete faster, > like .5 seconds. I''ve tried to hunt through the effects.js, but have > come up empty handed.Effect.toggle(''d3'', ''appear'', { duration: .5 }); -- Christophe Porteneuve aka TDD tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
Hey again, matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org a écrit :> <a href="#" onclick="Effect.toggle(''d3'',''appear''); return > false;">Toggle appear</a>BTW, this code is, well... ''could be better, I guess, is a nice way to qualify it. First, the "return false" thing is dead. Dead, dead, dead. Second, you shouldn''t put JS events in your HTML like that; you should use unobstrusive JS. For instance, you should assign this link an ID, then observe it from an external script file, with something such as: function toggleLink(e) { Event.stop(e); Effect.toggle(''d3'', ''appear'', { duration: 0.5 }); } // toggleLink Event.observe(''yourLinkId'', ''click'', toggleLink); If you wish to reuse the toggleLink function on multiple links, for multiple DIVs, you can: function toggleLink(e, containerId) { Event.stop(e); Effect.toggle(containerId, ''appear'', { duration: 0.5 }); } Event.observe(''yourLinkId'', ''click'', toggleLink.bindAsEventListener(''d3''); ... -- Christophe Porteneuve aka TDD tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
Ya know, I see comments like this fairly regularly on the list, and it''s starting to grate a bit. There is nothing wrong with doing it the way he did. It''s faster to code when coding by hand. It will respond to events as soon as it''s displayed rather than after the entire page has loaded. Etc., etc. Yes, you are correct that current practice is to separate behavior from semantic meaning and meta-data. Yes, coding in a consistent style through multiple projects makes code easier to revisit. Yes, all of the (blee/lead)ding edge standards go so far as to suggest all js be in a separate file. In all of this, we forget that the "old ways" still work. You see, you took 5 lines to accomplish what he did with an inline handler. Sometimes quick and dirty is just fine (especially with an older DOCTYPE). Let''s not be too zealous about it. TAG On Sep 14, 2006, at 9:58 AM, Christophe Porteneuve aka TDD wrote:> > Hey again, > > matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org a écrit : >> <a href="#" onclick="Effect.toggle(''d3'',''appear''); return >> false;">Toggle appear</a> > > BTW, this code is, well... ''could be better, I guess, is a nice > way to > qualify it. First, the "return false" thing is dead. Dead, dead, > dead. > Second, you shouldn''t put JS events in your HTML like that; you > should > use unobstrusive JS. > > For instance, you should assign this link an ID, then observe it > from an > external script file, with something such as: > > > function toggleLink(e) { > Event.stop(e); > Effect.toggle(''d3'', ''appear'', { duration: 0.5 }); > } // toggleLink > > Event.observe(''yourLinkId'', ''click'', toggleLink); > > If you wish to reuse the toggleLink function on multiple links, for > multiple DIVs, you can: > > function toggleLink(e, containerId) { > Event.stop(e); > Effect.toggle(containerId, ''appear'', { duration: 0.5 }); > } > > Event.observe(''yourLinkId'', ''click'', > toggleLink.bindAsEventListener(''d3''); > ... > > -- > Christophe Porteneuve aka TDD > tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
Hi Tom. While I feel what you''re saying, at the same time I think sometimes we "seasoned" folks forget how we got here. For some people just entering this arena, who may not yet be aware of the golden separation of concerns/semanticially correct models, it may just be that they need to hear it in order to move through that natural progression... and if we stop actively ranting about it then we''re just leaving it to chance for them to stumble upon an article on the subject (not that there is any shortage of those)... whereas we can keep up the good fight and help out the noobs by pointing out these methods, even though that may come across as being pedantic at times... just some thoughts from the flip side I guess. On 9/14/06, Tom Gregory <tomg-PGZyUNKar/Q@public.gmane.org> wrote:> > > Ya know, I see comments like this fairly regularly on the list, and > it''s starting to grate a bit. > > There is nothing wrong with doing it the way he did. It''s faster to > code when coding by hand. It will respond to events as soon as it''s > displayed rather than after the entire page has loaded. Etc., etc. > > Yes, you are correct that current practice is to separate behavior > from semantic meaning and meta-data. Yes, coding in a consistent > style through multiple projects makes code easier to revisit. Yes, > all of the (blee/lead)ding edge standards go so far as to suggest all > js be in a separate file. In all of this, we forget that the "old > ways" still work. You see, you took 5 lines to accomplish what he did > with an inline handler. > > Sometimes quick and dirty is just fine (especially with an older > DOCTYPE). Let''s not be too zealous about it. > > > TAG > > On Sep 14, 2006, at 9:58 AM, Christophe Porteneuve aka TDD wrote: > > > > > Hey again, > > > > matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org a écrit : > >> <a href="#" onclick="Effect.toggle(''d3'',''appear''); return > >> false;">Toggle appear</a> > > > > BTW, this code is, well... ''could be better, I guess, is a nice > > way to > > qualify it. First, the "return false" thing is dead. Dead, dead, > > dead. > > Second, you shouldn''t put JS events in your HTML like that; you > > should > > use unobstrusive JS. > > > > For instance, you should assign this link an ID, then observe it > > from an > > external script file, with something such as: > > > > > > function toggleLink(e) { > > Event.stop(e); > > Effect.toggle(''d3'', ''appear'', { duration: 0.5 }); > > } // toggleLink > > > > Event.observe(''yourLinkId'', ''click'', toggleLink); > > > > If you wish to reuse the toggleLink function on multiple links, for > > multiple DIVs, you can: > > > > function toggleLink(e, containerId) { > > Event.stop(e); > > Effect.toggle(containerId, ''appear'', { duration: 0.5 }); > > } > > > > Event.observe(''yourLinkId'', ''click'', > > toggleLink.bindAsEventListener(''d3''); > > ... > > > > -- > > Christophe Porteneuve aka TDD > > tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org > > > > > > > > > >-- Ryan Gahl Application Development Consultant Athena Group, Inc. Inquire: 1-888-919-8700 x2903 Blog: http://www.someElement.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
I think it''s more the manner than the message. He could''ve just said "It''s better to do it this way", but he said "it''s dead, dead, dead". Kind of over-dramatic, if you ask me, which you didn''t :-) Anyhoo, that''s my $0.02. Greg ________________________________ From: rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org [mailto:rubyonrails-spinoffs@googlegroups.com] On Behalf Of Ryan Gahl Sent: Thursday, September 14, 2006 10:42 AM To: rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Subject: [Rails-spinoffs] Re: scriptaculous Toggle Appear rate Hi Tom. While I feel what you''re saying, at the same time I think sometimes we "seasoned" folks forget how we got here. For some people just entering this arena, who may not yet be aware of the golden separation of concerns/semanticially correct models, it may just be that they need to hear it in order to move through that natural progression... and if we stop actively ranting about it then we''re just leaving it to chance for them to stumble upon an article on the subject (not that there is any shortage of those)... whereas we can keep up the good fight and help out the noobs by pointing out these methods, even though that may come across as being pedantic at times... just some thoughts from the flip side I guess. On 9/14/06, Tom Gregory <tomg-PGZyUNKar/Q@public.gmane.org> wrote: Ya know, I see comments like this fairly regularly on the list, and it''s starting to grate a bit. There is nothing wrong with doing it the way he did. It''s faster to code when coding by hand. It will respond to events as soon as it''s displayed rather than after the entire page has loaded. Etc., etc. Yes, you are correct that current practice is to separate behavior from semantic meaning and meta-data. Yes, coding in a consistent style through multiple projects makes code easier to revisit. Yes, all of the (blee/lead)ding edge standards go so far as to suggest all js be in a separate file. In all of this, we forget that the "old ways" still work. You see, you took 5 lines to accomplish what he did with an inline handler. Sometimes quick and dirty is just fine (especially with an older DOCTYPE). Let''s not be too zealous about it. TAG On Sep 14, 2006, at 9:58 AM, Christophe Porteneuve aka TDD wrote:> > Hey again, > > matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org a écrit : >> <a href="#" onclick="Effect.toggle(''d3'',''appear''); return >> false;">Toggle appear</a> > > BTW, this code is, well... ''could be better, I guess, is a nice > way to > qualify it. First, the "return false" thing is dead. Dead, dead, > dead. > Second, you shouldn''t put JS events in your HTML like that; you > should > use unobstrusive JS. > > For instance, you should assign this link an ID, then observe it > from an > external script file, with something such as: > > > function toggleLink(e) { > Event.stop(e); > Effect.toggle(''d3'', ''appear'', { duration: 0.5 }); > } // toggleLink > > Event.observe(''yourLinkId'', ''click'', toggleLink); > > If you wish to reuse the toggleLink function on multiple links, for > multiple DIVs, you can: > > function toggleLink(e, containerId) { > Event.stop(e); > Effect.toggle(containerId, ''appear'', { duration: 0.5 }); > } > > Event.observe(''yourLinkId'', ''click'', > toggleLink.bindAsEventListener (''d3''); > ... > > -- > Christophe Porteneuve aka TDD > tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org > > >Athena Group, Inc. Inquire: 1-888-919-8700 x2903 Blog: http://www.someElement.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
:-) I can see that. I can also understand being adamant about something, and the fact that when replying to a list like this it''s not often practical to take time to edit for emotion, so that adamant tone can seep in pretty easily. Harmless really, if the readers can filter it out effectively. My rule of thumb: look for the message, ignore the emotion. Sorry, we''re waxing philisophical I guess, and I''m just in that kind of mood this morning. Resume normalcy now... On 9/14/06, Hill, Greg <grhill-W2hqgAdRMsX2eFz/2MeuCQ@public.gmane.org> wrote:> > I think it''s more the manner than the message. He could''ve just said > "It''s better to do it this way", but he said "it''s dead, dead, dead". Kind > of over-dramatic, if you ask me, which you didn''t J > > > > Anyhoo, that''s my $0.02. > > > > Greg > > > ------------------------------ > > *From:* rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org [mailto: > rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org] *On Behalf Of *Ryan Gahl > *Sent:* Thursday, September 14, 2006 10:42 AM > *To:* rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > *Subject:* [Rails-spinoffs] Re: scriptaculous Toggle Appear rate > > > > Hi Tom. While I feel what you''re saying, at the same time I think > sometimes we "seasoned" folks forget how we got here. For some people just > entering this arena, who may not yet be aware of the golden separation of > concerns/semanticially correct models, it may just be that they need to hear > it in order to move through that natural progression... and if we stop > actively ranting about it then we''re just leaving it to chance for them to > stumble upon an article on the subject (not that there is any shortage of > those)... whereas we can keep up the good fight and help out the noobs by > pointing out these methods, even though that may come across as being > pedantic at times... just some thoughts from the flip side I guess. > > On 9/14/06, *Tom Gregory* <tomg-PGZyUNKar/Q@public.gmane.org> wrote: > > > Ya know, I see comments like this fairly regularly on the list, and > it''s starting to grate a bit. > > There is nothing wrong with doing it the way he did. It''s faster to > code when coding by hand. It will respond to events as soon as it''s > displayed rather than after the entire page has loaded. Etc., etc. > > Yes, you are correct that current practice is to separate behavior > from semantic meaning and meta-data. Yes, coding in a consistent > style through multiple projects makes code easier to revisit. Yes, > all of the (blee/lead)ding edge standards go so far as to suggest all > js be in a separate file. In all of this, we forget that the "old > ways" still work. You see, you took 5 lines to accomplish what he did > with an inline handler. > > Sometimes quick and dirty is just fine (especially with an older > DOCTYPE). Let''s not be too zealous about it. > > > TAG > > On Sep 14, 2006, at 9:58 AM, Christophe Porteneuve aka TDD wrote: > > > > > Hey again, > > > > matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org a écrit : > >> <a href="#" onclick="Effect.toggle(''d3'',''appear''); return > >> false;">Toggle appear</a> > > > > BTW, this code is, well... ''could be better, I guess, is a nice > > way to > > qualify it. First, the "return false" thing is dead. Dead, dead, > > dead. > > Second, you shouldn''t put JS events in your HTML like that; you > > should > > use unobstrusive JS. > > > > For instance, you should assign this link an ID, then observe it > > from an > > external script file, with something such as: > > > > > > function toggleLink(e) { > > Event.stop(e); > > Effect.toggle(''d3'', ''appear'', { duration: 0.5 }); > > } // toggleLink > > > > Event.observe(''yourLinkId'', ''click'', toggleLink); > > > > If you wish to reuse the toggleLink function on multiple links, for > > multiple DIVs, you can: > > > > function toggleLink(e, containerId) { > > Event.stop(e); > > Effect.toggle(containerId, ''appear'', { duration: 0.5 }); > > } > > > > Event.observe(''yourLinkId'', ''click'', > > toggleLink.bindAsEventListener (''d3''); > > ... > > > > -- > > Christophe Porteneuve aka TDD > > tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org > > > > > > > > Athena Group, Inc. > Inquire: 1-888-919-8700 x2903 > Blog: http://www.someElement.com > > > > >-- Ryan Gahl Application Development Consultant Athena Group, Inc. Inquire: 1-888-919-8700 x2903 Blog: http://www.someElement.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---
Completely true. "Unobstrusive" JS is nice for bigger things, but in many situations it''s overengineering. I also kind of dislike the definition of this as "unobstrusive". If you name a programming technique in a negative way, you''re automatically saying that other ways of achieving the result are worse. Which they aren''t in this case. Both approaches are valid. I presonally tend to use both at the same time, external JS when I need something in more than one place, and inline stuff if it''s just a quick fire and forget thing (when "coding by hand", as opposed to using things like the Rails UJS plugin). I also concur with Tom that your LOC count is a good measuring device for this. -Thomas Am 14.09.2006 um 18:21 schrieb Tom Gregory:> > Ya know, I see comments like this fairly regularly on the list, and > it''s starting to grate a bit. > > There is nothing wrong with doing it the way he did. It''s faster to > code when coding by hand. It will respond to events as soon as it''s > displayed rather than after the entire page has loaded. Etc., etc. > > Yes, you are correct that current practice is to separate behavior > from semantic meaning and meta-data. Yes, coding in a consistent > style through multiple projects makes code easier to revisit. Yes, > all of the (blee/lead)ding edge standards go so far as to suggest all > js be in a separate file. In all of this, we forget that the "old > ways" still work. You see, you took 5 lines to accomplish what he did > with an inline handler. > > Sometimes quick and dirty is just fine (especially with an older > DOCTYPE). Let''s not be too zealous about it. > > > TAG > > On Sep 14, 2006, at 9:58 AM, Christophe Porteneuve aka TDD wrote: > >> >> Hey again, >> >> matt1dmb-aYIB8uWIUb2Vn7q6wjsIow@public.gmane.org a écrit : >>> <a href="#" onclick="Effect.toggle(''d3'',''appear''); return >>> false;">Toggle appear</a> >> >> BTW, this code is, well... ''could be better, I guess, is a nice >> way to >> qualify it. First, the "return false" thing is dead. Dead, dead, >> dead. >> Second, you shouldn''t put JS events in your HTML like that; you >> should >> use unobstrusive JS. >> >> For instance, you should assign this link an ID, then observe it >> from an >> external script file, with something such as: >> >> >> function toggleLink(e) { >> Event.stop(e); >> Effect.toggle(''d3'', ''appear'', { duration: 0.5 }); >> } // toggleLink >> >> Event.observe(''yourLinkId'', ''click'', toggleLink); >> >> If you wish to reuse the toggleLink function on multiple links, for >> multiple DIVs, you can: >> >> function toggleLink(e, containerId) { >> Event.stop(e); >> Effect.toggle(containerId, ''appear'', { duration: 0.5 }); >> } >> >> Event.observe(''yourLinkId'', ''click'', >> toggleLink.bindAsEventListener(''d3''); >> ... >> >> -- >> Christophe Porteneuve aka TDD >> tdd-x+CfDp/qHev2eFz/2MeuCQ@public.gmane.org >> >>> > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs -~----------~----~----~----~------~----~------~--~---