Should I put the code somewhere so that you can look at it? Frankly, this builder has hard-coded dependencies on specific WTK classes all over the place. It's just not possible to build a user-friendly editor without doing that.
And the requirements for a round-tripping builder are pretty messy, so I'd be wary about trying to push it into WTKXSerializer. But the builder does make extensive use of various bits of the Pivot infrastructure, and there are definitely a couple of places where I'd rather add some small amount of code to existing classes, than to do a massive copy'n'paste. On Mon, Apr 13, 2009 at 16:50, Greg Brown <[email protected]> wrote: > It sounds like this serializer might have some hard-coded dependencies on > specific WTK classes. If so, might it be better to attempt to generalize it > such that we could actually put the serialization code in > WTKXSerializer#writeObject()? I'm not suggesting that this is definitely the > right approach - but I do think it is worth considering. >
