Project task management system for managing project schedules over a network
First Claim
1. A computer-implemented method for managing a project schedule with a client-server based project schedule system, the method comprising:
- receiving a request to view an editor associated with said schedule system;
in response to said request, a server accessing first schedule-related information from a database;
said server generating first client-executable code for execution by a client for displaying said editor and displaying said first schedule-related information in said editor and for managing said editor by said client;
said server passing said first client-executable code and said first schedule-related information to said client;
said client executing at least a portion of said first client-executable code to display said editor and display said first schedule-related information in said editor and to manage said editor.
1 Assignment
0 Petitions
Accused Products
Abstract
A client-server based project schedule management system comprises multiple editors accessible through a web browser to perform various scheduling tasks by members of a project. Client-executable code is generated by the server for the client, which is passed to the client along with schedule-related information for populating the respective editors. The client executes the server-generated code to display the respective editor with pertinent information populated therein, and to manage and maintain any new or updated information in response to user interactions with the editor. Rows of tasks are represented by corresponding objects, where editor elements are object attributes which are directly accessible by the respective objects. Database queries are generated by the server based on constant strings containing placeholders which are replaced with information used by the query.
-
Citations
24 Claims
-
1. A computer-implemented method for managing a project schedule with a client-server based project schedule system, the method comprising:
-
receiving a request to view an editor associated with said schedule system; in response to said request, a server accessing first schedule-related information from a database; said server generating first client-executable code for execution by a client for displaying said editor and displaying said first schedule-related information in said editor and for managing said editor by said client; said server passing said first client-executable code and said first schedule-related information to said client; said client executing at least a portion of said first client-executable code to display said editor and display said first schedule-related information in said editor and to manage said editor. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
-
23. A system comprising:
-
one or more processors; one or more memory communicatively coupled to said one or more processors; wherein said one or more memory stores instructions comprising; a first software module associated with a server constituent to a project schedule system, wherein said first module, when executed by at least one of said one or more processors, causes performance of; accessing first schedule-related information from a database in response to a request to view an editor interface associated with said schedule system, and generating first client-executable code for execution by a client for displaying said editor interface and displaying said first schedule-related information in said editor interface and for managing operation of said editor by a client of said project schedule system; a second module associated with said client, wherein said second module, when executed by at least one of said one or more processors, causes performance of; displaying said editor interface and said first schedule-related information in said editor interface and managing operation of said editor based on said first client-executable code, and receiving second schedule-related information from a user via said editor interface; a third module associated with said server, wherein said third module, when executed by at least one of said one or more processors, causes performance of; receiving said second schedule-related information from said client, and storing said second schedule-related information in said database; and a fourth module associated with said server, wherein said fourth module, when executed by at least one of said one or more processors, causes performance of; accessing said second schedule-related information from said database in response to said client requesting a web page associated with said editor, and generating second client-executable code for execution by said client for displayings said web page associated with said editor and displaying said second schedule-related information in said web page associated with said editor. - View Dependent Claims (24)
-
Specification