Pelatihan / Inhouse training project management methodologies with ms project bersama staff dari PT Denki Engineering berlokasi di ruko sentral niaga bekasi, 24-25 jan 2015
Terima kasih atas undangan dan peran sertanya, semoga bermanfaat
Hery Purnama
Freelance Certified Trainer
081.223344.506
Http://good.web.id
Http://freelance-it-trainer.blogspot.com
Bandung
Training mobile Application Development for android bersama staff bank BJB bandung
Terima kasih atas undangan dan Semoga bermanfaat
Hery Purnama
Freelance Certified Trainer
081.223344.506
Pelatihan / Inhouse training project management methodologies with ms project bersama staff dari PT Denki Engineering berlokasi di ruko sentral niaga bekasi, 24-25 jan 2015
Terima kasih atas undangan dan peran sertanya, semoga bermanfaat
Hery Purnama
Freelance Certified Trainer
081.223344.506
Http://good.web.id
Http://freelance-it-trainer.blogspot.com
Bandung
Training mobile Application Development for android bersama staff bank BJB bandung
Terima kasih atas undangan dan Semoga bermanfaat
Hery Purnama
Freelance Certified Trainer
081.223344.506
Training mobile Application Development for android bersama staff bank BJB bandung
Terima kasih atas undangan dan Semoga bermanfaat
Hery Purnama
Freelance Certified Trainer
081.223344.506
Pelatihan / Inhouse training project management methodologies with ms project bersama staff dari PT Denki Engineering berlokasi di ruko sentral niaga bekasi, 24-25 jan 2015
Terima kasih atas undangan dan peran sertanya, semoga bermanfaat
Hery Purnama
Freelance Certified Trainer
081.223344.506
Http://good.web.id
Http://freelance-it-trainer.blogspot.com
Bandung
Setelah heboh foto mesra palsu abraham samad ketua kpk dengan wanita coba diungkit reskrim, kini giliran bambang wakil ketua kpk ditangkap dengan mengungkit ungkit kasus lama, apa peran presiden jokowi ? tidak ada, tidak berperan layaknya negarawan dan presiden.
Selamatkan kpk
Hery Purnama 081.223344.506 - Freelance Certified IT Trainer , Excel VBA , Android Phonegap, Google Map API, Google Sketchup3D , MS Project, ExtJS, Oracle, SQL Server, MySQL, MS. Access VBA, Facebook API Developer dll.. Berpengalaman 15 Tahun sebagai Trainer bersertifikasi CIW, OCA, ITILF, MCP, MOS , Visit : http://freelance-it-trainer.blogspot.com/2014/12/freelance-certified-it-trainer-bandung.html
Hery 081.223344.506 - Freelance Certified IT Trainer , Excel VBA , Android Phonegap, Google Map API, Google Sketchup3D , MS Project, ExtJS, Oracle, SQL Server, MySQL, MS. Access VBA, Facebook API Developer dll.. Berpengalaman 15 Tahun sebagai Trainer bersertifikasi CIW, OCA, ITILF, MCP, MOS , Visit : http://freelance-it-trainer.blogspot.com/2014/12/freelance-certified-it-trainer-bandung.html
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
2 Hari , Start : on demand |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
2 Hari , Start : 8 Jan , 12 Feb , 19 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
4 Hari , Start : 12,19 Jan, 9,16 Feb , 7,21 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
3 Hari , Start : 5,19 Jan, 9,23 Feb , 2,16 Mar 2015 |
Requoted by
Hery Purnama
http://freelance-it-trainer.blogspot.com , http://good.web.id
081.223344.506
Misalkan kita punya blog dengan alamat blogkita.blogspot.com dan kita ingin merubahnya ke alamat milik kita sendiri yang telah kita beli misalkan www.namadomain.xyz
Bagaimana cara settingnya?
Caranya Mudah, anda dapat melakukan setting blogspot dengan cara :
1. Pastikan anda telah memesan Free Domain Parking (Gratis) atau domain berbayar Anda
2. Setelah Free Domain Parking aktif , selanjutnya login blogger , lalu masuk ke menu "Setting"
3. Tambahkan domain dengan mengklick + Add a custom domain, isikan nama domain, saat anda klik "save", blogger akan meminta verifikasi CNAME
4. 2 kode Cname akan muncul yaitu www dengan address ghs.google.com dan satu lagi berupa kode acak dari google ( kode berbeda setiap orang)
5. Login ke Cpanel di tab baru dan masuk ke menu Advanced DNS editor
Advance DNS Zone Editor
Note: Nameserver domain anda harus sudah mengarah ke hosting dimana anda melakukan setting Cpanel diatas. hubungi pihak penyedia domain anda untuk request pengarahan nameserve
Whenever you create a new website or blog for your business, the first thing you probably want to happen is have people find it. And, of course, one of the ways you hope they will find it is through search. But typically, you have to wait around for the Googlebot to crawl your website and add it (or your newest content) to the Google index.
So the question is: how do you ensure this happens as quickly as possible? Here are the basics of how website content is crawled and indexed, plus some great ways to get the Googlebot to your website or blog to index your content sooner rather than later.
Before we get started on some good tips to attract the Googlebot to your site, let's start with what the Googlebot is, plus the difference between indexing and crawling.
So how does the Googlebot find new content on the web such as new websites, blogs, pages, etc.? It starts with web pages captured during previous crawl processes and adds in sitemap data provided by webmasters. As it browses web pages previously crawled, it will detect links upon those pages to add to the list of pages to be crawled. If you want more details, you can read about them in Webmaster Tools Help.
Hence, new content on the web is discovered through sitemaps and links. Now we'll take a look at how to get sitemaps on your website and links to it that will help the Googlebot discover new websites, blogs, and content.
So how can you get your new website discovered by the Googlebot? Here are some great ways. The best part is that some of the following will help you get referral traffic to your new website too!
So what if your new website is a blog? Then in additional to all of the above options, you can also do the following to help get it found by Google.
Once your website or blog is indexed, you'll start to see more traffic from Google search. Plus, getting your new content discovered will happen faster if you have set up sitemaps or have a RSS feed. The best way to ensure that your new content is discovered quickly is simply by sharing it on social media networks through status updates, especially on Google+.
Also remember that blog content is generally crawled and indexed much faster than regular pages on a static website, so consider having a blog that supports your website. For example, if you have a new product page, write a blog post about it and link to the product page in your blog post. This will help the product page get found much faster by the Googlebot!
Requoted by
Hery Purnama
You can export a copy of your blog to your computer and import the posts and comments into a different Blogger blog.
Your blog will be saved as a .xml file. Don't worry, the blog is still in your dashboard and on Blogger.com.
Here's how to import the blog you exported into a new blog:
By default, all of your imported posts will remain unpublished until you publish them from your dashboard later. However, if you would rather have all posts published immediately, make sure to check the box next to Automatically publish all imported posts before you click Import Blog.
Requoted by
When loading data from a remote source I'd use jQuery or Zepto's ajax() function like this:
1 | $.ajax({ |
2 | url: 'http://your-app.com/api/news/12', |
3 | dataType: 'JSONp', |
4 | success: function(data, status) { |
5 | $.each(data, function(key, value){ |
6 | //handle the data |
7 | }); |
8 | }, |
9 | error: function() { |
10 | //handle the error |
11 | } |
12 | } |
In this example I'm accessing a fictional data source to load a news article.
Once the article is loaded the user might browse another article but later on may return to read this particular one again. You could load the article from your server again. But that's a bit inefficient if you have already loaded it before. You could just as easily store the article locally, using HTML5's localStorage, on the device and request the details from there. That's pretty simple to setup.
HTML5 introduced several methods of storing data within the clients browser. Two of these methods are local and session storage. localStorage saves data until it is removed by the client or app whereas sessionStorage saves data until the session ends, when the browser window/tab is closed.
Mark Pilgrim sums up HTML5 local storage as:
a way for web pages to store named key/value pairs locally, within the client web browser. Like cookies, this data persists even after you navigate away from the web site, close your browser tab, exit your browser, or what have you. Unlike cookies, this data is never transmitted to the remote web server (unless you go out of your way to send it manually).
Dive into HTML – Introducing HTML5 local storage
Storing a key/value pair is very straightforward:
1 | localStorage.setItem('yourKeyName', 'your value'); |
This works great for simple key/value pairs.
Attempting to store a JSON object, or an ordinary array of data, in local storage will yield an error. Local storage requires you to store strings of information. To store a JSON object in local storage you will need to convert it into a JSON-formatted string, using the JSON.stringify() function.
Referring back to the ajax example above, we could take the data object and stringify it:
1 | var dataToStore = JSON.stringify(data); |
Then it's just a case of storing the new JSON-formatted string in local storage:
1 | localStorage.setItem('someData', dataToStore); |
Now that the JSON object is stored locally you can access the data directly from the device, without having to make a request to the remote server. However, because the object was previously converted to a JSON-formatted string, you will have to reverse the effects of the stringify function before you can access the data within the object. This is easily done through use of the JSON.parse() function:
1 | var localData = JSON.parse(localStorage.getItem('someData')); |
Now you can access the object and handle it as you normally would:
1 | $.each(localData, function(key, value){ |
2 | console.log(key + ' = ' + value); |
3 | }); |
The above example will work in any modern browser as well as in your PhoneGap app, but PhoneGap also provides local storage access via its api:
1 | //setting an item |
2 | window.localStorage.setItem('key', 'value'); |
3 |
4 | //loading an item |
5 | var value = window.localStorage.getItem('key'); |
The only difference here being window. prepended to the ordinary localStorage methods.
Taking all of this into account you might end up with something like this:
1 | $.ajax({ |
2 | url: 'http://your-app.com/api/news/12', |
3 | dataType: 'JSONp', |
4 | success: function(data, status) { |
5 | $.each(data, function(key, value){ |
6 | //handle the data |
7 | }); |
8 | |
9 | var localData = JSON.stringify(data); |
10 | |
11 | window.localStorage.setItem('newsArticle12', localData); |
12 | }, |
13 | error: function() { |
14 | //handle the error |
15 | } |
16 | } |
And when you want to get access to that data the next time:
1 | var localData = JSON.parse(window.localStorage.getItem('newsArticle12'); |
2 |
3 | $.each(function(key, value){ |
4 | //handle the data |
5 | }); |
This is a useful technique to use in PhoneGap apps, it can be a significant optimisation when used appropriately. It reduces server requests and loads your [previously loaded] data faster.
There are some considerations with using local storage though.
There is a limit to how much data you can store via localStorage – approximately 5mb. If you are dealing with a lot of data you could soon reach that limit.
The main consideration should always evaluating the type of data that you are storing locally. Maybe sessionStorage is the better choice if your users require up to date information each time they open your app. Or maybe you need to include an expiry data in your JSON object and check against that before serving the data.
In my last article (Prepare a JSON Web Service and access it with JQuery), I had explained JSON, how to return JSON data from a Web Service, and how to use a JSON-enabled Web Service with JQuery. In this article, I will explain how JavaScript Object Notation with Padding (JSONP), an extended concept from JSON, can be used to solve cross domain issues.
AJAX is a key technology in web 2.0 that is being used widely in web sites. AJAX uses the XMLHttpRequest client side API for communicating with the server in the background. However, this approach doesn't allow cross domain communication due to security reasons. JavaScript Object Notation with Padding (JSONP) is a way to grab JSON data from external domains. It's a better and cleaner alternative to other approaches (web proxy and IFrame) to get data from an external domain.
Same-origin policy is a concept in browser-side programming languages (such as JavaScript) which allows accessing resources in the same site (same domain) but preventing accessing resources in different domains. To overcome the same origin policy, we have the two following popular options in our hand:
As XMLHttpRequest (in AJAX) doesn't allow cross domain calls, the common approach is to use a proxy Web Service to access third party data. Say your site is hosted in www.mydomain.com and you need to access data from a different domain called www.thirdpartydomain.com. With AJAX, you can't directly call a Web Service on www.thirdpartydomain.com, but you can write a Web Service in your domain which will get data from www.thirdpartydomain.com. The approach is shown in figure 1:
This approach works as the XMLHttpRequest calls the Web Service (i.e., the proxy Web Service) in my own domain and then the proxy Web Service calls the actual Web Service on the different domain. But though this is the easiest and widely used solution, it requires two Web Services calls, which is slower. Also, every call to the external Web Service requires going through my Web Service, which takes my server's valuable thread to process.
Using IFrame, we can easily fetch data from a third party site. IFrame is easy to use but difficult to manage as each IFrame is an independent element in a page and interactions between IFrames are difficult. Also, once the content in the IFrame is loaded, the content itself is subjected to the same same-origin policy.
Today's web applications are rich in both data and UI, complex from a technical point of view, and combine different sets of data from different sources. For example, you have a university site where students visit. Also, you have a Facebook group for this university and you want to show group activities in your university site. To get activities from Facebook, you need to access services on the Facebook site (a different domain) from you web page. And here comes the cross domain issue. You can access Facebook site services from your server side code without any cross-domain issue. But this will prevent the processing of the page from finishing until the Web Service call finishes. Instead of calling the Web Service from server side code, you can add a JavaScript block which call the Web Service from the client's browser and thus alleviate load on your server. In a Mashup application, we need to access data from different sources. In the computing world, Mashup is a web application that combines data or functionality from two or more external sources.
The same-origin policy doesn't allow a script loaded from one domain to manipulate properties of a document loaded from a different domain. The browser does so to isolate contents from different domains to protect from improper manipulation. However the same-origin policy doesn't prevent adding scripts dynamically in the page from a different domain as long as the script doesn't try to load document from a different domain. The JSONP is a combination of these facilities: "On-demand JavaScript", and "Same-origin's flexibility for adding JavaScript from different domains":
On-demand JavaScript: This allows adding JavaScript to the page after the page is loaded. The JavaScript can be added by calling a Web Service with AJAX/
XMLHttpRequest. So, due to this on-demand JavaScript facility, JavaScript can be added after the page is loaded. The script will be executed as soon as it will be added to the page. Details on on-demand JavaScript can be found here.
To explain how JSONP works, consider there's an external third party site www.thirdpartydomain.com and we have our site www.mydoman.com, and our site will call a third party site's Web Service to get data. Let's consider the following scenario to explain JSONP:
showThirdpartyData which takes an argument (of type JSON) and process this argument to show data on your site's web page. However, the data showThirdPartyData expects (dataArgument in the following code snippet) that ans argument will come from a Web Service on a different domain www.thirdpartydomain.com. The following code snippet shows the function signature:
<script type="text/javascript"> function showThirdPartyData(dataArgument) { //process data here } </script>showThirdPartyData('{ firstName: 'Sohel', lastName: 'Rana' }');So, by calling the Web Service on www.thirdpartydomain.com, we will generate JSON data as shown above. Calling the Web Service will generate JSON data which is actually a JavaScript function call. The function name (in which data will be packed) needs to be configurable. Say, we can pass the function name in the querystring in the Web Service call and the Web Service will pack data inside the function name. That's how Flickr API works and we'll see that later.
callWebService) on a button's OnClick event:function callWebService() { // Insert dynamic script var script = document.createElement('script'); script.src = 'http://www.thirdpartydomain.com/webservice/... '; // append the script in the document body. // As per on-deman script behaviour as soon as you add the script to // the document,the script will be execute and the web service will // be called. document.body.appendChild(script); } Here is the sequence of how JSONP will work:
callWebService method will add a script tag in the page and will set the source of the script tag to the URL of the third party Web Service.CallWebService method on some events, say on a button's click event. As soon as the callWebService method is called, the script from the third party site will be added in the page.showThirdPartyData will be called in the page.For JSONP to work, the Web Service from www.thirdpartydomain.com will support JSONP. To support JSONP, the Web Service must return JSON data in the format:
functionName('{JSONData}') Here the function name is a JavaScript function name. So when you call the Web Service from another site, the Web Service will generate JSON data which is actually a JavaScript function call. For example, to get the latest images tagged as 'cat' from Flickr, we can call the Web Service as: http://api.flickr.com/services/feeds/photos_public.gne?tags=cat&tagmode=any&format=json&jsoncallback=myFunctionName.
In the above URL, the querystring tags=cat tells the service to return images tagged with cat. Here, the important one is jsoncallback=myFunctionName. This tells the service that the return data will be packed in a function call named myFunctionName. If you hit the URL, you will get the JSON data as shown below:
So the above call to the Flickr API takes the function name in the querysting jsoncallback and we can pass the method name we are interested to use.
In the code provided along with this article, I have used the Flickr API to show recent images. Using JSONP, I have accessed data from flickr.com which is different from my domain. The Web Service URL is: http://api.flickr.com/services/feeds/photos_public.gne?tags=dog&tagmode=any&format=json&jsoncallback=showFilckrDataDog.
When you run the application provided along with this code, you will get two buttons in a web page. Clicking on a button will show the images tagged with cat, and clicking on another will show images tagged with dog. The two buttons invoke two different JavaScript functions: getFlickrDataWithDogTag and getFlickrDataWithCatTag. getFlickrDataWithDogTag uses the native JavaScript approach to add a script to the page. Whereas getFlickrDataWithCatTag uses JQuery to call the JSONP supported Web Service. The JQuery.getJSON method allows to load JSON data from a different domain. The format of the getJSON method is:
jQuery.getJSON(url, data, callback) url is the URL for the Web Service. data (which is JSON data to the Web Service) can be omitted if not needed. callback is the callback method which will be called once the JSON data will be returned from the Web Service. Remember when you call the Web Service with the getJSON method, the Web Service URL will be a bit different. The jsoncallback querystring needs to have a '?' value. The URL to be used in the getJSON method is shown below:
$.getJSON("http://api.flickr.com/services/feeds/photos_public.gne?" + "tags=cat&tagmode=any&format=json&jsoncallback=?", showFilckrDataCat); jQuery will automatically replace the '?' with the callback method (in the above URL, this is the showFlickrDataCat). And also, jQuery will add the script tag for you. So, when the Web Service call will return, jQuery will add the script tag which will invoke the JavaScript method in your page.