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

Seo Master present to you: By Chris DiBona, Open Source Team

When we first launched code.google.com (webarchive), it was largely a site for documenting our open source activities and had some details about Google's supported APIs and file formats. In the ensuing 3 years, code has grown to encompass protocol documentation, project hosting and even a mobile operating system. Similarly, the activities of the Open Source Team have grown from simple license compliance to the aforementioned hosting, releasing massive amounts of code and introducing student programs like the Summer of Code and its high school cousin, the Highly Open Participation Contest. Since we've grown so much, we felt it was well past time to spin off a blog that specifically covers the open source activities of the company. So that's just what we've done. Come check it out, and if you like, subscribe!2013, By: Seo Master

Seo Master present to you: By Ali Pasha & Jacob Moon, Google Code

As the number of developers and projects have grown on Google Code, we've started thinking about how to get projects to learn from and work with each other. Today, we're happy to announce that we have made a few steps towards that goal.

First, we've added user update streams to make it easy to see what a particular user has been doing across Project hosting on Google Code. As an example, take a look at Ben Collins-Sussman's activities on his profile page. Ben works on Google Code, but it's obvious that he has other interests as well.

In addition, tracking open source projects and other developers is as easy as starring a project or a developer profile. Starring a project or developer adds a link in your new "Starred Projects" and "Starred Developers" section of your profile page, making it really easy to find those projects or developers again. Starred projects are also added to the new "My projects" drop-down, which makes it easy to navigate to a project from anywhere on the site.

Once a project or a developer is starred, all updates from starred projects and developers can be tracked by looking at your personalized updates.
For those that prefer to use their feed reader, use the following new feeds:

• Updates for a user - http://code.google.com/feeds/u/{username}/updates/user/basic
• Developers a user is tracking - http://code.google.com/feeds/u/{username}/updates/projects/basic
• Projects a user is tracking - http://code.google.com/feeds/u/{username}/updates/developers/basic

As always, we look forward to your feedback.2013, By: Seo Master

Seo Master present to you: By Ben Collins-Sussman, Google Code Project Hosting

We're pleased to announce that the Subversion component of Google Code Project Hosting has been upgraded to version 1.5. What does this mean to users? If you're using a Subversion 1.5 client, you can now take advantage of Subversion's improved "merge tracking" feature to manage branches.

Prior to Subversion 1.5, branching wasn't very friendly to users. A developer had to manually keep track of the revision from which a branch was copied. She also had to keep track of exactly which changes had been merged into a branch already (to avoid repeated application of changesets), and to always specify the exact range of revisions to merge next. Merging a branch back to trunk was even more difficult, since it required comparing two precise URLs in a very specific way.

With improved merge-tracking, users never have to type a single revision number. Here's a basic example of branch workflow.

1. Make a branch for your experimental work:
   $ cd trunk-working-copy
$ svn cp trunkURL branchURL
$ svn switch branchURL



2. Work on the branch for a while:
   # ...edit files
$ svn commit
# ...edit files
$ svn commit



3. Sync your branch with the trunk, so it doesn’t fall behind:
   $ svn merge trunkURL
--- Merging r3452 through r3580 into '.':
U button.c
U integer.c
...
$ svn commit



4. Repeat the prior two steps until you’re done coding.


5. Merge your branch back into the trunk:
   $ svn switch trunkURL
$ svn merge --reintegrate branchURL
--- Merging differences between repository URLs into '.':
U button.c
U integer.c
...
$ svn commit

For a more detailed discussion of merge-tracking (and its limitations), see chapter 4 of the online Subversion Book. Live in fear of branches no more!2013, By: Seo Master

Seo Master present to you: By Ben Lisbakken, Developer Programs Engineer

For me, documentation isn't always enough to learn about APIs; I need examples that I can play with. That's why I started a fun project recently--a tool for teaching developers how to use Google's JavaScript APIs: the AJAX API Playground. I have been working on this in my 20% time and today I am proud to announce that we are launching the AJAX API Playground as the official way that Google will show JavaScript samples!

The AJAX API Playground is currently loaded with over 170 samples for 8 Google JavaScript APIs (Maps, Search, Feeds, Calendar, Visualization, Language, Blogger, Libraries and Earth) that you can edit and run to help you explore what Google's APIs have to offer. There are also save and export features. The save feature allows you to hold onto an edited sample so you can continue working on it later, while export lets you modify a sample and publish the code to a permanent url.

As the AJAX API Playground is built on App Engine, you can create your own App Engine instance to show off your code samples. The code is open sourced under an Apache 2.0 license and uses several open source libraries and tools, including jQuery, jQuery UI, YUI Compressor, and CodeMirror. You can find the code on Google Project Hosting and learn about adding samples on the project wiki.

Stay tuned for more samples for more APIs. Enjoy!2013, By: Seo Master