Layout management using data-descriptive meta language documents

• US 7,827,494 B1
• Filed: 04/08/2005
• Issued: 11/02/2010
• Est. Priority Date: 04/08/2005
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Dreier, Scott, Hedayatpour, Ramin
• Primary Examiner(s): Huynh; Ba
• Assistant Examiner(s): Hassan; Rashedul
• Application Number:
  US11/102,614
• Time in Patent Office: 2,034 Days
• Field of Search: 715/771, 715/742, 715/749, 715/788, 715/234, 715/235, 715/236, 715/239, 715/243, 715/744, 709/218, 709/219, 709/236, 709/203, 709/201, 709/217
• US Class Current: 715/742
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A data-descriptive meta language file, such as XML, is created that defines the layout operation within the visual interface of a component-based application at runtime. At runtime, the application receives a data-descriptive meta language file that defines the layout operation of the various components within the application visual interface. The application parses the data-descriptive meta language file and uses the parsed information to complete the layout and operation of the rendered interface. The runtime application includes functionality that uses selected data to specify unique applications and/or unique content associated with the application.

Claims

1. A computer implemented method comprising:

receiving a portal application;

after receiving the portal application and in response to receiving the portal application, executing the portal application in a runtime container, the portal application defining presentation of a plurality of portlets on a computer display, wherein each one of said plurality of portlets operates separately and independently from each other of said plurality of portlets, wherein executing the portal application comprises;

after executing begins, accessing a layout source file, the layout source file comprising a separate content item from the portal application;

parsing the layout source file for layout information and data source information for said plurality of portlets, wherein said layout source file is associated with said portal application;

accessing a library on a storage device having a plurality of class definitions associated with said data source information;

receiving data from one or more data sources described in ones of said plurality of class definitions;

rendering a visual display on said computer display using said layout information and said received data; and

in response to receiving update data for a portlet of said plurality of portlets, re-rendering said portlet of said plurality of portlets within said visual display using said update data, wherein remaining ones of said plurality of portlets are not re-rendered.

2. The method of claim 1 wherein each of said plurality of class definitions include one or more of:

one or more input events; and

one or more output events.

3. The method of claim 2 further comprising:

registering one or more of;

said one or more input events; and

said one or more output events

with an event manager.

4. The method of claim 2 further comprising:

distributing input to said one or more input events according to at least one of;

said received data; and

said one or more output events.

5. The method of claim 1 further comprising:

downloading said layout source file from a remote location prior to accessing the layout source file.

6. The method of claim 1 further comprising:

manipulating said visual display;

re-configuring said layout source file responsive to said manipulating; and

saving said reconfigured layout source file.

7. The method of claim 6 wherein said saving comprises one or more of:

saving on remote storage; and

saving on local storage.

8. The method of claim 1 wherein said layout source file is written using a metadata language.

9. The method of claim 8 wherein said metadata language comprises one or more of:

extensible markup language (XML);

distributive hypertext markup language (DHTML);

standard generalized markup language (SGML); and

standard text.

10. A computer implemented method comprising:

executing a portal application using a runtime container in response to receiving the portal application, the portal application configured to display a plurality of components on a display, wherein executing comprises;

after executing begins, accessing a source file, the source file separate from the portal application;

parsing the source file for;

component location data for each of said plurality,

component appearance data for each of said plurality, and

component class data for each of said plurality;

retrieving component data from a data source defined in component data management information, wherein said component data management information is obtained from a component library stored on a storage device and accessible using said component class data;

creating each of said plurality of components using one or more of associated component class data and said retrieved component data;

rendering each of said created plurality of components on said display according to said component location data and said component appearance data; and

in response to receiving update data for a portlet of said plurality of portlets, re-rendering said portlet of said plurality of portlets on said display without re-rendering remaining ones of said plurality of portlets.

11. The method of claim 10 further comprising:

downloading said source file from a remote location prior to accessing said source file.

12. The method of claim 10 wherein said component library includes one or more of:

input event data; and

output event data for each of said plurality of components indexed according to said component class data.

13. The method of claim 12 further comprising:

registering with an event manager one or more of said input event data and said output event data for each of said plurality of components.

14. The method of claim 12 wherein said creating includes:

distributing said retrieved component data according to said input event data; and

retrieving said output event data from one or more of said plurality of components according to said input event data for ones of said plurality of components.

15. The method of claim 10 further comprising:

changing one or more of said plurality of components displayed on said display;

amending one or more of;

component location data;

component appearance data; and

component class data responsive to said changing.

16. The method of claim 15 further comprising:

locally storing said amended source file; and

remotely storing said amended source file.

17. A computer program product having a non-transitory computer readable medium with computer program logic recorded thereon, said computer program product comprising:

code for executing a portal application in a runtime container in response to receiving the portal application, the portal application defining presentation of a plurality of portlets on a computer display, wherein each one of said plurality of portlets operates separately and independently from each other of said plurality of portlets, wherein the code for executing comprises;

code for accessing a layout source file in response to executing the portal application, the layout source file comprising a content item separate from the portal application;

code for parsing the layout source file for layout information and data source information for said plurality of portlets;

code for accessing a library on a storage device having a plurality class definitions associated with said data source information;

code for receiving data from one or more data sources described in ones of said plurality of class definitions;

code for rendering a visual display on said computer display using said layout information and said received data; and

code for re-rendering a specified portlet within said visual display without re-rendering remaining ones of said portlets in response to receiving update data directed to said specified portlet of said plurality of portlets.

18. The computer program product of claim 17 wherein each of said plurality of class definitions include one or more of:

one or more input events; and

one or more output events.

19. The computer program product of claim 18 further comprising:

code for registering one or more of;

said one or more input events; and

said one or more output events with an event manager.

20. The computer program product of claim 18 further comprising:

code for distributing input to said one or more input events according to at least one of;

said received data; and

said one or more output events.

21. The computer program product of claim 17, wherein the code for executing the portal application further comprises:

code for downloading said layout source file from a remote location prior to accessing said layout source file.

22. The computer program product of claim 17 further comprising:

code for manipulating said visual display;

code for re-configuring said layout source file responsive to execution of said code for manipulating; and

code for saving said reconfigured layout source file.

23. The computer program product of claim 22 wherein said code for saving comprises one or more of:

code for saving on remote storage; and

code for saving on local storage.

24. The computer program product of claim 17 wherein said layout source file is written using a metadata language.

25. The computer program product of claim 24 wherein said metadata language comprises one or more of:

extensible markup language (XML);

distributive hypertext markup language (DHTML);

standard generalized markup language (SGML); and

standard text.

26. The computer program product set forth in claim 17, wherein the non-transitory computer-readable medium comprises a storage device.

27. A system comprising:

a central processing unit (CPU);

a storage device coupled to said CPU;

a display device coupled to said CPU;

a communication interface coupled to said CPU;

a parser stored on said storage device; and

a runtime container stored on said storage device;

wherein said communication interface is configured to receive a portal application from a portal server;

wherein, in response to receiving said portal application, said CPU is configured to execute said runtime container after receiving said portal application;

wherein, in response to said execution, said runtime container is configured to run said portal application and retrieve a layout source file from said portal server, said layout source file being a separate content item from the portal application;

wherein, on receipt of said layout source file, said CPU executes said parser to parse said layout source file for;

portlet location data for each of a plurality of portlets;

portlet appearance data for each of said plurality of portlets; and

portlet class data for each of said plurality of portlets;

wherein, using said portlet class data, said portal application configures said communication interface to retrieve portlet data from a data source defined by portlet data management information obtained from a class library accessible using said portlet class data;

wherein said portal application configures said display device to render each of said plurality of portlets on said display device according to said portlet location data, said portlet appearance data, and said portlet data; and

wherein, in response to receiving update data from said data source directed at a portlet of said plurality of portlets, said portal application configures said display device to re-render said portlet using said update data without re-rendering remaining ones of said plurality of portlets.

28. The system of claim 27 further comprising:

a user input device coupled to said CPU, wherein said user input device is configured to receive a uniform resource locator (URL) from a user, wherein said URL provides access information for said portal server to retrieve said portal application.

29. The system of claim 27 wherein said class library includes one or more of:

input event data; and

output event data for each of said plurality of portlets indexed according to said portlet class data.

30. The system of claim 29 wherein said portal application is configured to register with an event manager one or more of said input event data and said output event data for each of said plurality of portlets.

31. The system of claim 29 wherein said portal application is configured to distribute said retrieved portlet data according to said input event data;

and retrieve said output event data from one or more of said plurality of portlets according to said input event data for ones of said plurality of portlets.

32. The system of claim 27 wherein said portal application is configured to change one or more of said plurality of portlets displayed on said display device including amending one or more of:

portlet location data;

portlet appearance data; and

portlet class data responsive to said change.