Each document should have a shareable link directly to freshly compiled pdf without source view
At the moment, each document has two shareable links: one leads to an editable view, the other to a read-only version of source and compiled document. But sometimes you only want to give someone access to the (continually updated) pdf/compiled version of the doc. For people who don't need or want to see the source. My suggestion is to add a third shareable link; one which leads directly to a pdf file (compiled fresh from the current source) and nothing else.
This is different from sharing on figleaf as you may want to share a window to work-in-progress as it happens as opposed to 'final' or milestone versions. It is also different from the writelatex gallery as this would just be a pdf which you don't necessarily want to make visible to the public, only to those with whom you share the link.
Thanks for the feedback. I think this is a good idea, and we’ll try to work it into our API plans for the near future.
Just a sidenote to my last comment:
while the document is being compiled the link gives a error message in some browsers saying the pdf is being displayed errornously.
Workaround for v2:
1. klick onto menu
2. under Download right-click the PDF button
3. copy link to a texteditor and remove everything after the .pdf ending
This link displays the last compiled version available exactly as described in the question.
Tyler's trick does not seem to work in v2. Is there a different link that works?
Tyler Read commented
In case anyone is still interested in this, you can use the read-only link of a document, change "read" to "docs" and then add append the url with /pdf.pdf
This should become a live link to your document.
Any update on this? Andrew's tip didn't work for me.
Andrew MacFie commented
Try this: Go to read-only view, at the end of the url, replace the # and everything after with /pdf.pdf
Kurt Reed commented
Planned in 2014 and still a non-implemented must have feature.
Just adding one tip, when sending out work to reviewers that should add comments or changes, a workable way is to: for each reviewer, make copy, tag a version, distribute read-write link to the copy. This way I can compare several reviewers additions to the original version.
In fact with git its possible to clone each reviewers copy to a local git project, create patches and apply these on the original.
Agree! This would be a really good feature.
I could add that two cases are obviously useful:
1) link to pdf of the latest version (follows development)
2) link to pdf of tagged version (means reviewers can review a stable version)