Let me provide a little more info as a motivation for an answer. I realize that I could use PPR to allow changes to the page to occur without having to overload the shuttle button functionality; however, I'm trying to avoid the client/server round trip for one thing. Another issue; however, is that I also want the user to be able to modify an animated JavaScript object within the page from within the browser so that they can see the effect of their changes _before_ they have to commit their final changes which will, in turn, cause an immediate site-wide change, since this object is displayed on every page of the site. Changes to the shuttle list items will affect this animated object, so I need control over the shuttle buttons so that I can react immediately within the browser to user changes.
Given this, is the approach that I describe below the only one available
to me?
-=>
Gregg <=-
Gregg Leichtman wrote:
> I looked in the forum archive and didn't see anything pertinent to this
> question.
>
> Is there a recommended way to replace the JavaScript functionality of
> the shuttle buttons such as move, remove, move up, move down, etc.? I
> see that these "buttons" are generated as anchor href's using JavaScript
> bookmarklets, but there is no generated HTML ID or name associated with
> the buttons and the only way that I can see to modify the generated
> JavaScript code is to track down the link tag using the unique button
> text, which is a fragile way to do this of course, and then replace the
> href handler with my own bookmarklet handler.
>
> I want to do this, because I need to trigger additional JavaScript
> functionality when the user clicks these buttons.
>
> -=> Gregg <=-
>
>
>
signature.asc
Description: OpenPGP digital signature
