This means that the core of the widget is HTML and CSS code which contains the actual content of the widget, namely text, linked images/video or content pulled from a server of Web service. Alternatively, the widget content can be created using Flash, although this may limit its use on some mobile devices. The content is contained within an XML file that provides essential metadata about the widget, such as its name, version, language, etc. The third component of most widgets is JavaScript, which is used to provide the programming logic behind any interactivity in the widget. To make widgets run in different environments typically necessitates only changing elements of the metadata contained in the XML file. There are sites such as Wix.com or Sproutbuilder.com that provide tools for creating widgets through a simple drag and drop interface (Godwin-Jones, 2009).
A powerful feature of widgets is the ability to pull information from a server in order to continuously update data displayed to the user, or to have data pre-loaded to browser memory, so as to be available for quick display as needed. This kind of background server-client interaction is often described as AJAX (Asynchronous JavaScript and XML). There are many AJAX code libraries available, which make the tasks of creating widgets on Web pages using AJAX much easier. There is an effort underway, called OpenAjax Alliance, which aims to make it easier to mix and match components from different AJAX libraries. Another effort to achieve increased interoperability is OpenSocial, from Google. OpenSocial defines a set of APIs for social networking services to be accessed and run within different Web environments, including widgets.
One of the more popular tools for building social networks, Ning, has adopted the OpenSocial standard, as has iGoogle (Godwin-Jones, 2009). In addition, organization-wide information access, and the ongoing requirement to provide value for money, will increase the demand for tools to enhance collaboration and the sharing of information and knowledge. The effort to develop tools that support collaborative working across the workplace will become even more critical as professionals seek to foster, support and record collaborative innovation. The demand for Web 2.0 and beyond in the workplace-using tools such as SharePoint, blogs and aggregate tools such as Pageflakes to encourage collaboration-seems destined to continue (Hill, 2008).
Scope of Study
Rationale of Study
Overview of Study
This study used a five-chapter format to achieve the above-stated research objectives. To this end, chapter one was used to introduce the topics under consideration, provide a statement of the problem, the purpose and importance of the study, as well as its scope and rationale. Chapter two provides a critical review of the relevant and peer-reviewed literature, and chapter three presents the study's methodology, a description of the study approach, the data-gathering method and the database of study consulted. Chapter four is comprised of an analysis of the data developed during the research process and chapter five presents the study's conclusions, a summary of the research and salient recommendations.
Chapter 2: Review of Related Literature
1.
The idea of putting web-application as widgets right on the desktop was invented way back by Microsoft in 1994 (in Windows Nashville which was to be released in 1996). You could use an HTML and JavaScript page as you desktop background which would be running in the Internet Explorer. Microsoft even had a set of Active Desktop widgets. Java applets are dynamically downloaded Java code used to provide processing capability at the user's machine. Java applets make a thin client thick (see discussed of thin/thick clients below) (Proctor & Vu, 2005).
2.
One more technology that played a role in inventing desktop widgets is HTA (HTML application) which runs as a standalone application for that you were required to put you VBScript or JavaScript code and style in a single HTML file and rename it to .hta extension. The HTA is a thin client as opposed to a thick client application; the terms refer to a continuum of processing capability at the user's machine in a client-server environment. With a thin client application, there are few data and little processing capability at the user's machine; with a thick client application, data and computing capability are at, or transferred to, the user's machine. A pure HTML application would be an example of a thin client (Proctor & Vu, 2005, p. 496).
3.
Netvibes has developed its universal widget API (UWA)[6] which is a free and elegant widget framework that uses XHTML for its structure, CSS for styling and JavaScript/AJAX for Data Object Model control. UWA has support for all the major widgets platforms e.g. "Netvibes, iGoogle, Windows Vista, Mac OS X, iPhone."
Historically, a major type...
How will JavaScript Technology change my life The best benefit of all of learning JavaScript, its syntax, integration with XML and AJAX is the how marketable this skill is today. Being able to define which rich client is best for a given need is an essential skill going forward in any programming or technical career (Zeichick, 2008). JavaScript will hopefully give me an opportunity to earn more money over time. What are
Java vs. JavaScript Java was introduced by Sun Microsystems in 1995. The programming language designed for use in the distributed environment of the Internet (TechTarget). Although it was designed to have the "look and feel" of the C++ language, it offers greater ease of use and enforces an object-oriented programming model. Programmers can use Java to create complete applications that may run on a single computer or be distributed among servers
Asynchronous JAVA Script & XML (AJAX) Asynchronous JavaScript and XML (AJAX) are set of technologies with different function that work together to allow the client-server to create a rich web application (Deursen & Mesbah, 2009). The purpose of this paper is to describe more about AJAX, how is it used to create a web application, the difference from classical web application, companies utilizing this technique, security issues, and how to migrate
The report develops mathematical model and Excel is ideal spreadsheet to implement a mathematical model because it is developed to carry out a number of iteration. The report uses the spreadsheet to determine the time that the engine takes to reach 3000 rpm with continuous 100% fuel input. The Table 1 provides the layout of the spreadsheet, which reveals the time on the first row and the system variables on
DHTML dead? In the view of many pundits there seems to be little doubt that DHTML has seen its best days and is, in terms of serious development, a dead issue. As Russell Jones writing for DevX.Com, states: The bottom line is: DHTML is dead for serious application development; browsers, as application delivery platforms, are past their peak; and the future of distributed, interactive applications -- at least on Windows --
To make sure there was as little variation introduced, Ruby on Rails was used as the programming language. Ruby on Rails supports TCP/IP and XML network integration through an Application Programmer Interface (API). The APIs to support TCP/IP and XML have been used for several years. As a result they are considered highly reliable and more accurate than other coding language APIs. Phase 3 With the test-bed created, the AJAX applet
Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.
Get Started Now