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

Seo Master present to you:
Preview Liga Champion Real Madrid Versus Manchester United
Preview Liga Champion Real Madrid Versus Manchester United - Pertandingan akbar terjadi lagi, Real Madrid berturut-turut mengemban tugas yang berat, walaupun tugas-tugas sebelumnya sudah dilaksanakan dengan baik ketika melibas Barcelona, baik di Piala Raja dan di La Liga, kini hadangan berat ada didepan mata di liga champion menghadapi Manchester United.

Real Madrid mau tidak mau harus benar-benar serius untuk melangkah ke jalur berikutnya, harus menang jika ingin berpeluang menyabet double winner musim ini. Namun tidak semudah itu, Manchester United berada di posisi pertama klasmen sementara di liga inggris, sedangkan real madrid masih bertahan di posisi ke 3 di La Liga.


Tahukah Anda.....

- Pertandingan liga champion berat bagi real madrid karena bermain di kandang lawan yaitu manchester united.
- Namun masih bisa dipertimbangkan, pekan lalu real madrid bisa menang dikandang lawan barcelona
- Tidak hanya itu, Chiristiano Ronaldo adalah pemain madrid yang pernah membela manchester united, dipastikan akan tampil superiror, karena merasa semua pendunkung real atau MU adalah pendukungnya
- Manchester United berada di klasmen atas di liga inggris, dan sudah menang melawan derby inggris
- Manchester United pada musim lalu, gagal melaju keluar dari grup di liga champion, kali ini MU tidak akan main-main.

Kedua tim dipastikan akan main ngotot dan menyerang, ahsil imbang sebenarnya tidak ada yang diuntungkan, walaupun beruntung bagi Mu, namun gol pertama akan menjadi gol yang sangat panas di perjalanan pertandingan nanti. Siapakah yang akan memenangkan pertandingan... Siapa Pilihan Anda.

2013, By: Seo Master
Seo Master present to you:

As Google's developer program continues to grow -- already over 60 APIs and tools on Google Code today -- we credit much of this growth to a culture of exploration and rapid iteration, and to the invaluable feedback and insights we receive from you about each product as it evolves.

Reflecting this culture, we're pleased to introduce Google Code Labs today as a home for developer products still in their early stages of development. Our hope, of course, is that all of our developer products grow up to be huge successes, but we realize that not every single one will reach that goal. The Labs program offers engineering teams at Google and the developer community a chance to explore ideas and get involved early.

With that background, we're also announcing that several of our best-known and most-used APIs and tools are among the first set of Google Code Labs "graduates" -- including App Engine, Google Web Toolkit, AJAX Search API, Maps API, Earth API, Calendar Data API, YouTube APIs, and more. See the full list of graduates on the Google Code Labs page.

For these graduates, we're increasing our commitment with published deprecation policies and other critical support services. The Visualization API terms, Contacts Data API terms, and Picasa Web Albums Data API terms include good examples of transparent deprecation policies. They state that we'll support each version for at least 3 years from when it's deprecated or a newer version is introduced. We're working to get policies posted for the other graduates as well, though the time period may vary a bit from product to product. It will be 3 years for most, but it might be less for some. The AdWords API, for example, has a policy of supporting old versions for 4 months.

Of course, even established products need a way to experiment with new features. With that in mind, some products will have features labeled "experimental" that could change (or even be removed) at any time, while the rest of the API is covered by a deprecation policy with long-term support.

There are additional hurdles for an API to graduate from Labs. They include requirements like having a dedicated, ongoing engineering team and comprehensive test suite. We also want to do things like the App Engine System Status Dashboard for more products.

Finally, we'd like to bid a fond adieu to one of our first developer products, the venerable SOAP Search API. It has been deprecated since 2006, when we stopped accepting new developers for the API, and it's finally hanging up the gloves and retiring on August 31st. It has been steadily declining in usage over the last couple years and we believe that the majority of use cases are sufficiently handled by the more comprehensive AJAX Search API (which supports not only web search, but local, news, images, video, and more). For those interested in migrating, there are more details in the AJAX APIs blog.

Thank you for making the past five-plus years such a success. We look forward to doing great things together with Google Code Labs and we hope you'll join us in congratulating the new graduates.2013, By: Seo Master
Seo Master present to you: This post is part of the Who's @ Google I/O, a series of blog posts that give a closer look at developers who'll be speaking or demoing at Google I/O. This guest post is written by Seth Priebatsch, Chief Ninja of SCVNGR, who's creating a mobile game for the conference.


SCVNGR is a platform for quickly and easily building location-based mobile games. Each game is all about doing challenges at places. Go here and take a photo, go there and solve this riddle. You happen to be at this coffee shop? Awesome! Try this challenge and earn a couple points! SCVNGR powers games for all sorts of institutions ranging from Princeton to Harvard to the Smithsonian Institutes to SIGGRAPH and even the U.S Navy.


If you're attending Google I/O this year, you'll get to try out our mobile game at the conference! (Don't forget to bring your Android phone, if you've got one!) I'm not going to give it all away here, but I do want to talk about one of the especially cool features that we're rolling out using some neat Google APIs.


One of the biggest challenges that our game-builders face is how to build location-based challenges that truly verify the user has actually made it to the right location. There are some non-technical solutions to this problem, such as creating riddles that require the user to be there to solve them (i.e. what is the third word on the fourth line of the plaque on the back wall) or taking photos which are then verified manually by the community or the game developer themselves.


We've also looked at a number of more technical solutions. The most obvious being to take the geo-tagged coordinates of each of the locations with a game and then use GPS to ensure that the player is within a certain radius of the location. Unfortunately, GPS verification has issues when the locations are indoors (as many are) and can vary greatly in accuracy across difference devices.


A new option, one that we're launching in a couple of weeks, uses QR codes planted at locations within the game-board. Players must scan these QR codes to verify that they've made it to the right spot. We're using the Google Charts API as an easy way to programmatically generate QR codes. Of course, generating and planting the QR codes is only half of the equation. You've also got to be able to decode them from the phones during the game. We experimented with a couple of options as to how to best achieve this.


Our first thought was to simply have the players snap pictures of the QR code which we'd then post back to our server, decode and respond with whether or not that was in fact the right QR code (or a QR code at all). The benefit of this solution was only having to utilize one QR code processing library for both our iPhone and Android applications. But we ran into a couple issues right up front:


  1. The time cost incurred by having to transmit a reasonably high-resolution image to our servers.
  2. Most players aren't very good at taking pictures of QR codes. They move the lens of the camera very close and snap the picture. (It's actually best to take the picture from 12-24 inches away to enable the camera to focus sharply on the QR code.) This led to a high-number of failed submissions before we were actually able to recognize a valid QR code.

Add all this up and it created a pretty poor game-play experience.


So we turned to the ZXing project (pronounced Zebra Crossing) which is an open source barcode processing library written in Java and highly suited to the Android environment. Running the ZXing code right on the device rid us of the time-delay introduced by transmitting images to the server. But we still had the issue of the high-fail rate of the user snapping unsuitable images. Rather than trying to implement any form of "auto-scanning", we've chosen to simply grab images from the camera every 1/8 of a second or so, scan them and stop the process once a QR code is recognized.


As for the iPhone, ZXing has an objective-c port for the iPhone, but in order to grab images in real-time from the camera, you'll have to use a private API call for iPhone OS 3.1. Luckily, Apple has officially authorized its public usage until it's made public.


We're hard at work integrating QR codes into the great game that we're building for Google I/O and we hope you'll get a chance to play. The I/O team will let you know when the game is ready! The SCVNGR team will also be there in person, so please come by and say hello! We'd love to get your thoughts on the game or just chat about some of the Google APIs that we've used within SCVNGR.


2013, By: Seo Master
Powered by Blogger.