> The InPlaceEditor behavior is something that I've intended to be a
> rewrite of the Scripty version in a more Low Pro way but I've not
> started yet.  Although, I keep a few behaivors in subversion they are
> mostly to test and investigate the possiblities - Low Pro is a
> framework for attaching behaviors to elements not a widget library as
> such and I don't intend to write lots of behaviors with Low Pro.

> However, you can create a behavior wrapper around the scripty
> InPlaceEditor really easily that will allow you to attach it with
> Event.addBehavior:

> InPlaceEditor = Behavior.create({
>   initialize: function(url, options) {
>     this.ipe = new Ajax.InPlaceEditor( this.element, url, options || {});
>   }

> });

> Then attach with:

> Event.addBehavior({
>   'h2.editable': InPlaceEditor('/products', { method: 'post' });

> });

> You can do a similar thing with all the scripty widgets as well.

> Cheers,

> Dan

> On 1/29/08, Chris Cruft <c...@hapgoods.com> wrote:

> > I've recently been foiled by the pluginification of InPlaceEditor and
> > AutoCompleter in RoR and their incompatibilities with the current
> > Scriptaculous and Prototype.  In the past, being very comfortable in
> > Ruby,  I would have simply monkey patched the in_place_editor (for
> > example) to pass the htmlResponse variable.  But after doing some
> > research, I'm convinced that the Rails helpers are evil: I buy into
> > the behavior/content/style separation argument and I'm convinced that
> > the differing dev cycles on the three projects means the helpers will
> > forever be out of sync.

> > What's a developer to do?  I looked at jQuery, but I'm not ready to
> > ditch Prototype and Scriptaculous.  Then I found LowPro.  And while I
> > really don't like the idea of yet another library, I would consider a
> > small one if it is slick.

> > My first stab a LowPro involved removing the Rails JS helper
> > in_place_editor and adding code to application.js to add this behavior
> > to the relevant elements.  But WHERE is the InPlaceEditor behavior?
> > This behavior file in the lowpro subversion repository is only a
> > skeleton.  And the AutoCompleter is totally empty!  What gives?  Am I
> > expected to stitch Scriptaculous' AutoCompleter into LowPro myself?
> > If so, can anyone point me to an example?

> > -Chris

> --
> Dan Webbhttp://www.danwebb.net

> aim: danwrong123
> skype: danwrong