Browse Prior Art Database

A method for embedding Linux native applications inside Lotus Expeditor / Eclipse-based platforms

IP.com Disclosure Number: IPCOM000184094D
Original Publication Date: 2009-Jun-10
Included in the Prior Art Database: 2009-Jun-10
Document File: 4 page(s) / 75K

Publishing Venue

IBM

Abstract

Disclosed is a system and method for embedding Linux native applications inside Lotus Expeditor / Eclipse-based platforms. This disclosure will allow a user to embed native application windows into an Expeditor / Eclipse based views, thereby allowing the users of the platform more consistent user experience by presenting applications with different functions into a single unified view.

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 37% of the total text.

Page 1 of 4

A method for embedding Linux native applications inside Lotus Expeditor / Eclipse-based platforms

Expeditor product based on Eclipse* technology provides tools and extension points for programmers to create Rich Client Platform (RCP) based applications and embed these applications into the Expeditor Client using Eclipse perspectives and views. This feature of the product allows one to present RCP based applications with different functions into a single unified view. This enables the user to have access to the different applications without leaving the single application window. The weakness in such a model is that the native applications that have already been developed and launched via an external process can never make use of these tools to embed into Expeditor Client Platform. This presents an inconsistent view and experience to the users of Eclipse based products.

Companies frequently wish to restrict use of Information Technology (IT) systems to a limited set of applications. One means to do this is to collect multiple applications into a single application or shell. However, this is not possible on all occasions, as not all applications have the capability of merging different windows. One means of doing this is to re-parent applications into a host application, where the host limits access to only those re-parented applications. It is often difficult to do this, as different applications may have different User Interface (UI) models and behaviors and use different Application Programming Interfaces (APIs). This is particularly true of legacy applications, which may not be developed to the latest programming standards and techniques.

It is an inhibitor to this type of development that applications requiring merging into the host are launched by the user from outside the environment of the host application. A successful implementation must modify the host in some means to be aware of the independent launch and re-parent the window of the application into the host when appropriate.

It is a further inhibitor to this type of development that some operating systems, and specifically Linux**, have multiple window managers, these window managers having different APIs for re-parenting, and often having unresolved defects. This makes merging of applications in this manner particularly different, and is further addressed by the body of this disclosure.

A further inhibitor to this type of solution is that different applications have different document models, those being single document per window, and multiple documents per window. The closing behavior of such applications is therefore different in a re-parented environment, and any successful solution must address these issues as is disclosed here.

A further inhibitor is the effect of closing the application with respect to open and unsaved documents, If the docum...