Abstract: A message occurrence can be detected when a software application runs on a computing device. The message occurrence can be an occurrence where a text containing message is presented upon a user interface of the software application or a log associated with the software application is updated with a text containing message. A user context for the message occurrence can be determined. The user context can include a user sequence and an execution path. Message occurrence information can be conveyed to a message context catalog. Within the message context catalog, the message occurrence information can be indexed against unique message identifiers. Message occurrence information from the message context catalog can be presented in a computer's user interface when a message uniquely identified by the message identifier is presented in the user interface. The user interface can permit a user to edit text of messages.

Abstract: A message occurrence can be detected when a software application runs on a computing device. The message occurrence can be an occurrence where a text containing message is presented upon a user interface of the software application or a log associated with the software application is updated with a text containing message. A user context for the message occurrence can be determined. The user context can include a user sequence and an execution path. Message occurrence information can be conveyed to a message context catalog. Within the message context catalog, the message occurrence information can be indexed against unique message identifiers. Message occurrence information from the message context catalog can be presented in a computer's user interface when a message uniquely identified by the message identifier is presented in the user interface. The user interface can permit a user to edit text of messages.

Abstract: A system and method for automatically selecting a translator to translate a component request using semantic typing is presented. A mediator receives a component request from a first component that requests to invoke a second component. The mediator retrieves a launch target identifier and a requester provided property type identifier from the component request. The requester provided property type identifier includes semantic typing corresponding to a data value. The mediator retrieves a recipient input property type identifier corresponding to the launch target identifier, and uses the requester provided property type identifier and the recipient input property type identifier to select a translator. The mediator passes a data value included in the component request to the selected translator, and receives a translated data value from the translator. The mediator constructs a property using the translated data value and includes the constructed property in a call that is sent to the second component.

Abstract: Under the present invention, a sequence of actions made by a user in operating a software system is tracked. Upon request by the user, predictive help is given based on the sequence of actions. In a typical embodiment, the predictive help is contained in a knowledge base, which is initially built during development of the software system. Specifically, the knowledge base is populated based on sequences of actions by other users as they operate the software system during its development. Moreover, the knowledge base can be updated after release of the software system as the user operates the system. To this extent, the knowledge base will “learn” the patterns of the user, and the predictive help will be continually tailored based thereon.

Abstract: A system and method for automatically selecting a translator to translate a component request using semantic typing is presented. A mediator receives a component request from a first component that requests to invoke a second component. The mediator retrieves a launch target identifier and a requester provided property type identifier from the component request. The requester provided property type identifier includes semantic typing corresponding to a data value. The mediator retrieves a recipient input property type identifier corresponding to the launch target identifier, and uses the requester provided property type identifier and the recipient input property type identifier to select a translator. The mediator passes a data value included in the component request to the selected translator, and receives a translated data value from the translator. The mediator constructs a property using the translated data value and includes the constructed property in a call that is sent to the second component.