Feature requests?

Asked by foundation on 2009-12-03

Hey All,
First of all I want to say, thank you!!! This has great possibility for replacing my apophysis/flam4 workflow.
I am sure you all have lots of ideas with things you want to accomplish with this program, but I wanted to ask if you are open to ideas on how to improve it? If so, how would you like us to contribute those? I see some things in bugs that are more like feature requests (render in slices).

The couple things I had in mind:

Render auto naming - It would be great if there was a preference to name the rendered files such that they don't overwrite. Perhaps appending date and time to the flame name would be an easy way to implement that.

Random Batch - I enjoy the serendipity of looking through the randomly created flames in apophysis, that would be cool here too.

New transform UI - When creating a flame, it took me a while to find the new transform button. Perhaps the drop down for transforms could include an entry <new transform> which when selected does the same thing as the new transform button.

Anyway, thanks again!


PS I don't have any python experience, but I will start learning as I can. Let me know if there are other ways I can contribute.

Question information

English Edit question
Fractal Fr0st Edit question
No assignee Edit question
Last query:
Last reply:
Vitor Bosshard (algorias) said : #1

Yes, we're absolutely open to receiving feature requests. The best thing is to discuss them before adding an issue to the tracker. You can use the mailing list for that (http://groups.google.com/group/fr0st), or pop up in the IRC channel (#fr0st-users)

Regarding your specific suggestions:

Render auto naming: Sounds reasonable. Please put that in the tracker.

Random Batch: Currently, we're doing that through scripts. There are a whole bunch of batch scripts, and the random_flame script creates truly random flames. It's still a bit rough around the edges, so If you want to contribute, improving that script to produce better flames is a good start.

New transform UI: Adding a <new xform> selection to the list sounds like a good idea at first, but there are a bunch of related functions (adding final xforms, copying and removing xforms, etc), that would be left out of that part of the interface. This is problematic as we value consistency very highly, i.e. related functions need to be kept together in the UI and gratuitous duplication of elements should be avoided.

As for other ways to contribute, goo bug reports are always appreciated ;-)

Can you help with this problem?

Provide an answer of your own, or ask foundation for more information if necessary.

To post a message you must log in.