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

Seo Master present to you: By Mike Pinkerton, Software Engineer

For about two years now, people have been writing gadgets for Google Desktop on
Windows and for iGoogle on the web. Today, with the announcement of Google
Gadgets for Mac OS X, Google Desktop users on the Mac can now run the same
Windows and web-based gadgets in Apple's Dashboard with zero (or very few)
changes. Check it out for yourself.

Google Gadgets for the Mac uses WebKit's JavaScript engine inside Dashboard, so
the majority of gadgets just work if they're written properly. The rest can be
fixed by following a few guidelines:

• Use JavaScript, not JScript
• WebKit is case-sensitive, JScript is not, which can lead to problems if you assume can you do things like interchange SetTimeOut() and setTimeout().
• Avoid JScript-only features like collections and ActiveX.
• Avoid IE-specific DOM extensions, just as if you were writing a multi-browser web application.
• Avoid Windows-specific APIs
• You shouldn't assume ActiveX or certain DLLs are available. Neither WebKit nor Mac OS X supports ActiveX, so these gadgets must be rewritten.
• Avoid Windows-only APIs such as Google Talk. These APIs are not (yet) available on Mac OS X.
• Understand how Dashboard is different
• The Dashboard environment is very different from a web page or the Desktop sidebar on Windows in that it comes and goes as the user activates it. Don't rely on your gadget always being visible. Your gadget won't run or update when Dashboard isn't in the foreground.
• Don't rely on access to the file system. The security model for Dashboard doesn't allow arbitrary file access to the hard disk, although your gadget does have access to files in its own archive. Things like file pickers won't work. Note that while restricted file system access is a departure from how gadgets work on Windows, it's consistent with Dashboard's security model and the behavior of other widgets developed for Mac OS X.

For more details, see Writing a Cross-Platform Gadget, part of the Desktop Gadget API documentation.

If you're interested in developing your own gadget, visit the Gadgets API homepage. If you're already a gadget developer, download the beta today to test your gadget and ensure that it works correctly.2013, By: Seo Master

Seo Master present to you: Google Tidak Mementingkan Frekuensi Update Posting - Pada artikel ini saya  akan membahas sedikit pengertian yang saya dapatkan dari blogjuragan tentang “google tidak mementingkan frekuensi update artikel”memang cukup akurat pernyataan itu apalagi didukung dengan beberapa sumber yang cukup terpercaya.
2013, By: Seo Master

Seo Master present to you: By Artem Livshits, CEO of OblakSoft

This guest post was written by Artem Livshits, CEO of OblakSoft, which makes the ClouSE MySQL storage engine for cloud development. In this post, Artem describes his experience using Google Cloud Storage to store and serve a WordPress blog.


WordPress is popular blogging software used by over 60 million people. If you have a WordPress blog, you want to ensure that your server load is manageable and that your load times are fast. You also want your data to be protected in case your server fails. With that in mind, we at OblakSoft created the Cloud Storage Engine for MySQL (ClouSE). It stores all your WordPress data on Google Cloud Storage, taking the load off your server to improve reliability and speed, and to reduce hosting costs.

We’ve been very impressed with the performance of Google Cloud Storage. Because it’s built on Google’s infrastructure, storage objects are cached within Google’s global network and distributed globally without the need for a Content Distribution Network (CDN). This ensures content is delivered with the best possible performance.

Here is a high-level architectural diagram of a WordPress-powered website that uses Google Cloud Storage to store and serve content:


The website’s content management is done through WordPress, which uses a MySQL server to store the website’s data. It uses the WP2Cloud WordPress plugin we created to upload pictures (and other media files) to Google Cloud Storage. ClouSE makes the web server stateless by storing all data in Google Cloud Storage using the Google Cloud Storage API. Web pages (lightweight HTML) are served by WordPress, while media files are served by Google Cloud Storage directly.

WordPress is one example of a MySQL-based application that can take full advantage of Google Cloud Storage to:

• Keep the data highly available and highly durable.
• Serve media files in a highly scalable fashion.
• Distribute media files across the globe for fast access.

This solution works with any hosting provider, so our users can keep their current hosting arrangement, and move their data to Google Cloud Storage using WP2Cloud and ClouSE. Users who are limited preview customers of Google Compute Engine can get started immediately using a fully configured WordPress image that we created.

We’re very excited about the potential of the Google Cloud Platform to power dynamic web server applications. Launch your own WordPress site in the cloud today - it’s easy and there’s minimal setup. We found it easy to make ClouSe work with Google Cloud Storage, and you can see how you can integrate Google Cloud Storage into your app as well.


Artem Livshits is the Founder, CEO and software architect at OblakSoft, a company focusing on technologies that simplify adoption of cloud computing. Previously Artem led the development of several server products from inception to maturity during his 12 years at Microsoft, including the source control system managing most of the Microsoft code base.

Posted by Scott Knaster, Editor

2013, By: Seo Master