Andi Gutmans wrote: > You might want to put this into Pear. In any case, if you want to post the > API just to get people's input (naming conventions of functions and so on) > feel free to post here. > Thanks for the suggestion to put this into Pear. I have subscribed to the dev list and I'll see what they think :)
Regarding the API, I am planning 3 sets of functions. 1) Ecasound functions that simply wrap the Ecasound Control Interface. I have named these: eci_init(); eci_command(); eci_error(); etc, I really want to use this naming convention as it is exactly the same as the interface available in perl, python etc. 2) Higher level functions for manipulating sound files. These are what I would expect to be of most interest to others. As I mentioned before scripting ecasound is tricky so simple functions to play or convert files would be useful. I am planning to name these with the audio_ prefix, ie audio_playfile(); audio_convert_file(); audio_new_chain(); Is this a good idea, I thought of the audio_ prefix to clear up any confusion with other functions, but it will mean some function names will be a little long for example, audio_chain_set_position(); is this too long? 3) will be midi functions,this is a long way off yet so I haven't given it too much thought yet. Also it is likely to be a separate module as it will need to link against a separate library and I can't think of any PHP modules that link against 2 libs. One last question. I'm sure I read somewhere that the PHP licence is not compatible with the GPL. Is this true? If so what do I need to do is a simple agreement from the ecasound maintainer enough or will he need to release it under the PHP licence as well? Regards Tony Leake -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
