[sc-users] Re: top five sclang pet peeves

[jamshark70@xxxxxx]

brianlheim wrote
> James wrote:
> 
>> - IDE autocompletion includes only classes and methods. "thisProcess" and
>> "currentEnvironment"... nope, you're on your own.
> 
> Ideally, what would be covered under autocompletion, and under
> "intelligent" autocompletion? Just keywords, or also variables within
> current scope?

I would love it if local variables were included as well. Maybe even
environment variables (although that wouldn't help me with Proto-style code,
because a Proto wraps its own environment, but the auto-completer would have
access only to the current environment).

I don't know how much information the IDE tokenizer has. If it's a flat list
of tokens, it may be difficult/impossible to isolate the current scope and
enclosing scopes. If it has a nested structure for { functions }, then it
would be relatively easy, I would think.

But at this point, I'm so used to typing up variable names, I wouldn't
consider that essential. It's mainly the fixed keywords, especially the long
ones like currentEnvironment that I have to type quite often for Proto,
where there's no good reason to exclude them.


>> - The ability to extend the tokenizer / colorizing
> 
> This seems like a fairly massive undertaking; would other people benefit
> from this as well? Just trying to get a sense for how badly this is
> needed.

It probably isn't badly needed.

For my live coding framework, it would be nice to have a text window where
colorizing and auto completion are disabled, but you can still submit code
to the interpreter. Currently, you can submit code interactively *only* from
a "code window," and the code window enforces colors, auto completion,
indentation. So it's all or nothing -- you're either working on canonical SC
code, or it's arbitrary text that the IDE will refuse to execute.

That's inconsistent with the existence of the preprocessor.


>> - Lack of IDE extensibility
> 
> Is this just the highlighter point or is there more you'd like to see? I
> know we have several issues open on GH about little features to add or to
> give the option to configure.

I had written a wish list. Coloring and keyword completion, we already
discussed. The other suggestions were:

- Proper snippets, with multiple parameters. (Easy, I guess.)

- Git integration. (Harder -- but, when I was using scel, I got really
spoiled being able to commit something directly from Emacs with C-x v v.)

hjh



--
Sent from: http://new-supercollider-mailing-lists-forums-use-these.2681727.n2.nabble.com/SuperCollider-Users-New-Use-this-f2676391.html

_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/