Browse Prior Art Database

Method and system for developing interactive and multi-page view in Web based widget

IP.com Disclosure Number: IPCOM000198083D
Publication Date: 2010-Jul-26
Document File: 5 page(s) / 126K

Publishing Venue

The IP.com Prior Art Database

Abstract

Web widgets have been the featured components and widely used in Web application. To improve the interaction and usability of the Web widgets, the disclosure propose a novel method and system for developing interactive and multi-page view in Web based widget. The disclosure firstly defines pages and events centric widget model which explicitly defines navigation rule and event handling communication, and then proposes runtime container that can execute the widget model to enable interactive and multi-page view in widget. Through the proposed approach, developers can easily write a multi-page web widget without effort to handle the navigation control inside widget.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 5

Method and system for developing interactive and multi-page view in Web based widget

Web widgets have been the featured components and widely used in Web application, they are self-contained and can be mash-uped from different sources

within any separate HTML-based web page by an end user without requiring

additional compilation.Web widgets are implemented using web technologies including XML, JavaScript, HTML and CSS. There are several standards defining the widget definition, view and behaviors, as well as runtime environment, such as Google gadget, IBM iWidget, Yahoo! Widget.Communication among widgets is always supported by widget runtime container through event pub/sub model to enable application level functions for end user.

Due to the simplified widget programming model, the content and functions in the

widget are limited, it seems they are "Single Page" oriented.

1) Widgets couldn't contain navigation pages

2) Not rich user interaction and experience

To enable more interactive and multi-page view in widget, developer needs to put too much effort to handle the navigational control among pages in an ad -hoc way

1) IFrame solution:The remote content in IFrame couldn't communicate with other

widgets and elements on the page

2)

content and adjust UI in one widget and the expected behaviors in navigation such as back, forward, refresh and bookmarking are useless

To improve the interaction and enable multi-page view in widget, the disclosure propose a pages and events centric widget model (figure 1),

which

AJAX interaction:Much development effort needed to contain all the page

1) Looking at page as first class object

2) Explicitly defined navigation rule for declaring the page flow

3) Events handling communication and pages navigation

1

[This page contains 1 picture or other non-text object]

Page 2 of 5

Figure 1: Proposed widget model

Figure 2 shows the a widget definition in XML format,

navigation rule and attributes are explicitly defined. In the navigation rule part, "from-view-id" and "to-view-id" refer to the pages inside the widget, and the event

which triggers the navigation is defined in

                           "navigation-case". One "from-view" can have multiple "navigation-case" applied to different navigation logic.

Figure 2.

Based on the widget model, the disclosure further proposes a runtime container that can execute the widget model to enable interactive and multi-page view in widget. The runtime includes 4 parts:

1) Navigation engine to resolve navigation rule

2) Event system handling communication and navigational control at runtime

     Widget UI change can be triggered by communication event
Page flow change is the subscription of the navigation event published by its own widget or other widgets

3)

AJAX libraries to render pages inside widget

4) Manipulation mechanism for navigation history control in the flow of pages

Figure 3 shows the component interaction at runtime.

where the resource, events,

A widget definition in XML

2

[This page co...