System and method for developing an application for extending access to local software of a wireless device

• US 20060036941A1
• Filed: 02/22/2005
• Published: 02/16/2006
• Est. Priority Date: 01/09/2001
• Status: Abandoned Application

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Inventors: Neil, Tim
• Application Number:
  US11/061,890
• Publication Number:
  US 20060036941A1
• Time in Patent Office: Days
• US Class Current: 715/234
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A system and method for developing an application for subsequent deployment on a mobile device, the mobile device configured for using the deployed application to communicate over a network with a data source through a transaction server. The system and method comprising: an interface component module for providing access to a defined interface component for use in providing communication between the application and a local software configured to be resident on the mobile device; and a composer module for defining a text file containing definitions expressed in a structured definition language, the definitions describing a message section and a data section and a user interface section of the application, the composer module further for inserting handler definitions in the text file such that the handler definitions are configured for calling the interface component of the interface component module.

Claims

1. A system for developing an application for subsequent deployment on a mobile device, the mobile device configured for using the deployed application to communicate over a network with a data source through a transaction server, the system comprising:

an interface component module for providing access to a defined interface component for use in providing communication between the application and a local software configured to be resident on the mobile device; and

a composer module for defining a text file containing definitions expressed in a structured definition language, the definitions describing a message section and a data section and a user interface section of the application, the composer module further for inserting handler definitions in the text file such that the handler definitions are configured for calling the interface component of the interface component module.

2. The system of claim 1, wherein the interface components are selected from the group comprising:

when instantiated the interface component acts as a proxy communication interface between the application and the local software; and

when instantiated the interface component performs a called method directly and as such provides functionality itself as local software.

3. The system of claim 2 further comprising a software module for simulating the local software in response to request messages configured for receipt by the communication interface.

4. The system of claim 2, wherein the handler definitions of the text file are configured to identify the interface component object by name.

5. The system of claim 4, wherein the interface component is an object class and the communication interface is an instantiated object of the object class.

6. The system of claim 2 further comprising a communication service for communicating with the instantiated interface component.

7. The system of claim 2, wherein the handler definitions of the text file are configured to identify the interface component object by name.

8. The system of claim 7, wherein the call comprises querying whether the object having the name exists at the mobile device.

9. The system of claim 6, wherein the communication service is part of a virtual machine software for simulating the application from the text file.

10. The system of claim 2, wherein the handler definition is part of the user interface definition section with respect to a screen action of the application.

22. The system of claim 2, wherein the interface component is configured for simulation through a series of text entered by a developer of the interface component module.

23. The system of claim 2, wherein the interface component is resident on a memory coupled to the interface component module such that the interface component is executed in relation to the simulated application.

11. A method for developing an application for subsequent deployment on a mobile device, the mobile device configured for using the deployed application to communicate over a network with a data source through a transaction server, the method comprising the steps of:

providing access to a defined interface component for use in providing communication between the application and a local software configured to be resident on the mobile device;

defining a text file containing definitions expressed in a structured definition language, the definitions describing a message section and a data section and a user interface section of the application; and

inserting handler definitions in the text file such that the handler definitions are configured for calling the interface component of the interface component module.

12. The method of claim 11, wherein the interface components are selected from the group comprising:

when instantiated the interface component acts as a proxy communication interface between the application and the local software; and

when instantiated the interface component performs a called method directly and as such provides functionality itself as local software.

13. The system of claim 12 further comprising the step of simulating the local software in response to request messages configured for receipt by the communication interface.

14. The system of claim 12, wherein the handler definitions of the text file are configured to identify the interface component object by name.

15. The system of claim 14, wherein the interface component is an object class and the communication interface is an instantiated object of the object class.

16. The system of claim 12 further comprising the step of communicating with the instantiated interface component.

17. The system of claim 12, wherein the handler definitions of the text file are configured to identify the interface component object by name.

18. The system of claim 17 further comprising the step of querying whether the object having the name exists at the mobile device.

19. The system of claim 16, wherein a communication service is part of a virtual machine software for simulating the application from the text file.

20. The system of claim 12, wherein the handler definition is part of the user interface definition section with respect to a screen action of the application.

21. A computer program product for developing an application for subsequent deployment on a mobile device, the mobile device configured for using the deployed application to communicate over a network with a data source through a transaction server, the computer program product comprising:

a computer readable medium;

an interface component module stored on the computer readable medium for providing access to a defined interface component for use in providing communication between the application and a local software configured to be resident on the mobile device; and

a composer module coupled to the interface component module for defining a text file containing definitions expressed in a structured definition language, the definitions describing a message section and a data section and a user interface section of the application, the composer module further for inserting handler definitions in the text file such that the handler definitions are configured for calling the interface component of the interface component module.