MatrixAdapt | Logiciel de gestion d'Entreprise, Création et référencement des sites web

Seo Master present to you: By Matt Hansen, Google Developer Programs

2013, By: Seo Master

Seo Master present to you: By Mike Marchak, Google Code Team

This election season, the Google Code Team has been inspired by democracy. We have been looking at code.google.com and thinking about ways to make the site better for our users. For example, we updated the homepage a few weeks ago to make it easier to find some of our most popular products. However, we wanted to give our users the right to vote. So, when Google Moderator was released to the public, we thought it would be the perfect tool to get your feedback and ideas. The best part is that you can vote on good ideas so they move to the top of the list and vote against bad ideas so they don't. We added a feedback link in the footer on Google Code, but you can get started using the link below.

Vote on Google Code!

We plan to review your feedback to help us prioritize improvements to Google Code. We'll also respond periodically to the highest rated comments in the Google Code Blog.

So get out and vote on Google Code!2013, By: Seo Master

Seo Master present to you: By DeWitt Clinton, Google Developer Programs

In 2005 we launched Google Code to provide a home for our developer and open source programs. Two years, dozens of new products and new programs, and one major redesign later, Google Code is bigger and more dynamic than ever. With today's relaunch we've added a new search auto-complete feature (to help you find your favorite products with a keystroke or two in the search box), an expanded and improved search results page, a cleaner and more comprehensive site directory, new blog and group gadgets, and a simplified and unified look and feel for product documentation.

To get a sense of how far things have come you can take a look at the first version of Google Code, back when the whole site almost fit on one page. Today we have thousands and thousands of pages of content on Google Code, and we've added the new site directory and new search features to help you navigate them.

One of the most exciting things about the redesign is that everything you see here was built using technology and APIs that are available to everyone. The pages we're serving don't rely on any secret back-end tricks; the site is built on plain HTML, JavaScript and CSS, each using our public APIs. In fact, all of the techniques used on Google Code can be duplicated on your own site.

For example, the search results pages use a combination of the AJAX Search API and Custom Search Engines. The homepage gadgets use the AJAX Feed API and Google Reader feeds. The videos are powered by the YouTube API, the blogs by the Blogger API, the events powered by the Google Calendar API, the metrics by Google Analytics, the forums by Google Groups, etc., etc.. And we're pleased to use jQuery, the wonderful open source JavaScript library (not ours, we're just fans), to help power each page. Stay tuned -- over the upcoming weeks we'll offer detailed articles and tutorials about how we built the various parts of Google Code using open technologies.

But the best thing about Google Code hasn't changed: And that's you, the developer, our never-ending source of inspiration. Your projects provide countless examples for the Featured Projects feeds, your words and wisdom power the developer groups, and your accomplishments and ideas never cease to amaze us with the possibilities and potential for a better web. This redesign was for you, and I want to personally thank all of you for being such an integral part of Google Code. Together we're capable of doing something very special.

Please join us on the Google Code Blog, (where we'll be enabling comments for this and future posts), and let us know where you're headed and how we can help you get there.2013, By: Seo Master

Seo Master present to you: It's Friday, time for some fun!

Here is a captivating way to visualize your Google Analytics data in a Treemap visualization and you can visualize your own data with our live demo.
(note: IE currently not supported for visualization part)





The goal of this example was to teach people how to use the Google Analytics API on App Engine in Java. As well as demonstrating how to use both OAuth and AuthSub along with the App Engine's various services. The code looked great, but the output was a boring HTML table. So I used some open source tools to transform the table into a pretty tree map visualization!

All the code has been open sourced on Google Project hosting. I also wrote an article describing how this application works making it easy for developers to use this example as a starting point for new data visualizations and other Google Data projects.

For the data retrieval part, this example uses the App Engine Java SDK and the Google Analytics Data Export API Java Client Library to retrieve data from Google Analytics. The example code implements both unsigned AuthSub and registered OAuth authorization methods allowing developers to get up and running quickly in development environments and later switch to a secure authorization method in production environments. The application also uses the Model-View-Controller pattern, making it flexible and allowing developers to extend the code for new applications. (like adding support for other Google Data APIs)

For the visualization part, I used the open-sourced Protovis SVG Visualization Library to create the Treemap. This JavaScript library is maintained by the Stanford Visualization Group and excels at creating brand new visualizations from a data set (in this case a boring HTML table). To handle all of the interactions, including rollover, tooltips and slider controls, I used JQuery. Here is the JavaScript source to the visualization part of the sample.

Enjoy!

By Nick Mihailovski, The Google Analytics API Team

P.S. If you have created any cool new visualizations using the Google Analytics Data Export API, email us so we can highlight them as well.2013, By: Seo Master

Seo Master present to you: Custom Search themes make it easy for you to customize the look and feel of your search results pages. And if you want to take the customization gig further, you can also customize the result snippet—a small sample of content that gives search users an idea of what's in the webpage—by using structured data.

When you are reading a webpage that reviews a film, you can figure out what the title is, what reviewers thought of the film, and how they rated it. You can even search for stores with the best prices for the DVD. Structured data can convey the meaning of such key information to computers.

Structured data formats—such as microformats, RDFa, and PageMaps—are semantic markup that you add to your HTML page. Structured data make web content more meaningful to machines. These attributes do not change the formatting of your website, they just make the text enclosed within the XHTML tags "understandable" by computers and influence what shows up in the result snippets.

When you tag your webpages with structured data, Custom Search indexes them and sends the metadata back in the XML results for your page. You can then take this XML feed and transform it into HTML results that showcase key information—such as image thumbnails, summaries, dates, authorship, ratings, and prices. Having the most relevant information in your search results makes the webpages in your site more compelling to your users.

You can, for example, create the following kind of rich snippets:


You can even add thumbnails and actions that let your users download files or make purchases.


To learn more, read the Custom Search Developer's Guide.

By Kevin Griffin Lim, Custom Search Team2013, By: Seo Master

Seo Master present to you: If you can select headgear for your LEGO ® action figures, your search engine should let you customize the theme for your search results page, right? Darn tooting!

True, Custom Search already lets you customize the look and feel of your search results page, but we're making it easier. You can now go to the control panel and select one of the predefined themes that broadly matches the look and feel of your website.

If the standard themes are not quite what you want, you can make further changes. You can tinker with the page layout (Why stick with a single column of results, when you can have two?) and play with the font colors and types. The standard themes paired with the "Compact" layout option are optimized for mobile devices, so they work well on iPhone, Android devices, and Pre.

If you want a greater level of control than that, you can download the CSS, tweak it in a text editor, and host the CSS in your website. You can make your search results page blend with the style of the rest of your website.


To learn more, read the Custom Search Developer's Guide.

By Kevin Gnome Lim, Custom Search Team2013, By: Seo Master

Seo Master present to you: Post by Fernanda Weiden, Systems Administration Team

I recently traveled to the I Free Software Forum in Lisbon, Portugal, where I gave two talks. The first was on load balancing and the second focused on "Google e o Software Livre" (Google and Free Software). The main organizer of the conference was Ralf Braga, an old friend of mine from Brazil, who moved to Lisbon few months ago.

Both of the talks were well attended, which was great. During my load balancing talk, I covered things I found out while testing Linux Virtual Server and HAProxy, two open source software load balancing solutions. I explained a bit about the basics of load balancing, and then the pros and cons of each approach.

Lisbon is a very beautiful city. Everyone was chatting about the amazing growth of conferences about "Software Livre" in that country. There will be a total of 6 conferences about open source software around Portugal in just the next few months.

There were around of 200 people attending two simultaneous rooms of talks over two days, and most attendees were university students. One of the sponsors prepared the table for their booth in the same shape as the Ubuntu logo. Really cool. They also had Ubuntu pillows. Do we have Google Code pillows? We should. :)

The organizers are planning the second edition of the conference for next year already. I proposed to the participants that each one of them brings at least one friend who has never been to an free software conference before with them when they return. I know I'm already looking forward to going in 2008!

(The I Free Software Forum site is in Portugese. You can read an English translation.)2013, By: Seo Master

Seo Master present to you: Project Hosting on Google Code is a beehive of activity, with many large and active projects and even more that aspire to that level. Now it will be a little easier for project members to sort out who should be doing what by documenting each member's duties in plain language on the new People sub-tab. Here's an example from the zscreen project:


Duties describe what each member is expected to be doing. Project owners can grant permissions that control what each member is allowed to do. While permissions can be fairly fine-grained, it's usually best to grant broad permissions, and then trust your project members to do their duties or go above and beyond them when the situation calls for it.

In open source software development, anyone can access the source code of the project, and it's important to allow anyone to access issues and project documentation. But in some projects, there is a need to restrict some information to a subset of project members for a limited time. For example, you might want to quickly patch a security hole before publicizing the details of how to exploit it. Project members can now place restrictions on individual issues to control who can view, update, or comment on them.
Here's some of what our new permission system allows project owners to do when they need to:

• Acknowledge the role of a contributing user without giving them any additional permissions
• Trust a contributor to update issues or wiki pages without letting them modify source code
• Restrict access to specific issues to just committers, or to a specific subset of members
• Restrict comments on specific issues or wiki pages when another feedback channel should be used instead
• Automatically set access restrictions based on issue labels

Getting started is easy, just click the People sub-tab and start to document what you and your project team are supposed to be doing. If you need to mess with permissions, see our permission system documentation for all the details.

If you'd like to meet some of the people behind Google Code, please drop by the Google booth at OSCON 2009 this week.

By Jason Robins, Project Hosting on Google Code Team
2013, By: Seo Master

Seo Master present to you:

On this day 40 years ago, Neil Armstrong and Buzz Aldrin became the first humans to walk on the Moon. This was quite an achievement for mankind and a key milestone in world history.

To commemorate this event the Command Module code (Comanche054) and Lunar Module code (Luminary099) have been transcribed from scanned images to run on yaAGC (an open source AGC emulator) by the Virtual AGC and AGS project. As the project evolves, look for syntax highlighting done with a special extension for google-code-prettify.

Image - NASA/courtesy of nasaimages.org

By Nathaniel Manista, Project Hosting on Google Code2013, By: Seo Master

Seo Master present to you: We recently published deprecation policies for a number of APIs that graduated from Google Code Labs. They state how long we'll support each version from when it's deprecated or a newer version is introduced. It will be 3 years for most, but the time period varies a bit from product to product.

• AdWords API terms
• AdSense API terms
• AJAX Feed API terms
• AJAX Language API terms
• AJAX Libraries API terms
• AJAX Search API terms
• Apps APIs terms
• Calendar Data API terms
• Chart API terms
• Health API terms
• Geo APIs terms (Earth API, Mapplets, Maps API, Maps API for Flash, and Static Maps API)
• Secure Data Connector terms

We still need to update the terms for a couple remaining graduates, but should have them all done within the next couple weeks.

By Neel Kshetramade, Google Developer Programs2013, By: Seo Master

Seo Master present to you: We'd like your feedback about how to make Google Code a more useful destination for developers to find information about using Google's APIs and developer products.

Please take our survey and give us your feedback, it should only take you a few minutes.

http://code.google.com/survey

Everyone who submits the survey will have a chance to win a limited edition t-shirt.

The survey runs until midnight PST Friday June 11 2010 (that's this week!).

By Jocelyn Becker and the Google Code developer experience team2013, By: Seo Master

Seo Master present to you: We are happy to announce that Project Hosting on Google Code now supports the Mercurial version control system in addition to Subversion. This is being initially rolled out as a preview release to a few invited users on a per-project basis, so that we can iron out the kinks before making this available to the general public.


Mercurial, like Git and Bazaar, is a distributed version control system (DVCS) that enables developers to work offline and define more complex workflows such as peer-to-peer pushing/pulling of code. It also makes it easier for outside contributors to contribute to projects, as cloning and merging of remote repositories is really easy.

While there were several DVCSs that we could support, our decision to support Mercurial was based on two key reasons. The primary reason was to support our large base of existing Subversion users that want to use a distributed version control system. For these users we felt that Mercurial had the lowest barrier to adoption because of its similar command set, great documentation (including a great online book), and excellent tools such as Tortoise Hg. Second, given that Google Code's infrastructure is built for HTTP-based services, we found that Mercurial had the best protocol and performance characteristics for HTTP support. For more information, see our analysis.

If you would like to help us launch Mercurial and to try out the features as an invited user, please fill out the following form. We are currently looking for active projects with more than two users that are willing to try out Mercurial and work with us to identify issues and resolve them. For projects that plan on migrating from Subversion, see our conversion docs for the steps required for this process.

Our implementation of Mercurial is built on top of Bigtable, making it extremely scalable and reliable just like our Subversion on Bigtable implementation. For more information on our Mercurial implementation, we will have a TechTalk at Google IO that will be led by Jacob Lee, one of the core engineers working on Mercurial support. Let us know if you plan on attending and we'll give you access to Mercurial ahead of the talk.

By David Baum, Software Engineer
2013, By: Seo Master

Seo Master present to you: Last April, we started providing translations of code.google.com pages in five languages: Simplified Chinese (中文[简体]) , Japanese (日本語) , Portuguese (Português) , Russian (Pусский) , and Spanish (Español). You didn't think we were done, did you?

Today, we're happy to add Korean (한국어) and Traditional Chinese (中文[繁體]) to that list. We've translated the site directory and top-level site pages, and from now on, you'll find those languages in the drop-down language selector at the top of the page header on code.google.com.

For Korean, you can now find full developer guide translations for OpenSocial API, Gadgets API, Themes API, and Adwords API. We have some API guides coming soon in Traditional Chinese, but unfortunately you'll have to guess which ones while we finish putting the final touches on those translations. If you're interested in hearing about new translations in these languages, you might want to subscribe to the APAC Developer Blog for updates as we add more content.

Good code is a universal language, spoken by developers all over the world. We don't think you should have to read English to build a great app.

By Naomi Bilodeau, Google Code Team2013, By: Seo Master

Seo Master present to you: By Naomi Bilodeau, Google Code Team

Developers speak lots of languages, not just English and C++. We know that you use Google Code from all over the world, and we understand that the love of a good API is universal.

We're excited to announce that developer content on Google Code is now available in five new languages: Chinese, Japanese, Portuguese, Russian, and Spanish. Many of our pages, such as the site directory and landing pages for the various APIs have already been translated. You will also find that some of the deeper technical documentation, such as the Chart API and Maps API, has also been translated where appropriate. Where we haven't translated the content yet, you will continue to see the English version of the site.

We'll be working to keeping this content up-to-date, and we're looking forward to adding more support for languages and APIs throughout the year.

Update: Corrected to read "in five new languages." The sixth language, of course, is English.

2013, By: Seo Master

Seo Master present to you: We just posted updated terms of service for 5 more APIs to include transparent deprecation policies. This is part of their increased commitment as graduates of Google Code Labs. As we mentioned in March when we introduced Labs, each of these deprecation policies states that we'll support each version of the API for a guaranteed length of time from when it's deprecated or a newer version is introduced. While it's 3 years for most, it might be less for some. With this batch of updates, for example, the Checkout API has a policy of supporting old versions for 1 year while all of the others will support old versions for 3 years.

You can see the updated terms for all 5 APIs:

• App Engine terms
  
• Checkout API terms
  
• Documents List Data API terms
  
• SketchUp Ruby API terms
  
• YouTube APIs terms

By Neel Kshetramade, Google Developer Programs2013, By: Seo Master

Seo Master present to you: I am very pleased to announce version 2 of the AJAX APIs Playground. For those of you not familiar with it, the Playground is an educational application designed to show interactive code samples for some of Google's coolest Javascript APIs. Of the new changes, the most obvious is the sweet new UI, thanks to help from Roman Nurik of the Google Earth team.

The new features are:

* Break points (simulated in Javascript)

* Firebug Lite in output for debugging

* Line numbers in code editor

* Ability to edit HTML of samples



The breakpoints and Firebug Lite additions are my favorite new features. But why did I include Firebug Lite when all web developers (should!) have Firebug installed? Because when code runs on the Playground, it runs in an iFrame. That iFrame does not have the Firebug object initialized in it. Since it is a cross-domain iFrame, there's no simple way to add Firebug to the iFrame's window object, so adding Firebug Lite was the best approach. This makes it so you can now use all of your favorite Firebug debugging convenience functions in the Playground!

To use Firebug Lite and breakpoints, simply click on the line number you want to add a breakpoint to and hit "Debug Code". This will insert Firebug Lite into the output and pause the execution on the breakpoint line number until you to click the play button to continue. Try adding a breakpoint to a line, clicking "Debug Code", then opening Firebug Lite and typing in a variable name to inspect the contents/value of the variable at that point in the code.

Adding breakpoints and forcing Firebug into a local function context were really fun engineering problems, so if you want to check them out (or contribute code to the Playground) go to the open source repository for it, come chat it up on IRC, or talk with me in person at the quickly approaching Google I/O conference (early bird registration runs until May 1).

Also, it's really important that you share your feedback so that I know what you'd like to see in the next version of the Playground! Thanks, and enjoy the Playground!

By Ben Lisbakken, Google Developer Programs2013, By: Seo Master

Seo Master present to you: We've been working with our user experience team to help our users discover relevant and timely developer product information faster on the Google Code homepage. Where it previously required several clicks to find the latest product news and announcements on the Google Maps API blog, for example, the newly redesigned homepage now surfaces this information at a glance. The new homepage will be updated regularly with our latest product news, coding tips, developer profiles, videos, and cool examples. See the screenshot below for an example or visit Google Code now for the latest updates.


Be sure to subscribe to our new aggregate Google Code: News Feed in your favorite feed reader to receive all the Google developer updates as they happen.

And please tell us what you think about the new homepage.

By Mike Marchak, Google Code Team2013, By: Seo Master

Seo Master present to you: Google Summer of Code™ is a global program that offers student developers stipends to write code for various open source software projects. We have worked with several open source, free software, and technology-related groups to identify and fund several projects over a three month period. Since its inception in 2005, the program has brought together nearly 2500 successful student participants and 2500 mentors from 98 countries worldwide, all for the love of code. Stephanie Liu of the Developer Programs team sat down with Leslie to understand the history of the program, hear some of the many success stories and find out what's new for SoC 2009.




Leslie Hawthorn is a Program Manager for Google's Open Source Programs Office, where she's the Community Manager for Google Summer of Code. She serves on the Advisory Board of the GNOME Foundation and the Open Source Business Resource, as well as the Steering Committee for the Humanitarian FOSS Project. Her personal website is http://www.hawthornlandings.org.

This is the third episode in the "Code Conversations" video series on YouTube and Google Code. You can view the entire series at this link: http://www.youtube.com/view_play_list?p=633DD2FE10E46955

By Neel Kshetramade, Google Developer Programs2013, By: Seo Master

Seo Master present to you: At Google Checkout, we're constantly striving to improve our usability. That's why we've recently simplified and improved the installation and configuration process for the osCommerce Google Checkout module. osCommerce is a popular open-source e-commerce solution and the module is an open-source project hosted on code.google.com.

We've completely reworked the installation process by no longer requiring users to manually copy and paste large swaths of PHP code into their files. Instead, we've created an automated deployment app (shown below) that does this for you. This should ease concerns about lines of PHP getting copied into the wrong place. If you want to learn more about the installation process, you can take a look at our documentation, which contains a step-by-step walkthrough with screenshots showing exactly how it works.


For more details, check out our post on the Checkout blog. We're excited about the improvements to the osCommerce Checkout module. If you're using osCommerce, we invite you to give Checkout a try and share your feedback with us.

By Ed Davisson, Google Checkout Team2013, By: Seo Master

Seo Master present to you: How time flies! It was about five years ago that we launched Google Code to the world. When we launched Google Code, we wanted to make code.google.com a great resource where developers could learn about our vision for open source and the open web. We started in 2005 with a handful of our own open source projects, links to just eight APIs and an announcement of the first ever Google Summer of Code, our now-annual program that introduces university students to open source development. By 2006 our API list had grown to 21, in 2007 there were 37, and today our collection of more than 60 APIs receive over four billion hits per day. Check out the changing face of Google Code below -- from 2005, 2007 to the present.



With the meaning of open in mind, Google Code set out to foster best practices in developer documentation, build a community around web and open source development and demonstrate the power of Google technologies. Over the past five years code.google.com has come a long way from eight APIs, maturing into a destination for developers to explore our growing family of APIs and developer products, whether they speed up the web, alleviate cross-browser issues, make hosting web applications easy and scalable or make the web a more social place.

Google Code has also become an interactive place to share ideas. Not only can developers prototype their work in a Code Playground, they can also use Project Hosting on Google Code, a fast, reliable and easy way for developers to host all kinds of open source projects. Today, there are more than 240,000 projects registered, with commits coming in at about 17,000 per day...about 1 every 5 seconds. We also host 800 open source projects of our own, including four projects (Android, Chrome, Chrome OS and GWT) with over a million lines of code each.

It’s been an amazing five years, but there’s still a lot of work ahead. We’re dedicated to helping the developer and open source communities thrive in as many ways as we can. To celebrate our birthday and thank everyone for supporting code.google.com over the years we’re rolling out a new, faster Subversion server, which will double the source code storage for Project Hosting on Google Code from 1GB to 2GB. Happy coding!

By Chris DiBona, Open Source Programs Manager 2013, By: Seo Master