Method and computer system for document authoring

• US 20090024937A1
• Filed: 12/15/2004
• Published: 01/22/2009
• Est. Priority Date: 12/18/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Ziegert, Thomas, Spriestersbach, Axel, Lauff, Marcus, Seurat, Patrice, Nicoulaud, Florent, Rethore, Samuel, Spadone, Pascal T.C., Ulmer, Cedric S.P.
• Granted Patent: US 8,850,392 B2
• Time in Patent Office: Days
• US Class Current: 715/762
• CPC Class Codes: G06F 8/20 Software design

Abstract

Integrated development environment IDE (999), method and computer system for developing user interface documents. An editor (104) is used for editing a user interface document. An adaptation engine (105) generates device class specific representations of the user interface document. Each device class specific representation refers to a respective device class. Device class dependent tools (120) of the IDE (999) are used for generating device class specific information and providing it to the author. Device class specific information can be information about the complexity of the user interface by device class provided by a complexity indicator (121), information about how many pages are generated for which device class provided by a device class dependent view (122) or information about the layout for various device classes provided by a frames layouting view (124).

Claims

1. An integrated development environment for developing user interface documents, comprising:

an editor to edit a user interface document;

an adaptation engine to generate device class specific representations of the user interface document, each device class specific representation referring to a respective device class;

the integrated development environment further comprising a device class dependent complexity indicator to determine complexity values of layout components of the device class specific representations by using complexity evaluation functions, associated with the layout components and to aggregate the complexity values by device class according to a corresponding layout component hierarchy of the respective device class specific representation.

2. The integrated development environment of claim 1, further comprising:

a template wizard being interfaced to the editor to create a new user interface document by loading a predefined document template from the template wizard into the editor.

4. The integrated development environment of claim 1, further comprising

a tree-based outline editor to generate an outline view of the user interface document when loaded into the editor, the tree-based outline editor being interfaced to the editor so that selection of an element in the outline view causes the editor to highlight a corresponding text portion of the user interface document.

5. The integrated development environment of claim 1, further comprising:

a code completion tool to propose possibilities for auto-insertion of text in the editor dependent on document context at a specific position within the user interface document.

6. The integrated development environment of claim 1, further comprising:

a fragment repository to save from or loading to the user interface document a document fragment having a layout that is specific to a specific device class.

7. The integrated development environment of claim 1, further comprising:

a Java filtering tool to hide Java code in the editor when using an XML view for editing the user interface document, and to edit Java code when activating a Java code view for editing the user interface document, wherein the editor is configured to save the user interface document including Java code independent from the current editing view.

8. The integrated development environment of claim 1, further comprising:

a device class dependent frames layouting view being interfaced to the editor to provide an overview of presentation structures of the user interface document for various device classes.

9. The integrated development environment of claim 1, further comprising:

a device class dependent page view to use the adaptation engine to execute a pre-pagination run with respect to the device class specific representations and to visualize the result of the pre-pagination run for the respective device classes.

10. The integrated development environment of claim 1;

wherein the device class dependent complexity indicator is replaced by

a device class dependent page view to use the adaptation engine to execute a pre-pagination run with respect to the device class specific representations and to visualize the result of the pre-pagination run for the respective device classes.

11. The integrated development environment of claim 1;

wherein the device class dependent complexity indicator is replaced by

a device class dependent frames layouting view being interfaced to the editor to provide an overview of presentation structures of the user interface document for various device classes.

12. The integrated development environment claim 11, further comprising:

a device class dependent page view to use the adaptation engine to execute a pre-pagination run with respect to the device class specific representations and to visualize the result of the pre-pagination run for the respective device classes.

3. The integrated development environment of claim 3, where the editor is interfaced to a template XML description file including information about different available document templates, the information comprising meta data about device classes supported by the templates.

13. A computer implemented method for generating user interface documents, comprising:

loading a user interface document into an editor;

generating device class specific representations of the user interface document using an adaptation engine, each device class specific representation referring to a respective device class;

the method comprises the further operations performed by a complexity indicator;

determining complexity values of layout components of the device class specific representations by using complexity evaluation functions, associated with the layout components; and

aggregating the complexity values by device class according to a corresponding layout component hierarchy of the respective device class specific representation.

14. The method of claim 13, further comprising:

providing an overview of presentation structures of the user interface document for various device classes.

15. The method of claim 13, further comprising:

executing a pre-pagination run with respect to the device class specific representations by using the adaptation engine; and

visualizing the result of the pre-pagination run for the respective device classes in a device class dependent page view.

16. The method of claim 13, wherein the determining and aggregating operations are replaced by the operations:

executing a pre-pagination run with respect to the device class specific representations by using the adaptation engine; and

visualizing the result of the pre-pagination run for the respective device classes in a device class dependent page view.

17. (canceled)