Transforming HTML forms into mobile native forms

Patent metadata

Field	Value
Publication number	US-9772986-B2
Application number	US-201615165361-A
Country	US
Kind code	B2
Filing date	May 26, 2016
Priority date	Oct 24, 2013
Publication date	Sep 26, 2017
Grant date	Sep 26, 2017

Abstract

Techniques disclosed herein provide access to a markup document form. A user interface virtualization (UIV) agent identifies name fields and input fields in rows of the markup document form. The UIV agent maps each of the name fields to a respective one of the input fields to identify name-input pairs. The UIV agent generates user interface (UI) metadata having row metadata specifying the rows of the markup document and name-input pair metadata specifying the name-input pairs. The UIV agent sends the UI metadata to a mobile client device configured to render a form having UI elements native to the mobile client device based on the UI metadata.

First claim

What is claimed is:

1. A method of providing access to a markup document form, the method comprising:
identifying name fields and input fields in rows of the markup document form;
mapping each of the name fields to a respective one of the input fields to identify name-input pairs;
generating user interface (UI) metadata having row metadata specifying the rows of the markup document and name-input pair metadata specifying the name-input pairs; and
sending the UI metadata to a mobile client device configured to render a form having UI elements native to the mobile client device based on the UI metadata.

2. The method of claim 1 , further comprising:
determining the rows of the markup document form based on native rows of the markup document form.

3. The method of claim 1 , further comprising:
dividing the markup document form into rows based on row breaks by performing the steps of:
parsing nodes of a document object model (DOM) tree representing the markup document form;
decomposing the DOM nodes into float elements, pre-line elements, sur-inline elements, and full rows; and
merging the pre-inline elements and the sur-inline elements of adjacent DOM nodes to form rows.

4. The method of claim 1 , wherein the row metadata specifying the rows of the markup language is generated before the name-input pair metadata specifying the name-input pairs is generated, and wherein the name-input pair metadata is subsequently merged with the row metadata.

5. The method of claim 1 , wherein the row metadata specifying the rows of the markup language is generated with the name-input pair metadata specifying the name-input pairs.

6. The method of claim 1 , wherein the field names are determined using a trained naïve Bayes classification scheme.

7. The method of claim 1 , wherein mapping each of the name fields to a respective one of the input fields to identify name-input pairs, comprises:
analyzing the row containing the name field and adjacent rows.

8. The method of claim 1 , further comprising:
capturing an alert message; and
transmitting the alert message to the mobile client device, wherein the mobile client device is configured to render the alert using UI elements native the mobile client device.

9. A non-transitory computer-readable storage medium comprising instructions that, when executed in a computing device, provide access to a markup document form by performing the steps comprising:
identifying name fields and input fields in rows of the markup document form;
mapping each of the name fields to a respective one of the input fields to identify name-input pairs;
generating user interface (UI) metadata having row metadata specifying the rows of the markup document and name-input pair metadata specifying the name-input pairs; and
sending the UI metadata to a mobile client device configured to render a form having UI elements native to the mobile client device based on the UI metadata.

10. The non-transitory computer-readable storage medium of claim 9 , further comprising:
determining the rows of the markup document form based on native rows of the markup document form.

11. The non-transitory computer-readable storage medium of claim 9 , further comprising:
dividing the markup document form into rows based on row breaks by performing the steps of:
parsing nodes of a document object model (DOM) tree representing the markup document form;
decomposing the DOM nodes into float elements, pre-line elements, sur-inline elements, and full rows; and
merging the pre-inline elements and the sur-inline elements of adjacent DOM nodes to form rows.

12. The non-transitory computer-readable storage medium of claim 9 , wherein the row metadata specifying the rows of the markup language is generated before the name-input pair metadata specifying the name-input pairs is generated, and wherein the name-input pair metadata is subsequently merged with the row metadata.

13. The non-transitory computer-readable storage medium of claim 9 , wherein the row metadata specifying the rows of the markup language is generated with the name-input pair metadata specifying the name-input pairs.

14. The non-transitory computer-readable storage medium of claim 9 , wherein the field names are determined using a trained naïve Bayes classification scheme.

15. The non-transitory computer-readable storage medium of claim 9 , wherein mapping each of the name fields to a respective one of the input fields to identify name-input pairs, comprises:
analyzing the row containing the name field and adjacent rows.

16. The non-transitory computer-readable storage medium of claim 9 , further comprising:
capturing an alert message; and
transmitting the alert message to the mobile client device, wherein the mobile client device is configured to render the alert using UI elements native the mobile client device.

17. A system comprising:
a memory configured to store code; and
a processor, coupled to the memory, configured to execute the code to implement access to a markup document, comprising:
identifying name fields and input fields in rows of the markup document form;
mapping each of the name fields to a respective one of the input fields to identify name-input pairs;
generating user interface (UI) metadata having row metadata specifying the rows of the markup document and name-input pair metadata specifying the name-input pairs; and
sending the UI metadata to a mobile client device configured to render a form having UI elements native to the mobile client device based on the UI metadata.

18. The system of claim 17 , wherein the code to implement access to a markup document, further comprises:
determining the rows of the markup document form based on native rows of the markup document form.

19. The system of claim 17 , wherein the code to implement access to a markup document, further comprises:
dividing the markup document form into rows based on row breaks by performing the steps of:
parsing nodes of a document object model (DOM) tree representing the markup document form;
decomposing the DOM nodes into float elements, pre-line elements, sur-inline elements, and full rows; and
merging the pre-inline elements and the sur-inline elements of adjacent DOM nodes to form rows.

20. The system of claim 17 , wherein the row metadata specifying the rows of the markup language is generated before the name-input pair metadata specifying the name-input pairs is generated, and wherein the name-input pair metadata is subsequently merged with the row metadata.

Assignees

• Vmware Inc

Inventors

• Zhang Yao
• Kou Yu Xin
• Chi Chang Yan
• He Zhibin
• Wu Junfei

Classifications

• A47L9/0444

  for conveying motion by endless flexible members, e.g. belts · CPC title

• A47L9/0433

  Toothed gearings · CPC title

• A47L5/30 Primary

  with driven dust-loosening tools, e.g. rotating brushes · CPC title

• G06F17/243 Primary

  Physics · mapped topic

• G06F17/2247

  Physics · mapped topic