METHOD, APPARATUS, MOBILE TERMINAL AND COMPUTER PROGRAM PRODUCT FOR EMPLOYING A FORM ENGINE AS A SCRIPT ENGINE

• US 20100138733A1
• Filed: 12/02/2008
• Published: 06/03/2010
• Est. Priority Date: 12/02/2008
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Koskimies, Oskari
• Granted Patent: US 8,381,172 B2
• Time in Patent Office: Days
• US Class Current: 715/221
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/45512 Command shells

Abstract

An apparatus for employing a form engine as a script engine may include a processor. The processor may be configured to determine whether an event relates to starting a form or running a script, employ a form engine having a user interface portion including user interface components in response to a determination that the event relates to starting the form, and adapt the form engine by providing a reduced user interface portion that does not create user interface components and does not generate user interface events in response to a determination that the event relates to running the script. A corresponding method and computer program product are also provided.

Claims

1. A method comprising:

determining whether an event relates to starting a form or running a script;

employing a form engine having a user interface portion including user interface components in response to a determination that the event relates to starting the form; and

adapting the form engine by providing a reduced user interface portion that does not create user interface components and does not generate user interface events in response to a determination that the event relates to running the script.

2. The method of claim 1, wherein employing the form engine comprises employing an XForms form engine.

3. The method of claim 1, wherein adapting the form engine comprises replacing the user interface portion of the form engine with a null user interface binding.

4. The method of claim 1, wherein adapting the form engine comprises replacing the user interface portion of the form engine with an empty user interface binding.

5. The method of claim 1, further comprising defining a local representational state transfer (REST) service accessible by the script.

6. The method of claim 5, wherein defining the local REST service comprises defining a service accessible by the script via standard XForms submissions.

7. The method of claim 1, wherein adapting the form engine comprises enabling use of a model portion of the form engine to run the script via execution of an event handler without involving user interaction.

8. A computer program product comprising at least one computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instruction comprising:

program code instructions for determining whether an event relates to starting a form or running a script;

program code instructions for employing a form engine having a user interface portion including user interface components in response to a determination that the event relates to starting the form; and

program code instructions for adapting the form engine by providing a reduced user interface portion that does not create user interface components and does not generate user interface events in response to a determination that the event relates to running the script.

9. The computer program product of claim 8, wherein program code instructions for employing the form engine include instructions for employing a XForms form engine.

10. The computer program product of claim 8, wherein program code instructions for adapting the form engine include instructions for replacing the user interface portion of the form engine with a null user interface binding.

11. The computer program product of claim 8, wherein program code instructions for adapting the form engine include instructions for replacing the user interface portion of the form engine with an empty user interface binding.

12. The computer program product of claim 8, further comprising program code instructions for defining a local representational state transfer (REST) service accessible by the script.

13. The computer program product of claim 12, wherein program code instructions for defining the local REST service include instructions for defining a service accessible by the script via standard XForms submissions.

14. The computer program product of claim 8, wherein program code instructions for adapting the form engine include instructions for enabling use of a model portion of the form engine to run the script via execution of an event handler without involving user interaction.

15. An apparatus comprising a processor configured to:

determine whether an event relates to starting a form or running a script;

employ a form engine having a user interface portion including user interface components in response to a determination that the event relates to starting the form; and

adapt the form engine by providing a reduced user interface portion that does not create user interface components and does not generate user interface events in response to a determination that the event relates to running the script.

16. The apparatus of claim 15, wherein the processor is configured to employ the form engine by employing a XForms form engine.

17. The apparatus of claim 15, wherein the processor is configured to adapt the form engine by replacing the user interface portion of the form engine with a null user interface binding.

18. The apparatus of claim 15, wherein the processor is configured to adapt the form engine by replacing the user interface portion of the form engine with an empty user interface binding.

19. The apparatus of claim 15, wherein the processor is further configured to define a local representational state transfer (REST) service accessible by the script.

20. The apparatus of claim 19, wherein the processor is configured to define the local REST service by defining a service accessible by the script via standard XForms submissions.

21. The apparatus of claim 15, wherein the processor is configured to adapt the form engine by enabling use of a model portion of the form engine to run the script via execution of an event handler without involving user interaction.

22. The apparatus of claim 15, further comprising a memory device for storing instructions executable by the processor.

23. An apparatus comprising:

means for determining whether an event relates to starting a form or running a script;

means for employing a form engine having a user interface portion including user interface components in response to a determination that the event relates to starting the form; and

means for adapting the form engine by providing a reduced user interface portion that does not create user interface components and does not generate user interface events in response to a determination that the event relates to running the script.

24. The apparatus of claim 23, wherein means for employing the form engine comprises means for employing a XForms form engine.