Okay.  I threw out what I had and rewrote the thing to make it a bit more flexible.  Hopefully it shouldn't be too hard to extend this new form to include animatable joint centers.

I do have a question for the users, however.  The script will require four file paths: the donor .cr2 from which the weights are derived, the location of the base figure .cr2 to be loaded by the readScript, the save location for the readScript "runner" .cr2, and the save location for the actual joint insertion pose.

That's a bunch of file paths for a script user to have to select.  :scared:  And once the insertion pose is saved, it can't be relocated without breaking the readScript process.

So I thought I'd ask: how do you feel about browsing for four paths as part of the process?  Too confusing, somehow?  The script could try to simplify the process by saving the readScript .cr2 and the insertion pose to the same folder as the target base figure .cr2.  Or something of that sort.  But that could lead to unwanted clutter in that folder, with the files unable to be moved without being broken.

So: what do you, the users, want?  Any thoughts? 

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.