Includes aren't handled yet, but I don't expect them to be a problem - a marker node in the tree should suffice.
Non-primitive properties seems to be working fine. Not sure why this should be a problem? Nested collections I haven't seen in any wtkx files yet, so that won't work. Basically, I've focused on handling what appears to be the most common constructs, and I haven't run across any road-blocks yet. On Mon, Apr 13, 2009 at 15:38, Greg Brown <[email protected]> wrote: > It definitely sounds interesting. We were wondering how you handled some of > the issues around writing WTKX (includes, non-primitive properties, nested > collections such as list data that you may or may not want to write out, > etc.). >
