Re: [flexcoders] XML vs Model?
Thanks All! :) I think XML is the best buy for my situation but will keep the above opinions in the back of the mind for future use. On 5/18/05, Indy Nagpal <[EMAIL PROTECTED]> wrote: > Performance-wise I find that both to be equivalent. But > provides a much easier way to access nodes of an xml document (and > most of the times, the easier, the better!). But I agree with Matt's > observation that serves a better dataProvider for the Tree > control. > > Indy > > On 5/18/05, Tracy Spratt <[EMAIL PROTECTED]> wrote: > > One of my issues with Model is I had trouble determining how the xml was > > going to be deserialized into the object. What happens to attributes? > > What happens to child nodes and text nodes? > > > > Since I was comfortable with xml I mostly stuck with that. I haven't > > even needed the available Xpath library yet. And I hear that improved > > XML support is on the way. > > Tracy > > > > -Original Message- > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > > Behalf Of Abdul Qabiz > > Sent: Tuesday, May 17, 2005 6:08 AM > > To: flexcoders@yahoogroups.com > > Subject: RE: [flexcoders] XML vs Model? > > > > They are similar things IMO. If you specify a source file for XML or > > Model > > tag, source (xml)file is compiled into swf. So no loading on runtime but > > a > > large initial swf size. P > > > > I think, Model should be good at performance because it is simple Object > > not > > a XMLNode. > > > > Let's see, what other people say... > > > > -abdul > > > > -Original Message- > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > > Behalf Of Scott Barnes > > Sent: Tuesday, May 17, 2005 12:03 PM > > To: flexcoders@yahoogroups.com > > Subject: [flexcoders] XML vs Model? > > > > I've got a external source that pulls in XML file (config). > > > > Now, I'm having my own internal debate as to which of the two is > > betterere? > > > > I've noticed no real signficant performance gains (via profiler) with > > using either, the only thing it kind of brings to the table is that > > you can access a node XYZ levels deep by using property chains > > (parent.child.infant.siblings). > > > > Thats fine, but this will be parsed once-off, and i've found that i've > > i go the XML route (ie writing my own specific parser, it tends to be > > less work. > > > > (in that i've found that you have nodes in your XML that are using the > > same name, but can be either 1 or more, you have to test to see if the > > node in question is an array, otherwise its a literal object and treat > > it as such - when using model vs childNodes approach via XML (which is > > always array). > > > > What's folks here input on pro's / con's of XML vs Model? > > -- > > Regards, > > Scott Barnes > > http://www.mossyblog.com > > http://www.flexcoder.com > > > > Yahoo! Groups Links > > > > Yahoo! Groups Links > > > > > > Yahoo! Groups Links > > > > > > > > > > > > Yahoo! Groups Links > > > > > -- Regards, Scott Barnes http://www.mossyblog.com http://www.flexcoder.com (Coming Soon) Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
Re: [flexcoders] XML vs Model?
Performance-wise I find that both to be equivalent. But provides a much easier way to access nodes of an xml document (and most of the times, the easier, the better!). But I agree with Matt's observation that serves a better dataProvider for the Tree control. Indy On 5/18/05, Tracy Spratt <[EMAIL PROTECTED]> wrote: > One of my issues with Model is I had trouble determining how the xml was > going to be deserialized into the object. What happens to attributes? > What happens to child nodes and text nodes? > > Since I was comfortable with xml I mostly stuck with that. I haven't > even needed the available Xpath library yet. And I hear that improved > XML support is on the way. > Tracy > > -Original Message- > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Abdul Qabiz > Sent: Tuesday, May 17, 2005 6:08 AM > To: flexcoders@yahoogroups.com > Subject: RE: [flexcoders] XML vs Model? > > They are similar things IMO. If you specify a source file for XML or > Model > tag, source (xml)file is compiled into swf. So no loading on runtime but > a > large initial swf size. P > > I think, Model should be good at performance because it is simple Object > not > a XMLNode. > > Let's see, what other people say... > > -abdul > > -Original Message- > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Scott Barnes > Sent: Tuesday, May 17, 2005 12:03 PM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] XML vs Model? > > I've got a external source that pulls in XML file (config). > > Now, I'm having my own internal debate as to which of the two is > betterere? > > I've noticed no real signficant performance gains (via profiler) with > using either, the only thing it kind of brings to the table is that > you can access a node XYZ levels deep by using property chains > (parent.child.infant.siblings). > > Thats fine, but this will be parsed once-off, and i've found that i've > i go the XML route (ie writing my own specific parser, it tends to be > less work. > > (in that i've found that you have nodes in your XML that are using the > same name, but can be either 1 or more, you have to test to see if the > node in question is an array, otherwise its a literal object and treat > it as such - when using model vs childNodes approach via XML (which is > always array). > > What's folks here input on pro's / con's of XML vs Model? > -- > Regards, > Scott Barnes > http://www.mossyblog.com > http://www.flexcoder.com > > Yahoo! Groups Links > > Yahoo! Groups Links > > > Yahoo! Groups Links > > > > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
RE: [flexcoders] XML vs Model?
One of my issues with Model is I had trouble determining how the xml was going to be deserialized into the object. What happens to attributes? What happens to child nodes and text nodes? Since I was comfortable with xml I mostly stuck with that. I haven't even needed the available Xpath library yet. And I hear that improved XML support is on the way. Tracy -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Abdul Qabiz Sent: Tuesday, May 17, 2005 6:08 AM To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] XML vs Model? They are similar things IMO. If you specify a source file for XML or Model tag, source (xml)file is compiled into swf. So no loading on runtime but a large initial swf size. P I think, Model should be good at performance because it is simple Object not a XMLNode. Let's see, what other people say... -abdul -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Scott Barnes Sent: Tuesday, May 17, 2005 12:03 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] XML vs Model? I've got a external source that pulls in XML file (config). Now, I'm having my own internal debate as to which of the two is betterere? I've noticed no real signficant performance gains (via profiler) with using either, the only thing it kind of brings to the table is that you can access a node XYZ levels deep by using property chains (parent.child.infant.siblings). Thats fine, but this will be parsed once-off, and i've found that i've i go the XML route (ie writing my own specific parser, it tends to be less work. (in that i've found that you have nodes in your XML that are using the same name, but can be either 1 or more, you have to test to see if the node in question is an array, otherwise its a literal object and treat it as such - when using model vs childNodes approach via XML (which is always array). What's folks here input on pro's / con's of XML vs Model? -- Regards, Scott Barnes http://www.mossyblog.com http://www.flexcoder.com Yahoo! Groups Links Yahoo! Groups Links Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
RE: [flexcoders] XML vs Model?
>>What's folks here input on pro's / con's of XML vs Model?
It doesn't sound like it applies to your situation, but XML works better
as a dataprovider to the Tree and other list-based controls than does
Model. I found this out when working through a customer issue. Doc'd
here:
http://livedocs.macromedia.com/flex/15/flex_docs_en/0624.htm
hth,
matt horn
flex docs
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Barnes
Sent: Tuesday, May 17, 2005 2:33 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] XML vs Model?
I've got a external source that pulls in XML file (config).
Now, I'm having my own internal debate as to which of the two is
betterere?
I've noticed no real signficant performance gains (via profiler)
with
using either, the only thing it kind of brings to the table is
that
you can access a node XYZ levels deep by using property chains
(parent.child.infant.siblings).
Thats fine, but this will be parsed once-off, and i've found
that i've
i go the XML route (ie writing my own specific parser, it tends
to be
less work.
(in that i've found that you have nodes in your XML that are
using the
same name, but can be either 1 or more, you have to test to see
if the
node in question is an array, otherwise its a literal object and
treat
it as such - when using model vs childNodes approach via XML
(which is
always array).
What's folks here input on pro's / con's of XML vs Model?
--
Regards,
Scott Barnes
http://www.mossyblog.com
http://www.flexcoder.com
Yahoo! Groups Links
* To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
* Your use of Yahoo! Groups is subject to the Yahoo! Terms
of Service <http://docs.yahoo.com/info/terms/> .
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
RE: [flexcoders] XML vs Model?
They are similar things IMO. If you specify a source file for XML or Model tag, source (xml)file is compiled into swf. So no loading on runtime but a large initial swf size. P I think, Model should be good at performance because it is simple Object not a XMLNode. Let's see, what other people say... -abdul -Original Message- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Scott Barnes Sent: Tuesday, May 17, 2005 12:03 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] XML vs Model? I've got a external source that pulls in XML file (config). Now, I'm having my own internal debate as to which of the two is betterere? I've noticed no real signficant performance gains (via profiler) with using either, the only thing it kind of brings to the table is that you can access a node XYZ levels deep by using property chains (parent.child.infant.siblings). Thats fine, but this will be parsed once-off, and i've found that i've i go the XML route (ie writing my own specific parser, it tends to be less work. (in that i've found that you have nodes in your XML that are using the same name, but can be either 1 or more, you have to test to see if the node in question is an array, otherwise its a literal object and treat it as such - when using model vs childNodes approach via XML (which is always array). What's folks here input on pro's / con's of XML vs Model? -- Regards, Scott Barnes http://www.mossyblog.com http://www.flexcoder.com Yahoo! Groups Links Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
[flexcoders] XML vs Model?
I've got a external source that pulls in XML file (config). Now, I'm having my own internal debate as to which of the two is betterere? I've noticed no real signficant performance gains (via profiler) with using either, the only thing it kind of brings to the table is that you can access a node XYZ levels deep by using property chains (parent.child.infant.siblings). Thats fine, but this will be parsed once-off, and i've found that i've i go the XML route (ie writing my own specific parser, it tends to be less work. (in that i've found that you have nodes in your XML that are using the same name, but can be either 1 or more, you have to test to see if the node in question is an array, otherwise its a literal object and treat it as such - when using model vs childNodes approach via XML (which is always array). What's folks here input on pro's / con's of XML vs Model? -- Regards, Scott Barnes http://www.mossyblog.com http://www.flexcoder.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
