Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Loading...
Seo Master present to you: Author Photo
By Scott Knaster, Google Developers Blog Editor

As this is being posted, the last sessions are ending here at Google I/O 2012 in San Francisco. This year's event was our biggest and most amazing yet, with software and hardware launches, dozens of technical sessions and code labs, and an already legendary demo that required permission from the Federal Aviation Administration. We shared all this with more than 5500 developer attendees in person, and with millions more in 172 countries around the world via I/O Live and I/O Extended.

developers at Google I/O

We announced a lot of information, so it’s understandable if you missed some of it. Here are just a few of the highlights:
These really are just a few of the highlights. You can read a lot more news in our blogs about Google Drive SDK, Apps Script, YouTube API, Google Maps, App Engine, Google TV, and Google Analytics.

For all the details, you can watch full session videos, which we continue to upload as they’re ready.

Thanks for coming, thanks for watching, and most of all, thank you for being Google developers!


Scott Knaster is editor of this very blog. He's been enjoying Google I/O this week, and is going to go to sleep now.
2013, By: Seo Master

seo Google I/O 2012: that’s a wrap 2013

Seo Master present to you: We're happy to announce that today we shipped a substantial update to O3D, an API for creating rich 3D applications in a web browser. With today's release, we focused on addressing a theme we heard in the requests and feedback from the community: that O3D should run as well as possible on many different types of hardware. Toward that end, we're releasing two new additions: software rendering and feature requirements. If you've already installed the O3D plugin, you should receive these additions automatically.

Software rendering allows O3D to use the main processor to render 3D images if the machine running the app doesn't have supported graphics hardware. While the hardware O3D requires to run in hardware-accelerated mode is fairly modest by today's standards (a DirectX 9, Pixel Shader 2.0 capable graphics card), there are nonetheless PCs that don't meet these requirements, and we think it's important for web apps to run on all machines, regardless of hardware.

Because software rendering is significantly slower than hardware-accelerated rendering, we're also introducing a concept called "feature requirements" that will help minimize how often O3D will have to fall back to software rendering. Feature requirements allow developers to state upfront that their app will require certain hardware capabilities to render properly. If the machine running the app supports those features, O3D will run it fully hardware accelerated; if however, it is lacking any of the required capabilities, O3D will drop into a software rendered mode. Anecdotally, we found that this tiering allows 45 of our 48 samples to now run in hardware-accelerated mode with less capable graphics cards.

Finally, while it has nothing to do with extending hardware support, we're also adding a couple other goodies: a full-screen mode to make O3D apps more absorbing and a community gallery to feature cool demos that use O3D (like Infinite Journey, the first game developed outside Google using O3D). If you've developed an application or sample that would be useful to the O3D community, please be sure to submit it for our team to review for inclusion in the gallery using this form.

By Henry Bridge, Product Manager2013, By: Seo Master

seo O3D update: New capabilities and expanded compatibility 2013

salam every one, this is a topic from google web master centrale blog: Written by Ben D'Angelo, Search Quality Team

First, a brief recap: In late 2005, we started emailing webmasters to let them know that their site is violating our Webmaster Guidelines and that we have temporarily removed some of their pages from our index. A few months ago we put these emails on hold due to a number of spoofed messages being sent from outside Google, primarily to German webmasters. Then, in mid-July, we launched Message Center in our webmaster console, which allows us to send messages to verified site owners.

While Message Center is great for verified site owners, it doesn't allow us to notify webmasters who aren't registered in Google's Webmaster Tools. For this reason, we plan to resume sending emails in addition to the Message Center notifications. Please note that, as before, our emails will not include attachments. Currently, the Message Center won't keep messages waiting if you haven't previously registered, but we hope to add that feature in the next few months. We'll keep you posted as things change.this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com

from web contents: Update on penalty notifications 2013

Powered by Blogger.
Design by Dev Nasser