Layering, perhaps by 'tagging' triangles, (maybe in the 'transform' tag of the edit window?) perhaps by linking saved flames, perhaps some other method.
The ability to grow/shrink one axis of a triangle, rather than both. Think zooming one axis 110%-200% instead of both at the same time. This could be done with an additional row of arrows (+vert, -vert, percentage, +horiz, -horiz) in the 'triangle' tab of the editor window, perhaps.
Improved iterative fractal rendering. Instead of using the current script, which can only handle one static set of dimensions, allow for different size fractals to render automatically one at a time. Also better memory controls on that (as per the current render window),
Integrating 3D into the whole would IMO be a VERY good idea.
Bugfixes are always welcome.
Remove the 'you must upgrade - new version available' bit. If you want to do a popup saying there's a new version available, great. But forcing upgrades is IMO a bit much.
And, most importantly - whatever you folks want to do. I appreciate the heck out of what you've already done. Thank you for this wonderful tool.
more control in editing the fractal in the editor, when it previews every triangle some of them are very small...and hard to manipulate without using just math and zooming in and out and whatnot
I think it might be useful, if implausible, to have the ability to save an image mid-render, so you can see the quality of the image in progress. This way you could gauge the image as it rendered, perhaps arriving at an acceptable quality long before the projected render time is up. A lot of rendering time could be saved that way, I think.
I would love to be able to add gradients into the existing dropdown menu or switch gradients from the folder with the existing defaults in the dropdown menu.
A higher capacity for plugins would be nice and a build in solution that allows one to see which plugin is missing when an old flame looks "wrong".
One more thing I forgot...ability to assign a new script editor or incorporating color-coded key words and search/replace in the existing one.
And I like Michael's idea of a re-write or re-design. Maybe ~Apophysis-J could spur some of that. It is in active development and has a new release a couple of time a week. Right now, it is trying to maintain the same look and feel as the original, but why replicate things that people want replaced or improved?
Here's my list: 1. Ability to launch a flame or flame pack from the command line so that you could "open with" Apo from the Windows Explorer and associate these file types with Apo 2. Ability to drag a script or flame onto the Apo app like what Apo-J allows 3. Default of adding flame parameters to rendered image comments like Apo-J, and ability to open those images in Apo 4. Ability to have more detail in the render progress window (elapsed time and time remaining) or ability to display the Render>Output window from a script 5. Change the flame name on external renders to the actual flame name, not render.flame for every single one. 6. Error messages for missing variations if a script that is opened calls for one 7. A master script and plugin repository that Apo could reference and download as needed 8. Ability to simulate more RAM with a swap file for extra large renders 9. Ability to save partial renders and re-start them 10. Incorporation of 3D ability in standard version 11. Incorporation of layers or ability to produce one "flame" as a background and one as a foreground. Alternatively, ability to set background transparency and foreground/background attributes for each transform and have it all as one large flame. 12. Incorporation of CalculateColors as an internal function so that missing Functions.asc files no longer continue to be a support nightmare 13. An up-to-date major release incorporating donated gradients, flame packs, scripts, tutorials, and other resources that the community can vote on including. 14. Ability to grab and move specific gradient colors in the selected gradient in order to re-arrange them or re-size their "width" 15. A "converter" kind of like what Apo-J does when it converts the regular Apo scripts into JS scripts - except that it would convert the flame parameters into a script and ask you which variations/variables you would like to randomize. It might put me out of work because that is how I get a lot of my scripts, but it would be very handy as a starting point to play with.
Sta.sh
Devious Comments
Layering, perhaps by 'tagging' triangles, (maybe in the 'transform' tag of the edit window?) perhaps by linking saved flames, perhaps some other method.
The ability to grow/shrink one axis of a triangle, rather than both. Think zooming one axis 110%-200% instead of both at the same time. This could be done with an additional row of arrows (+vert, -vert, percentage, +horiz, -horiz) in the 'triangle' tab of the editor window, perhaps.
Improved iterative fractal rendering. Instead of using the current script, which can only handle one static set of dimensions, allow for different size fractals to render automatically one at a time. Also better memory controls on that (as per the current render window),
Integrating 3D into the whole would IMO be a VERY good idea.
Bugfixes are always welcome.
Remove the 'you must upgrade - new version available' bit. If you want to do a popup saying there's a new version available, great. But forcing upgrades is IMO a bit much.
And, most importantly - whatever you folks want to do. I appreciate the heck out of what you've already done. Thank you for this wonderful tool.
Sincerely,
John
A higher capacity for plugins would be nice and a build in solution that allows one to see which plugin is missing when an old flame looks "wrong".
Bunny
And I like Michael's idea of a re-write or re-design. Maybe ~Apophysis-J could spur some of that. It is in active development and has a new release a couple of time a week. Right now, it is trying to maintain the same look and feel as the original, but why replicate things that people want replaced or improved?
1. Ability to launch a flame or flame pack from the command line so that you could "open with" Apo from the Windows Explorer and associate these file types with Apo
2. Ability to drag a script or flame onto the Apo app like what Apo-J allows
3. Default of adding flame parameters to rendered image comments like Apo-J, and ability to open those images in Apo
4. Ability to have more detail in the render progress window (elapsed time and time remaining) or ability to display the Render>Output window from a script
5. Change the flame name on external renders to the actual flame name, not render.flame for every single one.
6. Error messages for missing variations if a script that is opened calls for one
7. A master script and plugin repository that Apo could reference and download as needed
8. Ability to simulate more RAM with a swap file for extra large renders
9. Ability to save partial renders and re-start them
10. Incorporation of 3D ability in standard version
11. Incorporation of layers or ability to produce one "flame" as a background and one as a foreground. Alternatively, ability to set background transparency and foreground/background attributes for each transform and have it all as one large flame.
12. Incorporation of CalculateColors as an internal function so that missing Functions.asc files no longer continue to be a support nightmare
13. An up-to-date major release incorporating donated gradients, flame packs, scripts, tutorials, and other resources that the community can vote on including.
14. Ability to grab and move specific gradient colors in the selected gradient in order to re-arrange them or re-size their "width"
15. A "converter" kind of like what Apo-J does when it converts the regular Apo scripts into JS scripts - except that it would convert the flame parameters into a script and ask you which variations/variables you would like to randomize. It might put me out of work because that is how I get a lot of my scripts, but it would be very handy as a starting point to play with.