Christian Walther wrote:boblishman wrote:Oh ... one little thing ... to whoever compiles the next release ... when you zip up the files, please do NOT have the /scr path in the zip ... as it simply causes unnecessary confusion (for first time installers) ...
Good point. Putting all the Python files at the top level of the archive would make it a bit hard to find the Readme, documentation etc. though. Perhaps giving that folder a more human-readable name, like "scripts", would help already?
Along these lines, I've also wondered whether giving the thing a proper Python package structure would make the heap of loose files a bit more manageable.
I just tried this and found that it works pretty straightforwardly. The result (prototype based on trunk r380) is available at http://svn.guildofwriters.com/pyprp/contrib/CWalther/package/. From there, you just take the PyPRP folder and put it into your .blender/scripts folder. Neat and tidy. Easier to install for users (hopefully - once they found their scripts folder...), and with the added benefit for developers that you can now directly use a Subversion checkout (or a symlink to one).
Developers (and users too), what do you think about this? Should we transform PyPRP like this for the upcoming release?
One caveat is that I'm relying on the fact that Blender also finds the #!BPY scripts to display in its menus in subfolders of the scripts folder. I have not found any documentation about whether that is a supported feature or just an implementation detail that might disappear in a future version.
While I was at it, I removed some imports, and one entire file, that struck me as unused. The simple things I tested still seem to work, but all the from module import * make it a bit messy, so I might have missed something.