https://wiki.blender.jp/index.php?action=history&feed=atom&title=%E5%88%A9%E7%94%A8%E8%80%85%3AKnekke%2Fworkgroups 2026-07-23T17:11:35Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Knekke/workgroups&diff=151563&oldid=prev 2018-06-28T21:17:12Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 21:17時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Knekke/workgroups&diff=151562&oldid=prev 2016-05-26T09:12:47Z

<p>‎<span dir="auto"><span class="autocomment">Solution</span></span></p> <p><b>新規ページ</b></p><div>== Multiple custom Addon/settings locations (e.g. workgroups in Nuke/Softimage/Max) ==<br /> <br /> <br /> <br /> Integrating Blender into a pipeline eventually means you have to be able to roll out plugins/addons to the team and make sure everyone uses the correct versions, settings, etc.<br /> <br /> You might even need different setups for different projects. This is where workgroups come in quite handy. Let’s say you have a Studio-Workgroup that everyone is connected to, that supplies some everyday-use custom addons and presets, and a workgroup that loads some stuff that is only needed for the project you are currently working on. Maybe you also even have your personal workgroup in a dropbox folder with all your personal tools,keymaps,whatnot so that you have them accessible everywhere.<br /> <br /> Many studios have custom launchers for their applications, that connects the right workgroups and creates the right bookmarks inside the application. <br /> Also blender could detect environment variables to determine if it should read a custom directory instead of the default one. That behaviour is quite usual in industry pipelines.<br /> <br /> <br /> To give a real life example: <br /> <br /> Some time ago I wanted to render something on our renderfarm, but I was using an external renderer (mitsuba) that wasn't installed on the farm machines. There are hacky ways how you can get it to work, but none is convenient. <br /> With Softimage for example I would just pass &quot;-w &lt;workgroup-directory&gt;&quot; as a commandline parameter and all machines would load all addons from that directory.<br /> <br /> ==Solution==<br /> Add a place to insert Workgroup locations to the preferences-UI (see mockup below), and add a commandline flag to pass workgrouplocations (e.g. -w &quot;//foo/bar/Workgroup;/home/bla/myworkgroup;/path/to/another/workgroup&quot;). All addons and startupscripts will be activated automatically. <br /> <br /> <br /> [[File:Dev-workgroup-prefs.jpg|600px]]</div>

wiki>Knekke