Kaz, we've been hobbling along with a set of somewhat unstable PCS2 builds for some time. We've asked several times for a move to a more modern VCS, of which you hadn't seem opposed to but have yet to do. The code for Collada support has been published several times in whole on the forums in the new PCS 2.1 format, and now you've only recently asked Spicious to commit it himself instead of doing this at some point in the last six months or more. I'm not mad or anything, but there are many modders who have grown tired of waiting for this tool to get to a usable state, and The_E has picked up work on ModelView, as apparently the interface is more desirable than that found in PCS2 to many modders. Since there is a lot of good code in PCS2's core, The_E has decided to utilize some of that to replace the ModelView core, starting with texture processing. I suggested that perhaps the core could be modified in such a way that both ModelView and PCS2 could be built against it, since I don't see ModelView ever being a cross platform interface, and any enhancements made to the PCS2 core through that project could then immediately be available to PCS2 as well. Keeping it in one repository would allow for a checkout that could build either ModelView or PCS2, from a common backend model handling library. The Windows modders would have ModelView, or PCS2, and PCS2 could still be developed into a cross platform tool, all while maintaining a common core. But with this much new interest in the project, we need to get it out of CVS right meow and into something newer.
Now don't get me wrong, I'm not chewing you, I'm just pointing out that there's been a lot of frustration as of late and these are observations that have been made by most of the community. I'm personally against any forking but we need a little help and cooperation from you to avoid that I think.
