Hi Willem and Artur
Good to know you're finding CodeRunner useful and interesting to hear about your use of the GraphUI.
I appreciate that the question authoring UI isn't very user friendly but it is at least fairly consistent with the standard Moodle question authoring UI. I think it would be difficult to incorporate a customised GUI-fied authoring UI just for questions using the GraphUI in a clean way that was consistent with the various other CodeRunner UI components (currently AceUI, TableUI, GapFillerUI, GraphUI and HtmlUI). It would be possible with major refactoring to extend the existing UI plugin API to allow companion question-authoring UIs as well, but it would be a massive effort and I don't think the complexity would be warranted. CodeRunner has already been accused of suffering from feature bloat. Also, your proposed UI, while it looks very nice and quite likely perfectly fits your own team requirements, wouldn't cover many of our own GraphUI use cases, and GraphUI is already a niche market.
So unfortunately I think your own project lies outside the main CodeRunner development path.
Off the top of my head I can see three ways you might proceed:
- Write a completely independent question-authoring program (not even a CodeRunner plugin) that outputs the Moodle-XML representation of CodeRunner questions. Import those questions into Moodle. This is the easiest approach from a coding standpoint but is very clumsy (unacceptably so?) when you need to do any question maintenance. Certainly not a good long-term solution but perhaps worth considering as a way of getting yourself up and running.
- Write a new Moodle plug-in that allows you to create or edit CodeRunner questions independently of CodeRunner itself. I think this would be the nicest solution but is also probably the most work. It gives you reasonably good long-term compatibility with CodeRunner itself, although you would still need to adapt your code if/when CodeRunner modifies its database schema.
A big advantage of (3) is that question authors who wanted to go beyond the GUI-fied interface you provide will still be able to use the more-powerful code-based approach. I predict this will happen almost immediately, following the Software Engineering rule "People seldom know what they want until you give them what they ask for"!
Thank you for your extensive answer!
After some careful consideration we have decided to choose the second option and fork CodeRunner to give a clean setup for GraphChecker, while being able to build on the great setup CodeRunner offers. Our project is slowly taking shape and by now we have a preliminary alpha version that is giving us the behavior we hoped to achieve. Hopefully within reasonable time we will be able to publish a initial version. At the moment we are in the process of ensuring that CodeRunner and GraphChecker can run successfully next to each other. So far everything is going fine, however we ran into one issue.
After changing the name of the plugin, we noticed that
qbehaviour_adaptive_adapted_for_coderunner refuses to run for any questions that are not CodeRunner questions (see here).
We were wondering if you would be willing to update
qbehaviour_adaptive_adapted_for_coderunner, so that it also accepts GraphChecker questions. (An alternative would be to make a separate
but that seems redundant.)
Alternatively, we found a topic where you mention that you would like for CodeRunner to do the caching in the same way that the STACK question type does it, so that maybe the
qbehaviour_adaptive_adapted_for_coderunner would not be necessary at all anymore. Would you think it makes sense for us to look into this approach as well?
Kind regards, Arthur and Willem