Support for very large documents

[krusynth]

We need an elegant way to handle Huuuuuuge documents. Right now doc_contents just has a text field in there, so we'd need to bump that to a medium_text. Even with that, though, we probably want to have pagination since it's a lot of content to load at once - and ideally allow authors to set where those pages break in an easy way. I'm thinking multiple rows in this table, and allow the user to break these up via separate editor windows somehow. Annotations would need to be tied to a specific page (defaulting to 1 for everything we've already got).

[cmbirk]

I would love to see a lazy / deferred load, but the behind-the-scenes would still have to be pagination, so that's probably the quickest route here.

[cmbirk]

We could potentially move a true pagination to a deferred load by appending the new content. This includes appending to the ToC.

The difficult part here is a permalink to an annotation that is on a separate page.

[sethetter]

Annotations would have to start pointing to a specific page. The page it's on could get loaded first and then the rest incrementally in the background somehow?

[cmbirk]

I would say for this ticket normal pagination is the way to go and we can refine from there

[cmbirk]

I've used this in a different project, and it worked decently well. I'm taking a look to see how it operates ( if it's just faking ).

http://chieffancypants.github.io/angular-loading-bar

[krusynth]

After talking this through, it looks like we need to :

• Make doc_content use a mediumtext field for document data
• allow multiple doc_contents per document, adding a page number flag
• add a page number to annotation targets
• add pagination to the frontend for documents
• add pagination to the frontend for annotations
• create a way on the backend to edit multiple pages