Integration rich client views in server presentations

• US 7,475,075 B2
• Filed: 09/09/2005
• Issued: 01/06/2009
• Est. Priority Date: 09/09/2005
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bishop, Paul D., Song, Jianlan, Lindhorst, Gregory S., Black, Neil W., Bould, Jason A., Miller, Andrew R., Balsara, Cyrus R.
• Primary Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US11/223,455
• Publication Number:
  US 20070074120A1
• Time in Patent Office: 1,215 Days
• Field of Search: 707/10, 707/102, 707/104.1, 707/200, 709/209, 709/203
• US Class Current: 1/1
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A rich client view of server data is integrated within a server presentation of data provided by a portal server application. The rich client view of data is included with other web based views provided according to the server presentation of data when the rich client view is created. The rich client view is integrated among the web based views such that the rich client view and web based views are organized together. A separate application is launched to render the rich client view in response to a selection to render the rich client view. The selection to render the rich client view is integrated within the server presentation of data such that rich client view is provided seamlessly within the server presentation.

Claims

1. A computer-implemented method for integrating a rich client view of data within a server presentation of data, the method comprising:

including the rich client view of data with web based views provided according to the server presentation of data associated with a portal server application when the rich client view is created on a client using a rich client application, wherein the rich client view is integrated among the web based views in a view list such that the rich client view is a peer of the web based views;

wherein the web based views are views of data provided by the portal server application on the server;

wherein the web based views are limited in features and qualities of the view by features that the portal server application user interface provides;

wherein the rich client view is presented by the rich client application on the client that includes views separate from the web based view provided by the portal server application;

wherein data presented in the rich client view may be changed and entered, and data from the view is usable outside of the context of the portal server application; and

launching the rich client application on the client to render the rich client view in response to a selection to render the rich client view, wherein the selection is integrated within the server presentation of data.

2. The computer-implemented method of claim 1, further comprising creating the rich client view in response to a selection of the rich client view from a view selection web page provided in association with the server presentation of data.

3. The computer-implemented method of claim 2, wherein the view selection web page provides alternative types of views for creation in association with the server presentation of data.

4. The computer-implemented method of claim 3, wherein the alternative types of views includes both web based views and the rich client view.

5. The computer-implemented method of claim 1, further comprising determining whether the separate application corresponds to an application in which the rich client view was created before launching the rich client application.

6. The computer-implemented method of claim 5, further comprising launching a different application on the client to render the rich client view.

7. The computer-implemented method of claim 1, further comprising determining whether to publish the rich client view to the server when the rich client view is at least one of created and modified.

8. The computer-implemented method of claim 7, wherein the determination of whether to publish is triggered by a save operation occurring for the rich client view within the separate application.

9. The computer-implemented method of claim 7, wherein publishing the rich client view to the server comprises transmitting the rich client view to the server and storing the rich client view in a document database and updating the view list on the server.

10. The computer-implemented method of claim 9, wherein the document database corresponds to a storage location for views that are launched according to the server presentation of data and the rich client application.

11. The computer-implemented method of claim 1, wherein integrating the selection within the server presentation of data further comprises providing the rich client view in a list of views that includes the web based views associated with server presentation of data.

12. The computer-implemented method of claim 1, wherein the server presentation of data corresponds to a display of at least one web page corresponding to a portal server application.

13. A computer-readable storage medium having stored thereon instructions that when executed implements the computer-implemented method of claim 1.

14. A computer-implemented system, comprising:

a server application that is arranged to include a server application file, wherein the server application provides a presentation of data that corresponds to the data corresponding to the server application file;

a rich client view that is configured to provide an alternate presentation of data, wherein the rich client view is integrated among web based views associated with the server application file; and

a client application that is arranged to provide interaction with the rich client view, wherein the client application is launched in response to a selection of the rich client view within the presentation of data provided by the server application file;

wherein the web based views are views of data provided by the server application;

wherein the web based views are limited in features and qualities of the view by features that the portal server application user interface provides;

wherein the rich client view is presented by the client application on the client that includes views separate from the web based view provided by the portal server application;

wherein data presented in the rich client view may be changed and entered, and data from the view is usable outside of the context of the server application.

15. The system of claim 14, wherein the selection of the rich client view is made from a list of views provided in association with the server application file.

16. The system of claim 14, wherein the selection of the rich client view is made from a view selection page that provides types of views available for creation in association with the server application file.

17. The system of claim 14, further comprising a publication notification that is arranged to determine whether to publish the rich client view to the server after the rich client view is at least one of provided and modified by the client application.

18. The system of claim 14, further comprising a document database that is associated with the server application file, wherein the document database includes the rich client view associated with the server application file.

19. A computer-readable storage medium having stored thereon instructions that when executed implements the system of claim 14.

20. A computer-readable storage medium having stored thereon computer-executable instructions for integrating a rich client view of data within a server presentation of data, the computer-executable instructions comprising:

from a portal server application;

presenting a view selection user interface element for receiving a type of view to be created;

wherein the view created is one of a web based view and a rich client view;

wherein the web based view is a view of data provided by the portal server application on the server;

wherein the web based view is limited in features and qualities of the view by features that the portal server application user interface provides;

wherein the rich client view is presented by a rich client application on a client that includes views separate from the web based view provided by the portal server application;

wherein data presented in the rich client view may be changed and entered, and data from the view is usable outside of the context of the portal server application;

determining whether to create at least one of the web based view and the rich client view;

instantiating a view selection section when a determination is made to create at least one of a web based view and the rich client view;

determining a type of view selected for creation when the determination is made to create at least one of a web based view and the rich client view;

in response to determining a selection to create a rich client view, initiating a rich client application on the client;

determining whether creation of the rich client view on the client is complete;

receiving the rich client view for inclusion in a view list presented by the portal server application;

wherein the view list includes web based views that are associated with the portal server application and rich views that are associated with the rich client application; and

updating the view list on the server.