I must say that IMO xml is dead. Why use such a format when we have a readable, usable formats such as JSON (or even yml)
On Fri, Nov 26, 2010 at 11:21 AM, stratboy <[email protected]> wrote: > Hi thank you but I don't think this will work in IE. > Maybe I'll go for the JSON way, but frankly, I'm quite sad.. > I hope that the mootools devs solve this problem rapidly, because it's > a huge one. > These days where js is massively obfuscating flash, the ability of > easily consume an xml document, for a js library is really important, > a must, i think. Definitely. Also, somewhere I read that jQuery is > already on the right way. Don't know if it's true. But probably. > > > > On 25 Nov, 21:00, Sean McArthur <[email protected]> wrote: > > Not ideal, but you could try passing every element into the $ function. > > > > $($(Slick.search(xml,'regione')[0]).getElement('nome')).get('text') > > > > On Thu, Nov 25, 2010 at 6:48 AM, stratboy <[email protected]> wrote: > > > There's a problem. Explorer. As always. > > > > > Yes Slick.search is good in ff. > > > > > <?xml version="1.0" encoding="utf-8"?> > > > <regioni> > > > <regione> > > > <nome>argentina</nome> > > > <id>22</id> > > > </regione> > > > <regione> > > > <nome>australia</nome> > > > <id>23</id> > > > </regione> > > > </regioni> > > > > > Slick.search(xml,'regione')[0].getElement('nome').get('text'); //ok in > > > ff!!!! > > > > > BUT, explorer stops at .getElement. In general, explorer doesn't > > > understand the Element methods. > > > > > Is there a way to solve this issue? > > > > > On 24 Nov, 17:36, אריה גלזר <[email protected]> wrote: > > > > On Wed, Nov 24, 2010 at 6:34 PM, stratboy <[email protected]> > wrote: > > > > > But how can I pass the xml document to $$? > > > > > > > On 24 Nov, 17:09, Ryan Florence <[email protected]> wrote: > > > > > > $$ = Slick.search(document, selector); > > > > > > Slick.seach(xml,selector); > > > > > > > > You can use either. As for documentation, just pass it a CSS > > > selector > > > > > and you'll get your elements. > > > > > > > > On Nov 24, 2010, at 8:14 AM, stratboy wrote: > > > > > > > > > Excuse me for some reason I posted twice. > > > > > > > > > I wanted to make 2 more questions: > > > > > > > > > 1. The motools built in slick is v0.9, but the current version > is > > > 1.0. > > > > > > > > > console.log(Slick) -> Object { version="0.9dev"} etc.. > > > > > > > > > So, should I use a stand alone Slick v1.0 instead of using the > > > > > > > mootools built in one ? > > > > > > > > > 2. If i use the built in, is there any mootools.slick - like > prop > > > that > > > > > > > references Slick? Or should I always use directly Slick? > > > > > > > > > Thank you > > > > > > > > > On 24 Nov, 15:19, ken <[email protected]> wrote: > > > > > > >> see Slick, it can parse any form of xml > > > > > > > > >> On Nov 24, 7:55 pm, stratboy <[email protected]> wrote: > > > > > > > > >>> Hi, I'm building a small app. > > > > > > >>> My php programmer will pass me some xml file. I was wandering > if > > > > > maybe > > > > > > >>> Element is good even for parsing xml code. > > > > > > >>> Or maybe, is there any other (moo)tool for doing it? > > > > > > -- > > > > Arieh Glazer > > > > אריה גלזר > > > > 052-5348-561 > > > > 5561 > -- Arieh Glazer אריה גלזר 052-5348-561 5561
