<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Dear Nathan.<br>
<br>
I think that this is a very, very good proposition!<br>
<br>
I have some colleagues, who also work with the <i>Atomic Blender
addons</i> [1] (import/export of PDB and XYZ files). <br>
When there is a very new version from my side and my colleagues
want to use this version, it mostly ends<br>
up in a Team Viewer session: I manually replace the Python files
in the main Blender directory via <br>
overwriting the old version - work done in a shell, which my
colleagues cannot do due to a lack of shell <br>
knowledge. All this is quite time consuming ... .<br>
Note that an existing addon (from trunc and I think also from
contrib) cannot be replaced by manually installing <br>
the same addon via the preferences (we tried a couple of times
without any success).<br>
<br>
So, if Blender allows installing one and the same addon several
times and shows all different versions it would <br>
help a lot: the user can then use the preferences and manually
install a new version of the addon himself. After,<br>
he decides, which version he wants to use (only one version).<br>
<br>
Regards,<br>
<br>
Clemens.<br>
<br>
[1] Atomic Blender:<br>
<a class="moz-txt-link-freetext" href="http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Import-Export/PDB">http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Import-Export/PDB</a><br>
<a class="moz-txt-link-freetext" href="http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Import-Export/XYZ">http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Import-Export/XYZ</a><br>
<br>
<br>
<br>
</div>
<blockquote
cite="mid:CAE91w2v7j+_PQ=pnf6RWaGA0KtxGoYPki-ZLiLOdmzgqvrHkFw@mail.gmail.com"
type="cite">
<div dir="ltr">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.
<div><br>
</div>
<div style="">
Consider the following use-cases:</div>
<div style=""><br>
</div>
<div style="">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.</div>
<div style=""><br>
</div>
<div style="">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.</div>
<div style=""><br>
</div>
<div style="">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.</div>
<div style=""><br>
</div>
<div style="">--Nathan</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bf-python mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bf-python@blender.org">Bf-python@blender.org</a>
<a class="moz-txt-link-freetext" href="http://lists.blender.org/mailman/listinfo/bf-python">http://lists.blender.org/mailman/listinfo/bf-python</a>
</pre>
</blockquote>
<br>
</body>
</html>