Google signs up three schools for Chromebooks

9to5 Staff

Google’s put in motion an Apple-like plan calling for Chromebooks in education, traditionally a strong market for Apple’s Macintosh computers. The company announced on its official Enterprise blog back-to-school deals with three schools that will begin using Chromebooks when students return over the coming weeks. First up, the Fessenden School in West Newton, MA, an independent K-9 institution which will add two carts of Chromebooks that will also be available for use in the library.

Grace Lutheran School, a small private school in Oshkosh, central Wisconsin, will be sharing Chromebooks throughout the day in classrooms among 5th through 8th grade students. And finally, Merton Community School District, also in Wisconsin, will give 110 sixth graders Chromebooks to keep and use until they graduate from eighth grade. At $20 per user per month, users get a Chromebook, a web-based management console for IT and 24/7 support from Google. The company says it’s seeing “a lot of interest from K-12 institutions” from their Chromebook for Education initiative.

Read more

Chrome gets Omnibar history sync, Lion multitouch gestures, more

9to5 Staff

Several new enhancements have surfaced in the latest developer version of Google’s Chrome browser. As previously announced, the software now respects Apple’s multitouch gesturing philosophy in OS X Lion. This means you can flick your finger left or right on your Magic Mouse (or two fingers on a trackpad) to advance and go back in your history. Unfortunately, the browser doesn’t yet support double-tap or pinch to smoothly zoom in and out of web pages iPhone-style, like Safari on Lion. Another handy treat: You can now rest assured that accidentally hitting the Command + Q combo won’t quit Chrome because a subtle overlay appears telling you to hold down the combo briefly in order to quit.

In addition, Chrome now supports Lion’s Full-Screen feature through the standard full-screen button found in the upper right corner of the window. The latest nightly build across all platforms also sports the brand new Omnibar history syncing feature which comes on top of the previously available syncing capabilities for Chrome extensions, passwords, bookmarks, web apps, autofill items, browser settings and themes. A multi-profile feature has also seen some work in the visual department, even though it is not yet available in nightly Chrome builds for OS X. If you wish to try out those experimental features, we recommend installing the Google Chrome Canary build. This particular version, unlike other Chrome channels, runs without a hiccup alongside your existing stable Chrome installation.

Cross-posted on 9to5Mac.com
Read more

Offline Gmail and Calendar coming to Chrome OS by the end of the summer

Jake Smith

Google engineer Ido Green just made comment on This week in Google that offline mode for Gmail and Calendar are on their way by the end of the summer. There was talk of these features at this year’s Google I/O, but it’s nice to know offline mode is still on track. Besides Gmail and Calendar, Green also said there are a few more offline features coming.

WebKit-based Chrome (Chromium) port coming to Android soon

Jordan Kahn

When we think of Google and browsers we usually think of the latest Chrome build, the fastest real world use desktop browser around. While the browser currently shipping on Android is nothing to sneeze at, Google’s real innovation in the browser space is arguably happening with Chrome. That’s why it’s surprising we haven’t heard more about a potential port of Chrome to Android, a project the Android team is now actively working on with the open source WebKit community.

Googler Andrei Popescu, along with a couple others working on the project, took to WeKit-Dev group today (via TechCrunch) to announce their focus on the port:

We would like to give an update about WebKit on Android. A while ago, we started the effort to upstream the Android port of WebKit. For a variety of reasons, this work took longer than anticipated and was never finished. We realize that the incomplete Android port that exists today in WebKit ToT has caused quite a bit of confusion and inconvenience to the project as a whole and we are very sorry for that.

In case you’re confused, the browser currently running on Android was originally based on the WeKit layout engine and Chrome’s V8 Javascript engine, but also varies from the desktop version of Chrome enough that two separate teams work on the two browsers.
Read more

Mozilla wants web apps to compete with native iOS and Android apps

Jordan Kahn

 

Apple and Google are clearly the two front-runners competing for market share in the mobile world, which is why it’s no surprise we think of iOS and Android when we think of apps. With the growth of the smartphone industry also came the resurgence of native apps (thanks largely in part to Apple’s App Store which still dominates the space). However, Mozilla hopes that web apps will soon mature to provide a comparable experience for end users and an even better alternative for developers.

“We are aiming at providing all the necessary APIs to build a basic HTML5 phone experience within the next 3-6 months”

While Chrome OS has shown promise, it isn’t the only browser-based platform planning on entering the web app space… If Mozilla has its way, developers can use the results of their new WebAPI project to build an “HTML5 phone experience” that’s compatible across all operating systems (whether it’s Android, iOS, Windows Phone, etc).

A report from CNET claims Mozilla has plans for the APIs to “interact with a phone’s dialler, address book, contacts list, and camera”, essentially giving you access to the same functionality of native apps but directly in your device’s browser.

The WebAPI project certainly isn’t trying to create a full-blown operating system. However, working hand in hand with Mozilla’s Boot to Gecko project, which aims to build a “complete, standalone operating system for the web”, it could create a potentially compelling alternative to Google’s browser-based Chrome OS.

It appears that Mozilla is serious about the project, as a report from CNET claims they’re in the process of hiring full time programmers and plan to have the basics in place by February. Read more

Huge win for web apps: Chrome can now run native code

9to5 Staff


Image credit: dropit2entrecard.blogspot.com

Something fell off our plate amid the late craze in tech reporting, especially with Google buying Motorola and HP abandoning PC biz and webOS devices. That doesn’t mean this little nugget is not worthy your attention, quite the contrary. Three years ago, Google mentioned it would eventually enable the so-called native code execution in Chrome. The latest beta of Chrome 14, unleashed a week ago, now supports this functionality, the Google Operating System blog has discovered.

In Layman’s terms, native code execution lets the Chrome browser run snippets of web code specifically optimized for your computer’s processor rather than analyze, interpret and painstakingly turn HTML code line by line into a machine-readable format – that takes a lot of time, slowing down code execution as a result.

Google’s definition simply states the technique lets developers “build web applications that seamlessly execute native compiled code inside the browser”. For our tech-savvy readers, Google outlined some of the benefits of this technique in the announcement blog post three years ago:

Modern PCs can execute billions of instructions per second, but today’s web applications can access only a small fraction of this computational power. If web developers could use all of this power, just imagine the rich, dynamic experiences they could create. At Google we’re always trying to make the web a better platform. That’s why we’re working on Native Client, a technology that aims to give web developers access to the full power of the client’s CPU while maintaining the browser neutrality, OS portability and safety that people expect from web applications.

The stable Chrome 14 release is expected within a month, when native code execution will become standard feature for the 160 million active Chrome users, as of May 11. So, why should you care? Read on…

Read more