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

Seo Master present to you:


2013, By: Seo Master

Seo Master present to you: By Leslie Hawthorn, Open Source Team

Last weekend, Google hosted the first Joomla!Day to be held in New York City. We had around 80 users and developers join us to discuss everything from the GPL to cool new features added to the project's latest release candidate. We had a mix of scheduled talks and unconference-styl breakout sessions, plus a cool hacking lounge open throughout the day. We concluded with a review and collaborative feedback session on the Joomla! sites created by several of the conference attendees.




If you'd like to hear a bit more about the event and some of the co-conspirators who made our day a success, check out the wrap up post by Louis Landry, Joomla! Project Manager and one of their developers.

Many thanks to all of our guests for joining us and sharing their time and collective creativity!2013, By: Seo Master

Seo Master present to you: By Christian Stefansen, Native Client Team

Native Client (NaCl) enables you to write high-performance apps that run your C and C++ code in the browser. With the new Native Client add-in for Microsoft Visual Studio and the new Native Client debugger it just got a lot easier.

The Visual Studio add-in makes it easy to set up, build, run, and debug your app as a Pepper plug-in and as a Native Client module. If you are porting an existing application to Native Client, building as a Pepper plug-in is a convenient intermediate stage for development enabling you to gradually rewrite the app to use the Pepper APIs (video).


The Native Client debugger, affectionately called nacl-gdb, works on Windows, Mac, and Linux and is now available in the SDK. So whatever your development platform, you can now spend more time coding features and less time chasing bugs with printf.

Following the Native Client philosophy of being OS-independent and open source, nacl-gdb is based on... well... gdb! For those of you who are not excited by a text interface, the Visual Studio add-in makes interacting with the debugger easier. If you use a different development environment that can interact with gdb, you can point it to nacl-gdb and use the same commands plus some additional NaCl-specific commands.


Whether you’re an existing Native Client developer or thinking about using Native Client for your next project, now is a great time to grab the SDK, write an amazing app, and quickly squash any bugs you find. We look forward to questions on Stack Overflow and ideas and comments in the discussion forum.


Christian Stefansen is the Product Manager for Native Client and Pepper (PPAPI). When he is not busy planning new features for Native Client, he likes traveling and writing. He is currently writing a book about India.

Posted by Scott Knaster, Editor

2013, By: Seo Master

Seo Master present to you:
By Carol Smith, Google Code-in Program Manager, Open Source Team

Cross-posted from the Google Open Source Blog


Listen up, future coders of the world: today we’re launching the second annual Google Code-in competition, an open source development contest for 13-17 year old students around the world. The purpose of the Google Code-in competition is to give students everywhere an opportunity to explore the world of open source development. We not only run open source software throughout our business, we also value the way the open source model encourages people to work together on shared goals over the Internet.

Open source development involves much more than just computer programming, and the Google Code-in competition reflects that by having lots of different tasks to choose from. We organize the tasks into eight major categories:

1. Code: Writing or refactoring code
2. Documentation: Creating and editing documents
3. Outreach: Community management and outreach, as well as marketing
4. Quality Assurance: Testing and ensuring code is of high quality
5. Research: Studying a problem and recommending solutions
6. Training: Helping others learn more
7. Translation: Localization (adapting code to your region and language)
8. User interface: User experience research or user interface design and interaction

On November 9, we’ll announce the participating mentoring organizations. Mentoring organizations are open source software organizations chosen from a pool of applicants who have participated in our Google Summer of Code program in the past. Last year we had 20 organizations participate.

Last year’s competition drew 361 participating students from 48 countries, who worked for two months on a wide variety of brain-teasing tasks ranging from coding to video editing, all in support of open source software. In January, we announced the 14 grand prize winners, who we flew to our headquarters in Mountain View, California to enjoy a day talking to Google engineers and learning what it’s like to work at Google, and another day enjoying the northern California sights and sun.

Visit the Frequently Asked Questions page on the Google Code-in site for more details on how to sign up and participate. Our goal this year is to have even more pre-university students in the contest than last time around, so help us spread the word, too.

Stay tuned to the contest site and subscribe to our mailing list for more updates on the contest. The Google Code-in contest starts on November 21, 2011, and we look forward to seeing the clever and creative ways all of the participants tackle their open source challenges.


Carol Smith is Google Code-in Program Manager, Open Source Team

Posted by Scott Knaster, Editor

2013, By: Seo Master

Seo Master present to you:
By Monica Tran, Developer Marketing Team

UPDATE 11/28/11: We have moved the dates of Google I/O 2012 so that we can extend the conference to three days. The new dates are June 27-29, 2012. For full details, please see the announcement post.


This year’s Google I/O saw 1 million developers join us from around the world at Moscone Center, via I/O Live, and at our I/O Extended viewing parties. As we prepare to round the corner into 2012, mark your calendars: Google I/O 2012 will be returning to Moscone Center West in San Francisco on April 24-25 (UPDATE: now June 27-29).

Registration details will be coming soon, but for a preview of what’s to come, check out videos from last year’s event, as well as photos from our Google Developer Day events, currently taking place in eight cities around the world. Keep following us here on the Google Code Blog for the latest.

In the past four years, Monica Tran has been around the world, working as a Product Marketing Manager in Mountain View, London, and Tokyo. After a good run on Google I/O, Monica is back to lead the charge on Google Developer Day, happening in 8 cities worldwide in 2011.

Posted by Scott Knaster, Editor

2013, By: Seo Master

Seo Master present to you:

 

• Remove everything unnecessary:
  This tip may sound dumb, but please look at your website once again: do you really need this background sound (most people find them annoying anyways). Is that huge GIF animation with jumping bunny really that cool ? And do you really need this crappy JavaScript code for the flying clock ? Remember, all this stuff needs time and bandwidth to be loaded with every page view and don't forget the most important thing: People are visiting your website to get information - just give them what they want!
  
• Avoid nested tables:
  Don't place tables inside another table - the browsers need much longer to parse this.
  
• Use CSS where possible:
  
  By using a linked Cascading Style Sheet, which is basically just a set of instructions of how to represent elements your source code will be a lot lighter, therefore load faster. For example, you could replace this code:
  
  <div align="right"><font face="Arial, Verdana, Sans Serif" color="#008000" size="3"><b>Here is some text</b></font></div>
  
  to something like this:
  
  <div class="style1">Here is some text</div>
  
  See the difference? There are many good internet sources where you can learn some CSS basics. Invest some time in it - it's worth it!
  
• Optimize your images:
  Images are the most heavy part of many websites. Try to reduce the amount of images as much as you can. Remove all the fancy GIF animations and replace them with static images.
  
  Always define the width and height of an image by setting the image tag attributes. That way, the browser will already know how the things will look like and will load the rest of the page. Otherwise, it loads the image first and then the rest of the page.
  
  Consider using smaller clickable thumbnails instead of big images where possible.
  
  Reduce the filesize of your images - there are a lot of free tools out there. For example, GIFCruncher for GIFs and JPEG Wizard for JPEGs.
  
  Use GIFs instead of JPEGs. JPEGS are only good for fine images like photos, for all other web graphics GIF is usually a better choice.
  
• Clean up your code :
  Many WYSIWYG HTML editors leave a lot of unnecessary code like empty tags (like <font> </font>) and comments in your source code. remove them with a simple text editor for a faster website loading.
  
• Remove whitespaces:
  Every unnecessary space between your tags and new line characters are increasing your page size. You can remove them easily with our free HTML Optimizer
  

 

2013, By: Seo Master

Seo Master present to you: Sudah lama tidak posting dimari, mau ngasi info saja salah satu Seo Tool yang lumayan bermanfaat buat optimasi google. Seo Link Robot.
ini fitur-fiturnya:
2013, By: Seo Master

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