|Chromebook Pixel (left) with external monitor displaying PDF (right)|
It's the best Chromebook out there right now, and was produced as more of a showcase for Chrome OS. It's got more power than most people need in a Chromebook. Also, it can simultaneously run Ubuntu Linux thanks to the Crouton project. This comes into play later in the post.
Next, in the local/MS Office corner, I present the Compaq Presario C700:
It's old, but still going. It runs Windows 8 (soon to be 8.1) and Microsoft Office 2013. Its battery is now useless, requiring constant hookup to the mains; fortunately, I can access it from my Chromebook remotely via Chrome Remote Desktop, if I need to be portable.
As with all good scientific sensitivity tests, I need to keep everything the same in both cases, and just change the variable I'm testing. Here are the other helpers in my paper-writing factory:
Bibliography management: MendeleyFirst, I use Mendeley to manage my biblography. It's an "iTunes for scientific papers and PDFs", as I've once heard it described. It syncs all my PDFs (metadata and all) to the cloud, so I can access everything from the browser, or download a desktop program (Mac, Linux, Windows). Its major flaw for us Chrome OS users is the almost-impossible way to get PDFs into your online catalogue, as you can't download the application (and shouldn't need to!). Yes, this is
When I'm using ShareLaTeX, I can upload a .bib file automatically generated by Mendeley. Then I can easily cite references within LaTeX (this ease is a major advantage of LaTeX over Word). And when I'm using Word, there is a plug-in that allows Word to import citations from Word, and automatically generate a bibliography. I've only had experience with ShareLaTeX; I will report back on Word-and-Mendeley integration in Part 2.
Figure creation: Google DrawingsI'm creating figures for publication with Python, but this is maintained on a separate server. I access the server via SSH from Chrome OS. The outputted images are then downloaded onto my Chromebook via a public_html folder on the server, and uploaded into Google Drawings if required (for annotating, combining etc). I've previously mentioned Google Drawings as a good all-round image editor. It can combine smaller images while maintaining their resolution (good for publications); it is good for quick schematic diagrams; it integrates well with other Google Drive office-style applications. It is easy to export (download) the final product as a .pdf to create good-quality figures for either Word or ShareLaTeX. And it certainly beats using Word or Powerpoint to mash together a diagram (often the case in academia it seems!).
Verdict: Using ShareLaTeX for collaborationIf the other person is not as comfortable using LaTeX, it can become difficult. A lot of people are much more comfortable with Word due to its malleable, What-You-See-Is-What-You-Get nature.
|Example of ShareLaTeX.com screen, with code in the middle, and the compiled PDF on the right.|
Otherwise, ShareLaTeX shows history of edits (with a paid account), has a chat facility, is accessible simultaneously by two (or more, with paid account) people, and compiles relatively reliably. I found that large documents (my thesis, for example) sometimes wouldn't compile, but this was only ever temporary and more likely to do with the huge volume of high-DPI figure files in my project.
The main advantages with (Share)LaTeX is as follows:
- Seamless, easy management of bibliography
- An organised folder of high-resolution figures that precludes the need to chase images round your Word document
- Everyone has the same 'version'; no compatibility errors like with Word (both different years and different OSs!)
- Fast help from the website developers when there were issues compiling
- ShareLaTeX is free at its base feature level, which is sufficient for many people (poor students like me included)
However, there are shortcomings:
- Can be tedious when trying to get a manuscript to output perfectly in line with a journal's style guide. Sometimes, where a change would be a couple of keystrokes in Word, it would be a time-consuming Google goose-chase to track down the relevant 'hack'.
- ShareLaTeX is still missing a mature 'track changes' equivalent for collaboration (and the ability to point fingers at whoever just deleted that supremely-written paragraph)
- Some journals don't like LaTeX. Full stop.
I hope to discuss these matters further when I begin the entire process again for the second paper, but in Microsoft Word. I look forward to sharing my experiences...