In Object-Oriented languages an interface defines a set of methods which a Class must include in order to implement the interface (otherwise, if the Class is missing the required methods, the code will fail and the interface will throw an error).

Interfaces are useful for making sure developers use the correct implementation of an API.

In JavaScript there are no true ‘classic’ Object-Oriented features, but through clever usage of the language you can emulate an Interface for use with a JavaScript API.

First thing you want to do is include the following JavaScript file (Interface.js) into your HTML:

Winter is typically flu season, and talk around the water cooler in 2009 has turned to the H1N1 virus, the so-called “swine flu.”

<!-- This is a HTML comment, it will not display in any page. Feel free to remove this comment if it cause any inconvenient to you.
Thanks for using digg digg, please visit http://www.mkyong.com/blog/digg-digg-wordpress-plugin for any comments and ideas,

Author : Yong Mook Kim
Website : http://www.mkyong.com
-->

I am going to keep this post simple. The past couple of days I have been writing intently on some ideas about mental well-being and human relationships. It is a short ebook – no more than 10 pages – but I think whoever reads it and tries to apply these ideas will find positive change in their lives.

Overview

Like most people, I have a large number of personal documents in a variety of formats (PDF, Excel, Word, RTF, PowerPoint, etc.). For the typical user, organizing these documents in a ‘My Documents’ folder and having MS Office/Open Office/Adobe Acrobat installed simply gets the job done. However, I’ve been looking for some sort of “Web 2.0″ solution to view my documents while I’m on the go. And, since my knowledge manager is web-based, I’d like a way to browse and embed personal documents directly in my wiki without needing any special software.

I’ve been impressed with services like Scribd (think YouTube for Documents). Most people have probably already used Scribd, but in case you haven’t, this service allows you to upload your documents (variety of formats supported) and view them online in Flash format. The beauty of this service is that you can also share documents and embed directly inside you website/blog/wiki. While this works great for sharing certain types of documents, it’s not really appropriate for uploading my entire collection of documents (especially since many contain personal information). So, I decided to figure out how to create my own hosted document/book viewer like Scribd or Google Books.

Example

The science of cognitive enhancement is evolving, which means the business of cognitive enhancement is evolving.

If you’re new to AJAX you may be wondering how you can pull in just a single element from another HTML page (as calling an HTML page with AJAX pulls the entire HTML content in as a String).

It has also been explained to me that the particular solution I’m going to discuss here is the same technique used by the jQuery library.

I’m not going to run through how to actually write an AJAX method as that is outside the scope of this post, so feel free to use your own home baked JavaScript code, or use any one of the numerous JavaScript libraries as they all include their own variation of a cross-browser AJAX call.

With most AJAX scripts you’ll also specify a callback function which will run once the requested data has been retrieved. In my case this looks something like this…

$.Remote.load({
	url: "Test.html",
	callback: function(response)
	{
		// Do something with the response object
	}
});

Once my AJAX function has successfully retrieved the data, it runs the callback function which then processes the data and grabs the element we’re interested in.

Within the callback function we first need to create a new element and then set the elements innerHTML to the response data (which is returned as a String).

We then grab all the elements we’re interested in (for this example I’m specifically looking for a DIV element that has an ID value of “content”) and loop through them until we find the relevant node…

<!-- This is a HTML comment, it will not display in any page. Feel free to remove this comment if it cause any inconvenient to you.
Thanks for using digg digg, please visit http://www.mkyong.com/blog/digg-digg-wordpress-plugin for any comments and ideas,

Author : Yong Mook Kim
Website : http://www.mkyong.com
-->

There is karma to everything that we say. This means that our words have consequences. They can bring inspiration and joy to others but they can also bring sadness and pain.

Created page with ''''Essay: Mapping Commercial Web 2.0 Worlds: Towards a New Critical Ontogenesis. By Ganaele Langlois, Fenwick McKelvey, Greg Elmer, and Kenneth Werbin. Fibreculture Journal, Issu...'

New page

Lebbeus Woods. Terrain 2.

A little know, but incredibly influential and constricting aspect of the Internet (or any networked body of sufficient size), is the protocols used to transport information between nodes of the network. The protocols most people are familiar with are http and html (directly influencing css, javascript, etc). These two protocols completely determine what your experience on the web is like. In other words, if you're looking at a website, it is strictly conforming to http/html. The protocol of http/html, based around a grandmother's recipe catalog, is what forces 95% of the internet into looking like the world's largest magazine collection.

Presumably we all see deficiencies in this protocol and believe that a Polytopian system is the solution. But, what, exactly, are the problems with the existing state of internet protocols? So far I have identified several deficiencies:

• Lack of social presence on a "site". If 3000 people are all looking at a website at the same time, you are not aware of any of them.
• A lack of perspective on the people using the Internet. If I want to see where clusters of people are, I am unable. If a crowd forms around an idea, if they're all listening to a particular feed of data, I am unaware.