Texgen.js – Lightweight Procedural Texture Generator
1–10 of 22 posts
Re: Texgen.js – Lightweight Procedural Texture Generator
#2Those are very beautiful. I played around, but could not create anything interesting. Adding the source for each sample, not only the first, could be a great addition. I have absolutely no idea how to achieve the effect of #7 or #8, for example.
And I never understood the copyright status of this stuff. If I use texgen to create a texture, is it mine or mrdoob's?
Re: Texgen.js – Lightweight Procedural Texture Generator
#3Those are very beautiful. I played around, but could not create anything interesting. Adding the source for each sample, not only the first, could be a great addition. I have absolutely no idea how to achieve the effect of #7 or #8, for example. And I never understood the copyright status of this stuff. If I use texgen to create a texture, is it mine or mrdoob's?
If you read the License file you'll see its the standard MIT license. It's very permissive and allows you to use the cide, modify it and many things without asking for special permission. Read up on the MIT license for a better understanding.
Re: Texgen.js – Lightweight Procedural Texture Generator
#4Those are very beautiful. I played around, but could not create anything interesting. Adding the source for each sample, not only the first, could be a great addition. I have absolutely no idea how to achieve the effect of #7 or #8, for example. And I never understood the copyright status of this stuff. If I use texgen to create a texture, is it mine or mrdoob's?
If you read the License file you'll see its the standard MIT license. It's very permissive and allows you to use the cide, modify it and many things without asking for special permission. Read up on the MIT license for a better understanding.
Correct. But my doubts are over the output of the software.
On one hand, the output depends on your artistic instructions, so you are entitled to it. On the other hand, the tool greatly restricts the solution space, so the tool itself (and consequently its author) has artistic merit over the result.
Re: Texgen.js – Lightweight Procedural Texture Generator
#5https://github.com/mrdoob/texgen.js/blob/564c6efb5b5647ad44d...
I'll admit to being a bit concerned about programming practices like this. I'm mostly inept at Javascript, but surely the language has better mechanisms for accomplishing the goal here.
Re: Texgen.js – Lightweight Procedural Texture Generator
#6Around 2002, I made something similar using WinAPI, in Pascal (FPC). Sadly, the sources are gone, but the executable survives:
http://students.mimuw.edu.pl/~dj189395/nhp/czynic/programy/w... [22 KiB, no external dependencies].
Screenshot: http://students.mimuw.edu.pl/~dj189395/nhp/czynic/programy/w...
Use at your peril, preferably in a VM, Wine, or similarly sandboxed environment.
Re: Texgen.js – Lightweight Procedural Texture Generator
#7Earlier quoted context omitted.
If you read the License file you'll see its the standard MIT license. It's very permissive and allows you to use the cide, modify it and many things without asking for special permission. Read up on the MIT license for a better understanding.
Correct. But my doubts are over the output of the software. On one hand, the output depends on your artistic instructions, so you are entitled to it. On the other hand, the tool greatly restricts the solution space, so the tool itself (and consequently its author) has artistic merit over the result.
I think a simple way to explain the MIT license is that you can do whatever you want with it as long as you don't say that you created the library yourself.
Textures that you create are as yours are images you create in Photoshop. Probably even more yours than that ;)
Re: Texgen.js – Lightweight Procedural Texture Generator
#8Those are very beautiful. I played around, but could not create anything interesting. Adding the source for each sample, not only the first, could be a great addition. I have absolutely no idea how to achieve the effect of #7 or #8, for example. And I never understood the copyright status of this stuff. If I use texgen to create a texture, is it mine or mrdoob's?
If you read the License file you'll see its the standard MIT license. It's very permissive and allows you to use the cide, modify it and many things without asking for special permission. Read up on the MIT license for a better understanding.
Actually, it seems like a good question to me. The MIT license (and the other major ones, afaik) specifically applies to the software (and docs), not what artifacts the software might produce. It's not clear to me whether those would be included under the same terms. I would assume they're free to use, but I'm not sure that's (always) true and IANAL.
Something to think about: if I write a program that outputs a work under copyright (without actually containing the copywritten work), can I still use a permissive license?
Re: Texgen.js – Lightweight Procedural Texture Generator
#9https://github.com/mrdoob/texgen.js/blob/564c6efb5b5647ad44d... I'll admit to being a bit concerned about programming practices like this. I'm mostly inept at Javascript, but surely the language has better mechanisms for accomplishing the goal here.
I did it like this because I wanted to create the drawing loop as efficient as possible, without switches or conditionals. That method gets executed per pixel so the less logic the better.
If someone knows a better way I'm all ears!
Re: Texgen.js – Lightweight Procedural Texture Generator
#10https://github.com/mrdoob/texgen.js/blob/564c6efb5b5647ad44d... I'll admit to being a bit concerned about programming practices like this. I'm mostly inept at Javascript, but surely the language has better mechanisms for accomplishing the goal here.
I did it like this because I wanted to create the drawing loop as efficient as possible, without switches or conditionals. That method gets executed per pixel so the less logic the better. If someone knows a better way I'm all ears!
I fail to see the logic behind optimizing around conditionals when you are running in an interpreted language.