Filippos wrote in post #974933:
> i tried it but i've run into other posts asking the same question.
> Not any answer related to Rails 3 and Periodically_call_remote

I'd guess that periodically_call_remote was pulled because it's directly 
dependent on the Prototype JavaScript framework. It's a thin wrapper 
around Ajax.PeriodicalUpdater.

http://api.prototypejs.org/ajax/Ajax/PeriodicalUpdater/

In any case it's relatively easy to implement that functionality. The JS 
frameworks don't even really make it all that much easier than straight 
up JavaScript.

If you really want it back the helper has been extracted to:

https://github.com/rails/prototype_legacy_helper

-----------------
def periodically_call_remote(options = {})
     frequency = options[:frequency] || 10 # every ten seconds by 
default
     code = "new PeriodicalExecuter(function() 
{#{remote_function(options)}}, #{frequency})"
     javascript_tag(code)
  end
-----------------

As you can see here, all it really does is write out some JavaScript 
that you could easily write yourself. To make matters worse, the helper 
writes Obtrusive JavaScript. Rails 3 is has moved to Unobtrusive 
JavaScript (UJS), which is probably another reason this was extracted.

-- 
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 [email protected].
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.

Reply via email to