Developing Web 2.0 user interfaces with iWidgets and the Dojo Toolkit
Recommend Documents
Apr 17, 2009 ... Dojo Basics. • Heavily object based. • Very configurable, via tags or objects. •
Built-in debug and console. • Load basics:.
May 27, 2008 ... In order to deliver an out-of-the-box experience,. Zend Framework will bundle the
Dojo. Toolkit and will feature. Dojo-specific components.
and development of Web applications involving cooperation among multiple ... their refinement, down to the corresponding basic tasks performed by each.
Utilising the Dojo Toolkit to create web browser applications from CICS. Matter of
Fact Software. Stephen Mitchell. May 2012.
Mar 27, 2011 ... with the Dojo Toolkit to Get Highly-Compact, Fully-Obfuscated,. Fully-Optimized
Builds. Author: Stephen Chung ([email protected]).
Mar 1, 2011 ... The Dojo toolkit is a JavaScript library that makes the process of ... Dojo Toolkit
1.5 or later (can be loaded using the Google Content Delivery.
systems (ITS) can be distinguished. The first focuses on offering means to model new learning domains and their corresponding interfaces for use within a ...
those that are not (the well-known Midas Touch) are still open. In this paper we consider the kitchen environment as an example for such kind of applications.
svn co http://svn.dojotoolkit.org/dojo/view/anon/all/trunk dojo. Dojo's Package
System. At the heart of the Dojo Toolkit is a package system that allows code to
be ...
H5.2 User interfaces; H3.3 Information Search and. Retrieval. INTRODUCTION ..... For example, Harry Potter is the topic that requires the longest time to resolve ...
Magnetic tracking uses a transmitting device that emits a low frequency magnetic ... micro-machined quartz tuning forks. .... Sampling rate and lag. a) Sinusoidal back-and-forth motion of a mouse at 6 Hz is shown. b) At 60 Hz. sampling, the.
Nov 22, 2013 ... The following coding guidance are current for the Dojo 1.9 release. ... Dojo, some
of these newer guidelines may not be relevant, but you ...
ically rely on APIs (Application Programming Interface, a set of HTTP-callable URL's .... or implemented in the form of native desktop or mobile applications (see ...
user interface to the context of web archive search. We describe how we adapted
a typical search user interface to address full-text and URL search over ...
May 3, 2007 - In experiments using simplified designs of automated teller machines, aesthetics was correlated with perceived usability, and the designs rated ...
simulation of realistic haptic material properties is not man- datory necessary for the communication process between man and machine. A sensible abstraction ...
Oct 30, 2013 - 2. Head unit: offers the driver functions, which are di- rectly required for driving, but which also provide ad- .... HTML as main language for the layout description of the ele- ..... tainers are positioned freely or in a column layou
current Programming]: Distributed programming. .... tributed a UI over many workstations connected to the same net- ...... 1995), ACM Press, New York, pp.
This first exercise dealing with Web Dynpro Tables in SAP NetWeaver 7.0 is ...
This Exercise is based on the following Web Dynpro project and view layout:.
Nov 20, 2012 ... Design and Evaluation of User. Interfaces for Mobile Web Search. ACADEMIC
DISSERTATION. To be presented with the permission of the ...
Using the Dojo Toolkit in a WebWorks application. Michelle Mendoza. RIM
Developer Relations. Dylan Schiemann. Co-founder of Dojo Toolkit & CEO of
SitePen ...
trend in user modelling was initiated by Allen and Perrault [Allen & Perrault 801 and has been followed up by a variety of .... The Netherlands. MCKEOWN 1139.
Application providers compete for customers on features, quality, price ... Cost of infrastructure is shared by many apps; app providers can enter the marketplace ...
Developing Web 2.0 user interfaces with iWidgets and the Dojo Toolkit
The agenda for this session is: – An introduction to Web 2.0 and the key IBM
products in the Web 2.0 space. – The Dojo Toolkit and its core concepts. –
iWidget ...
IBM Software Lab Services
Developing Web 2.0 user interfaces with iWidgets and the Dojo Toolkit Martin Gale Master Inventor, IBM Certified IT Specialist IBM Software Lab Services, Hursley
The session will introduce the the IBM recommended approach for developing Web 2.0 user interfaces The agenda for this session is: – An introduction to Web 2.0 and the key IBM products in the Web 2.0 space. – The Dojo Toolkit and its core concepts. – iWidget concepts and developing iWidgets for IBM Mashup Center. – Questions.
Web 2.0 technologies provide simple mechanisms for rapid (re)assembly of applications and new services Feeds – streams of information formatted to agreed standards providing a regular stream of updates POST
What are AJAX frameworks and why do we need them? There are a number of challenges posed by the browser environment including – differences between browser brands – lack of a consistent component/packaging model – limitations of the standard HTML widgets – extensions to UI behaviour always require scripting – lack of a natural separation of concerns between presentation and data AJAX frameworks raise the level of abstraction above the base HTML/JavaScript runtime. There are in the order of hundreds currently available today, by and large through Open Source.
Introducing the Dojo Toolkit The Dojo Toolkit is IBM’s choice as best of breed AJAX framework. – Open source, freely available from http://www.dojotoolkit.org – Built on open web standards such as HTML, JavaScript and CSS. – Seeks to insulate the developer from browser differences and quirks and promote modular, open web UIs.
Key features include: – Extensible and flexible component model – Allows declarative UI extensions – Rich user interface components and themes. – Support for accessibility and internationalisation.
WebSphere Application Server Feature Pack for Web 2.0 Publish and Subscribe Event Handling Enables dynamic scenarios such as streaming stock updates and real time collaborative web applications
WebSphere Application Server Proxy
JMS
EJBs
Services
Ajax Proxy Provides safe, reliable access to Internet based services and mashups from browser based Ajax applications
POJOs
IBM $125.25 +$2.50… MSFT $43.75 -$1.50 …
JSON and HTTP Enablement Simplifies Ajax and web 2.0 based access to traditional web services, Java objects and EJBs in the application server
Ajax Client Runtime Eases development of client side Ajax code; based on Dojo, an open source Javascript library
WebSphere sMash WebSphere sMash is an Agile Web Application Platform – Architected around Dynamic Scripting, REST, Rich Web Interfaces, AJAX, and Feeds – Optimized for • Speed • Simplicity • Agility
Business/IT challenges in the Web 2.0 world Strategic, longterm apps (created by IT.)
Backlog of simple, tactical applications.
Business Challenges Lack of agility – IT can’t respond fast enough to business requirements Spreadsheet “apps” hard to manage, share, keep current Silo-ed, outdated information
IT Challenges IT is backlogged and suffering from too many business requests Underground or “shadow” IT Security violations Loss of information
What is a Mashup? A “mashup” is a lightweight web application created by combining information or capabilities from more than one existing source to deliver new functions & insights.
Rapid creation (days not months) Reuses existing capabilities, but delivers new functions + insights Requires limited to no technical skills Often mixes internal and external sources
What are iWidgets? iWidget is IBM-developed standard to describe reusable and configurable browser UI components. An iWidget – shares the page with other components. – is usually designed to be wired to other components on the page. – is often constructed from finer-grained widgets from a toolkit such as Dojo
The iWidget specification builds on XML, web standards and AJAX toolkits to define meta-data describing – modes of operation for the component (view, edit) – any application events emitted and consumed. – configurable attributes understood by the component.
Components of an iWidget An iWidget is instantiated in a supporting iWidget runtime environment e.g. – IBM Mashup Center – WebSphere Portal with the iWidget Portlet
iContext Dojo Widget
Dojo Widget
Dojo Widget
Encapsulation
An iWidget typically consists of – an XML meta-data descriptor and rendering markup – a JavaScript class called the iScope to provide the programmatic logic for the widget such as • responding to and emitting events from its surrounding framework known as the iContext. • managing the lifecycle of the iWidget. • application logic to underpin the user interface.
At runtime, the iContext supplied to the iScope by the runtime environment provides the means for the iWidget instance to interact with its surroundings such as – a localised getElementById() method for accessing UI elements. – accessors for attributes defined for the specific iWidget instance.
Components of the iWidget XML definition The XML definition describes the widget configuration with details such as – the viewing modes the iWidget supports. • view is the most commonly used mode and is the mode in which the iWidget displays its UI. • edit to modify settings about the iWidget. • help to provide help to the user of the iWidget.
– References to any required resources such as JavaScript files or CSS style sheets. • iWidgets often have at least one referenced resource which is the .JS file containing the iScope class.
– Markup content for each of the required modes. This is the basic display logic for the iWidget and can contain other widgets within it.
The name of the JavaScript class implementing the programmatic logic for the widget as the iScope. Value: 0
