Forum Moderators: Staff
Poser Python Scripting F.A.Q (Last Updated: 2024 Dec 02 3:16 pm)
I found this to be a good read.
97 Things Every Programmer Should Know
Kevlin Henney - O'Reilly Media
1st ed Feb 2010
ISBN: 978-0-596-80948-5
"Few are agreeable in conversation, because each thinks more of what he intends to say than that of what others are saying, and listens no more when he himself has a chance to speak." - Francois de la Rochefoucauld
Intel Core i7 920, 24GB RAM, GeForce GTX 1050 4GB video, 6TB HDD
space
Poser 12: Inches (Poser(PC) user since 1 and the floppies/manual to prove it!)
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
It looks like all compiled Python scripts will need to be recompiled to be compatible with Poser 9. As long as you are doing that, may I please ask you to revisit all of your scripts - compiled or not - and do a little housekeeping:
a. Please remove any scripts that have been made obsolete by native Poser functions. Maybe the script was really cool back in the days of P4, but now it's just clutter or some curious artifact. Anyone still working with P4 has probably collected all the scripts they will ever need. There's a reason why software publishers quit supporting older versions at some point.
b. Please remove any scripts that you yourself have made obsolete. In the scripts that come with P8 there are at least three that I know of that have a GUI based version and a "hard coded" version. I would guess that the whole point of making a GUI version was to make it unnecessary to make the user edit the script and type in their own parameters, so why keep the old version around?
c. A little documentation, please. Again I'm looking only at the scripts that come with P8. In many cases the only indication of what the script does comes from the name of the script, and that can be anywhere from vague to useless. Often you have to read through the code to see what it does, but not everyone can read Python. I'm not asking for a lot, just a line or two at the top of your code or a ReadMe file will usually do just fine.
d. Please don't name your ReadMe file ReadMe.txt. Append the name of the associated script to it like this - MyScript_ReadMe.txt - or however you want to do it.
e. A few notes about documentation. Please don't just say what your script does, say what its purpose is. Tell the users why they might want to use the script or what problem it will solve or what "pain" it addresses.
I, for one, would really appreciate these updates, and I suspect that entire Poser community would, also. Just a little bit of time put in by each developer will save a lot of time and frustration on the part of the users.
Thanking you in advance.
OS: Windows 10 64-bit, Poser: 10