Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Ui Integration
Ähnlich wie Ui Integration (20)
Mehr von Jaana Metsamaa
Ui Integration
- 1. UNDERSTANDING UI INTEGRATION: A SURVEY OF PROBLEMS, TECHNOLOGIES, Jaana Metsamaa, 24/11/2008 1
- 2. ui design time 2
- 3. ui design time 45% 2
- 4. do less ui 3
- 5. ui + ui = new app 4
- 7. dimension of the ui integ. 1.Coordinating existing ui-s 2.Composition language 3.Component visualization 4.Communication style 5.Discovery and binding 6
- 9. composition language 8
- 10. component visualization who is in charge of visualizing a UI component the component or the 9
- 11. communication style 10
- 12. discovery and binding 11
- 13. composite technologies • Desktop UI components - have them • Browser Plug-In Components - simple • Web Mashups – No UI programming at all • Web Portals and Portlets –user creates the ui 12
- 14. Questions? 13
Hinweis der Redaktion
- * The average percent of the time devoted to the user interface during the various phases of the system development (N = 63 for design, N = 63 for implementation and N = 42 for maintenance) . * User interface (UI) development is one of the most time-consuming parts of application development, testing, and maintenance, so, clearly, reusing UI components is just as important as reusing application logic.
- the integration of coarse-grained and possibly stand-alone applications at the UI level hasn’t received much attention
- the goal is to build composite applications that leverage the components’ individual UIs to produce richer, composite UI applications
- Coordinating existing ui-s = how the different monitoring components can be accessed and what is shown on their UI can be modified so to achieve a coordinated, integrated display GUI-only - simulate mouse clicks or keyboard strokes Hidden interface (http protocol) Published interface
- Coordinating existing ui-s = how the different monitoring components can be accessed and what is shown on their UI can be modified so to achieve a coordinated, integrated display GUI-only - simulate mouse clicks or keyboard strokes Hidden interface Published interface
- Component-rendered UI: The rendering and displaying of the UI is handled by the component. The composite application is a collection of the components’ UIs. This is the case of classical desktop applications that leverage executable components with linked graphics libraries. Markup-based UI: UI components may return UI code and delegate the actual rendering of the final UI to the composite application, or to the environment in which the composite application is executed. The composite application must thus be able to interpret the components’ UI code, and must allocate suitable space on the display for the rendering of the components.
- Communication style how the monitoring components exchange UI events to notify user actions significant to the composite application In UI integration we can also distinguish between Centrally-mediated communication, where the composite application has a central coordinator that receives events from components and issues instructions - e.g., via API calls - to modify the components’ UIs, and direct component to component communication, where the composite application is a cooperation of components, and there is no first-class application orchestrating the activities of the other components.
- In the management example, the problem is how the composite application identifies and binds to the relevant monitoring applications.
- A web portlet is a small, self-contained window within a web portal that displays useful information or offers a relevant service. (related posts) simply embedded areas that can add to your visitors experience. (WYSIWYG)