FS: Structured syntax Editor for Turbo algorithms

[DarkStar]

I would find it very helpful to be able to edit the algorithms in MTurboReverb and MTurboFIlter (and ....?) in a structured Editor. Editing a one-liner or free-format multi-liner is awkward,

Which would you prefer to edit?

widening(-1);4a;cc[b[v(0.15)];[fh;fl];8[2a];8b[2an[fh(2;0.5);b(0.9)[d(17)]]]];f(700;bandpass;0.2);fh;fl

Or

....widening(-1);
....4a;
....cc[
........b[
............v(0.15)
........];
........[
............fh;fl
........];
........8[
............2a
........];
........8b[
............2an[
................fh(2;0.5);
................b(0.9)[
....................d(17)
................]
............] -- end of 2an"
........] -- end of "8b"
....];
....f(700;bandpass;0.2);
....fh;
....fl

Features:
-- sub-module automatic indenting,
-- colour coding for module names, repeats and parameters,
-- colours tbd, maybe different for dark and pale backgrounds,
-- ability to add notes, prefixed by --

[dmbaer]

Assuming that the font is tiny, as is the case with the help text editors, I would not use a Melda editor at all except for very brief changes. I would copy/past to UltraEdit and copy/paste back into TurboWhatever when done.

[MeldaProduction]

Well, it is available for MTurboFilter, for MTurboReverb there's no space...

[DarkStar]

Getting there,

MTF has a multiline editor-
But [Tab] only works in the pop-up Editor
And it does not have a virtual keyboard.

MTR has a single-line editor; its pop-up is also sing-line, with a reduced virtual keyboard.

And neither has the features that I was requesting:
-- sub-module automatic indenting,
-- colour coding for module names, repeats and parameters,
-- colours tbd, maybe different for dark and pale backgrounds,
-- ability to add notes, prefixed by --

Given that the syntax is slightly abstruse anything that helps editing and debugging would be a boon. I think it is currently very easy to make an editing mistake and not get the effect you were designing.

[MeldaProduction]

Sorry, but color coding and autointendation and stuff are just faaaaaar beyond the available development time. We are not talking about real programming here after all.

[DarkStar]

Yep, I understand the priorities.

But, to me, editing a one-liner with nested [] and no syntax-checking is awkward and error-prone. A structured editor would encourage more algorithms and presets (Devices) from users..

[mibby]

Just to qualify my vote - I'm nowhere near the point of being ABLE to edit the algorithms. But when I am, I don't see it being a big deal to step outside and use my favorite editor, Notepad++ or whatever, then copy it into the plugin...

[Gamma-UT]

I haven't done a lot of work in MTR as yet but I'd just use an external text editor like the others have suggested. I wouldn't break every bit of nesting on to a new line but keep the simpler chunks together. The example above is way too spread out to convey a lot of useful information but I'd expect people to differ on that one. It's going to be easier to control that in <insert favourite editor> than to expect that this sort of customisation should go into the plugin.