Skip to main content

Google Docs and Writing

By
My students like to use Google Docs for collaborative drafts of projects. They like the "Suggesting" mode for editing, though it takes time to get used to this approach compared to Microsoft Word, and they really like the "Chat" mode for working together remotely.

I'm not as comfortable with Google's "Suggesting" edit mode. I like the "Track Changes" approach of Word, but that might be out of familiarity.

The "Revision History" is also little clunky in Google Docs. Students have rolled back edits by accident, especially on tablets. Maybe the location of the "Editing Mode" and "History" (the upper right) makes them prone to accidental "palm clicks" when holding the devices.

I've not used the JavaScript-based macro features, but I am glad there is a way to automate editing tasks. One of the reasons I love Word is the ease of Visual Basic for Applications. JavaScript ("GScript") macros might enable me to add similar editing tools to Docs I have created for Word.

The extensions and add-ons for Docs range from lousy to okay. I've not seen many that are "WOW!" and my students don't seem to be curious about the add-on library.

Writing always changes with technology. I'm not sure Google Docs is a step forward, but it is a step towards greater convenience.

Related articles

Labels:

Comments

Post a Comment

Popular posts from this blog

MarsEdit and Blogging

By
MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail
2 comments
Read more

Learning to Program

By
Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor
2 comments
Read more

Learning to Code: Comments Count

By
I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.
3 comments
Read more