GitLab

Needed for all the copying I'm doing for the HTML export.

Mostly this is to cheaply get rid of the wall post form.

Now the default render_self for internal artefacts escapes their output, need to make sure the introduction is treated as HTML.

This required splitting up the export polling of artefact plugins into two steps - one where we establish what stylesheets are going to be needed, and the second for actually doing the export. This is because the second step writes out templates, so we have to know the stylesheets before this.

This required re-calculating the progress bar, those changes are reflected here too.

IE doesn't remove dom nodes when they're display: none, but can't handle visibility well it seems. So use display instead.

Don't automatically serve the file if the browser is opera - it fails horribly and tries to display the content inline.

It doesn't seem to appear in some browsers (I'm looking at you, Opera and Safari), but does make things a little nicer in IE.

Added a TODO about separating the generation of archives from the export() method so it can be generalised.
(cherry picked from commit 7165e6921d05fca753e91c47d6a8bf224c67f14a)

Recursively look for all files and folders, not just two levels deep, when creating a strategy for root level folders.

Removed the old system for this and implemented one that is similar to how it's being done for HTML export.

Make the render_self() implementation for internal artefacts escape the title, as they shouldn't have HTML in them.

I don't think this is actually called anywhere so it's not a security vuln or anything - the implementation is just there to complete the api.

We're not exporting as xhtml any more - that work would unfortunately conflict with future work we have planned.

Now there's a new method, get_content_type, which elements should define to say what type they should be. The default implementation of get_content is now applicable in many more cases. All escaping and cleaning is done in the template, where it should be.

The system still supports exporting content with type=xhtml - we're just not going to use it.

If just exporting a list of views for someone, don't bother with the summaries for the artefact plugins.

This allows them to inform code on the outside about what's going on. This is used by the export UI.

When javascript is available, show some links to assist managing the checkboxes for views (select all, reverse selection).