Robby Russell wrote: > On Sun, Oct 5, 2008 at 5:38 AM, Jon Stenqvist > <[EMAIL PROTECTED]> wrote: >>> Maybe Im not understanding your situation, but filters are more used for >>> application logic and typical cases like logging, benchmarking etc. >>> Wouldnt it be better to use the layouts folder and stick the javascript >>> in there ? >> >> This will be a plugin that enable auto-refresh with ajax, and the >> after_filter is starting the javascript-update-check-script for the >> configured actions. > > This isn't really how you'd use the before/after filters. What it > sounds like is that you need to be able to trigger js to be called on > specific actions? You might consider adding the js code to your > application layout view... and use a before filter on the specific > actions you want this to run and have that show the corresponding js. > > For example: > > before_filter :trigger_js_stuff > > def trigger_js_stuff > @reload_page = true > end > > In your view... > > > <% if @reload_page %> > // trigger your js code here > <% end %> > > Good luck! > > Robby
Thanks Robby, i just put it on github, please have a look and see if it's correct usage, http://github.com/jnstq/content_refresher/tree/master. I would like to just javascript_tag @ line 60 on http://github.com/jnstq/content_refresher/tree/master/lib/equipe/content_refresher.rb Jon -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
