Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.
Click here to check if anything new just came in.
April 14 2011
Pagination comes to Google Docs
(Cross-posted from the Google Docs Blog)
Exactly one year ago, we launched a new version of the Google document editor, created from the ground up to take advantage of the latest capabilities in modern web browsers like Chrome. In particular, we baked in a way of supporting text features that aren’t natively included with browsers—for example, we added a ruler for controlling the margins, text that wraps around images to create eye-catching docs and discussions for a more collaborative editing experience.
Today, we’re doing another first for web browsers by adding a classic word processing feature—pagination, the ability to see visual pages on your screen. We’re also using pagination and some of Chrome’s capabilities to improve how printing works in Google Docs. Pagination is rolling out now and should be available to everyone by the end of the day.
Pagination adds visual page breaks while you’re editing your documents, so now you can see how many pages of that report you’ve actually finished. Because we’re able to show you individual pages, we can improve the way other features work too: headers now show up at the top of each page instead of just at the top of your doc, manual page breaks actually move text onto a new page and footnotes appear at the bottom of the pages themselves.
If you prefer editing documents with a continuous layout, you can hide page breaks by selecting the “Compact” document view from the “View” menu.
Pagination also changes what’s possible with printing in modern browsers. We’ve worked closely with the Chrome team to implement a recent web standard so we can support a feature called native printing. Before, if you wanted to print your document we’d need to first convert it into a PDF, which you would then need to open and print yourself. With native printing, you can print directly from your browser and the printed document will always exactly match what you see on your screen.
For now, native printing is only available in Google Chrome, but we’re hoping other browsers will implement the same web standard so everyone can have the best possible printing experience with Docs.
Pagination and native printing are great examples of how modern browsers are making it possible to take the best parts of the desktop experience and bring them online. Please share your feedback on the Google Docs forum.
Posted by Luiz Pereira, Software Engineer
Exactly one year ago, we launched a new version of the Google document editor, created from the ground up to take advantage of the latest capabilities in modern web browsers like Chrome. In particular, we baked in a way of supporting text features that aren’t natively included with browsers—for example, we added a ruler for controlling the margins, text that wraps around images to create eye-catching docs and discussions for a more collaborative editing experience.
Today, we’re doing another first for web browsers by adding a classic word processing feature—pagination, the ability to see visual pages on your screen. We’re also using pagination and some of Chrome’s capabilities to improve how printing works in Google Docs. Pagination is rolling out now and should be available to everyone by the end of the day.
Pagination adds visual page breaks while you’re editing your documents, so now you can see how many pages of that report you’ve actually finished. Because we’re able to show you individual pages, we can improve the way other features work too: headers now show up at the top of each page instead of just at the top of your doc, manual page breaks actually move text onto a new page and footnotes appear at the bottom of the pages themselves.
If you prefer editing documents with a continuous layout, you can hide page breaks by selecting the “Compact” document view from the “View” menu.
Pagination also changes what’s possible with printing in modern browsers. We’ve worked closely with the Chrome team to implement a recent web standard so we can support a feature called native printing. Before, if you wanted to print your document we’d need to first convert it into a PDF, which you would then need to open and print yourself. With native printing, you can print directly from your browser and the printed document will always exactly match what you see on your screen.
For now, native printing is only available in Google Chrome, but we’re hoping other browsers will implement the same web standard so everyone can have the best possible printing experience with Docs.
Pagination and native printing are great examples of how modern browsers are making it possible to take the best parts of the desktop experience and bring them online. Please share your feedback on the Google Docs forum.
Posted by Luiz Pereira, Software Engineer
August 04 2010
Update on Google Wave
We have always pursued innovative projects because we want to drive breakthroughs in computer science that dramatically improve our users’ lives. Last year at Google I/O, when we launched our developer preview of Google Wave, a web app for real time communication and collaboration, it set a high bar for what was possible in a web browser. We showed character-by-character live typing, and the ability to drag-and-drop files from the desktop, even “playback” the history of changes—all within a browser. Developers in the audience stood and cheered. Some even waved their laptops.
We were equally jazzed about Google Wave internally, even though we weren’t quite sure how users would respond to this radically different kind of communication. The use cases we’ve seen show the power of this technology: sharing images and other media in real time; improving spell-checking by understanding not just an individual word, but also the context of each word; and enabling third-party developers to build new tools like consumer gadgets for travel, or robots to check code.
But despite these wins, and numerous loyal fans, Wave has not seen the user adoption we would have liked. We don’t plan to continue developing Wave as a standalone product, but we will maintain the site at least through the end of the year and extend the technology for use in other Google projects. The central parts of the code, as well as the protocols that have driven many of Wave’s innovations, like drag-and-drop and character-by-character live typing, are already available as open source, so customers and partners can continue the innovation we began. In addition, we will work on tools so that users can easily “liberate” their content from Wave.
Wave has taught us a lot, and we are proud of the team for the ways in which they have pushed the boundaries of computer science. We are excited about what they will develop next as we continue to create innovations with the potential to advance technology and the wider web.
Posted by Urs Hölzle, Senior Vice President, Operations & Google Fellow
We were equally jazzed about Google Wave internally, even though we weren’t quite sure how users would respond to this radically different kind of communication. The use cases we’ve seen show the power of this technology: sharing images and other media in real time; improving spell-checking by understanding not just an individual word, but also the context of each word; and enabling third-party developers to build new tools like consumer gadgets for travel, or robots to check code.
But despite these wins, and numerous loyal fans, Wave has not seen the user adoption we would have liked. We don’t plan to continue developing Wave as a standalone product, but we will maintain the site at least through the end of the year and extend the technology for use in other Google projects. The central parts of the code, as well as the protocols that have driven many of Wave’s innovations, like drag-and-drop and character-by-character live typing, are already available as open source, so customers and partners can continue the innovation we began. In addition, we will work on tools so that users can easily “liberate” their content from Wave.
Wave has taught us a lot, and we are proud of the team for the ways in which they have pushed the boundaries of computer science. We are excited about what they will develop next as we continue to create innovations with the potential to advance technology and the wider web.
Posted by Urs Hölzle, Senior Vice President, Operations & Google Fellow
Older posts are this way
If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.
