Hey Everyone,
So this comes up again, but I can''t help it, its necessary!
Prototype needs better XML collection support. Every time I bring
this up somebody counters it with "Just use JSON" well that''d
be nice
if everyone was on board, or the client developer has control over the
model. In making a gadget for Google Calendar and ripping hair out
trying to traverse massive Atom documents I had to bring this back
up. If prototype isn''t getting on board with an XML API, does anyone
know of another framework that does?
Regards,
Matt
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
Hi Matt, I agree, XML support is by far not Prototype''s strongest point. The fact is, most of the people contributing code to Prototype avoid XML as much as possible, mainly because it''s slow to parse an generally not very friendly to use (at, least, that''s why I avoid it). I think we''d all welcome any patch that allowed for better XML handling, as long as it doesn''t hinder the framework''s general performance or adds excessive bloat. Depending on what''s required, this could also be a good candidate for a plugin. Please feel free to bring up the subject (and any suggestion you might have) to the core mailing list. Thanks, Tobie On Jan 11, 5:42 pm, Matt Foster <mattfoste...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hey Everyone, > > So this comes up again, but I can''t help it, its necessary! > Prototype needs better XML collection support. Every time I bring > this up somebody counters it with "Just use JSON" well that''d be nice > if everyone was on board, or the client developer has control over the > model. In making a gadget for Google Calendar and ripping hair out > trying to traverse massive Atom documents I had to bring this back > up. If prototype isn''t getting on board with an XML API, does anyone > know of another framework that does? > > Regards, > Matt--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
http://www.terracoder.com/ This looks quite promising - and this approach of mapping from xml to json is definitely the way I would go if I did not already have json services behind the scenes. The linked library seems to have originally been written with jQuery in mind, but it says there is now a standalone version that does not require it. Worth a look anyway. On 1/11/08, Tobie Langel <tobie.langel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > > Hi Matt, > > I agree, XML support is by far not Prototype''s strongest point. The > fact is, most of the people contributing code to Prototype avoid XML > as much as possible, mainly because it''s slow to parse an generally > not very friendly to use (at, least, that''s why I avoid it). > > I think we''d all welcome any patch that allowed for better XML > handling, as long as it doesn''t hinder the framework''s general > performance or adds excessive bloat. Depending on what''s required, > this could also be a good candidate for a plugin. > > Please feel free to bring up the subject (and any suggestion you might > have) to the core mailing list. > > Thanks, > > Tobie > > > On Jan 11, 5:42pm, Matt Foster <mattfoste...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > Hey Everyone, > > > > So this comes up again, but I can''t help it, its necessary! > > Prototype needs better XML collection support. Every time I bring > > this up somebody counters it with "Just use JSON" well that''d be nice > > if everyone was on board, or the client developer has control over the > > model. In making a gadget for Google Calendar and ripping hair out > > trying to traverse massive Atom documents I had to bring this back > > up. If prototype isn''t getting on board with an XML API, does anyone > > know of another framework that does? > > > > Regards, > > Matt > > >-- Ryan Gahl Manager, Senior Software Engineer Nth Penguin, LLC http://www.nthpenguin.com -- WebWidgetry.com / MashupStudio.com Future Home of the World''s First Complete Web Platform -- Inquire: 1-920-574-2218 Blog: http://www.someElement.com LinkedIn Profile: http://www.linkedin.com/in/ryangahl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
rubyonrails-lists-V6RNgr6nmX0AvxtiuMwx3w@public.gmane.org
2008-Jan-12 18:01 UTC
Re: Another argument for XML and prototype
I''ve always wanted to take Prototype, rip out all the HTML-specific stuff and tweak the tree traversal and editing stuff to work with XML. Although a side project like this would probably be hard to keep in sync with Prototype, it would be self-contained, have the same syntax as Prototype and may just be a bit faster (than Prototype on HTML trees, not JSON, of course). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
rubyonrails-lists-V6RNgr6nmX0AvxtiuMwx3w@public.gmane.org wrote:> I''ve always wanted to take Prototype, rip out all the HTML-specific > stuff and tweak the tree traversal and editing stuff to work with XML. > Although a side project like this would probably be hard to keep in > sync with Prototype, it would be self-contained, have the same syntax > as Prototype and may just be a bit faster (than Prototype on HTML > trees, not JSON, of course).That would be great! -- Bertilo Wennergren <http://bertilow.com> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---