Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- Chrisir February 2018
- jeremydouglass February 2018
- kfrajer February 2018
- ordsen February 2018
Build trees to define rendering rules in visual editor without watering them
Hey all,
I recently started building a visual editor for Processing available through my GitHub repo. I thought I'd share it with you in case anyone has interest in this project (sadly I won't have much time to continue it and its still mainly "Work in Progress", thats also why I put it into this category)
Alright then, check out the gif showcase in the readme if you want to peek at the user interface and see how it works. To sum up (taken from the readme):
Components that will be rendered / animated follow certain cutomizable rules. Rules are attached to each other through a tree structure. As the user builds that tree structure (visually) he specifies each rule as a tree node. The tree edges describe the control flow starting at the root node. When rendering, each rule is executed sequentially just like the order in the tree implies. Rendering happens once per frame for each root node. The root node specifies the context of the rendered component. This includes available colors, variables and a cursor. Existing rules are "Draw Elipse" and "Update Variable". Those rules accept parameters like "width" for "Draw Ellipse" or "function" for "Update Variable". Basically, you can just type in the variables available through the root node and thus modify them each frame through your own custom function.
That allows you to manipulate shape, color, size and other properties of rendered objects during animation. One use case I started building this project for is e.g. generative art.
Comments
I am not sure how I can run it
Is there an exe file for Win included?
Can I open the project with processing?
Great! I cross-posted this to a long-running question about node-based IDE options for Processing or p5.js:
@Chrisir: I updated the README with some more information and added a jar file for you here. There is a file called Spectrum_v0.0.1.jar; you can download it and launch it by double clicking it. Once the app runs you need to press 'm' to show the menu (I forgot to mention that in my last post)
@jeremydouglass thans for sharing!
thanks a lot!
Which program do I need to run the jar? The jar is not associated with anything on my Win 10.
Javafx.exe or so?
Are you in Windows @Chrisir? I can run it by just dbl clicking on it. The file is Associated with Java(TM) Platform SE Binary. You should also be able to execute this jar file by setting your command prompt in the folder containing this jar and typing java -jar Spectrum_v0.0.01.jar. It works for me.
Kf
I am on Win 10, maybe I haven't java installed properly
Cheers!