|
From: Bernard B. <ber...@gm...> - 2020-07-08 04:46:36
|
It would be great to have a sort of "--outfile" option saving the production to some/.../path/the_file… My first plan is to develop a minimum PHP environment loading a grammar and its associated text files to HTML forms with "save", "compile" and "run" buttons. Basically the commands we see on the old GUI. Then refine a little bit using a better editor, or do the same in a Wordpress environment… Ideas are coming! ;-) I am also planning to investigate a MIDI real-time output such as: https://www.smashingmagazine.com/2018/03/web-midi-api/ Not sure it is the one we need but it might teach us useful things… Bernard Anthony Kozar wrote on 07/07/2020 23:43: > > I haven't implemented the functionality for sending output directly to a > file yet. But, you're right, it shouldn't be too hard. It might be as > simple as taking the next argument after --csoundout or --midiout, > opening the file, and setting the appropriate entry in gOutDestinations[]. > > My intention was not to leave stdout & stderr as the default > destinations for so many things. I probably just hooked them up that > way to get BP console working quickly back in 2013 and haven't gotten > back to finishing what I had in mind. (What I had in mind 7 years ago > might not be so clear now...) I do remember that I was not just > thinking about the console version but looking ahead to developing the > "Bol Processor API" that will be used by GUI clients in the future. > Having many different destinations for output messages will allow > clients to handle each category of messages uniquely. > > Maybe I can work on the output issues this weekend. Until then you can > make whatever changes to your copy that you find helpful. :) (If you > check the code out of the Sourceforge Git repository you can save your > changes on a local branch and switch back and forth between my version > and yours). > > Anthony |
