<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-23105477.post1336810715345737715..comments</id><updated>2007-02-11T18:24:54.386-05:00</updated><title type='text'>Comments on Web Development Central: Is E4X Strong Enough to Obviate the Need for an Ob...</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.webdevelopmentcentral.net/feeds/1336810715345737715/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/23105477/1336810715345737715/comments/default'/><link rel='alternate' type='text/html' href='http://www.webdevelopmentcentral.net/2007/02/is-e4x-strong-enough-to-obviate-need.html'/><author><name>HUWebDev</name><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>3</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-23105477.post-2330955290970463171</id><published>2007-02-11T20:21:00.000-05:00</published><updated>2007-02-11T20:21:00.000-05:00</updated><title type='text'>I've worked fairly heavily with e4X on the Mozilla...</title><summary type='text'>I've worked fairly heavily with e4X on the Mozilla side, and tend to agree with your assessment about the object method limitation. Typically, the only way around it is to build a wrapper on the e4X object itself:&lt;BR/&gt;&lt;BR/&gt;var E4X = function(e4x,props){ &lt;BR/&gt;   var _E4X = this; &lt;BR/&gt;   this.e4x = e4x; &lt;BR/&gt;   for (key in props){ &lt;BR/&gt;       _E4X[key] = props[key]; &lt;BR/&gt;       } &lt;BR/&gt;    } &lt;BR/&gt;&lt;</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/23105477/1336810715345737715/comments/default/2330955290970463171'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/23105477/1336810715345737715/comments/default/2330955290970463171'/><link rel='alternate' type='text/html' href='http://www.webdevelopmentcentral.net/2007/02/is-e4x-strong-enough-to-obviate-need.html?showComment=1171243260000#c2330955290970463171' title=''/><author><name>Kurt</name><uri>http://www.blogger.com/profile/11746604103523406806</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.webdevelopmentcentral.net/2007/02/is-e4x-strong-enough-to-obviate-need.html' ref='tag:blogger.com,1999:blog-23105477.post-1336810715345737715' source='http://www.blogger.com/feeds/23105477/posts/default/1336810715345737715' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-23105477.post-7161632023240829705</id><published>2007-02-11T18:24:00.000-05:00</published><updated>2007-02-11T18:24:00.000-05:00</updated><title type='text'>It's tempting to use the XML directly now with E4X...</title><summary type='text'>It's tempting to use the XML directly now with E4X, pass it around to the classes that need it etc, but I think there's still value in creating a strongly typed model that your application refers to. &lt;BR/&gt;&lt;BR/&gt;If you ever decided to power your app without XML you'd be able to switch over without a global search and replace. You'd just need to modify the way in which your model objects were </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/23105477/1336810715345737715/comments/default/7161632023240829705'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/23105477/1336810715345737715/comments/default/7161632023240829705'/><link rel='alternate' type='text/html' href='http://www.webdevelopmentcentral.net/2007/02/is-e4x-strong-enough-to-obviate-need.html?showComment=1171236240000#c7161632023240829705' title=''/><author><name>Tim</name><uri>http://www.blogger.com/profile/10018692172638988873</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.webdevelopmentcentral.net/2007/02/is-e4x-strong-enough-to-obviate-need.html' ref='tag:blogger.com,1999:blog-23105477.post-1336810715345737715' source='http://www.blogger.com/feeds/23105477/posts/default/1336810715345737715' type='text/html'/></entry><entry><id>tag:blogger.com,1999:blog-23105477.post-2191697932615501883</id><published>2007-02-11T14:55:00.000-05:00</published><updated>2007-02-11T14:55:00.000-05:00</updated><title type='text'>If you have any time to make a benchmark I will re...</title><summary type='text'>If you have any time to make a benchmark I will really like to know how it costs to use directly E4X on little or huge structures.</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/23105477/1336810715345737715/comments/default/2191697932615501883'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/23105477/1336810715345737715/comments/default/2191697932615501883'/><link rel='alternate' type='text/html' href='http://www.webdevelopmentcentral.net/2007/02/is-e4x-strong-enough-to-obviate-need.html?showComment=1171223700000#c2191697932615501883' title=''/><author><name>Tek</name><uri>http://www.blogger.com/profile/03639132795534615163</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.webdevelopmentcentral.net/2007/02/is-e4x-strong-enough-to-obviate-need.html' ref='tag:blogger.com,1999:blog-23105477.post-1336810715345737715' source='http://www.blogger.com/feeds/23105477/posts/default/1336810715345737715' type='text/html'/></entry></feed>