A random material idea.
A random material idea.
Indigo currently has support for referencing external .igs files, through the include tag. This was added to allow usage of materials without manually inserting the xml into the main .igs file.
I could extend this functionality to allow usage of the http protocol - in this way, people could reference Indigo materials (igm files perhaps) on a website, e.g. the indigo material database site that will be created sometime hopefully
Then when the scene is first run, the material would be downloaded to a cache directory, and would be subsequently served from the cache.
Thoughts?
I could extend this functionality to allow usage of the http protocol - in this way, people could reference Indigo materials (igm files perhaps) on a website, e.g. the indigo material database site that will be created sometime hopefully
Then when the scene is first run, the material would be downloaded to a cache directory, and would be subsequently served from the cache.
Thoughts?
-
- Posts: 289
- Joined: Wed Apr 18, 2007 1:52 am
- Location: Odense, Denmark
No thoughts, that's an excellent idea. The exporters should be able to update their list of materials by the same way, so the user will have all materials available at any time.
I think most users will download the full database and use http to update db only.
The link to arneoog's database is still invisible here... and [edit] users have to use and expand it.
I think most users will download the full database and use http to update db only.
The link to arneoog's database is still invisible here... and [edit] users have to use and expand it.
obsolete asset
Well, I was thinking that each material would be a zip file, containing all needed textures.suvakas wrote:What if there are bitmap textures involved?
Not really a feature i would actually use i think.
Don't like the idea, that my scene relies on my internet connection
The whole zip file would be cached after first use, so a net connection wouldn't be needed subsequently.
Yup.
something like, in the main .igs file:
where .igmz = Indigo material zip
something like, in the main .igs file:
Code: Select all
<scene>
<material>
<name>somemat</name>
<url>http://www.matserver.com/mats/amat.igmz</url>
</material>
</scene>
Yeah, and ideally the login systems should be tied together.neepneep wrote:I like this idea, it makes things even more portable and my HD less cluttered
I'm just wondering what is still needed to finalize/port the Arneoog's mat DB to the current server? Is it just a matter of turning it into a Joomla module?
Who is online
Users browsing this forum: Majestic-12 [Bot] and 53 guests