Layered user interface

• US 9,454,619 B2
• Filed: 09/14/2012
• Issued: 09/27/2016
• Est. Priority Date: 02/19/2004
• Status: Expired due to Fees

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Butlin, Stefan Geoffrey, Clarey, Nicholas Holder, Brook, Nicholas Carl
• Primary Examiner(s): Vu, Vanh
• Application Number:
  US13/618,650
• Publication Number:
  US 20130063479A1
• Time in Patent Office: 1,474 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: H04M 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 1/72448 with means for adapting the functionality of the device according to specific conditions
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A user interface for a device comprises a plurality of layers. The content for the user interface is associated with one of the plurality of layers.

Claims

1. A method for rendering user interface elements on a display, the method comprising:

storing one or more user interface elements in each of a plurality of archive files, wherein at least one of the one or more user interface elements comprises an obscuring element;

defining an archive file hierarchy, wherein the archive file hierarchy includes the plurality of archive files and each of the plurality of archive files has a position in the archive file hierarchy in a range between a highest position and a lowest position;

fetching each of the one or more user interface elements to be rendered based on a position in the archive file hierarchy of a respective archive file in which each of the one or more user elements is stored, beginning with the archive file at the highest position, wherein user interface elements that are located in more than one archive file are only fetched from the highest position archive file; and

rendering each of the fetched one or more user interface elements on the display.

2. The method of claim 1, wherein the obscuring element is stored in a first archive file and masks a user element in a second archive file, wherein the obscuring element is fetched from the first archive file and rendered on the display and the masked user element is not fetched from the second archive file.

3. The method of claim 1, wherein the plurality of archive files comprise at least one common archive file used by a plurality of applications and a plurality of application-specific archive files.

4. The method of claim 1, wherein the one or more user interface elements are defined by a mobile network operator, a device manufacturer, a trig, a user, or a combination thereof.

5. The method of claim 1, wherein archive files containing the one or more user interface elements are prioritized in the following order from highest to lowest:

mobile network operator defined, device manufacturer defined, trig defined, and user defined.

6. The method of claim 1, further comprising:

defining a windowtitle.txt element in one or more archive files.

7. The method of claim 6, wherein the windowtitle.txt element defines one or more attributes for text used in a title of a window to be rendered at a display.

8. The method of claim 6, further comprising:

displaying text associated with a windowtitle.txt element stored in an archive file having a highest position in the archive file hierarchy unless an archive file not associated with a windowtitle.txt element and having a higher position in the archive file hierarchy than the archive file containing the windowtitle.txt element includes an instruction to ignore any windowtitle.txt elements associated with lower archive files.

9. The method of claim 1, further comprising:

defining the obscuring element to mask a user interface element that occupies a common region of a display.

10. The method of claim 9, wherein the obscuring element is stored within the first archive file having a higher position in the archive file hierarchy than the second archive file in which the masked user interface element is located.

11. A computer system for rendering user interface elements on a display, the system comprising:

a processor operable for;

storing one or more user interface elements in each of a plurality of archive files, wherein at least one of the one or more user interface elements comprises an obscuring element;

defining an archive file hierarchy, wherein the archive file hierarchy includes the plurality of archive files and each of the plurality of archive files has a position in the archive file hierarchy in a range between a highest position and a lowest position;

fetching each of the one or more user interface elements to be rendered based on a position in the archive file hierarchy of a respective archive file in which each of the one or more user elements is stored, beginning with the archive file at the highest position, wherein user interface elements that are located in more than one archive file are only fetched from the highest position archive files; and

rendering each of the fetched one or more user interface elements on the display.

12. The system of claim 11, wherein the obscuring element is stored in a first archive file and masks a user element in a second archive file, wherein the obscuring element is fetched from the first archive file and rendered on the display and the masked user element is not fetched from the second archive file.

13. The system of claim 11, wherein the plurality of archive files comprise at least one common archive file used by a plurality of applications and a plurality of application-specific archive files.

14. The system of claim 11, wherein the one or more user interface elements are defined by a mobile network operator, a device manufacturer, a trig, a user, or a combination thereof.

15. The system of claim 11, wherein archive files containing the one or more user interface elements are prioritized in the following order from highest to lowest:

mobile network operator defined, device manufacturer defined, trig defined, and user defined.

16. The system of claim 11, wherein the processor is further operable for:

defining a windowtitle.txt element in one or more archive files.

17. The system of claim 16, wherein the windowtitle.txt element defines one or more attributes for text used in a title of a window to be rendered at a display.

18. The system of claim 16, wherein the processor is further operable for:

displaying text associated with a windowtitle.txt element stored in an archive file having a highest position in the archive file hierarchy unless an archive file not associated with a windowtitle.txt element and having a higher position in the archive file hierarchy than the archive file containing the windowtitle.txt element includes an instruction to ignore any windowtitle.txt elements associated with lower archive files.

19. The system of claim 11, wherein the processor is further operable for:

defining the obscuring element to mask a user interface element that occupies a common region of a display.

20. The system of claim 19, wherein the obscuring element is stored within the first archive file having a higher position in the archive file hierarchy than the second archive file in which the masked user interface element is located.

21. A computer system for rendering user interface elements on a display, the system comprising:

means for storing one or more user interface elements in each a plurality of archive files, wherein at least one of the one or more user interface elements comprises an obscuring element;

means for defining an archive file hierarchy, wherein the archive file hierarchy includes the plurality of archive files and each of the plurality of archive files has a position in the archive file hierarchy in a range between a highest position and a lowest position;

means for fetching each of the one or more user interface elements to be rendered based on a position in the archive file hierarchy of a respective archive file in which each of the one or more user elements is stored, beginning with the archive file at the highest position, wherein user interface elements that are located in more than one archive file are only fetched from the highest position archive file; and

means for rendering each of the fetched one or more user interface elements on the display.

22. The system of claim 21, wherein the obscuring element is stored in a first archive file and masks a user element in a second archive file, and the obscuring element is fetched from the first archive file and rendered on the display and the masked user element is not fetched from the second archive file.

23. The system of claim 21, wherein the plurality of archive files comprise at least one common archive file used by a plurality of applications and a plurality of application-specific archive files.

24. The system of claim 21, wherein the one or more user interface elements are defined by a mobile network operator, a device manufacturer, a trig, a user, or a combination thereof.

25. The system of claim 21, wherein archive files containing the one or more user interface elements are prioritized in the following order from highest to lowest:

mobile network operator defined, device manufacturer defined, trig defined, and user defined.

26. The method of claim 21, further comprising defining a windowtitle.txt element in one or more archive files.

27. The system of claim 26, wherein the windowtitle.txt element defines one or more attributes for text used in a title of a window to be rendered at a display.

28. The system of claim 26, further comprising:

means for displaying text associated with a windowtitle.txt element stored in an archive file having a highest position in the archive file hierarchy unless an archive file not associated with a windowtitle.txt element and having a higher position in the archive file hierarchy than the archive file containing the windowtitle.txt element includes an instruction to ignore any windowtitle.txt elements associated with lower archive files.

29. The system of claim 21, further comprising:

means for defining the obscuring element to mask a user interface element that occupies a common region of a display.

30. The system of claim 21, wherein the obscuring element is stored within the first archive file having a higher position in the archive file hierarchy than the second archive file in which the masked user interface element is located.

31. A computer program product comprising a non-transitory computer usable medium having a computer readable program code embodied therein, said computer readable program code adapted to be executed to implement a method for rendering user interface elements on a display, said method comprising:

storing one or more user interface elements in each a plurality of archive files, wherein at least one of the one or more user interface elements comprises an obscuring element;

defining an archive file hierarchy, wherein the archive file hierarchy includes the plurality of archive files and each of the plurality of archive files has a position in the archive file hierarchy in a range between a highest position and a lowest position;

fetching each of the one or more user interface elements to be rendered based on a position in the archive file hierarchy of a respective archive file in which each of the one or more user elements is stored, beginning with the archive file at the highest position, wherein user interface elements that are located in more than one archive file are only fetched from the highest position archive file; and

rendering each of the fetched one or more user interface elements on the display.

32. The computer program product of claim 31, wherein the program code implementing the method further comprises:

defining the obscuring element in a first archive file to mask a user element in a second archive file, wherein the obscuring element is fetched from the first archive file and rendered on the display and the masked user element is not fetched from the second archive file.

33. The computer program product of claim 31, wherein the plurality of archive files comprise at least one common archive file used by a plurality of applications and a plurality of application-specific archive files.

34. The computer program product of claim 31, wherein the one or more user interface elements are defined by a mobile network operator, a device manufacturer, a trig, a user, or a combination thereof.

35. The computer program product of claim 31, wherein archive files containing the one or more user interface elements are prioritized in the following order from highest to lowest:

mobile network operator defined, device manufacturer defined, trig defined, and user defined.

36. The computer program product of claim 31, wherein the program code implementing the method further comprises:

defining a windowtitle.txt element in one or more archive files.

37. The computer program product of claim 36, wherein the windowtitle.txt element defines one or more attributes for text used in a title of a window to be rendered at a display.

38. The computer program product of claim 31, wherein the program code implementing the method further comprises:

displaying text associated with a windowtitle.txt element stored in an archive file having a highest position in the archive file hierarchy unless an archive file not associated with a windowtitle.txt element and having a higher position in the archive file hierarchy than the archive file containing the windowtitle.txt element includes an instruction to ignore any windowtitle.txt elements associated with lower archive files.

39. The computer program product of claim 31, wherein the program code implementing the method further comprises:

defining the obscuring element to mask a user interface element that occupies a common region of a display.

40. The computer program product of claim 31, wherein the obscuring element is stored within the first archive file having a higher position in the archive file hierarchy than the second archive file in which the masked user interface element is located.