Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] F L T K

Date	2024-06-08 16:27
From	Menno Knevel
Subject	Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] F L T K
	are the plugins from https://github.com/csound/plugins the 3rd party plugins? For the p5glove for example, the text is: 'Plugin opcode in p5g. This opcode is part of the plugin repository and has to be installed separately. The plugin repository can be found here: https://github.com/csound/plugins' we (I) could change the text to: 'Plugin opcode in p5g. This opcode is part of a 3rd party plugin repository and has to be installed separately. It may be that this plugin opcode is not maintained or will not install on all platforms. The plugin repository can be found here: https://github.com/csound/plugins'

Date	2024-06-08 16:46
From	Eduardo Moguillansky
Subject	Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] F L T K
	If I may chime in, I would personally recommend that the manual pages for opcodes provided by third-party plugins be removed from the manual. Their presence generates false expectations and gives the impression of csound not being maintained, which is of course not true. Other systems, like pd or supercollider follow this policy: each plugin provides help pages for their externals/ugens and it is left to the front ends to collect those into a usable help system. For plugins installable via risset this is actually the case and csoundqt is aware of those manual pages. Eduardo On Sat, Jun 8, 2024 at 5:27 PM Menno Knevel <magknevel@gmail.com> wrote: are the plugins from https://github.com/csound/plugins the 3rd party plugins? For the p5glove for example, the text is: 'Plugin opcode in p5g. This opcode is part of the plugin repository and has to be installed separately. The plugin repository can be found here: https://github.com/csound/plugins' we (I) could change the text to: 'Plugin opcode in p5g. This opcode is part of a 3rd party plugin repository and has to be installed separately. It may be that this plugin opcode is not maintained or will not install on all platforms. The plugin repository can be found here: https://github.com/csound/plugins'

Date	2024-06-08 16:55
From	Victor Lazzarini <000010b17ddd988e-dmarc-request@LISTSERV.HEANET.IE>
Subject	Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] F L T K
	I agree with that. Prof. Victor Lazzarini Maynooth University Ireland On 8 Jun 2024, at 16:46, Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote: If I may chime in, I would personally recommend that the manual pages for opcodes provided by third-party plugins be removed from the manual. Their presence generates false expectations and gives the impression of csound not being maintained, which is of course not true. Other systems, like pd or supercollider follow this policy: each plugin provides help pages for their externals/ugens and it is left to the front ends to collect those into a usable help system. For plugins installable via risset this is actually the case and csoundqt is aware of those manual pages. Eduardo On Sat, Jun 8, 2024 at 5:27 PM Menno Knevel <magknevel@gmail.com> wrote: are the plugins from https://github.com/csound/plugins the 3rd party plugins? For the p5glove for example, the text is: 'Plugin opcode in p5g. This opcode is part of the plugin repository and has to be installed separately. The plugin repository can be found here: https://github.com/csound/plugins' we (I) could change the text to: 'Plugin opcode in p5g. This opcode is part of a 3rd party plugin repository and has to be installed separately. It may be that this plugin opcode is not maintained or will not install on all platforms. The plugin repository can be found here: https://github.com/csound/plugins'

Date	2024-06-08 17:20
From	Michael Gogins
Subject	Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] F L T K
	I agree but the manual should point users to resources for these plugins. On Sat, Jun 8, 2024, 11:46 Eduardo Moguillansky <eduardo.moguillansky@gmail.com> wrote: If I may chime in, I would personally recommend that the manual pages for opcodes provided by third-party plugins be removed from the manual. Their presence generates false expectations and gives the impression of csound not being maintained, which is of course not true. Other systems, like pd or supercollider follow this policy: each plugin provides help pages for their externals/ugens and it is left to the front ends to collect those into a usable help system. For plugins installable via risset this is actually the case and csoundqt is aware of those manual pages. Eduardo On Sat, Jun 8, 2024 at 5:27 PM Menno Knevel <magknevel@gmail.com> wrote: are the plugins from https://github.com/csound/plugins the 3rd party plugins? For the p5glove for example, the text is: 'Plugin opcode in p5g. This opcode is part of the plugin repository and has to be installed separately. The plugin repository can be found here: https://github.com/csound/plugins' we (I) could change the text to: 'Plugin opcode in p5g. This opcode is part of a 3rd party plugin repository and has to be installed separately. It may be that this plugin opcode is not maintained or will not install on all platforms. The plugin repository can be found here: https://github.com/csound/plugins'