RE: lingo-l Xml parser xtra question

2003-08-01 Thread roymeo
Check out the technotes at MACR.

I think it has a memory leak, I think it may crash otherwise, and basically 
MACR says well, use the Flash one.

roymeo

At 08:18 AM 7/29/2003 -0400, you wrote:
Thanks, Mathew.

 after hearing some of the issues people had with it and remaining bugs
that are not fixed.
So, what are some of the remaining bugs and issues with Macromedia's xml
parser xtra?
- Michael M.



[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L 
is for learning and helping with programming Lingo.  Thanks!]


[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi  To post messages to the list, email [EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo.  Thanks!]


RE: lingo-l Xml parser xtra question

2003-08-01 Thread Thomas Higgins
 Check out the technotes at MACR.
 
 I think it has a memory leak, I think it may crash otherwise, 
 and basically MACR says well, use the Flash one.

No, not quite. To start, yes, there is a memory leak in the XML parser Xtra that's 
documented in a tech note:

http://www.macromedia.com/go/16805

When I was asked the question how do I avoid the memory leak? I answered by 
indicating that folks should use the Flash XML parsing abilities as you simply can't 
prevent the XML Xtra's memory leak, you can only minimize it. If you ask me can this 
Xtra be used in any way such that the memory leak isn't a problem? then I can answer 
yes. The issue is that each time you call parseString you leak memory, the amount 
lost is proportional to the size of the string being parsed. If your movie parses a 
string once (for initializing as an example) then go ahead and use the XML parser 
Xtra, if instead your project does lots of repeated parsing then we get into a more 
gray area and you have to make some careful decisions. How much parsing? How often? 
How large are the strings you'll parse? etc.

The only time I have recall having said use the Flash XML parsing abilities was in 
replying folks asking how to avoid the memory leak altogether. But you still can 
strategize on how to use the XML parser Xtra while minimizing the memory leak so it's 
not a problem, but that comes on a per-project evaluation of how you'll use it. Have 
you heard from another source that you should always and definitively use the Flash 
XML parsing abilities and completely forego using the XML parsing Xtra?

Now, if I can get some dev time focused on fixing the memory leak we can get over this 
hump... ;)

Cheers,
Tom Higgins
Product Specialist - Director Team
Macromedia

...

[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email [EMAIL 
PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping 
with programming Lingo.  Thanks!]


RE: lingo-l Xml parser xtra question

2003-08-01 Thread Mendelsohn, Michael
Thanks for addressing the issue, Tom.

Pardon my naiveté, but to what extent is the memory leak an issue?  I am developing a 
learning tool that parses XML.  Depending on how far into this DVD-ROM they get, the 
XML could get lengthier and lengthier, but I'd say not more than 10-20k of text.  
Could the memory leak cause a crash?  I'm just not familiar with what the consequences 
could be with memory leaks in using the XML parser xtra.  Could you please specify?  
And, I'd much rather use this xtra than parse the XML in Flash.  

Thanks, and keep up the good work developing Director!
Michael M.






[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email [EMAIL 
PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping 
with programming Lingo.  Thanks!]


RE: lingo-l Xml parser xtra question

2003-07-30 Thread Mendelsohn, Michael
Nice observation, Troy!  Thanks!!  I really do dig that object
inspector.

- Michael M.




 When debugging, is there any way to see the structure of parsed xml 
 under the variable tabs (DMX interface).  Currently, all I see there 
 is the instance of the xtra: Xtra child XmlParser 2 2c1bfe0.  I'd 
 like to be able to see a tree view of the data.  Am I missing 
 something?

When you parse the data, you parse it into an object variable... drag 
that into the object inspector, and viola ... tree-viewed for debugging.









[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email [EMAIL 
PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping 
with programming Lingo.  Thanks!]


RE: lingo-l Xml parser xtra question

2003-07-29 Thread Mendelsohn, Michael
Thanks, Mathew.

 after hearing some of the issues people had with it and remaining bugs
that are not fixed.

So, what are some of the remaining bugs and issues with Macromedia's xml
parser xtra?

- Michael M.



[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email [EMAIL 
PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping 
with programming Lingo.  Thanks!]


RE: lingo-l Xml parser xtra question

2003-07-28 Thread Mathew Ray
Try using Andy White's XML Parser scripts... Organizes everything nice
and neat for ya... Even provides search functions...
http://www.shocknet.org.uk/defpage.asp?pageID=90

If you like the way flash does it (and if you find out it is more
efficient), you can always use global flash objects in director without
having to use the xml xtra. But I like Andy's personally and avoided the
xml xtra after hearing some of the issues people had with it and
remaining bugs that are not fixed.

~Mathew



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mendelsohn,
Michael
Sent: Monday, July 28, 2003 3:07 PM
To: [EMAIL PROTECTED]
Subject: lingo-l Xml parser xtra question


Hi list...

When debugging, is there any way to see the structure of parsed xml
under the variable tabs (DMX interface).  Currently, all I see there is
the instance of the xtra: Xtra child XmlParser 2 2c1bfe0.  I'd like
to be able to see a tree view of the data.  Am I missing something?

chalkboard scratch soundFlash does it, so Director should
too.chalkboard scratch sound

Thanks in advance,
Michael M.



[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email [EMAIL 
PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping 
with programming Lingo.  Thanks!]


Re: lingo-l Xml parser xtra question

2003-07-28 Thread Troy Rollins
On Monday, July 28, 2003, at 03:07  PM, Mendelsohn, Michael wrote:

When debugging, is there any way to see the structure of parsed xml
under the variable tabs (DMX interface).  Currently, all I see there is
the instance of the xtra: Xtra child XmlParser 2 2c1bfe0.  I'd like
to be able to see a tree view of the data.  Am I missing something?
When you parse the data, you parse it into an object variable... drag 
that into the object inspector, and viola ... tree-viewed for debugging.

--
Troy
RPSystems, Ltd.
http://www.rpsystems.net
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi  To post messages to the list, email [EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo.  Thanks!]