Texgen.js – Lightweight Procedural Texture Generator

by mef • 11 years ago

98 21 11 years ago

BoppreH3• 11 years ago

Those 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?

endergen• 11 years ago

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.

BoppreH3• 11 years ago

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.

caipre• 11 years ago

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?

chengsun• 11 years ago

The source for each sample is all in index.html: https://github.com/mrdoob/texgen.js/blob/master/index.html

akerl_• 11 years ago

https://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.

mrdoob25• 11 years ago

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!

bgtnhz• 11 years ago

I fail to see the logic behind optimizing around conditionals when you are running in an interpreted language.

nathell• 11 years ago

Around 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.

javajosh• 11 years ago

Wow, what a strange and wonderful little program. I think it's neat how @mrdoob put together a little standard library of functions that can be chained together in a totally understandable abstraction "pass". It's a good project, too, for people who, like me, want to have a good template for doing general pixel-wise manipulation with canvas.

Thanks!

M4v3R• 11 years ago

It's worth mentioning that Mr.doob (author of this code) is also an author of three.js graphics library and many astonishing demos. Check out his Github and home page (http://mrdoob.com) for (many) more interesting things!

Example: http://mrdoob.github.io/three.js/examples/webgl_terrain_dyna...

mrdoob25• 11 years ago

Hehe! Thanks for that. But, to be fair, that last example was done by http://alteredqualia.com/.

Texgen.js – Lightweight Procedural Texture Generator

Related Stories