Tom, I know the thread, honestly, as I mentioned above, I just don't have the time to digg into this issue.
Regarding the JSON "workaround" - as you call it - the idea was not to offer a workaround, but to trigger a discussion on whether (or not) JSON wasn't a more appropriate solution in some cases, and if we should add toJSON methods for form elements to the framework. As I've said, I'm not familiar with this issue - so I'm basically just thinking out loud here. Regards, Tobie On Mar 26, 5:28 pm, Tom Gregory <[EMAIL PROTECTED]> wrote: > On Mar 26, 2007, at 3:06 PM, Tobie Langel wrote: > > > Honestly, I haven't followed the toQueryString debate myself to > > closely... so I can't really voice an opinion. > > FYI, the discussion he's referring to is > here:http://groups.google.com/group/prototype-core/browse_frm/thread/ > 0140fdf88eed057d > > The JSON answer you give--while accurate--is, I think, not germane to > the discussion of how the library should behave. Yes, there are > workarounds, but that's not the point he's trying to make. > > I don't agree with everything Colin says, but I would like to see > some response from the Core Team. He makes some valid points that I > believe deserve consideration, especially concerning Ajax.Request. > The last thread on the issue just sorta died. > > TAG --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
