Chromium code hints at Google Now for OS X

DNP Google

A few months back Chromium whiz François Beaufort spotted a piece of code in the open source web browser that hinted at Google Now possibly coming to Chrome. Today, the programmer has uncovered an issue log pointing out notification center enhancements for OS X. An entry, listed as “[Mac][MC] Implement notification updates and relayouts” could possibly indicate Google Now having a future on Apple’s desktop platform. With Google’s I/O a little over a week away, hopefully we won’t have to wait too long to find out. In the meantime, we’ll reach out to the company for a comment on Beaufort’s findings and see what turns up.

Filed under: , ,

Comments

Via: The Next Web

Source: François Beaufort (Google+)

Rockmelt says goodbye to its social web browser, says hello to Rockmelt for Web

Rockmelt says goodbye to its social web browser, says hello to Rockmelt for Web

It was a good ride while it lasted, but the browser wars haven’t been kind to Rockmelt, which has announced that it’ll cease supporting its socially-inclined desktop browser sometime in the next few months. The decision was made because keeping up with the steady stream of updates for Chromium, the code upon which the Rockmelt browser was based, was simply too costly.

In its place, the company has announced Rockmelt for Web, a portal that may serve to alleviate some of the Reader rage many of us are experiencing. It aggregates content from “your favorite sites, your favorite people, and a dash of crazy stuff you never would have discovered,” so it’s like a combination of RSS, social networks and StumbleUpon. It’s an invite-only beta for now, though users of the browser and iOS app have already been invited to the party. The rest of you lot can get on the list by hitting the source and signing up.

Filed under: ,

Comments

Via: TechCrunch

Source: Rockmelt Blog (1), (2), Rockmelt for Web

Webkit’s Chromium-specific code to be removed in effort to streamline

Webkit's Chromium-specific code to be removed in effort to streamline

Now that Chromium has pledged its allegiance to Google’s new Blink rendering engine, Webkit is set to have the now-unnecessary Chrome-specific code stripped from it. Apple Webkit developer Geoffrey Garen kicked off a conversation on the project’s mailing list about removing the Mountain View-centric cruft, saying that it would streamline things and hopefully “make development easier and more coherent for everyone.” Garen adds that Googlers Adam Barth and Eric Seidel have already offered to pitch in with the clean up, but he asks that devs who will continue using the engine tidy things up as well. Over the next few weeks, code in Webkit related to the search giant’s browser, such as the V8 JavaScript engine, will be put up on the chopping block. With a Blink-infused Chrome slated to arrive in roughly 10 weeks, these changes shouldn’t mean much for the average web surfer, save for Webkit being a bit trimmer under the hood.

Filed under: , , , ,

Comments

Via: Slashdot

Source: Webkit Developer Mailing List

Google’s Blink engine (gently) hints at a more streamlined future for Chrome

Google's Blink engine gently hints at a more streamlined future for Chrome

Word that Google had decided to fork WebKit and build its own rendering engine is still echoing through the spidery halls of the internet. The true ramifications aren’t entirely clear yet, but Opera has pledged to embrace Blink and WebKit is already talking about removing Chrome-specific code from its repositories. This doesn’t necessarily indicate a seismic shift in the industry, but it certainly suggests that we won’t be looking at a world so thoroughly dominated by the direct descendant of KHTML. At least at first, the new entrant won’t actually deviate much from WebKit. Primarily the focus will be on stripping away unnecessary code and files to streamline the rendering engine specifically for Chrome. Obviously, this won’t prevent other developers from using Blink, since the project is open source. But Google has been pretty up front about the rationale behind the fork — the multi-process architecture favored by Chromium-based projects is quite different than that used in other WebKit browsers. This has, to put it in the plainest terms possible, kinda gummed up the works.

Blink is about 10 weeks away from landing in the stable version of Chrome (it’s expected to be turned on by default in version 28), but it’s already available as part of the Canary build. We downloaded the experimental browser and spent some time with it in an effort to identify what, if anything, was different. Keep reading after the break to find out just what Google has bought by shedding some of WebKit’s baggage.

Filed under: , ,

Comments

New Chrome Beta Is Faster…By 5%

New Chrome Beta Is Faster...By 5%Remember the Daft Punk song, “Harder Better Faster Stronger”? Well, that is certainly a mantra worth following if you want to improve your company’s performance, and of course, it also applies to athletes who are competing for honors. The same goes for the technology scene as well for certain of the adjectives, where Chrome 27 on the Beta channel has been launched, and this particular release is said to unleash smarter behind-the-scenes resource scheduling in addition to a slew of new features that will be a boon for web developers.

Basically, the end user would be able to experience faster page loads, which are approximately 5% speedier on average, courtesy of changes made to Chrome’s resource scheduler. Basically, Chrome 27 Beta and future iterations will have a more aggressive scheduler when it comes to using an idle connection, where it will demote the priority of preloaded resources as part of an effort not to interfere with critical assets. Have you given Chrome 27 Beta a go yet?

By Ubergizmo. Related articles: Bill Gates And Paul Allen Recreate Classic 1981 Shot, Mushkin Announces New Chronos GO SATA 3 SSD,

Google Is Forking WebKit to Create a New Rendering Engine For Chrome and Opera

Google announced last night that it’s going to stop using WebKit—the rendering engine currently used by the likes of Safari and Chrome to display web pages—in favor of its own solution which will be called Blink. More »

Google forks WebKit with Blink, a new web engine for Chromium and Chrome (update)

Google forks WebKit with Blink, a new web engine for Chromium and Chrome (update)

You could call WebKit the glue that binds the modern web: the rendering engine powers Apple’s Safari, Google’s Chrome, and many mobile browsers past and present. Things are about to unstick a little. Google believes that Chromium’s multi-process approach has added too much complexity for both the browser and WebKit itself, so it’s creating a separate, simpler fork named Blink. Although the new engine will be much the same as WebKit at the start, it’s expected to differ over time as Google strips out unnecessary code and tweaks the underlying platform. We’d also expect it to spread, as the company has confirmed to us that both Chrome and Chrome OS will be using Blink in the future. We’re safely distant from the Bad Old Days of wildly incompatible web engines, but the shift may prove a mixed blessing — it could lead to more advancements on the web, but it also gives developers that much more code to support.

Update: The Next Web has confirmed that Opera, which recently ditched its Presto engine for Webkit, will indeed be using Blink as it’s already hitching its proverbial wagon to Chromium.

Filed under: , ,

Comments

Source: Chromium Blog

Google Now Arriving On Chrome OS And Windows

Google Now Arriving On Chrome OS And WindowsGoogle Now could very well soon be integrated into Google’s Windows browser as well as the Chrome OS platform, as it was spotted in a new reference that was left behind by engineers in the most recent Chromium release. Of course, this particular bit of sleuthing was achieved by Chromium enthusiast François Beaufort, where it was noticed that a new flag was thrown into the mix that is known as the Chromium backend, where it enables users to turn on the option should they know the relevant Google Now server. Of course, being what it is at the moment, the feature has yet to be made public, and this means that Google Now cards (some call it notifications) will not be displayed – yet.

For the moment, Google Now will most probably be enabled in Chrome for Windows, without any sight of a Mac version to date, as well as in Chrome OS, although there is no concrete date as to when this might happen. Let us keep our fingers crossed that it will be sooner rather than later.

By Ubergizmo. Related articles: App That Makes Your Notebook Sound Like A Typewriter, Students Get Half Year Of Free Office 365 And 20GB Storage From Microsoft,

Chrome for Android build may tout a proxy-based speed boost

Chrome for Android on Galaxy Note II

A fast smartphone will only go so far toward improving browser load times if the connection isn’t there to back it up. If a discovery within a recent build of Chrome for Android is any hint, Google may have its own solution to that bottleneck. New code flags reference Google-run proxy servers that would squeeze pages using SPDY, improving performance at least slightly for the bandwidth-deprived. While there’s not much more to go on, the finding is enough to suggest that roughly equivalent boosters like Amazon Silk and Opera Turbo could have a real fight on their hands. We’d advise caution when the flags are only accessible by running an ADB command — they’re clearly not ready for prime time. Should Google flick the switch on compression for Chrome’s main release track, though, Android users may not need a third-party browser to sip the web through a thin straw.

Filed under: , , , ,

Comments

Via: François Beaufort (Google+)

Source: Chromium.org

Google Possibly Adding Notification Center, Google Now To Chrome

Google Possibly Adding Notification Center, Google Now To Chrome

A new version of Chromium for Windows was released recently, and which already should be cause for celebration, but it seems an eagle-eyed developer has spotted some code within the latest build in order to allow for a notification center to be enabled.

In order to see the notification center for yourself, you’ll need to toggle the “Enable Rich Notifications” flag in chrome://flags once you download the latest build of Chromium for Windows. The notification center pops up like you would expect towards the bottom right of the Chromium browser and can be dismissed by clicked on the cross in the upper-right corner of the notification. A “Clear All” function is also available, which could hint at the possibility of multiple notifications alerting the user.

The addition of a notification center to Chromium may hint at a future release to Google’s Chrome browser. Not only that, but the code may also hint at support for Google Now in Chrome somewhere down the line.

By Ubergizmo. Related articles: Hacker Coerced And Blackmailed Women Into Taking Nude Photos Via Webcam, Google Maps The Grand Canyon,