I remember talking with you years ago
when I contributed some code to PCGen. I think that was back in the... oh, about 2.4 days?
The best shot for support would likely be to come up with a basic output sheet that includes everything that PCGen is tracking. CharTool would then import everything
. And when CharTool goes to write the data to MapTool, it would only write certain fields as needed by a particular framework.
That way only a single export sheet is needed for PCGen and it's not tied directly to a FW, since some of the FWs are quite vibrant and tend to change swiftly -- trying to keep up would be a mess. Instead, the FW could supply the proper exchange file so that the CharTool output could be imported into MapTool. This allows the FW developer(s) to keep the token conversion file in sync at the same time.
Most of the FWs are not changing properties much at this point. There are a few new ones that are still developing, but the 3.5/PF and 4E frameworks are pretty stable. So I don't see the FW developer(s) really needing to do much with it. And if they do need to make changes, they can push a lot of that work to the folks who are currently using the FW in their games.
How does that sound?