Integration of command surfaces with multiple active components

FIELD: physics, computation hardware.

SUBSTANCE: invention relates to integration of command surfaces with active components on web-page. Command section is integrated on web-page with first component associated with first application and second component associated with second application and not associated. Note here that said command section comprises user-selected execution commands. Access to first list for first component is executed, said list identifying the command instruction section. First component is registered to allow reception notification therefrom. Access to second list for second component is executed, said list identifying the command instruction section. Second component is registered to allow reception notification therefrom. Then, defined is whether one of the commands included in said list is activated. Defined is when the component should receive the command to define when second component should receive the command. Command is directed to first component for processing when this is defined to direct the command second component processing when this is defined.

EFFECT: decreased time of access to active commands on web-page.

20 cl, 4 dwg

Prior art

In order to accommodate the various components supported web platforms and applications, many online products and services realized by the development of user interfaces with distributed teams. These user interfaces have multiple, separate command surface so that each component in the application has its own set of commands. Each application is well integrated with associated with them component in the user interface. For example, a web page may include two distinct components, which contain similar functionality (namely, two different text fields), but each component includes its own command surface.

The invention

This is a brief description of the invention provided to introduce a selection of concepts in a simplified form, which further described below in the detailed description. This is a brief description of the invention is not intended to identify key features or essential features of the claimed invention and not intended for use as an aid in determining the scope of the claimed invention.

The same command surface can be related to independent the mi components and applications on the page. Components register related commands common command surface, which they will use. Each component may use an arbitrary number of commands that are associated with the same command surface. Tool management teams (Manager commands) acts as an intermediary (broker) messages between the components on the page, and General control surfaces. When a command is received that is associated with the command surface Manager command sends a command message corresponding components.

Brief description of drawings

Figure 1 shows an exemplary computing system.

Figure 2 shows a system for binding a command surfaces with multiple active components.

Figure 3 illustrates a process for associating a command surface with multiple components; and

Figure 4 shows the process for obtaining and sending commands to the components, which is obtained from the command surface.

Detailed description

Now referring to the drawings, in which identical numbers represent identical elements will be described different ways of implementation. In particular, figure 1 and the corresponding discussion are intended to provide a brief General description of a suitable computing environment in which can be implemented in the ways of carrying out the invention.

Generally, program modules include procedures, programs, components, data structures, and other types of structures that perform specific tasks and/or implement particular abstract data types. Other configurations of computing systems can also be used, including handheld devices, multiprocessor systems, microprocessor-based systems or programmable consumer electronics, minicomputers, universal computing machines and the like. Distributed computing environment can also be used where tasks are performed by remote processing devices that are linked through a data network. In a distributed computing environment, program modules can be placed on both local and remote storage devices.

Now with reference to figure 1, will be described an illustrative computer architecture for a computer 100 that is used in different variants of implementation. Although the computer 100, generally illustrated as client computing device, the computer 100 can be configured as a client, server, mobile device or any other computing device. The computer 100 includes a Central processor 5 (CPU, CPU), system memory 7, linking the random access memory 9 (RAM, RAM) and permanent memory device 10 (RAM, ROM), and a system bus 12 that connects the memory to the CPU 5. The system basic input/output, containing the basic routines that help to transfer information between elements within the computer, for example, during startup, is stored in the ROM 10. The computer 100 additionally includes a mass storage device 14 for storing an operating system 16, application programs 24, and other program modules, which will be described in more detail below.

The mass storage device 14 is connected to the CPU 5 via the controller, mass storage devices (not shown)connected to the bus 12. The mass storage device 14 and its associated computer-readable media provide nonvolatile storage for the computer 100. Although the description of computer-readable media contained in the materials of the present application, refers to a mass storage device, such as a hard disk or CD-ROM drive, CD-ROM, computer-readable media can be any available media that your computer can access 100.

As an example, and not limitation, computer-readable media may include computer storage media and data transfer environment. Computer storage media include saving the dependent and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media include, but not as a limitation, random access memory (RAM, RAM), a persistent storage device (RAM, ROM), electronically-programmable ROM (EEPROM, EPROM), electrically erasable and programmable ROM (EEPROM EEPROM), flash memory or other solid state memory technology, CD-ROM, digital multi-function disk (DVD) or other optical storage media, magnetic cassettes, magnetic tape, magnetic storage disks or other magnetic storage devices, or any other medium that can be used to store the desired information and which can be accessed by computer 100.

In accordance with the variations in implementation, the computer 100 may operate in a networked environment using logical connections to remote computers through a network 18, such as the Internet. The computer 100 may be connected to the network 18 through the device 20 of the network interface connected to the bus 12. The network connection may be wireless and/or wired. The device 20 of the network interface can also be used to connect the various other types of networks and remote computer systems. The computer 100 may also include a controller 22 I/o for receiving and processing input from other devices, including a keyboard, mouse, or electronic stylus (not shown in figure 1). Similarly, the controller 22 I/o can provide output to a display device that includes a user interface 28, a printer, or other types of output devices. The computer 100 may also be associated with data sources (not shown) via a network connection 18 and/or some other connection.

As briefly mentioned above, some software modules and data files may be stored in the mass storage device 14 and RAM 9 of the computer 100, including an operating system 16 suitable for controlling the operation of a networked personal computer, such as WINDOWS VISTA® from MICROSOFT (Microsoft Corp.) from Redmont, Washington. The mass storage device 14 and RAM 9 may also store one or more software modules. In particular, the mass storage device 14 and RAM 9 may store one or more application programs 26, such as an application 25 web browser. For example, the program 25 browser may be MICROSOFT INTERNET EXPLORER®.

The server 23 is configured to provide website services for the computer 100. As illustrated, the servo is R 23 includes software site which is configured to provide site access to which is provided by application 25 browser on the client computer 100. According to one variant of implementation, the website software, such as MICROSOFT SHAREPOINT SERVICES®, can be used to provide utilities sharing, utilities, storage and utilities management workflows that apply to the site. For example, the website can be created with components that provide users (team members) different ways of sharing documents, sharing calendar or event information, creating and discussing ideas with regards to the project and add, assign and track tasks related to the project. The website can be configured as an Internet site, extranet site and/or intranet site or any other site that is accessible to users.

UI (PI, UI) 28 is designed to provide the user with visual capabilities to browse the site and interact with the command surfaces and components on the web page. Instead of each team on the surface page was directly related to only one component on the page, the command surface can be connected in more than the one component on a page, even when the components associated with different applications. As illustrated in UI 28, the same command surface is associated with two different components (C1 and C2). Command surface can be such a command surface as Ribbon (Ribbon), a toolbar, a pie menu (pie menu), and the like. Components on the page can be linked to each other and to treat various applications. Typically, each component registers related commands command surface, so they were used by Manager 26 teams. Manager 26 teams acts as a message broker between the components on the page and the command surfaces. Each component may use an arbitrary number of commands that are associated with the command surface. For example, component C1 can use three commands command surface, and C2 can use two of these commands. Component (e.g., C3) can be a component that is not visible to the user. For example, component C3 may be a spelling checker, which is registered to be informed of the save command, which is associated with the command surface. Components can also attach or detach command from the command surface, or dynamically change the number of teams during the implementation of the. The component can register the command so that it was focused team or global team. When the team registered component as a global team, even when the component does not have the current focus, he still receives the command when the command is activated on the command surface. When the team is registered as a focused team, then the component receives the notification of the team when he has the focus at the present time. When a command is received that is associated with the command surface Manager 26 command sends a command message to the appropriate components. The job Manager 26 commands are described in more detail below.

Figure 2 shows a system for binding a command surfaces with multiple active components. As illustrated, system 200 includes page 205, the component 210, the component 212, the component 214 and the Manager of the 26 teams, which includes Manager 220 teams, Manager 225 focus, Manager 230 cancellation and Manager 235 command surfaces.

As described above, the Manager of the 26 teams manages the interaction between the command surfaces and various components. Although Manager 220 teams, Manager 225 focus, Manager 230 cancellation and Manager 235 command surfaces are shown as integrated into Manager 26 teams, some heaven or all of their functionality may be located outside Manager 26 teams.

Components on page 205 may submit multiple applications and controls that are placed on web sites, including web services and web applications. For example, advanced text editors, clock, table, modules, forms, data, drawing tools, and the like are components that may be contained on the page.

Any component that you want to use a common command surface, registered Manager 26 teams. After registration or during the registration component specifies commands that he wants to be informed when they will occur on the command surface. According to one variant of implementation, the commands given to the Manager of the teams in the form of a list of one or more commands (i.e. commands 211, 213 and 215). The component can set a command so that it was a global command or focused team. The global command is sent to the component Manager 26 teams, even when this component does not have focus. Thus the component can respond to the command on the command surface, even when this component is not active. Focus command is sent to the component only when the component has focus. The component can attach command or disconnect command from the command surface at any time. For example, the comp is element can change the active command, available in command of the surface based on the application state. The component can also specify whether he can or not to get the focus.

Manager 26 teams may periodically, or as a side effect of certain events on the page to poll the registered components on behalf of the command of the surfaces in order to determine the status of each command that they place. In one embodiment, this state of the team consists of whether the team is currently permitted or prohibited in the component, and the aggregate of the other state information associated with the team. For example, the bold button can query to determine whether it is currently enabled or not, in addition to being active if the button on the command surface. According to one variant of implementation, when the command received at the command surface (i.e. the user performs a mouse click on the team), Manager command sends a command Manager 220 commands.

Manager 220 teams interacts with the registered components on the page. In this example, the dispatcher 220 commands configured to interact with the component 210, component component 212 and 214. The command Manager is configured to send commands to components to query the status of the commands and will determine what, whether the team. The command Manager maintains a record of the command handlers registered for commands, and uses this information to route commands and messages to the components. According to one variant of implementation, the dispatcher 220 may send other messages to the components and/or additional information along with directed teams. For example, the information may relate to the data used in the processing of commands, status information and the like. Team Manager commands can also be sent via Manager 225 focus as through an intermediary, to help ensure that the relevant components of the received command. According to one variant of implementation, the Manager's focus is located between the main Manager 220 commands and components. In this embodiment, focused teams registered Manager 225 focus, and Manager 225 focus, in turn, registers them in the main Manager 220 teams. When the command is sent via the master Manager 220 teams Manager 225 focus, Manager 225 focus can then be routed command according to which component, if any, has the focus.

Manager 225 focus manages the selection of components on page 200. Manager 225 Fok the resources configured for tracking components, currently have the focus on the page (active components). When an event occurs on the page (for example, the user performs a mouse click), the component that detects the event, may request the Manager 225 of focus so he became an active component. Manager 225 focus then will report the previous active component of the assignment of focus. Manager 225 focus will then notify the requesting component that he now has the focus. When the selection will occur outside of the active component on the page, Manager of focus can send a message to the components that now there are no active components, so each component can take the focus. When the component receives focus, Manager 26 teams sends a notification to the component, so that it can query for the current focus. Similarly, the component loses focus, can be informed so that he can give the current focus. According to one variant of implementation, when another component requests focus, component, on which there was a focus is requested on the assignment of focus when using Manager 26 teams.

Manager 230 undo is used to undo/redo (undo/redo) commands that are executed. Manager 230 cancel monitors commands, which are executed, and when requested from the s/reissue the command, it helps to ensure that the appropriate component receives a request to cancel or re-execute the command.

Manager 235 command surfaces monitors the command surface(ti), which is associated with the components on the page. Command surface can be any type of command surfaces, such as Ribbon (Ribbon), a toolbar, a pie menu (pie menu), and the like. Though the command surface controls processing of the commands that are associated with it. Instead, when the command is activated on the command surface Manager 26 sends commands command corresponding components on the page. According to one variant of implementation, the command surface Manager 235 command surfaces support messages to update the control state of the commands that are associated with them, and to enable/disable commands for the components. Manager command surfaces also includes specific methods for using the command surface. For example, there may be provided a method in the control Ribbon (Ribbon) to display a previously invisible contextual bookmarks. Initialization command surface Manager 26 teams, it draws its contents by default. According to one variant of implementation, the data associated with the command surface is s, are stored in an XML file.

Although not illustrated in figure 2, other functionality may be included in Manager 26 teams. For example, can be implemented by other managers. For example, the task Manager can be programmed to process work requests related to the components.

Refer now to figure 3, which describes an illustrative process for binding a command surface with multiple components.

While reading the discussion of the procedures presented in the materials of this application, should be taken into account that the logical operations of various embodiments are implemented (1) as a sequence implemented by the computer acts or program modules running on a computing system, and/or (2) as interconnected electronic logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance requirements of the computing system that implements the invention. Therefore, illustrates the logical operations, the components of the embodiments of described in materials of this application, are listed under different names as operations, structural devices, acts or modules. These operations, structural devices, acts or modules may be implemented in software is mnom security firmware (firmware) software, digital logic, special purpose or in any combination thereof.

After the operation start, the process 300 goes to operation 310, where a is initialized Manager commands. Manager commands acts as a message broker between the components on the page and the command surfaces. According to one variant of implementation, Manager command initializes the command Manager, Manager focus, Manager undo command and the surface(s), which must be shared between the components on the page.

Moving to operation 320, the components on the page are registered Manager commands. Each component on the page to which you want to use a common command surface, registered commands.

Following to operation 330, components register command, about which they want to be notified when they occur on the command surface. The component can register to receive focused teams or global teams. When the team registered component as a global team, then even when the component does not have the current focus, he still receives the command when the command is activated on the command surface. When the team is registered as a focused team, then this component receives uvedomlenie team only when it has the focus at the present time. The component also provides methods of processing commands when the component is invoked on the command.

Turning to operation 340, the command is initialized surface(s), which must be connected with components. Command surface can be any type of command surface, such as Ribbon (Ribbon), a toolbar, a pie menu (pie menu), and the like. Command surface support messages to update the control state commands that relate to the components, and to enable/disable commands for the components. Manager command surfaces also includes specific methods for using the command surface.

The process then follows to the end of the operation and returns to processing other actions.

Figure 4 shows the process for obtaining and sending commands to the components, which is obtained from the command surface.

After the operation start, the process 400 goes to operation 410, where the team are from the command surface. When the command is activated on the command surface, the redirect command Manager commands, which handles routing commands to the respective components.

Moving to operation 420, determine the components that should get sent the command. It is to rule, determining where to send a command based on what components registered to receive notification commands, as well as on the current focus of the component. For example, as described above, some components require information about the team whenever it happens, while other components require information only when they have focus.

In operation 430 may be clarified whether certain components to process the command. Before sending commands to the component(s), Manager commands can query the component(s)to determine if you are ready each component to process the command.

For each component, which is ready to process the command, the process moves to operation 440 where the command is directed to these specific components.

Moving to operation 450, retain record against teams that have been made on the page, and what components have been notified. Thus, when requested cancellation/re-execution of a command, this helps to ensure that the correct component receives a request to cancel or re-execute the command.

The process then follows to the end of the operation and returns to processing other actions.

The above detailed description, examples and data provide a complete description of the manufacture and use of the project structure of the invention. Since many embodiments of the invention may be made without departing from the scope and essence of the invention, the scope of the invention is defined by the appended below by the claims.

1. A method of binding a command section with active components on the web page containing phases in which:
tie on a web page, the command section to the first component, which is associated with the first application and the second component, which is associated with the second application and is not associated with the first component, while the command section includes user-selectable command for action;
access to the first list of commands for the first component that identifies included in the command section command, to receive notifications from which the first component is registered, and access to the second list of commands for the second component that identifies included in the command section command, to receive notifications on which is recorded the second component with the first component and the second component can register for each of the commands in the command section;
tie each of the commands in the first command list to the first component and bind each of the commands in the second command list to the second component;
determine when the and activates one of the teams included in the command section;
determine, when the first component should receive the command, and determines, when the second component should receive the command; and
send a command to the first component for processing when it is determined, and send the command to the second component for processing, when it is defined.

2. The method according to claim 1, wherein when identifying the first command list and the second list of commands query the first component to obtain a first list of commands and poll the second component to obtain a second list of commands, while the first and second components can alter the registration of their commands.

3. The method according to claim 1, in which each of the commands in the first command list and the second list command is a global command or focused team, a global team corresponds to the fact that the team is sent regardless of the current focus on the component, and focused the team corresponds to the fact that the command is based on the current focus on the component.

4. The method according to claim 3, further comprising stages, which are:
determine that the first component must receive a command when the command is bound to the first component as a global command or as a focused team, when the first component has the current focus;
determine that the second components is t should get a team when the command is bound to the second component as a global team, when the first component has the current focus.

5. The method according to claim 3, additionally containing a stage at which change the current focus in response to receiving the request from the first component or the second component, the focus changes, or other instructions on the web page.

6. The method according to claim 4, in which before sending commands to the first component for processing when it is determined, before sending commands to the second component for processing when it is determined that additional poll the first component before sending commands to determine how ready is the first component to process the command and poll the second component before sending commands to determine how ready is the second component to process the command.

7. The method according to claim 4, further containing a stage on which to store commands that have been processed, and when initiated the cancellation process, inform each of the components of the command, the execution of which is subject to the cancellation.

8. The method according to claim 5, in which when associating each of the identified command lists each of the components bound to the command section, each component registers a command for activation.

9. The method according to claim 8, in which the first component and the second component can ukreplyat is bound to commands at runtime.

10. The method according to claim 8, in which the first application associated with the first component and the second application associated with the second component are different applications.

11. Machine-readable data carrier, on which are executable computer instructions to associate a command section with active components on the web page containing:
initialization means control command, which is configured to act as an intermediary between a command section that is bound to the first component and is not associated with the second component on the web page, while the command section includes user-selectable command for action;
accessing a first list of commands for the first component that identifies included in the command section command, to receive notifications on which is recorded the first component, and the implementation of the access to the second list of commands for the second component that identifies included in the command section command, to receive notifications on which is recorded the second component with the first component and the second component can register for each of the commands in the command section;
check each of the commands in the first command list and the second list of commands medium spans the PTO control commands;
determining when the first component must be activated in the command section, and determining, when the second component should receive the command; and
the direction by means of control commands commands to the first component for processing when it is determined, and the direction by means of control commands commands to the second component for processing, when it is defined.

12. Machine-readable data carrier according to claim 11, further containing a registration of the first component and the second component by means of control commands and the querying of the first component and the second component for receiving the first command list and the second list of commands.

13. Machine-readable data carrier according to claim 11, additionally containing the identification of each of the teams in the first list of commands and each command in the second command list as a global command or focused team, a global team corresponds to the fact that the team is sent regardless of the current focus on the component, and focused the team corresponds to the fact that the command is based on the current focus on the component.

14. Machine-readable data carrier according to claim 11, additionally containing the querying of the first component and the second component to determine the ready if the first component to process the command and to determine, is the second component to process the command.

15. Machine-readable data carrier according to claim 11, additionally containing the save commands that have been processed, and, when initiating cancellation, informing each of the components of the command, the execution of which is subject to the cancellation.

16. Machine-readable data carrier according to claim 11, further containing otsasyvanie one or more teams that are registered by means of control commands at runtime.

17. A system for binding a command section with the components on the web page containing:
processor, memory, and computer-readable media;
working environment, stored in a machine-readable carrier and executable in the processor;
a display configured to display a web page, which includes a command section that includes user-selectable commands; the first component that is associated with the first application, and is not associated with the second component, which is associated with the second application; and
tool management teams, configured:
to receive the registration request from the first component and the second component for linking with the command section;
take the first list of commands from the first component and the second list of commands from the second opponent, each of the first commands and the second commands list identifies the commands included in the command section;
to register the first component at each of the commands in the first command list and register of the second component at each of the commands in the second command list;
to get from the command section the command when it is activated, and to determine when the first component should receive this command, and to determine when the second component should receive the command; and
to send a command to the first component for processing when it is determined, and to direct the command to the second component for processing, when it is defined.

18. System 17, further implements the classification of each of the teams in the first list of commands and each command in the second command list as a global team or as a focused team, a global team corresponds to the fact that the command must be sent regardless of the current focus on the component, and focused the team corresponds to the fact that the command should be sent based on the current focus on the component.

19. System 17, additionally implements an opinion poll before sending commands to the first component for processing when it is determined that the first component to determine how ready is the first component of the processing is ü team and an opinion poll before sending the command to the second component for processing when it is determined that the second component to determine how ready is the second component to process the command.

20. System 17, further implements the save commands that were processed during the initiation of the procedure cancel each component shall be informed of the commands, the execution of which is subject to the cancellation.