INFORMATION NOW: docs

Showing posts with label docs. Show all posts

Wednesday, March 11, 2015

Download or print Google docs viewer file

Today I was amazed by not being able to properly print a Google Docs Viewer file. Not sure if that was due to some protection of the document, but it was really not nice. All I got from printing was the first page. Through PDF or direct print. No "Download" button or anything like it. I assume it is due to protection levels anyway.

After few minutes, the only solution possible was:

1. Open Firefox
2. Install "downthemall"
3. Scroll through all the file so all the images render
4. Select "DownThemAll" from the blank space in the centre of the page

Got all the images to my local disk, so then just selected them all and print (now this is really good feature in Windows 7, congratulations MS).

Using Google Document List APIs to build Memeo Connect for Google Docs

Building Memeo Connect™ for Google Docs

Editors Note: This post was written by our partner Memeo, a digital media management company. Memeo Connect™ for Google Docs enhances Google Docs capabilities. We invited Memeo to share their experiences building an application on top of Google Apps utilizing some of our APIs. Other partners will share their experiences in future posts.

Hi Im Matthew Tonkin, Mac Applications Architect at Memeo. Google has been a great partner in helping us bring Memeo Connect to market. Were excited about the new additions to the Google Documents List APIs and the products weve been working on for them.

Google Apps is a great way for businesses to share and collaborate on documents, but more importantly, it has allowed businesses to move much of their office and IT infrastructure online for dramatic operating cost reductions. Until recently, Google Docs users had no way of uploading, storing, syncing and sharing files of any type. The big news is that Google Docs now supports all file types and there are Documents List APIs to prove it. January saw the release of the updated Documents List API with this new arbitrary file support, but no desktop client software to manage file syncing between the desktop and the cloud. Memeo Connect for Google Apps is that missing link. Memeo set out to bridge Google Docs cloud storage with desktop software. A simple goal that has big implications for where users store documents and how they are shared.

The end result is a desktop application that is fully supported by Google Docs for online storage, synchronization, sharing and data management. With Memeo Connect, instant access to your important documents while online or offline is now very possible. Memeo Connect is available on both Windows and Mac platforms.

Our timeline for Memeo Connect was impossibly short due to Google’s aggressive timeline for launch. How did we do it? Apart from the obvious late nights, junk food and beer, we received help from Google to take this product from concept to reality. Some of it came in the form of new APIs, some directly from the Documents List API team, some from the client libraries and some from the discussion groups.

1. Keeping native file formats

Google Docs now supports keeping files in their native format. Previously Microsoft Office files and images were converted to the online Google Document formats, removing much of the application specific formatting options used in the Office file formats. However, its now possible to upload Microsoft Office files and images without conversion, meaning users can keep all of their custom file formatting.

You can get all of this with a simple parameter in the post URL when uploading the new document.

Google Documents List API

https://docs.google.com/feeds/default/private/full?convert=false

If like us, you use the client libraries, then its just as easy.

Google Data Objective-C client library**

NSURL *uploadURL = [[mDocListFeed postLink] URL];
GDataQueryDocs *uploadQuery = [GDataQueryDocs queryWithFeedURL:uploadURL];
[uploadQuery setShouldConvertUpload:NO];

Google Data .NET client library

string uploadURL = DocumentsListQuery.documentsBaseUri + "?convert=false";
docService.StreamSend(new Uri(uploadURL), fileStreamHandle, GDataRequestType.Insert, contentType, docTitle);

The new features dont just handle Microsoft Office files. Any file type is supported with no additional parameters or changes to client code, however the support for these features is only available through the Google Documents List API for users that have a Premier account.

2. Bigger file size limits and resumable uploads

Google Docs now supports file uploads up to 1GB and is resumable, so failed or paused uploads can pick up where they left off.

Google Documents List API
http://code.google.com/apis/documents/docs/3.0/developers_guide_protocol.html#ResumableUpload

Resumable post link:

resumable-create-media" type="application/atom+xml"
   href="https://docs.google.com/feeds/upload/create-session/default/private/full"/>

Request:

POST /feeds/upload/create-session/default/private/full HTTP/1.1
Host: docs.google.com
GData-Version: 3.0
Authorization:
Content-Length: 0
Content-Type: application/pdf
Slug: MyTitle
X-Upload-Content-Type: application/pdf
X-Upload-Content-Length: 1234567

Resuming:

POST HTTP/1.1
Host: docs.google.com
Content-Length: 100000
Content-Type: application/pdf
Content-Range: bytes 0-99999/1234567

Google Data Objective-C client library**

Resumable uploads are automatically enabled when switching to the uploadLink URL

NSURL *uploadURL = [[mDocListFeed uploadLink] URL];
GDataQueryDocs * uploadQuery = [GDataQueryDocs queryWithFeedURL:uploadURL];

Pausing and resuming uploads is also made easy.

[mUploadTicket pauseUpload];
[mUploadTicket resumeUpload];

Google Data .NET client library

ResumableUploader resumableUploader = new ResumableUploader();
if (newFile)
   resumableUploader.Insert(authentication, docEntry);
else if (partialFile)
   resumableUploader.Resume(authentication, resumeUri, httpMethod, fileStream, cotentType);
else if (updateExistingFile)
   resumableUploader.Update(authentication, docEntry);

** Objective-C code samples have been taken from the Docs Sample code

3. Client Libraries for Mac & Windows

The Google Documents List API provides all of the backend server functionality but isnt ideal for rapid client application development. As client developers, we prefer the efficiencies provided by a wrapper in our native client languages. This is where the client libraries for Objective-C and .NET allowed us to shorten our application development time significantly. Without the client libraries, we simply would not have been able to achieve our goals for Memeo Connect in the time we had available.

Many of the Documents List API features we worked with in our early development were not available through the client libraries. This was initially quite daunting because of the risk that we would have to drop down to raw server calls and miss out on the efficiencies we gained through using the client libraries. However as we got to know the client libraries better, we found they were written flexibly enough that we never had to do that - there was always a way to bend them enough to get what we needed. A sign of great design by their architects.

For example uploading without conversion was simple in the Objective-C client library even before it was officially updated to support it.

NSURL *uploadURL = [[mDocListFeed postLink] URL];
GDataQueryDocs *uploadQuery = [GDataQueryDocs queryWithFeedURL:uploadURL];
[uploadQuery addCustomParameterWithName:@"convert" value:@"false"];

4. Support from Google

The Documents List API team were of enormous help throughout the course of this project. As with most of Googles public APIs, theres always an avenue to ask questions about how to best use the technology, pursue bugs or request new features. The new Google Apps Discussion Groups are simply the best way to get an answer quickly and is invaluable in getting past whatever is blocking your progress. Google Developer Relations people monitor the discussion groups and frequently answer questions, link to other relevant resources, and provide code samples.

Whats next?

We had a sizable list of things we really wanted to do with Memeo Connect 1.0 and some of that had to wait for 1.x or 2.0. Were looking forward to continuing to work with Google and file as many feature requests as we can to make some of these new features a reality. Anyone can file a feature request for Google Apps APIs and I can assure you they all get considered.

In future releases well be adding more support for direct file system integration, better tools to manage sharing and were really excited about supporting new devices. Get ready to see more Google Docs in more places.

Build add ons for Google Docs and Sheets

Weve just announced Google Docs and Sheets add-ons — new tools created by developers like you that give Google users even more features in their documents and spreadsheets. Joining the launch are more than 60 add-ons that partners have built using Apps Script. Now, were opening up the platform in a developer-preview phase. If you have a cool idea for Docs and Sheets users, wed love to publish your code in the add-on store and get it in front of millions of users.

To browse through add-ons for Docs and Sheets, select Get add-ons in the Add-ons menu of any document or spreadsheet. (Add-ons for spreadsheets are only available in the new Google Sheets).

Under the hood

Docs and Sheets add-ons are powered by Google Apps Script, a server-side JavaScript platform that requires zero setup. Even though add-ons are in developer preview right now, the tools and APIs are available to everyone. The only restriction is on final publication to the store.

Once you have a great working prototype in Docs or Sheets, please apply to publish. Scripts that are distributed as add-ons gain a host of benefits:

Better discovery: Apps Script has long been popular among programmers and other power users, but difficult for non-technical users to find and install. Add-ons let you distribute your code through a polished storefront—as well as direct links and even Google search results.
Sharing: When two people collaborate on a document and one of them uses an add-on, it appears in the Add-ons menu for both to see. Similarly, once you get an add-on from the store, it appears in the menu in every document you create or open, although your collaborators will only see it in documents where you use it. For more info on this sharing model, see the guide to the add-on authorization lifecycle.
Automatic updates: When you republish an add-on, the update pushes out automatically to all your users. Theres no more hounding people to switch to the latest version.
Share functionality without sharing code: Unlike regular Apps Script projects, add-ons dont expose your source code for all to see. Thats reassuring both to less-technical users and to the keepers of your codebases secrets.
Enterprise features: If your company has its own Google Apps domain, you can publish add-ons restricted just to your employees. This private distribution channel is a great way for organizations that run on Google Apps to solve their own unique problems.

Beautiful, professional appearance

Thanks to hard work from our developer partners, the add-ons in the store look and feel just like native features of Google Docs and Sheets. Were providing a couple of new resources to help all developers achieve the same visual quality: a CSS package that applies standard Google styling to typography, buttons, and other form elements, and a UI style guide that provides great guidance on designing a Googley user experience.

A replacement for the script gallery

Add-ons are available in the new version of Google Sheets as a replacement for the older versions script gallery. If you have a popular script in the old gallery, nows a great time to upgrade it to newer technology.

We cant wait to see the new uses youll dream up for add-ons, and were looking forward to your feedback on Google+ and questions on Stack Overflow. Better yet, if youre free at noon Eastern time this Friday, join us live on YouTube for a special add-on-centric episode of Apps Unscripted.

Dan Lazin profile | twitter

Dan is a technical writer on the Developer Relations team for Google Apps Script. Before joining Google, he worked as video-game designer and newspaper reporter. He has bicycled through 17 countries.

INFORMATION NOW

Pages