Layered user interface

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

defining an archive file hierarchy, wherein the archive file hierarchy includes a 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, 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;

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

fetching each of the one or more user interface elements to be rendered based on the position in the archive file hierarchy of a respective archive file in which each of the one or more user elements is stored, wherein user interface elements that are masked by obscuring elements stored in higher position archive files are not fetched; and

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

2. 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.

3. The method of claim 2 , 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.

4. The method of claim 1 , further comprising:

defining a windowtitle.txt element in one or more archive files, 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; and

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

5. 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 as the obscuring element and is stored within an archive file having a lower position in the archive file hierarchy than an archive file in which the obscuring element is located.

6. A device, comprising:

means for defining an archive file hierarchy, wherein the archive file hierarchy includes a 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, and 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;

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

means for fetching each of the one or more user interface elements to be rendered based on the position in the archive file hierarchy of a respective archive file in which each of the one or more user elements is stored, wherein user interface elements that are masked by obscuring elements stored in higher position archive files are not fetched; and

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

7. The device of claim 6 , 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.

8. The device of claim 7 , 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.

9. The device of claim 6 , further comprising:

means for defining a windowtitle.txt element in one or more archive files, 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; and

means for displaying text associated with a windowtitle.txt element 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 than the windowtitle.txt element includes an instruction to ignore any windowtitle.txt elements associated with lower archive files.

10. The device of claim 6 , further comprising:

means for defining the obscuring element to mask a user interface element that occupies a common region of a display as the obscuring element and is stored within an archive file having a lower position in the archive file hierarchy than an archive file in which the obscuring element is located.

11. A device, comprising:

a memory;

a processor coupled to the memory, wherein the processor is operable to execute one or more instructions stored within the memory in order to:

define an archive file hierarchy, wherein the archive file hierarchy includes a 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, 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;

store one or more user interface elements in each of the plurality of archive files, wherein the one or more user interface elements comprise an obscuring element;

fetch each of the one or more user interface elements to be rendered based on the position in the archive file hierarchy of a respective archive file in which each of the one or more user elements is stored, wherein user interface elements that are masked by obscuring elements stored in higher position archive files are not fetched; and

render each of the fetched one or more user interface elements.

12. The device 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.

13. The device of claim 12 , 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.

14. The device of claim 11 , wherein the processor is further operable to:

define a windowtitle.txt element in one or more archive files, 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; and

display text associated with a windowtitle.txt element 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 than the windowtitle.txt element includes an instruction to ignore any windowtitle.lxt elements associated with lower archive files.

15. The device of claim 11 , wherein the processor is further operable to:

define the obscuring element to mask a user interface element that occupies a common region of a display as the obscuring element and is stored within an archive file having a lower position in the archive file hierarchy than an archive file in which the obscuring element is located.

16. A non-transitory computer readable medium having stored thereon processor-executable instructions configured to cause a processor to perform operations comprising:

defining an archive file hierarchy, wherein the archive file hierarchy includes a 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, 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;

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

fetching each of the one or more user interface elements to be rendered based on the position in the archive file hierarchy of a respective archive file in which each of the one or more user elements is stored, wherein user interface elements that are masked by obscuring elements stored in higher position archive files are not fetched; and

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

17. The non-transitory computer readable medium of claim 16 , wherein the one or more user interface elements are defined by a mobile network operator, a computer readable medium manufacturer, a trig, a user, or a combination thereof.

18. The non-transitory computer readable medium of claim 17 , 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, computer readable medium manufacturer defined, trig defined, and user defined.

19. The non-transitory computer readable medium of claim 16 , wherein the stored processor-executable instructions are configured to cause the processor to perform operations further comprising:

defining a windowtitle.txt element in one or more archive files, 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; and

displaying text associated with a windowtitle.txt element 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 than the windowtitle.txt element includes an instruction to ignore any windowtitle.txt elements associated with lower archive files.

20. The non-transitory computer readable medium of claim 16 , wherein the stored processor-executable instructions are configured to cause the processor to perform operations further comprising:

defining the obscuring element to mask a user interface element that occupies a common region of a display as the obscuring element and is stored within an archive file having a lower position in the archive file hierarchy than an archive file in which the obscuring element is located.