Abstract: Systems and techniques to rapidly load multiple frames' content. According to an aspect, a system includes a server to transmit an initial document including frames corresponding to multiple information sources, to retrieve data from the multiple information sources, and to transmit one or more subsequent documents including the data and one or more scripts. The system further includes a browser to receive and display the initial document including the frames without the data, to receive the one or more subsequent documents, and to run the one or more scripts that cause writing of the data, with external scripts inserted, inside the frames. As a result, the data can be displayed in an order of receipt, irrespective of a layout order of the frames.

Abstract: Systems and techniques to design and deploy portal pages include selectively interpreting a portal page template based on a mode of operation. The interpretation of the portal page template results in presentation of a design-time application operable to edit the portal page template if the mode of operation is design-time, and the interpretation of the portal page template results in presentation of a run-time application operable to interact with portal dynamic content if the mode of operation is run-time. Interpreting the portal page template at design-time can result in code that enables editing of the portal page template being added, and the added code can be client-side scripting that enables addition of a content component to a content container in the portal page template using a drag-and-drop action in a WYSIWYG portal layout editor.

Abstract: Systems and techniques to provide a unifying navigation model with a navigation service that provides an interface to information sources. In general, in one implementation, the technique includes: uniting navigation hierarchies from different application sources, and providing a unified navigation area based on the united navigation hierarchy. Uniting the navigation hierarchies can involve supplying a navigation service with a navigation object model that provides, to a presentation layer, a homogeneous view of navigation information from the different application sources. Providing the unified navigation area can involve displaying a navigation window in a portal presentation, the navigation window including navigation links to resources of the different application sources, and the navigation links being organized according to the united navigation hierarchy.

Abstract: Techniques are provided for automating determination of properties information for a portal entity. The properties information for a portal entity is determined from attributes specified for items upon which the portal entity is based. The properties information may be provided to a portal and used by the portal to execute the portal entity.

Abstract: Techniques for developing applications for various frameworks. An IDE is provided comprising user-selectable options for building applications for a first framework and also for building applications for a portal based upon a second framework different from the first framework. The portal applications for the portal based upon the second framework may be developed using a language supported by the first framework. User-selectable options provided by the IDE also enable deployment of the portal applications to the portal. A single IDE can be used to develop applications for different frameworks. For example, Visual Studio .NET may be used to develop applications for the .NET framework and also to develop and deploy portal applications (e.g., portal snippets) for a portal based upon a Java-based framework such as J2EE. The portal snippets may be developed using a .NET language.

Abstract: Techniques that enable an application or component developed according to a first framework specification to use services provided by an application executing on a second framework that is different from the first framework. A portal architecture is described that is capable of running portal snippets developed according to different framework specifications. A J2EE framework-based portal is configured to execute portal snippets developed using Java for a Java-based framework and also to provide support for and execute portal snippets that have been developed using a language supported by another framework such as .NET framework.

Abstract: Systems and techniques to preserve state information in a client-server environment. In general, in one implementation, the technique includes: storing, in a shared memory of a client, a scripting object that retains state information for an original document, and cloning the stored scripting object to a newly loaded document. Storing the scripting object can involve copying a scripting object reference to the shared memory to cause retention of the scripting object by the client during document loading. Cloning the stored scripting object to the newly loaded document can be performed recursively, and can involve creating a new scripting object in the new document and copying data from the stored scripting object to the new scripting object. The state information retained in the scripting object can be navigation information associated with the loaded document, and the loaded document can be a portal page in a portal system.

Abstract: Techniques that enable an application or component developed according to a first framework specification to use services provided by an application executing on a second framework that is different from the first framework. A portal architecture is described that is capable of running portal snippets developed according to different framework specifications. A J2EE framework-based portal is configured to execute portal snippets developed using Java for a Java-based framework and also to provide support for and execute portal snippets that have been developed using a language supported by another framework such as .NET framework.

Abstract: Techniques for developing applications for various frameworks. An IDE is provided comprising user-selectable options for building applications for a first framework and also for building applications for a portal based upon a second framework different from the first framework. The portal applications for the portal based upon the second framework may be developed using a language supported by the first framework. User-selectable options provided by the IDE also enable deployment of the portal applications to the portal. A single IDE can be used to develop applications for different frameworks. For example, Visual Studio .NET may be used to develop applications for the .NET framework and also to develop and deploy portal applications (e.g., portal snippets) for a portal based upon a Java-based framework such as J2EE. The portal snippets may be developed using a .NET language.

Abstract: Systems and techniques to provide a unifying navigation model with a navigation service that provides an interface to information sources. In general, in one implementation, the technique includes: uniting navigation hierarchies from different application sources, and providing a unified navigation area based on the united navigation hierarchy. Uniting the navigation hierarchies can involve supplying a navigation service with a navigation object model that provides, to a presentation layer, a homogeneous view of navigation information from the different application sources. Providing the unified navigation area can involve displaying a navigation window in a portal presentation, the navigation window including navigation links to resources of the different application sources, and the navigation links being organized according to the united navigation hierarchy.

Abstract: Systems and techniques to preserve state information in a client-server environment. In general, in one implementation, the technique includes: storing, in a shared memory of a client, a scripting object that retains state information for an original document, and cloning the stored scripting object to a newly loaded document. Storing the scripting object can involve copying a scripting object reference to the shared memory to cause retention of the scripting object by the client during document loading. Cloning the stored scripting object to the newly loaded document can be performed recursively, and can involve creating a new scripting object in the new document and copying data from the stored scripting object to the new scripting object. The state information retained in the scripting object can be navigation information associated with the loaded document, and the loaded document can be a portal page in a portal system.

Abstract: Systems and techniques to design and deploy portal pages include selectively interpreting a portal page template based on a mode of operation. The interpretation of the portal page template results in presentation of a design-time application operable to edit the portal page template if the mode of operation is design-time, and the interpretation of the portal page template results in presentation of a run-time application operable to interact with portal dynamic content if the mode of operation is run-time. Interpreting the portal page template at design-time can result in code that enables editing of the portal page template being added, and the added code can be client-side scripting that enables addition of a content component to a content container in the portal page template using a drag-and-drop action in a WYSIWYG portal layout editor.