As Oxidzer 0.5 slowly crawls towards release its time to plan 0.6 so I though I’d let you guys to throw your hats in to the ring.
Here’s the ideas that I have in the pot, either my own, or ideas that people have suggested.
Take these as given…
- Update flam3 to the latest version .
- Update LuaObjCBridge if I see any advantage in doing so.
So the proper idea’s are in no particular order…
- Save / Load of sparse gradients.
- Double Click and Drag and Drop loading of flam3 files.
- A browser for the auto backups.
- Auto-previews for changes to all parameters like the Transformation editor
- Keyboard shortcut shift-cmd-L (or similar) for Lua Script.
- A genome pin board to keep genomes around on possibly persistent between sessions.
- An additional “#” column in the main list that gives the index of a flame
- Ditto in the transform editor, a column with numbers to identify the flames
- A “clear” button in the Breeder in addition to the load/+/- buttons, or multi-select genome ability.
- Check auto-post
- A script library/launcher integrated with the Main Oxidizer window.
- A Lua script console, to see the output of scripts.
- A reorganization of the XForms window to put the affine and post coefficients under the same tab.
- Persist the current set of flames across Oxidizer sessions.
- Allow the preview image size to be altered, hovering over the image well shows the bigger preview.
And the real blue sky one…
- Multi-preview - choose a parameter, set max and min and render a number of previews with that parameter set between max and min
So, over to you, which of these do you think would be is there anything else you can think of.
Dave
p.s. I’ll know if you’re hyping your own ideas :-)
Posted in Developer's Corner, Oxidizer Community
Recent Comments