Ideally, this would be the foundation for http://issues.apache.org/jira/browse/PIVOT-81, so I'm in favor of this tool. I think it should go in the tools sub-project, and I think any commits against it should reference PIVOT-81.
As for Eclipse, I would love an Eclipse-based GUI builder and think it'd help sell Pivot to other developers, but that doesn't invalidate the use case for a pure-Pivot app like this. If anyone wants to bite off the EclipseApplicationContext using the AWT/SWT bridge, I'd like that a +2 :) -T On Mon, Apr 13, 2009 at 9:57 AM, Noel Grandin <[email protected]> wrote: > 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.). >> >
