I’m glad you had a chance to go down this path. I think it’s great to have some options, and I see that you went with some of the ideas we’ve discussed previously for the underlying mechanism with which to support it.
Looks like you chose a more formal MVC approach and a django-esque structure, which seems to be what the world uses most these days,soitwillbemorefamiliar. This, however, is one of the main reasons I don’t like usingDjango and similar frameworks like Pyramid, but that’s just a pet peeve of mine.
I think the documentation is off to a great start. I’ve not made the time to typethatupformypackage, though I did try to keep up with docstrings so a standard “help()” from the interpreter can provide a bit of usage info. I also plan on writing an article on using sofi to make a front-end for a dumb python debugger which may help illustrate my end a little better and hopefully clarify a few things.
As far as where this leads, I’ll say there’s quite a few possibilities. The most important thing I’ve made sure to do is separating the socket protocol from my ui, which will allow me to pluck that out at some point and use it for a whole other application. It seems you’ve done something similar, and gone a bit farther into making the widgets more interchangeable, whereas I’m more bound to bootstrap at the moment,mostlybecausemyexpansionplansgobeyondtheweb.
A good example of future work is a request I had the other day to look into producing an electron application out of this. Which seems fairly reasonable and doable, though not entirely sure of the practicality if you’re keeping python as the backend.
Keep up the good work, let’s stay in touch and see how we can help our projects move forward.