User interface archive

• US 20080313603A1
• Filed: 06/13/2007
• Published: 12/18/2008
• Est. Priority Date: 06/13/2007
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Denkel, Christian
• Application Number:
  US11/811,977
• Publication Number:
  US 20080313603A1
• Time in Patent Office: Days
• US Class Current: 717/106
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Source code associated with rendering an interface responsive to a user interaction may be stored in an archive, the source code including one or more network-resource locators identifying network locations of one or more resource files used in the rendering. The one or more resource files may be retrieved from the network locations based on the network-resource locators. The one or more retrieved resource files may be stored in the archive, wherein a local-resource locator identifies a local-resource location of each retrieved resource file in the archive. The network-resource locators may be replaced in the source code with the local-resource locators.

Claims

1. A method comprising:

storing source code associated with rendering an interface responsive to a user interaction in an archive, the source code including one or more network-resource locators identifying network locations of one or more resource files used in the rendering;

retrieving the one or more resource files from the network locations based on the network-resource locators;

storing the one or more retrieved resource files in the archive, wherein a local-resource locator identifies a local-resource location of each retrieved resource file in the archive; and

replacing, in the source code, the network-resource locators with the local-resource locators.

2. The method of claim 1, further comprising:

generating user code based on the user interaction; and

storing the user code in the archive.

3. The method of claim 1 wherein storing the source code comprises:

capturing user code that is associated with the user interface and that is sent to a server configured to provide the source code responsive to the user code; and

storing the user code in the archive.

4. The method of claim 1 wherein storing the source code comprises receiving the source code associated with rendering the interface in response to the user interaction, wherein the interface changes responsive to the user interaction.

5. The method of claim 1 wherein storing the source code comprises storing an extensible markup language (XML) file associated with rendering the interface.

6. The method of claim 1 wherein storing the source code comprises receiving the source code including one or more uniform resource locators (URLs) identifying the network locations.

7. The method of claim 1 wherein retrieving the one or more resource files comprises downloading, from the one or more network locations, the one or more resource files based on the network-resource locators.

8. The method of claim 1 wherein replacing the network-resource locators with the local-resource locators comprises replacing a first network-resource locator identifying a first network location of a first resource with a first local-resource locator identifying a first local-resource location of the first resource.

9. The method of claim 1 wherein the replacing the network-resource locators with the local-resource locators comprises replacing, in the source code, the network-resource locators with the local-resource locators during a rendering of the interface based on the archive, wherein during the rendering, the local resource-locators are used in lieu of the network-resource locators.

10. The method of claim 1 further comprising:

rendering the interface based on the source code and retrieved one or more resource files stored in the archive.

11. A system comprising:

a request handler configured to determine user code based on a user interaction with a first interface;

an archiving engine configured to store the user code and source code for rendering a second interface in response to the user code, in an archive, the source code including a network-resource locator identifying a network location of a resource used in the rendering of the second interface;

a download engine configured to retrieve the resource from the network location based on the network-resource locator and store the retrieved resource in a local-resource location in the archive, the local-resource location being identified by a local-resource locator; and

resource logic configured to associate the network-resource locator with the local-resource locator in the source code.

12. The system of claim 11 wherein the request handler is configured to:

receive the user interaction with the first interface; and

generate the user code based on the user interaction.

13. The system of claim 11 wherein the archiving engine is configured to receive the source code from a server configured to generate the source code in response to the user code.

14. The system of claim 11 wherein the archiving engine is configured to store first source code used for rendering the first user interface in the archive.

15. The system of claim 11 wherein the resource logic is configured to replace the network resource-locator with the local resource-locator in the source code

16. The system of claim 11 further comprising a rendering engine configured to render the second interface based on the archive and using the retrieved resource stored in the local-resource location.

17. The system of claim 11 further comprising a rendering engine configured to render a plurality of interfaces based on the source code stored in the archive, wherein the plurality of interfaces are associated with a plurality of user interactions with the plurality of interfaces.

18. A method for archiving a plurality of user interactions with an interface comprising:

repeating for each of the plurality of user interactions with the interface;

storing user code associated with a first user interaction of the plurality of user interactions in an archive;

storing source code generated in response to the first user interaction in the archive, wherein a first rendering of the interface based on the source code uses one or more resources; and

downloading the one or more resources into the archive, wherein a second rendering of the interface based on the archive uses the one or more downloaded resources.

19. The method of claim 18 wherein storing the source code comprises storing the source code, generated in response to the first user interaction, in the archive, wherein the interface changes responsive to the first user interaction.

20. The method of claim 18 wherein the first rendering of the interface and the second rendering of the interface are identical.