Electrical computers and digital processing systems: multicomput – Computer-to-computer data routing – Least weight routing
Reexamination Certificate
2000-01-05
2003-08-05
Banankhah, Majid (Department: 2127)
Electrical computers and digital processing systems: multicomput
Computer-to-computer data routing
Least weight routing
C709S241000, C709S206000, C709S226000, C709S230000, C709S243000, C345S215000, C345S215000, C345S215000
Reexamination Certificate
active
06604150
ABSTRACT:
TECHNICAL FIELD
The present invention relates to an integration technology for extending an application with a message-based user interface by an independent supplementary application.
BACKGROUND OF THE INVENTION
According to the current state of the art applications executed by modern operating systems are offering their functionality by some sort of user interface. In many cases the user interfaces are of graphical nature and one is talking of so-called GUI (Graphical User Interface) applications. Microsoft Windows, IBM OS/2 or Mac OS are some well-known examples of modern operating systems providing such graphical user interface technology. According to this state of the art technology the operating system and the GUI application are exchanging information units, called messages, used on one hand to inform the GUI application of the particular user interactions with respect to the particular user interface. On the other hand the messages are used by the GUI application to requests changes of the particular user interface in response to reported user interactions. Further information may be found for instance in Charles Petzold, Programming the OS/2 Presentation Manager, Microsoft Press, Redmond 1989.
The handling and exchange of these messages via message queues exchanged by the operating system and the GUI application is done on a programming level, i.e. the source code level of the application, only; with the result that the setup and handling of an application's particular user interface is an application internal aspect; other applications, i.e. the application's “external world”, are excluded from participating within the application's particular user interface: Therefore the other applications cannot be integrated within the particular user interface of a certain application.
On the other hand there is a strong requirement that within the user interface of a certain application, for convenience for the further discussion it can be called the main application, other applications, for the further discussion we call them supplementary applications, can be integrated to for instance provide additional functions or to cooperate with the main application. The user of this particular interface should get the impression of interacting with a single application only.
Two technologies are available to cope with this problem.
In a first approach the source code of the main application is adapted accordingly, which means that additional program code for further user interface capabilities is included and provisions are integrated that, depending on user's interactions with the user interface, supplementary application code is called and executed. Apparently this approach is only possible if the source code of the main application is available. Typically applications can be commercially bought in an executable, i.e. binary, version only with the result, that this first approach is excluded in almost all practical cases.
In a second approach the main application provides a set of application programming interfaces (API) which can be called by a supplementary application and which allow this supplementary application to participate within the processing of the main application. In this case, the supplementary application depends on the set of APIs provided by the existing main application. Functionalities and integration capabilities not supported by these APIs cannot be implemented and thus integration is only possible to the extend foreseen by the provider of the main application in terms of the set of APIs.
Thus the technical approaches for integration of GUI application, if available at all, are very limited.
SUMMARY OF THE INVENTION
The invention is based on the objective to provide an improved integration methodology supporting integration of a supplementary application within a main application and the main application's user interface.
It is a further objective of the current invention that the proposed integration methodology provides integration without requiring any provisions within the main applications and without requiring invasive changes in the main application.
The objectives of the invention are solved by the independent claims. Further advantageous arrangements and embodiments of the invention are set forth in the respective subclaims.
The invention relates to a computerized method for dynamically extending a main application comprising a first user-interface-control by at least one supplementary application.
The method comprises a first-step of monitoring system-messages of a system-message-queue, said system-message-queue transferring one or more system-messages comprising user-interaction-requests to said main application, and determines if a monitored system-messages comprises a user-interaction-request for creating said first user-interface-control of said main application. In the affirmative case, an indicator is set that said user-interaction-request for creating said first user-interface-control has been detected. Said method comprises a second-step monitoring application-messages of an application-message-queue, said application-message-queue transferring one or more application-messages comprising a request for said main application, and associates in response to setting said indicator the next one or multitude of application-message with said monitored system-message. Said method interprets said next one or multitude of application-message as application-message comprising the request for creating said first user-interface-control by determining based on said next application-message a first user-interface-control-handle, which is used by said GUI system as unique identification of said first user-interface-control. Finally said method executes said supplementary application.
The current invention provides an integration technology for extending an application with a message-based user interface by an independent supplementary application. The current approach completely avoids rewriting or modifying and recompiling the existing application, which in most cases is not possible because the existing main application and the supplementary application which should be integrated are owned by different companies or different divisions within a company; in most cases the source code of the main application is therefore not available. Also the current approach does not depend on any API provided for integration purposes by the main application. Even the best set of APIs (the known approaches based on plug-ins also fall under this category) cannot provide all the functionality which might be needed at a future point in time. Restrictions set up by main applications distinguishing between GUI elements which are allowed to be modified and others which are not are removed completely. These advantages are achieved as the roles of the main application and the supplementary application to be integrated are reversed with respect to an important aspect: while in the state of the art approaches the main application controls under which circumstances and to which extend the supplementary application maybe integrated, these roles are reversed by the current invention; now it is the supplementary application only controlling the point of integration. The result is a proposed integration approach which is noninvasive, dynamic and transparent with respect to the main application.
The current invention provides an integration technology for extending an application with a message-based user interface by an independent supplementary application. The current approach completely avoids rewriting or modifying and recompiling the existing application, which in most cases is not possible because the existing main application and the supplementary application which should be integrated are owned by different companies or different divisions within a company; in most cases the source code of the main application is therefore not available. Also the current approach does not depend on any API provided for integration purposes by the main application. Even the
Gebhart Alexander
Gottschall Dieter
Jung Juergen
Wastl Silke
Banankhah Majid
Nock James R.
LandOfFree
Integration of GUI application with external application... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Integration of GUI application with external application..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Integration of GUI application with external application... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3108603