Theres also NodeBox, particularly if youre partial to Python. You can save your scene in a XML based format (like GeeXLab) which is very nice. Seeing the drawing thread take off made me want to get a generative art thread moving. I did a test with a square (rect node) with transparency, translation and rotation: Both texts are additioned (compound1) and the sum is scattered (scatter1) before using the “a” letter for the final rendering (place1).Ī cool node is the copy node: it performs multiple copiues of the input node with a transformation (like orientation or size) for each copy. Each text uses the “a” letter (textpath2) for the rendering. I created a small graph that includes 2 texts (textpath1 and textpath3).
Each node has some parameters you can tweak with the mouse and for graphics hackers, the source code in Python of the node is available and editable. There are different nodes like shape nodes (star, ellipse, etc.), modifier nodes (scatter or wiggle). NodeBox allows to create a scene by connecting nodes in order to make a node graph.
It’s a free and open source tool that makes it possible to create graphics using a procedural approach. Oh well.I tested some days ago NodeBox 2.
Meantime I had to run away from people whose work I really respect saying nice things because my brain was just full. I’ve actually just caught up on my emails from the week now on Sunday evening.įortunately, Friday we had some time for independent work, and I know we will have more later, and I am glad: it is what I really need, I think. There are so many neat people and so much to learn, but 10-5 talks and group work is definitely hard on my introverted brain. The word of the week is definitely exhaustion. Plus, then an SFPC alum (who was also at Hacker School with Wes) expressed an interest in helping make an IRL shelf to power Timeline, which I am beyond psyched about.įinally and most importantly, I brought the beach bot to another audience. I totally have a list of things to pester people about. I was beyond impressed-all the way up to intimidated-by how cool everyone is and how impressive their work. Each student had four minutes to show work we’ve done and talk about what we want to work on. The evening was time to fully introduce ourselves to one another and the community. Speaking of community, I also have volunteered to teach a Github workshop next week, which I am pretty psyched about. I am attracted to the JS libraries since I love JS and both are open source, which means there is a great change for continuing contribution to the community. I’m thinking about two.js, though I may also end up doing more with NodeBox or even p5.js. Some folks may work with NodeBox 3, which is more visual programming–oriented and others are into sound tools, which I have completely elided from this post. In fact, one of our assignments is to choose a tool to investigate and report back on. I’d like to get it going with book data, but there are SO MANY things to be working on. I worked to get it drawing lines from a central radial point, something I had wanted to do on an older project but never got around to figuring out. Then I played around a bit with NodeBox 1, which is written in Python, so has a lot more functionality. You can then create a parameter to weight the randomness, like this: My favorite part is you can give different rules the same name, which causes them to be called randomly. The former is pretty entertaining, mostly good for creating weird generative things, like these: Day 3 began with covered different tools for creating generative art, in particular Context Free Art and Nodebox 1.