From: Mike S. <ms...@md...> - 2006-11-20 15:22:54
|
It appears that the new prototype might not be compatible with scriptaculous' sortable list ... I have a really hacked up Ajax framework right now, but can someone else confirm that sortable list demo throws an exception? It appears that the implementation of toQueryString changed in prototype such that it requires unique keys. Scriptaculous' Sortable.serialize, however, takes advantage of the fact that you can define non-unique keys. So if you're using sortable lists right now, just be aware that you might want to stay on the old scriptaculous/prototype until this is worked out. |
From: Timo H. <th...@on...> - 2006-11-20 16:06:31
|
Am 20.11.2006 um 16:22 schrieb Mike Schrag: > It appears that the new prototype might not be compatible with > scriptaculous' sortable list ... I have a really hacked up Ajax > framework right now, but can someone else confirm that sortable list > demo throws an exception? Oops, didn't notice that when I tested with the new versions... Looks like this might be the the problem: http://dev.rubyonrails.org/ticket/4436 It was fixed a few days after scriptacolous 1.6.5. I checked out prototype from svn and with that version, the sortable lists do work again in AjaxExamples. Should we revert to 1.6.4 or switch to the SVN version? Scriptacolous seems to prepare another relase, now titled 1.7.0beta1 (http://dev.rubyonrails.org/changeset/5583) *SVN* * Update to Prototype 1.5.0_rc2 revision [5580] * Add a paramName option to the inplace editor for overriding the default parameter name of "value" * Add Effect.Transform that generates parallel executing Effect.Morph sets Example: // set up transformation var transformation = new Effect.Transform([ { 'div.morphing': 'font-size:20px;padding-left:40em' }, { 'blah' : 'width:480px;border-width:10px;border- right-width:20px;margin:200px;margin-bottom:-20px;font-size:30px' } ],{ duration: 0.5 }); // play transformation (can be called more than once) transformation.play(); * Add Effect.Morph core effect that morphs to a given CSS style rule. Effect.Morph does take orginal styles given by CSS style rules or the style attribute into consideration when calculating the transforms. It works with all length and color based CSS properties, including margins, paddings, borders, opacity and text/background colors. Example: new Effect.Morph('mydiv',{ style: 'font-size:3em;color:#f00;border-width:2em', duration: 2.0 }); Timo |
From: Timo H. <th...@on...> - 2006-11-21 11:13:17
|
Am 20.11.2006 um 17:05 schrieb Timo Hoepfner: > Scriptacolous seems to prepare another relase, now titled 1.7.0beta1 > (http://dev.rubyonrails.org/changeset/5583) > For the record: script.aculo.us 1.7 beta 1 is out: http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta There is also an older blog post on 1.6.5: http://mir.aculo.us/2006/11/8/script-aculo-us-1-6-5 Timo |
From: Mike S. <ms...@md...> - 2006-11-20 16:13:10
|
I'm kind of thinking maybe we should drop back and wait for the official fix so there is less confusion? But I didn't notice what was fixed in 1.6.5. Are there some nasty bugs fixed that we would probably want 1.6.5 in for? On Nov 20, 2006, at 11:05 AM, Timo Hoepfner wrote: > > Am 20.11.2006 um 16:22 schrieb Mike Schrag: > >> It appears that the new prototype might not be compatible with >> scriptaculous' sortable list ... I have a really hacked up Ajax >> framework right now, but can someone else confirm that sortable list >> demo throws an exception? > > Oops, didn't notice that when I tested with the new versions... > > Looks like this might be the the problem: > > http://dev.rubyonrails.org/ticket/4436 > > It was fixed a few days after scriptacolous 1.6.5. > > I checked out prototype from svn and with that version, the > sortable lists do work again in AjaxExamples. > > Should we revert to 1.6.4 or switch to the SVN version? > > Scriptacolous seems to prepare another relase, now titled > 1.7.0beta1 (http://dev.rubyonrails.org/changeset/5583) > > *SVN* > > * Update to Prototype 1.5.0_rc2 revision [5580] > > * Add a paramName option to the inplace editor for overriding the > default parameter name of "value" > > * Add Effect.Transform that generates parallel executing > Effect.Morph sets > Example: > // set up transformation > var transformation = new Effect.Transform([ > { 'div.morphing': 'font-size:20px;padding-left:40em' }, > { 'blah' : 'width:480px;border-width:10px;border- > right-width:20px;margin:200px;margin-bottom:-20px;font-size:30px' } > ],{ duration: 0.5 }); > // play transformation (can be called more than once) > transformation.play(); > > * Add Effect.Morph core effect that morphs to a given CSS style > rule. Effect.Morph does take orginal styles given by CSS style > rules or the style attribute into consideration when calculating > the transforms. It works with all length and color based CSS > properties, including margins, paddings, borders, opacity and text/ > background colors. > Example: > new Effect.Morph('mydiv',{ > style: 'font-size:3em;color:#f00;border-width:2em', > duration: 2.0 > }); > > > Timo > > > |
From: Timo H. <th...@on...> - 2006-11-20 17:04:15
|
> I'm kind of thinking maybe we should drop back and wait for the > official fix so there is less confusion? Done. CVS is back to 1.6.4. > But I didn't notice what > was fixed in 1.6.5. Are there some nasty bugs fixed that we would > probably want 1.6.5 in for? I had it under suspicion for some strange IE issues. I'm now testing the stuff with 1.6.4 again and cannot reproduce the problems. Must have been something else. Sorry for that. Timo |