Method, apparatus, mobile terminal and computer program product for employing a form engine as a script engine

• US 8,381,172 B2
• Filed: 12/02/2008
• Issued: 02/19/2013
• Est. Priority Date: 12/02/2008
• Status: Expired due to Fees

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Koskimies, Oskari
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): CHEN, XI DONALD
• Application Number:
  US12/326,556
• Publication Number:
  US 20100138733A1
• Time in Patent Office: 1,540 Days
• Field of Search: None
• US Class Current: 717/104
• 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 model portion and 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 having the model portion for use as a script 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, wherein adapting the form engine having the model portion for use as the script engine comprises replacing the user interface portion of the form engine with a null user interface binding such that the user interface portion of a form markup language is eliminated resulting in the form markup language being a scripting language.

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 having the model portion for use as the script engine comprises replacing the user interface portion of the form engine with an empty user interface binding.

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

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

6. The method of claim 1, wherein adapting the form engine having the model portion for use as the script engine comprises enabling use of the model portion of the form engine to run the script via execution of an event handler without involving user interaction by removing the user interface portion of the form engine.

7. A computer program product comprising:

at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions 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 model portion and 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 having the model portion for use as a script 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, wherein program code instructions for adapting the form engine having the model portion for use as the script engine include instructions for replacing the user interface portion of the form engine with a null user interface binding such that the user interface portion of a form markup language is eliminated resulting in the form markup language being a scripting language.

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

9. The computer program product of claim 7, wherein program code instructions for adapting the form engine having the model portion for use as the script engine include instructions for replacing the user interface portion of the form engine with an empty user interface binding.

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

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

12. The computer program product of claim 7, wherein program code instructions for adapting the form engine having the model portion for use as the script engine include instructions for enabling use of the model portion of the form engine to run the script via execution of an event handler without involving user interaction by removing the user interface portion of the form engine.

13. An apparatus comprising:

a processor; and

a memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus to at least;

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

employ a form engine having a model portion and 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 having the model portion for use as the script 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, wherein the memory including the computer program code is further configured to with the processor, cause the apparatus to adapt the form engine having the model portion for use as the script engine by replacing the user interface portion of the form engine with a null user interface binding such that the user interface portion of a form markup language is eliminated resulting in the form makeup language being a scripting language.

14. The apparatus of claim 13, wherein the memory including the computer program code is further configured to, with the processor, cause the apparatus to employ the form engine by employing a XForms form engine.

15. The apparatus of claim 13, wherein the memory including the computer program code is further configured to, with the processor, cause the apparatus to adapt the form engine having the model portion for use as the script engine by replacing the user interface portion of the form engine with an empty user interface binding.

16. The apparatus of claim 13, wherein the memory including the computer program code is further configured to, with the processor, cause the apparatus to define a local representational state transfer (REST) service accessible by the script.

17. The apparatus of claim 16, wherein the memory including the computer program code is further configured to, with the processor, cause the apparatus to define the local REST service by defining a service accessible by the script via standard XForms submissions.

18. The apparatus of claim 13, wherein the memory including the computer program code is further configured to, with the processor, cause the apparatus to adapt the form engine having the model portion for use as the script 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 by removing the user interface portion of the form engine.

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

20. An apparatus comprising:

a processor, wherein the processor comprises;

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

means for employing a form engine having a model portion and 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 having the model portion for use as a script 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, wherein means for adapting the form engine having the model portion for use as the script engine comprises means for replacing the user interface portion of the form engine with a null user interface binding such that the user interface portion of a form markup language is eliminated resulting the form markup language being a scripting language.

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