OSDev.org

Chris Cromer wrote: Does it handle CDATA and such or will I have to work on stripping that stuff out of the struct to get to the real content? If it does then that would be perfect. It would save me from having to write a parser from scratch.

atm it handles nested xml, the <? xml tag at the start, plain text content (not yet mixed, it'll do that in a week, was on planning), doesn't do comments (which is pretty easy to put in, but just didn't have the time to do so), no explicit cdata etc.

It parses most of any random document fine. Since it was intended for computer-generated XML, it doesn't do any error checking or reporting, which would fit your application nice as well.

If anything you can use it as a base.

True I can always change it to work better for my app. The whole reason I needed CDATA parsing was since it's a forum people might post stuff that would conflict with the xml document. So I encase user submitted data in CDATA to make sure it validates and parses properly.

Joel, you know about editing your messages, right?

Yeah, but the stuff I would have edited out still seemed relevant to the thread. I guess I didn't need a separate post to point out that it was in a different thread. Sorry

But I also plan to work on some AGI related stuff, interpreting, and editing. I have written AGI tools in php with a web interface... but this will be something completey new to me, writing an actual program that works on the os level to do stuff with agi. So I need gui for the agi editors. And I beleive command line for a agi interpreter?

Depends on how you do it. Strictly speaking, you don't need GUI for either and GUI can be useful for either. Personally, if I were writing an interpreter I would probably use GUI stuff of some sort.

NAGI is kind of a hybrid because it has a version that pops up both a console window and a GUI window, but in the end it uses some form of GUI library to do what it does, since it creates a window and draws on it.