On Fri, Nov 3, 2017 at 1:42 PM, Richard Hipp <d...@sqlite.org> wrote:

> Option 1:
>
> This gives the most flexibility to the site administrator, to make the
> site work like she wants.  But it also makes writing your own header
> templates more complicated.  And when new capabilities come out (such
> as CSP) it requires existing repositories to edit their header
> templates in order to insert the new information.
>

Would "requiring existing repositories to edit" be a bad thing? We don't
want to inadvertently break any existing repos' HTML output after an update
of their fossil binary. While i'm all for my underlying tools managing
protocol-level details (e.g. HTTP headers), i'm always nervous when they
want to manage/finagle my lovingly hand-crafted content.


> Option 2:
> ...
> This approach is the most automatic.  The header and footer scripts
> become easier to manage, and required changes to the <head>...</head>
> needed for new features (such as CSP) happen automatically without the
> administrator having to make any changes.  It is relatively easy to
> upgrade legacy header and footer templates.  Just delete all text
> through the <body> in the header template and delete </body> and all
> that comes afterwards in the footer.
>
> Option 3:
> ...
> This approach continues to work on legacy repos.  It allows repos to
> upgrade easily just by deleting all header text up to and including
> the first <body> tag.  And it allows knowledgeable admins to set up
> their own custom <html><head>...</head><body> text if they have some
> unanticipated need.  The downside is that this system is more complex
> to explain and document.
>

In my old age i'm tending toward "most automatic" (#2), but but _someone_
out there is going to Have a Need which likely requires the flexibility of
#1 or #3.


> Option 4:
>
> Behave as in option 1 or option 2, depending on a setting.  The
> setting defaults to do legacy option 1 support.  Then when an admin
> goes to update the header and footer scripts to the option 2 style,
> she also changes a setting to cause the <html><head>...</head><body>
> content to be prepended and the </body></html> content to appended.
>

That sounds the most fiddly :/.


-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to