User Interaction Channel

Graphic selection

The users who are already familiar with the Atomic application patterns may take the following image as a fastpath approach to the logic patterns. For the others, the Logic patterns are described in detail below the image.

User Interaction Channel

e.g. the key approaches for rendering logical user interfaces and enabling user interactions with business applications using the full range of user device types
- containing browsers, iWidgets, rich clients, RSS readers etc.

The following Atomic application patterns along with candidate product mappings exist for the User Interaction Channel logic pattern:

• Fan-out pattern to support one of multiple UI channels with common controller
  • IBM Kuba asset (MVC f/w plus Dojo)
• Voice-enabled client
• Browser client
  • Firefox, Chrome, Safari, Opera, IE (w3c specs: html 5, css 3, javascript)
  • Dojo toolkit
  • IBM Kuba asset (MVC common controller f/w plus Dojo)
• Portlet
  • WebSphere
  • WebSphere sMash
  • PS
• iWidget
  • Business Space
  • Portal Server 6.2
  • Lotus Mashup Center
• Distributed application client
  • Lotus Expeditor
  • Integrator
  • Lotus Expeditor
  • Lotus Expeditor for Devices
  • Lotus Vulcan (Notes 9)
  • Ecllipse OSGi Equinox
  • Adobe AIR
  • appcelerator Titanium
• Distributed rich client (e.g. Rich Internet Application platforms, Lotus Expeditor)
  • Lotus Expeditor
  • Lotus Notes
  • Lotus Vulcan (Notes 9)
• Distributed collaboration client
  • Lotus Notes
• Media stream reader – local file/remote stream source
  • H.264 (Firefox, Chrome, Safari, Opera, IE)
  • Legacy Silverlight
  • Adobe Flash/Flex (e.g. iPlayer, NBA player etc)
• RSS/ATOM reader – subscription to remote XML feed
  • WebSphere Web 2.0 FP (Rome)
• Remote visual service proxy stub (e.g. Google gadget, Yahoo widget)
  • WebSphere Web 2.0 FP (Apache Wink, JSR 311)
  • DataPower
  • Cast Iron

The complete Atomic patterns hierarchy including Logic patterns, Atomic application patterns, Atomic runtime patterns, Product mappings and best practices is still work in progress.

Back to top