I take it you take issue with the Html class.
I did not write it, so take no offence :-)
I am wondering though, surely you can't read Django either. Does it matter so much how the code constructs the html output? The html construct is just a clever way so as not to forget closing tags and such.
I suppose what you mean here is that html developers can work with templates, and code should then process the missing items. As Django works. Whereas narweb is a big python file where paragraph after paragraph of html code is spit out, and you must be the developer knowing the code to understand it.
As to narweb, Doug has always stated he would like to rework it to plugin based. The experience with Django might help. That is, using some template system, instead of doing everything in code.
I've spent this morning looking over parts of the Gramps-Connect HTML +
and whoever else is involved to make the Gramps-Connect better and maybe
even responsive so that it will adapt well to smaller screens.
However, I also took a look at the Narrative Web template file. I was
considering the amount of work needed to improve that as well since it
has been stated that Gramps-Connect and Narrative Web would have shared
I can't remember who worked with Rob on that HTML-generator code for the
narrativeweb.py file, but to me it looks completely unapproachable. Last
time I worked on Narrative web the template was largely HTML with Python
handling the dynamic aspects. It was relatively easy to read and alter.
This current narrativeweb.py file is not that way. There is little or no
visible HTML in the file. I can kind of decipher this new HTML-generator
code, but there's no way I or probably any web designer is going to feel
comfortable writing new HTML with this mechanism.
However clever this HTML-generator is, I think its continued use will
only make the Narrative Web plugin less attractive to potential web
dev/designer contributors. And it has almost no relationship to the
template methods used on the new Gramps-Connect codebase.
I recommend divorcing the Gramps-Connect and Narrative Web resources. I
think there is and will continue to be a lot of interest in
to be as efficient and modern as possible. Trying to accomplish that
feat will be difficult enough without anchoring it to the aging and
now-difficult-to-update Narrative Web code.
Leave Narrative Web where it is (stable, useful) and develop a new,
cutting edge web platform on Gramps-Connect. Then, once Gramps-Connect
has stabilized, rebuild the Narrative Web template based on Gramps-Connect.
I hope I am not offending anyone. This is just my perspective and
opinion as a professional web designer and developer.
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
Gramps-devel mailing list