A topic that has come up over on bf-committers is the possibility of supporting multiple co-installed versions of the same addon, without it showing up as a conflict in the addon browser.
Consider the following use-cases: 1. A Blender user makes heavy use of an external renderer. For their professional work, they prefer to stick with an older tried-and-true stable version, but for personal experimentation they want to play with the latest bleeding-edge development version. They wish to install the addons for both versions of the renderer, and enable different versions of the addon depending on whether a project is personal or professional. 2. An animation studio is making their own custom changes to an officially supported addon, but wish to have both the original supported version and their own custom version available while their changes are still unstable and untested. I think a fairly straight-forward way to support this from the user perspective is simply to distinguish addons based on the version number, allowing the listing of multiple co-installed versions of an addon as long as the version number is different. Maybe that's a bit naive, though. I'm not entirely sure what back-end changes are needed to support this. --Nathan
_______________________________________________ Bf-python mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-python
