I still think David Akbari's editor is the best
candidate.

Victor

>
> I agree with you Anthony, and it looks to me like we want
> an improved csound5GUI....
> Looking at it just now, I really like it, and I think the
> changes it needs are not very major...
>
>
> Anthony Kozar wrote:
> > I agree with what Andres has to say here.  I think the
> > standard "Basic" GUI should be more than a simple CSD
> > player.  It should have the following basic features in
> my opinion: >
> > * Allow selecting of orc/sco/csd and the directories for
> > environment variables through standard "open file"
> dialogs. >
> >
> there
> > * Render/Pause/Stop buttons in the main window for
> controlling Csound. >
> >
> there
>
> > * Display csound messages in a separate tab or window.
> > Graphs would be nice as well.
> >
> >
> there
> > * A button in the main window for launching a soundfile
> > player application with the output soundfile so that it
> > can be listened to multiple times.  The player app would
> be selectable in a preferences dialog. >
> >
> has an "edit" button, could have a simple "play" button as
> > well. * Allow setting of the most commonly used options
> > using checkboxes/radio buttons/pop-up menus as
> > appropriate.  (Perhaps in a different tabbed pane from
> the "main" settings -- all preconfigured to reasonable
> > defaults for the current platform).
> >
> >
> there, but the defaults are not the best, IMO. I also
> think it could be designed to be easier to use.
> > * Able to choose between real-time and non-real-time
> > performance.  A menu item called "Buffer Sizes..."
> > should bring up a dialog to choose two sets of values
> for -b and -B: one for real-time, one for non.  A "Help"
> > button in this dialog would display text guiding the
> > user on how to configure these settings.
> >
> >
> Not there.
> > * A built-in text editor like cseditor would be great,
> > although the ability to launch an external editor and
> > open the orc/sco/csd files is a good second option.
> >
> >
> there. cseditor is not the default, vim is, which is not
> the most common choice.
> > * A dialog box for each analysis utility with GUI
> > controls for options (and reasonable defaults) would be
> > nice but could be considered something to add later).
> >
> >
> there, and very complete.
> > * Should either (a) remember the last configuration of
> > settings when launched again, (b) allow saving and
> > opening of configuration files, or (c) both of the
> above. >
> >
> not there.
> > That should cover most of the basics.  I have not tried
> > any of the Windows GUIs to see how well they fit this
> > specification.  I think a cross-platform GUI written in
> > Python might be the best way to go.  Using FLTK as the
> toolkit for the GUI seems very problematic.  It would be
> > nice if the GUI provided callbacks to Csound for
> messages, graphs, sensekey, and xyin. >
> >
> true, I agree, though Carlos Pita posted fixes (which I
> think haven't been incorporated) in the thread: Re: [Csnd]
> csound5gui and realtime (patches).
> > I think that the MacOS 9 GUI -- CsoundFront --
> > originally developed by Matt Ingalls and maintained by
> > me provides a very good model for how I think such a
> program should work.  It is not ideal in all respects, and
> > it provides many more "advanced" features than I've
> > listed above, but it provides a fairly comprehensive set
> > of controls for setting Csound options and running the
> most common utilities without having to type in any
> > commandline flags. That is the key I think: it should
> > not be necessary to type in commandline flags to
> accomplish most tasks. >
> > I've posted two screenshots of CsoundFront online.  The
> > first one shows what the program looks like when first
> > opened.  This main window is very simple and many new
> users could get by for awhile without ever having to go
> > beyond it.  Double-clicking the name of the orchestra or
> > score opens that file in the user-selected text editor.
> > I do think this main window should be redesigned to
> better support CSDs and other input file options.
> > Clicking on the (+) button in the corner reveals
> > real-time options and more advanced settings.
> >
> >
>
http://www.anthonykozar.net/csound-macos/CsoundFront-start.jpg
> >
> > The second screenshot shows as many of the CsoundFront
> > windows as I could fit on the screen.  All settings can
> > be saved in "project" files that can be opened later and
> even rendered automatically when opened. >
> >
>
http://www.anthonykozar.net/csound-macos/CsoundFront-full.jpg
> >
> > The menus contain the following commands:
> >
> > Apple:  About CsoundFront, About Csound5Lib (displays
> LGPL blurb) >
> > File:   New Project, Open Project, Close, Save Project,
> >     Save Project As, View Files in Text Editor, Quit.
> >
> > Edit:  Cut, Copy, Paste, Clear, Select All, Preferences
> >
> > Project:  Project Options, Default Directories, Reset
> All Options/Settings >
> > Csound:  Render, Analyze, Batch, Stop, Performance
> >     Settings, Buffer Settings, Override Settings, Score
> >     Extraction Settings, Additional Options (for typing
> >     in missing commandline flags), List Opcodes, List
> Opcode Arguments, List Utilities, Show Version, List
> >     Command Options, Run Command Line...
> >
> > Analysis:  Hetro Analysis, Linear Predictive Analysis,
> >     Phase Vocoder Analysis, Convolution Analysis, ATS
> >     Analysis, Export Hetro File, Import Hetro File,
> >     Export LPC File, Import LPC File, Export PV File,
> Import PV File, Examine PV File (runs PVLOOK) >
> > Score:  Sort Score, Extract from Score, Scot Score
> >     Translation, Score Generation... (using built-in
> >     generator), Other Score Processor... (user
> selectable) >
> > Tools:  Get Soundfile Info, Rescale Soundfile, Mix
> >     Soundfiles, Extract Audio, Extract Envelope,
> >     DeNoiser, Convert Sample Rate, Make CSD, MIDI to
> Csound, Mr. Tweaky, (followed by user-selectable tools
> >     such as Cecilia, Common Music, etc.), Customize This
> Menu... >
> > Help:  (eventually will have commands for opening Csound
> & Mac manuals) >
> > Not all of the miscellaneous utilities in the menus work
> > yet, but I am slowly getting to them ...
> >
> > Sorry for the length.  Mike asked for a specification
> > and/or screenshots and this is not a topic that can be
> adequately discussed in a few sentences :) >
> > Anthony
> >
> I think Istvan's csoundGUI is a good starting point, but
> it could be designed to be easier to use.
> I think the only reason not to reuse (at least parts of)
> csoundGUI is FLTK.
>
> Cheers,
> Andrés
>
>
> ----------------------------------------------------------
> --------------- Take Surveys. Earn Cash. Influence the
> Future of IT Join SourceForge.net's Techsay panel and
> you'll get the chance to share your opinions on IT &
> business topics through brief surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I agree. vim is definitely an advanced editor. I still don't get it yet....

Andrés

Victor Lazzarini wrote:
> I still think David Akbari's editor is the best
> candidate.
>
> Victor
>
>   
>> I agree with you Anthony, and it looks to me like we want
>> an improved csound5GUI....
>> Looking at it just now, I really like it, and I think the
>> changes it needs are not very major...
>>
>>
>> Anthony Kozar wrote:
>>     
>>> I agree with what Andres has to say here.  I think the
>>> standard "Basic" GUI should be more than a simple CSD
>>> player.  It should have the following basic features in
>>>       
>> my opinion: >
>>     
>>> * Allow selecting of orc/sco/csd and the directories for
>>> environment variables through standard "open file"
>>>       
>> dialogs. >
>>     
>> there
>>     
>>> * Render/Pause/Stop buttons in the main window for
>>>       
>> controlling Csound. >
>>     
>> there
>>
>>     
>>> * Display csound messages in a separate tab or window.
>>> Graphs would be nice as well.
>>>
>>>
>>>       
>> there
>>     
>>> * A button in the main window for launching a soundfile
>>> player application with the output soundfile so that it
>>> can be listened to multiple times.  The player app would
>>>       
>> be selectable in a preferences dialog. >
>>     
>> has an "edit" button, could have a simple "play" button as
>>     
>>> well. * Allow setting of the most commonly used options
>>> using checkboxes/radio buttons/pop-up menus as
>>> appropriate.  (Perhaps in a different tabbed pane from
>>>       
>> the "main" settings -- all preconfigured to reasonable
>>     
>>> defaults for the current platform).
>>>
>>>
>>>       
>> there, but the defaults are not the best, IMO. I also
>> think it could be designed to be easier to use.
>>     
>>> * Able to choose between real-time and non-real-time
>>> performance.  A menu item called "Buffer Sizes..."
>>> should bring up a dialog to choose two sets of values
>>>       
>> for -b and -B: one for real-time, one for non.  A "Help"
>>     
>>> button in this dialog would display text guiding the
>>> user on how to configure these settings.
>>>
>>>
>>>       
>> Not there.
>>     
>>> * A built-in text editor like cseditor would be great,
>>> although the ability to launch an external editor and
>>> open the orc/sco/csd files is a good second option.
>>>
>>>
>>>       
>> there. cseditor is not the default, vim is, which is not
>> the most common choice.
>>     
>>> * A dialog box for each analysis utility with GUI
>>> controls for options (and reasonable defaults) would be
>>> nice but could be considered something to add later).
>>>
>>>
>>>       
>> there, and very complete.
>>     
>>> * Should either (a) remember the last configuration of
>>> settings when launched again, (b) allow saving and
>>> opening of configuration files, or (c) both of the
>>>       
>> above. >
>>     
>> not there.
>>     
>>> That should cover most of the basics.  I have not tried
>>> any of the Windows GUIs to see how well they fit this
>>> specification.  I think a cross-platform GUI written in
>>> Python might be the best way to go.  Using FLTK as the
>>>       
>> toolkit for the GUI seems very problematic.  It would be
>>     
>>> nice if the GUI provided callbacks to Csound for
>>>       
>> messages, graphs, sensekey, and xyin. >
>>     
>> true, I agree, though Carlos Pita posted fixes (which I
>> think haven't been incorporated) in the thread: Re: [Csnd]
>> csound5gui and realtime (patches).
>>     
>>> I think that the MacOS 9 GUI -- CsoundFront --
>>> originally developed by Matt Ingalls and maintained by
>>> me provides a very good model for how I think such a
>>>       
>> program should work.  It is not ideal in all respects, and
>>     
>>> it provides many more "advanced" features than I've
>>> listed above, but it provides a fairly comprehensive set
>>> of controls for setting Csound options and running the
>>>       
>> most common utilities without having to type in any
>>     
>>> commandline flags. That is the key I think: it should
>>> not be necessary to type in commandline flags to
>>>       
>> accomplish most tasks. >
>>     
>>> I've posted two screenshots of CsoundFront online.  The
>>> first one shows what the program looks like when first
>>> opened.  This main window is very simple and many new
>>>       
>> users could get by for awhile without ever having to go
>>     
>>> beyond it.  Double-clicking the name of the orchestra or
>>> score opens that file in the user-selected text editor.
>>> I do think this main window should be redesigned to
>>>       
>> better support CSDs and other input file options.
>>     
>>> Clicking on the (+) button in the corner reveals
>>> real-time options and more advanced settings.
>>>
>>>
>>>       
> http://www.anthonykozar.net/csound-macos/CsoundFront-start.jpg
>   
>>> The second screenshot shows as many of the CsoundFront
>>> windows as I could fit on the screen.  All settings can
>>> be saved in "project" files that can be opened later and
>>>       
>> even rendered automatically when opened. >
>>     
> http://www.anthonykozar.net/csound-macos/CsoundFront-full.jpg
>   
>>> The menus contain the following commands:
>>>
>>> Apple:  About CsoundFront, About Csound5Lib (displays
>>>       
>> LGPL blurb) >
>>     
>>> File:   New Project, Open Project, Close, Save Project,
>>>     Save Project As, View Files in Text Editor, Quit.
>>>
>>> Edit:  Cut, Copy, Paste, Clear, Select All, Preferences
>>>
>>> Project:  Project Options, Default Directories, Reset
>>>       
>> All Options/Settings >
>>     
>>> Csound:  Render, Analyze, Batch, Stop, Performance
>>>     Settings, Buffer Settings, Override Settings, Score
>>>     Extraction Settings, Additional Options (for typing
>>>     in missing commandline flags), List Opcodes, List
>>>       
>> Opcode Arguments, List Utilities, Show Version, List
>>     
>>>     Command Options, Run Command Line...
>>>
>>> Analysis:  Hetro Analysis, Linear Predictive Analysis,
>>>     Phase Vocoder Analysis, Convolution Analysis, ATS
>>>     Analysis, Export Hetro File, Import Hetro File,
>>>     Export LPC File, Import LPC File, Export PV File,
>>>       
>> Import PV File, Examine PV File (runs PVLOOK) >
>>     
>>> Score:  Sort Score, Extract from Score, Scot Score
>>>     Translation, Score Generation... (using built-in
>>>     generator), Other Score Processor... (user
>>>       
>> selectable) >
>>     
>>> Tools:  Get Soundfile Info, Rescale Soundfile, Mix
>>>     Soundfiles, Extract Audio, Extract Envelope,
>>>     DeNoiser, Convert Sample Rate, Make CSD, MIDI to
>>>       
>> Csound, Mr. Tweaky, (followed by user-selectable tools
>>     
>>>     such as Cecilia, Common Music, etc.), Customize This
>>>       
>> Menu... >
>>     
>>> Help:  (eventually will have commands for opening Csound
>>>       
>> & Mac manuals) >
>>     
>>> Not all of the miscellaneous utilities in the menus work
>>> yet, but I am slowly getting to them ...
>>>
>>> Sorry for the length.  Mike asked for a specification
>>> and/or screenshots and this is not a topic that can be
>>>       
>> adequately discussed in a few sentences :) >
>>     
>>> Anthony
>>>
>>>       
>> I think Istvan's csoundGUI is a good starting point, but
>> it could be designed to be easier to use.
>> I think the only reason not to reuse (at least parts of)
>> csoundGUI is FLTK.
>>
>> Cheers,
>> Andrés
>>
>>
>> ----------------------------------------------------------
>> --------------- Take Surveys. Earn Cash. Influence the
>> Future of IT Join SourceForge.net's Techsay panel and
>> you'll get the chance to share your opinions on IT &
>> business topics through brief surveys - and earn cash
>>
>>     
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>   
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>     
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>   


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net