Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a first cut at autocomplete support. It assumes you're using
supercolliderjs with my recent socket PR.
Here it pulls the list of class names and documentation summaries right after
booting the server, and queries for class methods on-the-fly.
I agree with your comment elsewhere that loading the class info from a file
would be nice so we can still auto-complete if SCLang is crashing or otherwise
unavailable. The balance is basically making sure that the autocompletion is
up-to-date whenever possible, so if the user adds a Quark or custom class it
should show up after their next reboot. In general a reasonable fallback plan
seems like:
package with all the classes that ship with SC.
I'll test out whether getting all the class methods is fast enough to do it
up-front rather then at autocomplete-time.
Still more to do (this is somewhat aspirational, we'll see how far I get):
readable/writable indication
(maybe snippet support?)
variable it would be great to be able to autocomplete instance
members/methods
identifiers in the file.
I'll add a demo gif shortly. :)