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

Peluang bisnis online dewasa ini memang banyak sekali di jumpai di internet, namun jika ingin serius berbisnis online tentu anda harus mencari bisnis yang ada modalnya meski sedikit. Bisa saja kita berhasil di bisnis online dengan tanpa modal alias gratis, tapi saya yakin tidak akan maju bisnis anda.

Seperti halnya toyota yang sejak tahun 2010 selalu mengadakan kontes seo terakhir tahun 2012

Seo Master present to you: Software ini pasti sangat berguna bagi pakar IT, software ini bisa Mendiagnosis masalah komputer kalian dan kemudian bisa memperbaikinya!
Maaf sebelumnya saya hanya punya yang Litenya saja jadi kalo kamu pengen FullVersi update ajah langsung Gratis kok, udah langsung tertera disitu updatennya!

Berikut Fitur Fitur yang ada di Driver SoudPack 12.3 :

~Cek Spesifikasi PC (Komputer) dengan lengkap
~Test Memori (RAM)
~Cleanup (registri dll)
~Cek antivirus apakah berjalan dengan lancar
~Add Remove Program Secara Cepat
~Refresh Windos agar stabil
~Device Manager
~Defrag
~Dan lain lain

• Download Driver SoudPack 12.3 Lite (7MB) 

Oke sampai sini dulu, nanti lain waktu saya ngasih software gratis lagi..
Kalo mau request silahkan komntar!! Happy Blogging!


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: By Andy Chu, Google Code Team

We get a lot of feedback on Google Code and one of the biggest requests have been for feeds (as you can see in issue 8, issue 131, or issue 190). Therefore, I'm happy to announce that we now have Atom feed available for you to track issues, downloads, Subversion changes, and Wiki updates.

As an example, you can take a look at feeds for Google Web Toolkit:

• Issues feed at http://code.google.com/feeds/p/google-web-toolkit/issueupdates/basic
• Downloads feed at http://code.google.com/feeds/p/google-web-toolkit/downloads/basic
• Subversion changes feed at http://code.google.com/feeds/p/google-web-toolkit/svnchanges/basic
• Wiki changes feed at http://code.google.com/feeds/p/google-web-toolkit/svnchanges/basic?path=/wiki/

For the SVN changes feed you can add '?path=/path/' to the end of the url to filter the changes by path -- for example, '?path=/trunk/' or '?path=/wiki/'. Simply substitute 'google-web-toolkit' for your project to see your feeds.

As always, if you have any feedback please do not hesitate to let us know.

2013, By: Seo Master

Seo Master present to you: On April 7th, Google launched a new version of Gmail for mobile for iPhone and Android-powered devices. We shared the behind-the-scenes story through this blog and decided to share more of what we've learned in a brief series of follow-up blog posts. This week I'll talk about autogrowing textareas for entering large amounts of text.

When composing a long message in a web app, regardless of whether it's on a desktop or a mobile device, you really want to see as much of your draft as possible and make use of all the available screen space.
In today's blog post, I'll share a JavaScript solution for textareas that automatically grow (vertically) to the size of the content. They make composing long messages much easier and, for all those iPhone users out there, takes away the need to scroll with the dreaded magnifying glass! We're working on getting this into Gmail for mobile but here it is now as a teaser of things to come.





Measuring the height of the content

The first step is to detect when the content has changed. Some solutions on the net recommend using a timer (see our previous post to find out more about timers) to check if content has changed. However, that approach is not ideal on a mobile device, where both battery life and processor power are limited.

Instead, we will listen for key-up events from the browser. This guarantees that we only measure the textarea when the content has actually changed.

<textarea id="growingTextarea" onkeyup="grow();"></textarea>

The second step is to actually measure the height of the content. There are solutions on the net that recommend keeping a copy of the content in a div and measuring the div to get the height; however, due to memory and processor limitations on a mobile device, those solutions don't scale well when the content gets large (and it's also hard to replicate textarea line wrapping behavior exactly in a div).

Therefore we will make use of the scrollHeight and clientHeight properties. For our purposes, scrollHeight is the height of all the content while clientHeight is the height of the content that's visible in the textarea (for more precise definitions, see scrollHeight and clientHeight)

function grow() {
  var textarea = document.getElementById('growingTextarea');
  var newHeight = textarea.scrollHeight;
  var currentHeight = textarea.clientHeight;
…
}

One limitation of using scrollHeight and clientHeight is that we aren't able to shrink the textarea when content is deleted. When all the content of a textarea is visible, the scrollHeight is equal to the clientHeight. Therefore we aren't able to detect that our textarea is actually larger than the minimum size required to fit all the content (please do leave a comment if you think of a solution that doesn't require re-rendering the page).

Growing the textarea

To grow the text area, we modify the height CSS property:

if (newHeight > currentHeight) {
  textarea.style.height = newHeight + 5 * TEXTAREA_LINE_HEIGHT + 'px';
}

Notice how we only change the height if newHeight > currentHeight. Depending on the browser, changing the height (even if it's to the same value) will cause the page to re-render. On a mobile device, we want to try our best to minimize the number of operations.

Also, we grow the textarea by five lines every time we grow. From a UI perspective, this reduces the amount of jitter when composing a message but, from a performance perspective, this reduces the number of times we need to re-render the page.

(Quick note for developers implementing this for a browser with scrollbars: you might want to modify the CSS overflow property to preventing the scrollbar from appearing and disappearing as you grow your textarea)

The complete solution

Growing textareas are easy to implement and they make composing long messages infinitely more usable. So go out there add it to all your web apps!

<script>
// Value of the line-height CSS property for the textarea.
var TEXTAREA_LINE_HEIGHT = 13;

function grow() {
  var textarea = document.getElementById('growingTextarea');
  var newHeight = textarea.scrollHeight;
  var currentHeight = textarea.clientHeight;

  if (newHeight > currentHeight) {
     textarea.style.height = newHeight + 5 * TEXTAREA_LINE_HEIGHT + 'px';
  }
}
</script>
<textarea id="growingTextarea"
          onkeyup="grow();">
</textarea>

Using timers effectively

By Casey Ho, Software Engineer, Google Mobile2013, By: Seo Master