|
And in many cases, I absolutely do. But I don't have the time to contribute to all of the projects I use to a significant level. One has to pick and choose. Doesn't mean one is not able to discuss the relative merits of approaches.
If you open up the project to a standard templating system, rather than (as per threads here, I've not looked into the code) - make the content server some sort of non-replaceable embedded thing - then you of course open up the project to a whole group of developers you didn't perhaps have access to before as a project. That is - there are legions of folks with HTML/JS/CSS web dev skills (many more than Python skills I would venture to say)....that might be willing to help if it is creating a nice set of templates - which is for many a more digestible task than getting stuck into a full blown bit of Python dev.
It's easy to always say 'if you don't like it then *you* fix it' but here I am trying to work out why it was done as an embedded thing - in the first place, and certainly I can't work out why it would be done as a re-design effort - seems like that would have been the perfect opportunity to create a better modern infrastructure for future development work.
Indeed the already existent external projects (calibre-web etc) - that dip into the calibre db and present a web interface show that people DO want to do this, but it's just an awkward approach really.
|