PeriodicalUpdater is actually pretty easy to extract from Prototype, or to
simply rewrite yourself. It's just a wrapper around the
window.setInterval method, combined with the equivalent of $.load().
In fact, I think there's a plugin that does just that, called jHeartbeat.
Check the plugins page.
- Brian
> Think perhaps that jQuery rounded corners in one of those that needs to
> be re-done, 'cos
> no matter what order I call the libraries, whether I use
> jQuery.noConflict() or not, it just
> will not round the box corners.
>
> The sole reason of trying to use prototype is cos of PeriodicalUpdater
> which makes it easy
> for me to loop a function. I say easy cos I'm not a coder. So if anyone
> can point out a
> jQuery-equivalent to PeriodicalUpdater, I'll just stick with jQuery for
> all my js needs.
>
> TIA
>
> Mike Alsup wrote:
>>
>> Kelly,
>>
>> I assume that "your code" is jQuery based. The easiest approach is to
>> simply scope your code like this:
>>
>> (function($) {
>>
>> // your code here
>>
>> })(jQuery);
>>
>> This lets you write in typical jQuery style (using the $ symbol)
>> without worrying about collisions with other libraries. Most jQuery
>> plugins have been refactored to use this approach. However, as I
>> pointed our earlier, some older plugins still assume that $ == jQuery.
>> Thickbox is an older plugin that is known to rely on $ but Klaus
>> Hartl is currently rewritting it and a new and improved version will
>> be available soon(ish).
>>
>> Mike
>>
>>
>> On 4/23/07, kerford <[EMAIL PROTECTED]> wrote:
>>>
>>> I'd like to piggyback on this thread if I could. I'm writing for an
>>> environment that may or may not have other libraries included in the
>>> page. It's not something I can know beforehand. I also won't know in
>>> what order libraries (if any) are loaded. What is the best, most
>>> defensive approach to take for this kind of environment?
>>>
>>> Thanks,
>>> Kelly
