Hi again Chris
Another interesting suggestion. But here I'm a bit more conflicted.
I personally dislike code completion. I'm a good typist and find it very distracting to have stuff keep popping up on screen and interrupting my flow. But I accept that many users love it.
There's also a philosophical question of whether code completion is pedagogically good for beginners: I've heard it argued that it impedes learning. I have no idea whether there's any actual data to support that claim, but it does fit with my own prejudices :)
Personal prejudices and pedagogical philosophy aside, though, I do generally believe that it's best to give users options to configure their environments how they like. Earlier this year I had some students beg for us to switch Ace to a dark theme. Again, this isn't something I myself would choose but dark themes are certainly very popular at present, and why shouldn't student be allowed to use them? There's some discussion of this here. Currently the Ace UI does check for the media preference "prefers-color-scheme: dark" but it hasn't proved all that usable. I must revisit it and remind myself exactly why.
What I'd really like to see is something that lets the user set various Ace editor configuration options and have them "stick" for all subsequent uses. See here for example. Unfortunately that's an 8-year-old page and the functionality hasn't become standard.
In the absence of a convenient way for students to individually customise their environments, I think the best we could do would be to let individual teachers customise the Ace editor they way they wanted. That could be achieved as follows.
All CodeRunner UI plugins can have options that are configured in the question prototype and can be overridden by the question itself. Associated with each UI plugin is a json file listing the UI's configuration parameters. For example see this file for the Graph UI configuration parameters. Each parameter is documented within the lang file, e.g. for the Graph UI isfsm parameter, in the English language file, we have
$string['graphui_isfsm_descr'] = 'True if the graph represents a Finite State Machine,
in which case it can contain an incoming edge from nowhere (the start edge) and can
have \'accept\' nodes';
If a UI plugin has such options, the question authoring form displays a UI parameters entry field. For example, for the Graph UI:
You don't see this field with standard CodeRunner questions using the Ace UI because I very deliberately did not give it any parameters. I was trying to avoid adding extra complexity to the authoring form, which is already more complicated than I'd like. But it would be pretty trivial to add, say, autocompletion and darktheme UI parameters to Ace. The result then would be that you as a teacher could customise your own question types to turn on autocompletion, while I could leave it off for all of my questions.
The downside is that the question authoring form has now acquired the extra complexity of a UI parameters field for all questions, not just for those using non-Ace UIs.
I'm frankly unsure whether I want to go down this path or not. But we should discuss. Could you bounce that idea around among your colleagues to see what they think about it please? And of course comments are welcome from anyone else reading this forum.
Thanks again for the suggestion.