Birkemose, that was my plan :) I want to add some kind of toggle button to each row in the particle list so you can turn multiple ones on at the same time. There would probably need to be another option as well to sync all the particles they play in unison or on their own schedule. I think it would be neat to be able to change the position of the emitter as well.
Right now it uses cocos 2d particle plist files as it's input / output format. I originally thought it would be cool to output a .m file that was the particle system class so you could then further tweak it but now I think it is probably better to stick with plists. The big question for me is how to easily communicate particle data back and forth with your computer. I'm going to try using drop box first...
What do you mean by "correct implementation" of lifespan and emit rate? I assume you are referring to how it just divides the number of particles by the lifespan to figure out the emit rate? That is just how cocos2d does it, but I guess nothing is stopping me from creating a new particle system class that just implements a different create from file method which would be more flexible.
