Prototype would pass:item[]=1&other[]=1&another[]=4That works well with multiple lists; each list gets a unique identifier, and moving items from multiple lists into one list still works.
On 10/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> On Oct 27, 2006, at 8:00, Yehuda Katz wrote:>>> So
>
> On Oct 27, 2006, at 8:00, Yehuda Katz wrote:
>
>> So I'm working on various Rails solutions using jQuery and Interface.
>> The way Rails/Prototype handles sortables is as follows:
>> You have a series of id's in a list: item_2, item_4, item_1,
>> item_3, etc.
>> Prototype serializes as: item[]=
On Oct 27, 2006, at 8:00, Yehuda Katz wrote:
> So I'm working on various Rails solutions using jQuery and Interface.
> The way Rails/Prototype handles sortables is as follows:
> You have a series of id's in a list: item_2, item_4, item_1,
> item_3, etc.
> Prototype serializes as: item[]=2&item[
Is there any reason you can't just use hidden fields with the name "item[]"? I think there is a similar conversion process in PHP, and as long as you don't use the name (and the []) for jQuery selection it shouldn't be a problem. I haven't used the item[]=xy => item[0]="xy" thing myself (ColdFusion
So I'm working on various Rails solutions using jQuery and Interface.The way Rails/Prototype handles sortables is as follows:You have a series of id's in a list: item_2, item_4, item_1, item_3, etc.
Prototype serializes as: item[]=2&item[]=4&item[]=1&item=3 etc.Rails converts the serialized form in
