ReassignafterAjax in jq lowpro - Low Pro

Message from discussion ReassignafterAjax in jq lowpro

Dan Webb

More options 21 Apr, 15:56

From: "Dan Webb" <d...@danwebb.net>

Date: Mon, 21 Apr 2008 15:56:25 +0100

Local: Mon 21 Apr 2008 15:56

Subject: Re: ReassignafterAjax in jq lowpro

  Reply to author
  |
  Forward | Print | View thread
  | Show original
  | Report this message | Find messages by this author
  

Cheers Wynn, you beat me to it!

On Mon, Apr 21, 2008 at 3:52 PM, Wynn Netherland

<wynn.netherl...@gmail.com> wrote:

> Oops, I think I replied privately. Posting again here for the benefit
> of the group:

> Be sure you have livequery referenced in your <HEAD> before lowpro:

> http://brandonaaron.net/docs/livequery/

> Dan's attach method will look for it and automatically wire up this
> functionality for you if the script is there.

> Wynn Netherland
> Bit Wrangler, Geek Herder
> Squeejee
> www.squeejee.com

> On 20 Apr, 22:11, michelson <miguelmichel...@gmail.com> wrote:
> > Hi there,

> > im using the JQuery Lowpro, im trying to make an ajax will_paginate
> > links in a rails proyect, i have the following code in application.js
> > :
> > jQuery(function($) {
> > $('div.pagination a').attach(Remote.Link, { type: 'GET', dataType:
> > 'script' });
> > });

> > and in my controller:

> > @artists = Role.artists.users.top_artists(50).paginate :page =>
> > params[:page],:per_page => 8

> > respond_to do |format|
> > format.html # index.html.erb
> > format.js do
> > render :update do |page|
> > page.replace_html 'photos', :partial => "photos"
> > end
> > end
> > end

> > and the ajax call works!, but only for one time, since the ajax page
> > loads the links works like normal links and not like Remote.links.

> > i think that`s because the paginate links are loaded into the called
> > page, and I not declaring the ReassignafterAjax, is this correct?.

> > if that is the problem, how can I declare this behavior in jqlowpro?

> > regards

--
Dan Webb
http://www.danwebb.net

aim: danwrong123
skype: danwrong

Reply to author Forward