[Bf-committers] Materials Library for Blender

[Silvermindyarr]

Thats a good idea. Previous work was done by elubie:
http://wiki.blender.org/index.php/User:Elubie/AssetBrowser




On Sun, Jun 16, 2013 at 11:42 AM, Jürgen Herrmann <shadowrom at me.com> wrote:

> Hmm... Drag and drop is a good idea too ;)
> Maybe it is time to write down proposals somewhere and discuss these later
> to get a defined proposal package, then we can start to plan for
> implementation.
> Otherwise this will get really messy with all these proposals an
> discussion mixup ...
> I think we are all aware of the fact that, unfortunately, it will be
> impossible to meet the wishes of all users.
>
>
>
> Am 16.06.2013 um 20:18 schrieb Silvermindyarr <silvermindyarr at gmail.com>:
>
> > This asset browser definitely needs it's own panel with drag N drop as an
> > option. There have been a number of mockups in the past, especially on
> > blenderstorm.
> >
> >
> > On Sun, Jun 16, 2013 at 9:09 AM, Jürgen Herrmann <shadowrom at me.com>
> wrote:
> >
> >> The question is what does it take to implement an interface for saving
> >> material presets in a stripped blend file format?
> >> There should be a save and load function in the material panel and a
> >> decent, easy to use library for these.
> >> I personally like how this is done in Vue by e-on. (Vue 11 pioneer is
> free
> >> : http://www.cornucopia3d.com/products/vue/vue_11_pioneer/ )
> >>
> >> But we could do even better by adding meta data into the "material
> files"
> >> and maintain a simple library db within the presets folder of the users
> >> machine.
> >>
> >>
> >> Am 16.06.2013 um 17:38 schrieb Brecht Van Lommel <
> >> brechtvanlommel at pandora.be>:
> >>
> >>> In another discussion about using .blend files for this type of thing,
> >>> the big size of .blend files came up, which can be easily 400 kb even
> >>> with a single cube in it. This is because it also saves the user
> >>> interface and some other things which aren't needed here. For a
> >>> library.blend with many datablocks in it the overhead doesn't matter
> >>> as much, but if there are many files or some online material library
> >>> it could be useful.
> >>>
> >>> I did a little experiment to see how small you could get a .blend file
> >>> with a single datablock in it.  By stripping all datablocks except
> >>> some specified types, stripping unused DNA data, and using gzip
> >>> compression, we can store a simple node material in 4.4 kb. Note 4 kb
> >>> is the minimum file size on many file systems.
> >>>
> >>> Script strip_blend.py:
> >>> http://www.pasteall.org/43203/python
> >>>
> >>> Example terminal output:
> >>> http://www.pasteall.org/43212
> >>> http://www.pasteall.org/43211
> >>>
> >>>
> >>> Brecht.
> >>> _______________________________________________
> >>> Bf-committers mailing list
> >>> Bf-committers at blender.org
> >>> http://lists.blender.org/mailman/listinfo/bf-committers
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> http://lists.blender.org/mailman/listinfo/bf-committers
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>