Another argument for XML and prototype

3 views
Skip to first unread message

Matt Foster

unread,
Jan 11, 2008, 11:42:05 AM1/11/08
to Ruby on Rails: Spinoffs
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

Tobie Langel

unread,
Jan 11, 2008, 1:20:51 PM1/11/08
to Ruby on Rails: Spinoffs
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

Ryan Gahl

unread,
Jan 11, 2008, 1:40:43 PM1/11/08
to rubyonrail...@googlegroups.com
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....@gmail.com> 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...@gmail.com> 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

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

sli...@gmail.com

unread,
Jan 12, 2008, 1:01:47 PM1/12/08
to Ruby on Rails: Spinoffs
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).

Bertilo Wennergren

unread,
Jan 13, 2008, 1:14:24 AM1/13/08
to rubyonrail...@googlegroups.com
rubyonra...@6bitt.com wrote:

That would be great!

--
Bertilo Wennergren <http://bertilow.com>

Reply all
Reply to author
Forward
0 new messages