Closed michaelsmithxyz closed 11 years ago
I intend to unhardcode the paths now... I think web.py is kind of weak in general. It shouldn't be super hard to convert it away to another engine, but I'm kind of attached to web.py Make suggestions...
It's not weak. It's lightweight, but we weren't structured enough to make effective use of that. I'm looking into templates and perhaps a new framework, but I don't know yet.
I thought web.py's templating system worked well for us, but we didn't use it as effectively as we could have. I say this mainly concerning the code for the list of VMs in the sidebar that we had to copy and paste for every page.
On Sun, Apr 28, 2013 at 3:12 PM, Michael Smith notifications@github.comwrote:
It's not weak. It's lightweight, but we weren't structured enough to make effective use of that. I'm looking into templates and perhaps a new framework, but I don't know yet.
— Reply to this email directly or view it on GitHubhttps://github.com/jholtom/webvirt/issues/1#issuecomment-17140559 .
i'm going to use Jinja2 to redo the templates like data.
Jinja2 looks easy, and SOOO much better at using python in the html files.
This is somewhere between a bug and an enhancement; could we get someone definitely assigned to this?
I don't think any of us liked web.py's templating system, and it seemed to be the cause of a lot of our problems. I suggest we work on finding a new system, and making efforts to convert our templates to that, as well as to remove markup from urls.py.