Hello,
in the end we agreed to call this non-default scripts addons for now, so
Cambpell made changes in bf-blender to reflect this, while I've made the same
folders structure as of .blender/scripts in
https://svn.blender.org/svnroot/bf-extensions/
trunk/ (same for contrib/)
|-- plugins
|
Hi Campbell,
yesterday we discussed about the naming of non-default scripts, that as of now
you called extensions.
Referring to my previous mail,
http://lists.blender.org/pipermail/bf-committers/2010-February/026144.html ,
and after a discussion today with Brandon (meta-androcto), we prepared
Hi Charles, your mail mostly covers installation issues which are
important but not directly related to extensions.
Since we want users to be able to add scripts weather we have some
concept of an extension or not.
reply inline...
- You mention
On Sun, Feb 14, 2010 at 6:27 PM, Charles Wardlaw
Hi Campbell,
Hi Charles, your mail mostly covers installation issues which are
important but not directly related to extensions.
Since we want users to be able to add scripts weather we have some
concept of an extension or not.
Implementation-wise they might not be, but from a user-centric
On Sun, Feb 14, 2010 at 9:03 PM, Charles Wardlaw
cward...@marchentertainment.com wrote:
Hi Campbell,
Hi Charles, your mail mostly covers installation issues which are
important but not directly related to extensions.
Since we want users to be able to add scripts weather we have some
concept
Perhaps I'm too late in the discussion, but have existing Python distribution
tools been considered?
I was cruising through the plone site today, and noticed this tool :
http://peak.telecommunity.com/DevCenter/setuptools
Of course, I guess its probably as much work to integrate this with
From 2.4x there are lots of scripts that are really useful but fairly
specialized.
Examples...
- Mesh Unfolder (could do 3d - origami type unfolding)
- Tree Maker (Curve 2 Tree, useful but quite a specialized workflow)
- LipSync, never got this to work but I imaging it could be very
useful in some
Hi,
in the past i also thought it would be a good aproach to break blender
down in several packages, for e.g. core package and 2-3 script
packages. Shipping as much scripts as possible with the blender
package itself, putting scripts in categories, which then can be
enabled or disabled would be
Sure people will make their own 2.5 script packs, and we should make
this easy to install etc. however IMHO these are not mutually
exclusive.
For eg, You might get a script pack, yet not have it clutter your
menu's, and only enable say 4 useful scripts from the pack.
On Sat, Feb 13, 2010 at 6:35
On Sat, Feb 13, 2010 at 7:47 AM, Campbell Barton ideasma...@gmail.com wrote:
One of the reasons I thaught of this is Colin was asking if the durian
scripts we have would make it into blender.
We added some scripts in a shared script dir, its interesting that
mostly only 1-2 of the of the team
. WIth such organisation of the ui, this would be potentially
distributable with blender.(did you notice how many 2d movies are done with
blender?)
cheers,
Vilem
Původní zpráva
Od: Tom M letter...@gmail.com
Předmět: Re: [Bf-committers] Script Xtras (proposal)
Datum
11 matches
Mail list logo
