"ingo" <nomail@nomail> wrote:

> Not sure what you mean here, you can chop up any scene file in multiple include
> files and use a "render file" that unites them.

I can.  But I have a very military mindset when it comes to separability.
One is none.

If you CAN lose it, you WILL.

If a part can be "captive" rather than fully removable, do so.

I want a tar, zip, something file that is easily navigated for clean editing
without the clutter of constants and macros and functions, but is still all
right there in the SAME file.

I have many threads where I expand on all of this, but if I could svae an entire
directory structure with all of those includes, that would work for me too.

You yourself commented on the utility of an SQlite structure, which I applauded.

I have downloaded many scenes where I was missing the necessary variables or
include files.  Wrap them all up and keep them all together as a (still
immediately useable) package.  Even better if I can package that code into the
render image itself as metadata or a zip or pdf inside of a jpg/png.

You store ONE file - and either you have it or you don't.  You don't have to
worry about if you have missing pieces that you have to track down, or may be
gone forever.

- BW

Post a reply to this message