Skip to main content

Writing on a Chromebook

I've been playing with a budget Chromebook for the past few months and have to say, a Chromebook is a pretty good choice for writing. I'm using an Acer CB314-1H which cost me a whopping £79 (thanks to a £100 cashback deal). It has a bright, crystal clear FHD screen, a fantastic keyboard (much better than my HP laptop) and it is super lightweight.


As far as the keyboard goes, on first impressions, it seems that the keyboard has no delete key or CAPS lock, but both are available with help from the ALT key. It also seems that there is no way to turn the Trackpad off. This takes about ten seconds on Google to enable debug shortcuts, but to be honest, even with the option available, I rarely use. I catch my laptop trackpad all of the time, but hardly ever on the Chromebook.

The next thing to consider is software. There's Google docs. You can waste time searching the internet for alternatives, but this means enabling Linux and playing about and it's really not worth it. I managed to get LibreOffice working but it was slow and couldn't access Drive, which is where all the files are. But Google Docs is seamless, and a lot more powerful than it looks, certainly good enough to create a manuscript for ebook or publication. It can get a bit slow with large documents, but I haven't encountered too many problems and I'm working at just over 60,000 words, but for ease of use, I chop the document into five chunks. I use headings for titles which gives me a Document Outline (same as a Navigation pane and similar to Scrivener's Binder). I also use the comment pane all of the time when editing (a recent update allows you hide comments). Getting the work out is a breeze compared to Scrivener - you just download it as the format you want.

The next advantage is the grammar checker. The grammar check in Google Docs is amazing and picks up things that other word processors miss. It is certainly infinitely better than Scrivener, so when I get to proofing, I'd have to export to Google Docs anyway. I do like Scrivener for drafting simply for the option of coloured labels, but I can live without it. The grammar checker trumps any bells and whistles every single time because I continually miss out words when writing. Even drafting, I tend to write cleaner, stronger copy in Google Docs than anything else. 

So there you go. Yes, you can definitely use a Chromebook for writing novels. It's not the best solution. Hey, given the choice, I'd love a Macbook Pro, but those are way out of my budget, and probably always will be. For now, I'm more than happy with my £79 Chrome-buddy.



Comments

Popular posts from this blog

Rock Music, Stage Diving and a Fire Crew - It's the Clash Launch Party

Thursday 3rd March was one of the craziest nights of my life. Rather than launch the book in a shop or library, I booked a theatre and got local teen rock band, Hell's Marauders , to play. There were a few surprises during the night. The first was the cake Paula had made, with the full clash cover printed on the icing. The second was the fire engine in the car park.The third was being dragged up on stage to sing Anarchy in the UK with the band. I think I might be the first author to do a stage dive at a launch party. The fire crew were there thanks to Nev. Nev gave me some help on a few technical details in the novel. He was on call on Thursday night but wanted to come along, so he turned up in a fire engine with the whole crew. Catnip editor Non Pratt got up to do a truly wonderful introduction, then I jumped up, grabbed the mike and screamed out, "HELLO FATFIELD!" - proper rockstar style! I calmed down enough to do a short talk about YA fiction and a read...

Writing Challenge Day 3 - Back to Scrivener

Sorry Scrivener, all is forgiven. I've actually been using LibreOffice for about a month because I was using for a different project over the holiday period, and generally, everything was fine. But then today, right in the middle of a sprint, it started acting a little weird. I tried to undo a few things only to see it replace chunks of text with error messages. Then it crashed completely. Thing is, this document is less than 5,000 words. That's not a lot for a word processor to handle. And while it autorecovered the file, it's still one too many crashes for me.  Going to back to Scrivener, I suddenly remembered the Session Target tool. This makes life so much easier, as I can see, as I type, my progress. In LibreOffice I'd have to paste the word count into the spreadsheet I'd made.  Project targets window It also displays as a line bar at the top of the project with the Manuscript Target at the top, above the chapter title, and the Session Target below, so there...