HOME | DD

Published: 2010-04-17 06:16:13 +0000 UTC; Views: 926; Favourites: 2; Downloads: 20
Redirect to original
Description
On the left: The scene inside SimplexGui.On the right: Rendered via console-picogen (which not really has a name).
Meaning: Loading/Saving of scene-files is complete. Except for a little oversight: I totally forgot to add volumes (but not the volume renderer) into the GUI.
Expect a release in a week (some minor quality-assurance-todo-points are on my list)
edit: Ough I was too fast. I looked at my todo list, which says I have to:
* Have a standalone production rendering process
* Completize Spectral Raw Data Import (minor thing)
* Volumes into GUI
Still, I think I can hold the release date in a week
Related content
Comments: 5
Miarath [2010-07-27 17:33:40 +0000 UTC]
Hmm, the gui looks pretty good so far. Hope you're doing good on the other parts as well.
👍: 0 ⏩: 1
phresnel In reply to Miarath [2010-07-30 08:15:56 +0000 UTC]
Thank you
There already exist a number of new "widgets" to make it more usable, and someday (I actually hope before upcoming [northern hemisphere] winter, maybe in 2 months) a new GUI with focus on usability (instead of focus on completeness vs. the renderer) will emerge
👍: 0 ⏩: 1
Miarath In reply to phresnel [2010-07-30 20:27:53 +0000 UTC]
You're very welcome.
I agree, gui is as important as function, cause what use is a application
nobody is able to use?
👍: 0 ⏩: 1
phresnel In reply to Miarath [2010-08-02 07:24:08 +0000 UTC]
Absolutely. Or in this case, nobody but programmers, as the heightmap definition really is a tiny program manifested in actual source code
On the other hand, surely, having the heightmap as a program opens up for all possibilities GUI-wise. Photoshop-like layer editing is possible (and in fact I've already started implementing this under my old dA-account [~greenhybrid ], as well as node-based editing like many commercial packages employ.
A third idea is that the source-code can be parameterized, and then building a mini-GUI based on that. E.g., there could be
(* $HEIGHT ([LibnoisePerlin] x y))
and the $HEIGHT-variable in that example could be used to build a small GUI where there is a simple input-box that says "Height: []". I think it wouldn't get easier than that
👍: 0 ⏩: 1
Miarath In reply to phresnel [2010-08-02 19:04:54 +0000 UTC]
I agree, although even then it wouldn't been readable for all programmers... Source code can be really hard to read sometimes. Worst thing is if it's your own.
I rather like the idea of parameterized source-code and I think I've done something
similar in the past when I wanted things more flexible without having to write the
main class anew everytime I'd liked to add a new formula for my fractals.
👍: 0 ⏩: 0