Quote -
I have a suggestion.  It seems that lesbentley is working on the same issue.  Do you think that the Google Code project can facilitate the sharing of the "code" development?  I feel that we are in a kind of "open source" project.

I had thought about that. But since Poser files aren't modular, there's no point. A CR2 that someone else creates is useless for me because I have no practical way of distinguishing random changes Poser introduces from the meaningful ones. Pose files are much better, if they can be made. Failing that, they'll simply have to tell me.

What we would need for communal projects like this is some kind of specification language which would allow us to write modules for certain aspects of a figure which would then be interpreted and assembled to form a single CR2 file. We'd also need some powerful ways to extract just the information we're interested in from a CR2 that Poser (or D|S) wrote. I'm using some tools in my workflow that represent a tiny, tiny step in that direction.

-- I'm not mad at you, just Westphalian.