One of the nice things about being in Malta for the spring is that I've been able to step back and think about Runestone Interactive and some of the ways it can be improved and moved forward. One of the things that I think holds the overall goals of the project back somewhat is the initial choice of restructuredText as the main authoring language. It was a good technical choice, but it is not nearly as popular as some other alternatives.
Recent developments in the world of web development have lead me to believe that a new approach would make a lot of sense.
So I’ve been messing around with this new idea
Why do this you may ask?
- But more importantly this has the benefit of making runestone available to virtually anyone you would not need to write in RST at all, you could write in plain html if you wanted to. Or any other markup language that let you insert html. Or if you were a clever hacker you could write your own macros for whatever system you use that generates the html.
- Finally I think this is a move in the direction that the web is headed over the next few years which is custom tags. Imagine if we could just have an
<body> <pre data-component="activecode" data-lang="python" id="test1"> def foo(): print 'hello world' foo() </pre> <pre data-component="activecode" data-lang="python" id="test2" data-include="test1 test2"> def main(): print 'goodbye girl' main() ==== print "This is hidden suffix code you don't see it in the editor" </pre> </body>
and get a page that looked like this:
Anyway, I am looking at this as an excuse to learn about Polymer, AngularJS and Polyfills and web components in general. The repo I linked to above has got activecode working very nicely, and I like this implementation. It is Much cleaner. There is no reliance on creating special xxx_code, xxx_edit, xxx_output id values for different div elements, no need to mix and match a bunch of template code in the directive implementation. Take a look and let me know what you think.
I would be especially happy to have you look at the code on github and send me any comments about the current implementation, or pointers on how to convert that into a web component. Someday there will be an