Layout management using data-descriptive meta language documents
First Claim
Patent Images
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.
3 Assignments
0 Petitions
Accused Products
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.
78 Citations
32 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
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. - View Dependent Claims (11, 12, 13, 14, 15, 16)
-
-
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. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24, 25, 26)
-
-
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. - View Dependent Claims (28, 29, 30, 31, 32)
-
Specification