KR102545025B1 - Persistent viewports - Google Patents

Abstract

This persistent viewport architecture provides the user with a persistent, correctly positioned viewport as the collaborating document is updated. The architecture identifies and uses the user's interest-elements within the document's content to determine and recalculate the correct position of the user's viewport. This architecture tracks the topmost element of the content (or section of content) in the viewport and uses this topmost element as the reference element. This top-level element can be one or more of paragraphs, headings, text strings, and images. When the underlying document is updated, the viewport performs the reference element search and, after finding the reference element, adjusts the viewport's X and Y coordinate offsets so that the element of interest is within the viewport.

Description

Techniques for providing persistent viewports {PERSISTENT VIEWPORTS}

If the document size (e.g., length) exceeds what the device's physical screen can display, user interaction control elements such as scroll bars can be introduced to create a viewport through which a viewport can be created. You can view and read the document. When the user moves the position of the scroll bar's scroll thumb control element, the document appears to the user as if it is moving through the viewport, but the user is essentially moving the viewport across the document. This is one way an operating system or application can facilitate navigation of documents that are larger than the device's display can accommodate. This technique works in a single-user environment, but becomes problematic in multi-user collaboration tool environments where multiple users may edit the same document through corresponding user viewports.

The following provides a simplified summary to provide a basic understanding of some of the novel implementations described herein. This summary is not a comprehensive overview and is not intended to identify key/critical elements or to delineate the scope of the invention. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

The present persistent viewport architecture provides a persistent, correctly-positioned passive user viewport to passive users (and active users) when the virtual document is being updated. This architecture can also be applied to collaboration sessions. The present architecture identifies and uses the user's interest-elements within the document's content to determine and recalculate the correct position of the passive user's viewport. Also, the present architecture tracks the topmost element of the content (or section of content) from the passive user viewport and uses this topmost element as the reference element. This top-most element can be, for example, one or more of paragraphs, headings, text strings, and images.

When the underlying virtual document is due to be updated, the passive user viewport performs the reference element search and, after finding the reference element, adjusts the X and Y coordinate offsets of the passive user viewport so that the interest-element is within the passive user viewport. .

The persistent viewport architecture may be implemented as a system, wherein the system is an element component configured to identify an interest-element within the content of a virtual document, wherein the interest-element is (e.g., a collaboration session). the element component, present within a passive user viewport of the virtual document being presented to the passive user (of a session); an update component configured to receive and process updates of the virtual document from an active user (eg, of the collaboration session); and a viewport component configured to move the passive user viewport such that the interest-element is maintained within the passive user viewport of the passive user, regardless of any position change of the content due to the update by the active user. component).

The present persistent viewport architecture may be implemented as a method, the operation of identifying an element of interest within the content of a virtual document, the interest-element on a passive user system (e.g., of the collaboration session). the act of identifying, present within a passive user viewport of the virtual document being presented to; receiving updates about content of the virtual document from an active user system (eg, of the collaboration session); and maintaining the interest-element within the passive user viewport of the passive user system regardless of any positional change of the content due to the update by the active user system.

The present persistent viewport architecture may be implemented as another system as a means for identifying interest-elements within the content of a virtual document, where the interest-elements are, for example, the passive user system of a collaboration session. said means for identification, being within a passive user viewport of said virtual document being presented thereon; means for calculating the position of the passive user viewport relative to the interest-factor; means for identifying a reference element within content of the passive user viewport of the passive user system; means for receiving updates of the virtual document from an active user system of the collaboration session; and means for moving the passive user viewport so that the element of interest is included within the passive user viewport of the passive user system, regardless of any change in position of the content due to the update by the active user system. do.

To the accomplishment of the foregoing and related objectives, certain exemplary aspects are described herein in conjunction with the following description and accompanying drawings. These aspects represent the various ways in which the principles disclosed herein may be practiced and all aspects and equivalents thereof fall within the scope of the claimed subject matter. Other advantages and novel features will become apparent from the detailed description that follows when considered in conjunction with the drawings.

1 shows a system according to the disclosed architecture.
2 shows a more detailed diagram of elements of content that may be considered for viewport persistence in accordance with the disclosed architecture.
3 illustrates another implementation of a system of the disclosed persistent viewport architecture.
4 shows a method according to the disclosed architecture.
5 shows an alternative method according to the disclosed architecture.
6 shows another alternative method according to the disclosed architecture.
7 shows a block diagram of a computing system implementing a persistent viewport in accordance with the disclosed architecture.

When a document is longer than the device's physical screen can display, a scroll bar may appear to create a viewport. When the user moves the scroll position, the user essentially moves the viewport across the document. While this approach is commonly used, this approach can be used, for example, in collaborative applications, services and/or tools, where multiple users are editing the same document at the same time, or the content of a document is being read or edited by a user. Not used if changed. It is difficult to maintain the position of the viewport while some other users are updating the content of the same document.

Some existing applications keep the relative offset from the bottom of the document (virtual document as represented) measured in pixels as X and Y coordinates relative to the user's viewport. If the document is updated in any way, the X and Y pixel offsets become outdated. In this existing implementation, where the X and Y coordinates are relative to the bottom of the document, changing the length of the document (by an active (editing) user adding, attaching, and/or deleting content) is a passive user's effort. It can affect the viewport experience. This process applies the same way in legacy systems, even when the X and Y coordinates are relative to the top of the document (in this case, the change occurs in the part of the document that precedes the currently passive user's viewport). That is, if the length of the document changes (eg, through a dynamic web page update or some other user editing the same page), this causes the existing user's viewport to be positioned incorrectly. That is, the part of the document that the original user was reading no longer exists at the X and Y coordinates, which means that some other user may have updated the part (e.g. more text, more images, content such as text, images, headings, etc.) removed) was added. This viewport clutter can confuse (distract) the user, such that the content the user was viewing just before jumps to a new location in the viewport, becomes completely invisible in the viewport, or appears to jump to another location within the document.

The disclosed architecture solves this problem by persisting (or maintaining) the viewport over (or over) the content currently being viewed even after the document is updated by another user. This capability enables simultaneous collaboration over a network (eg, the Internet). Instead of using the X and Y pixel offsets to the top left corner or bottom of the document to determine the user's viewport, the persistent viewport architecture uses interest-elements within the content to quickly determine the viewport's position relative to the content currently being viewed. recalculate accordingly.

The persistent viewport architecture tracks the topmost element of the viewport as the base element. These elements can be at least one of paragraphs, headings, images, text strings, or other suitable content structures. When the document is updated, the viewport searches for this existing element in memory, finds the reference element on the virtual document, and adjusts the viewport's X and Y offsets so that the element-of-interest or reference element is still within that viewport. .

The present architecture can be applied to any kind of document (eg HTML (Hypertext Markup Language) pages or any other document, eg, under collaborative processing). While retrieval for an element-of-interest may be through a hash set with elements stored in memory (eg, a cache), browsers and any suitable office applications that facilitate user collaboration may incorporate the presently disclosed architecture. there is.

Reference is now made to the drawings, in which like reference numbers are used throughout the drawings to indicate like elements. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. Obviously, however, new implementations may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate a description thereof. This invention includes all modifications, equivalents and alternatives falling within the spirit and scope of the claimed subject matter.

1 shows a system 100 in accordance with the presently disclosed architecture. System 100 operates as part of a collaboration service that enables collaboration sessions 102 of active and passive users. (Although described in the context of document collaboration, it should be understood that the system also applies to non-collaborative implementations.) Thus, in this head-to-head example (one passive user and one active user), , system 100 includes a passive user system 104 in passive mode and an active user system 106 in active mode, although it should be understood that such a collaboration session may include more than two users.

An active user is currently editing the "active" instance of a virtual document in order to effect a change or update of content, whereas a passive user is not editing a "passive" instance of a virtual document and is actively editing during the editing process by the active user. You are simply viewing the same or a different instance of the virtual document's content. The same applies to cases where a passive user becomes an active user and an active user becomes a passive user. The functionality described according to the passive user system applies equally to the active user system 106, such that the persistent viewport functionality works simultaneously for all users in a collaboration session working on the same virtual document. Thus, active and passive modes can be switched quickly for collaboration session users such that these active and passive modes switch depending on who is editing the virtual document locally. In such an implementation, only one user may be an active user at any given point in time, but there may be more than one passive user for every active user.

For purposes of this description, certain items within the passive user system 104 are referenced “P,” and specific items within the active user system 106 are referenced “A.” For example, an instance of a virtual document in passive user system 104 will include a “-P” suffix, and a virtual document in active user system 106 will include a “-A” suffix.

Continuing the description of the passive user system 104 , a collaboration session 102 involves editing of a virtual document 108 . The instance of virtual document 108 on passive user system 104 is designated as virtual document 108-P, and the virtual document 108 on active user system 106 is designated as virtual document 108-A. Similarly, virtual document 108 includes content 110 designated as content 110-P on passive user system 104 and content 110-A on active user system 106.

During the passive mode for a passive user 112 on the passive user system 104, an element component 114 provides an element-of-interest (EOI) within the content 110-P of the virtual document 108-P. (116). An interest-element 116 is shown in a passive user viewport 118 (also designated VIEWPORT-P) as part of a collaboration session 102 .

EOI 116 may be any one or more of elements E in content section CONTENT1-P of content 110-P of passive user viewport 118. The same elements are present in the same content section (CONTENT1-A) of content 110-A of active user system 106; However, the active user system 106 need not identify the EOI in section CONTENT1-A when in active mode. However, in another implementation, elements may also be tracked when in active mode to prepare active user 120 for a passive mode state.

In accordance with the collaboration session 102, the content 110-A in the virtual document 108-A of the active user system 106 is transferred by the passive user 112 to the virtual document 108-A of the passive user system 104. P) can be viewed as content 110-P. Active user 120 may move active user viewport 122 to peruse content 110 -A in relation to portions to be edited. The passive user viewport 118 may not be synchronized with the content position of the active user viewport 122 within the virtual document 108-A. Thus, active user 120 may view sections or regions of content 110 -A that passive user 112 is not viewing, and vice versa.

Here, active user 120 creates update 124-A in section 126-A of content 110-A. Creating updates may include, for example, actions such as moving content elements, deleting content elements, attaching and inserting new elements. This action creates an update signal from active user system 106 to all passive user systems (eg, passive user system 104).

Updates 124-A by active user 120 within content section 126-A (e.g., a paragraph of text) appear and appear within active user 120's viewport 122 as edits are made. It can be. An update component 128 processes the update signal and operates on the passive user system 104 to update the update 124-A into the content 126-P of the virtual document 108-P (124-P). ) can be provided and configured to insert as.

If passive user 112 moves passive viewport 118 over sections or regions of content 110-P that do not include the portion of content 126-P to which update 124-P has been applied. There may be. Thus, updates 124-P as propagated to virtual document 108-P occur outside of passive user viewport 118 where passive user 112 is viewing content 110-P. This change in document length by inserting an update may also, for example, result in active user 120's deletion of a portion (eg, an image) of content 110-A in virtual document 108-A or content It may also be caused by moving part of 110-A to another area of virtual document 108-A.

However, the present persistent viewport architecture may be updated (124) in order not to interfere with actions (eg, viewing, reviewing, etc.) -P) to maintain the position of the passive user viewport 118 on a portion of the content 110-P during and after being applied to the passive user virtual document 108-P.

This viewport persistence is achieved by the element component 114 identifying the interest-element 116 within the content section CONTENT1-P that the passive user 112 is viewing in the passive user viewport 118. The interest-element 116 can be any element within the content section CONTENT1-P. Identification of the interest-element 116 identifies the content section CONTENT1-P that will ultimately be kept within the passive user's field of view. The element component 114 is also configured to identify a reference element (RE) 130 within the content of the passive user's passive user viewport 118 . The standard element 130 includes, for example, at least one of a paragraph, a header, an image, or a text string.

To provide a positive viewing experience for passive user 112, element component 114 places the topmost element of content (CONTENT1-P) in passive user viewport 118 of passive user system 104 on base element 130. It is further configured to identify as. Point of view component 132 is a passive user viewport of passive user 112 ( 118) is provided and configured to move the passive user viewport 118 to keep the interest-element 116 within. The viewport component 132 is configured to calculate the position of the passive user viewport 118 relative to the element-of-interest 116 . Viewport component 132 is configured to move passive element viewport 118 to include a predefined section of content 110-P (eg, CONTENT21-P) in which interest-element 116 resides. .

The element component 114 is configured to update and maintain the hash set and content elements in memory based on changes in the view of the virtual document 108-P within the passive user's 112's passive user viewport 118. .

Viewport component 132 is configured to move the viewport (passive user viewport 118 ) to include a predefined section of content (CONTENT1-P) in which interest-element 116 resides. In one embodiment, the viewport component 132 is configured to compute the position of the viewport (passive user viewport 118) relative to the element-of-interest 116. In another embodiment, viewport component 132 is configured to calculate the position of the viewport (passive user viewport 118 ) relative to reference element 130 . Such positioning may include moving the top boundary of the passive user viewport 118 above the reference element 130, where, for example, the reference element 130 is a text string of the first sentence of a paragraph, or The reference element 130 is then an image included within the passive user viewport 118, or the reference element 130 is heading text, such as a topic header in a multi-topic word processing document.

Viewport persistence has the technical effect of improving user efficiency by maintaining the user's focus on the work within the passive user viewport 118 during update propagation from the active user system 106 . As such, the passive user 112 does not have to re-navigate the virtual document 108-P to return to the previously viewed content.

In other words, system 100 includes element component 114 configured to identify an element-of-interest 116 within content 110-P of virtual document 108-P. The interest-element 116 is currently represented within the virtual document 108-P to the passive user 112 through the passive user viewport 118 of the passive user system 104 of the collaboration session 102. . The update component 128 is provided and configured to receive an update 124 -A of the virtual document 108 -A from the active user system 106 of the collaboration session 102 . The viewport component 132 is responsible for any changes in the position of the content 110-P resulting from the propagation of the update 124-A by the active user system 106 to the passive user system 104 (or in the virtual document). length change), it is provided and configured to move the passive user viewport 118 to keep the interest-element 116 within the passive user viewport 118 of the passive user system 104.

The element component 114 is configured to identify a reference element 130 within the content CONTENT1-P of the passive user viewport 118 of the passive user system 104 . The reference element 130 may include at least one of a paragraph, a heading, an image, or a text string. Element component 114 is configured to identify one of a number of possible top-level elements of content CONTENT1-P within passive user viewport 118 of passive element system 104 as said reference element 130 .

The element component 114 generates a set of hashes in memory and content elements (or content and to update and maintain element tags or identifiers of elements.

Viewport component 132 is configured to move the viewport (passive user viewport 118 ) to include a predefined section of content (CONTENT1-P) in which interest-element 116 resides. The viewport component 132 is configured to calculate the position of the viewport (passive user viewport 118 ) relative to the element-of-interest 116 .

It should be appreciated that all computing systems in collaboration session 102 may include the same persistent viewport components (eg, element component 114 , update component 128 , and viewport component 132 ). As such, these components operate on these passive user systems to enable a persistent viewport, while updates are propagated by the active user system to the passive user systems.

In one embodiment, and as described above, an active user mode of operation for collaborative processing may be initiated simply by one user editing the virtual document 108, such that this operation is automatically performed by other users passively. users, whereby these passive users are not allowed to edit at the same time as the active user is editing.

However, in another implementation, the collaboration service may process concurrent updates from multiple “active” users of a collaboration session, but in this case, in order to eventually complete updates to the virtual document 108. Updates can be queued sequentially. For example, user groups (eg pairs) may be assigned to work on specific content sections of virtual document 108 . In this case, the architecture maintains a view in each viewport of each of the passive/active group users (pairs), as described herein. In this more "active" implementation, the inputs and/or active/passive modes are "asynchronous", unlike a single active user and the rest of the session users as passive users being implemented synchronously at any given time. into" and can occur at high speed.

When an active user 120 performs an update 124-A and this update results in an adjustment of the passive user viewport 118, the passive user 112 is notified that the passive user viewport 118 has or will be adjusted. 140 (either with or prior to the update 124-P) and this notice may be displayed. Notification 140 may also provide an option to jump directly to the location of update 124-P within virtual document 108-P in active user viewport 118 and view said update 124-P. can For example, if active user 120 is pasting a large block of text, passive user content 110-P is adjusted, causing passive user 112 to jump to the position of the active user's viewport (viewport will also receive a notification 140 that allows the passive user 112 to view the content just pasted (by synchronizing them).

Notification 140 also provides an opt-in option allowing immediate insertion of passive users into virtual document 108-P or immediate insertion of passive users into virtual document 108-P. A forbidding opt-out option may be presented to the passive user 112. If an active user 120 (active user system 106) chooses to opt-in (accept) an update 124-A, the passive user 112 will receive an update 124 via the passive user viewport 118. -P) can be detected automatically. If opting out, this may temporarily delay the passive user's insertion into the virtual document 108-P. When this insertion is delayed, e.g., for the passive user's final input into the virtual document 108-P, the update 124-A from the active user system 106 is stored within the passive user system 104. can be queued.

The notification 140 may be displayed within the passive user viewport 118, and outside the passive viewport 118, it may simply be presented as a sound or any other suitable form of media indicating that an update has been received or is ready to be inserted. there is.

2 shows a more detailed diagram 200 of elements 202 of content 110-P that may be considered for viewport persistence in accordance with the presently disclosed architecture. Here, the virtual document 108 -P includes an image 204 , a heading 206 , a first paragraph 208 and a second paragraph 210 . Other elements of the content 110 -P may be part of the virtual document 108 -P and are outside the passive user viewport 118 . In one embodiment, an interest-element may be identified as the largest portion of the content 110-P within the virtual document 108-P, where the largest portion may be defined according to the number of pixels per area. Thus, in one case, the interest-element may be, for example, image 204 or first paragraph 208 . Also, the interest-factor may be a criterion factor. Here, image 204, which is the largest in pixel area, may also be the reference element. Alternatively, image 204 may also be the reference element, since image 204 is the topmost element in passive user viewport 118 .

There may also be cases where the interest-element is a string of text 212 within the content 110-P. However, since image 204 is the topmost element in this example, the element of interest is not the topmost element. However, by identifying image 204 in the topmost element, the string of text 212 can still be maintained within viewport 118 .

The dimensions of the passive user viewport 118 may also affect whether a particular region or portion of content 110 -P is within the passive user viewport 118 . An application that creates a passive user viewport 118 may automatically define the size of the passive user viewport 118 . Additionally, certain devices (eg, handheld devices, desktop devices, etc.) may also affect the size of the passive user viewport 118 . For example, a smartphone's (active or passive) viewport is typically much smaller in dimension than a desktop computer's (active or passive) viewport. In the case of a smartphone, the viewport may actually expand to the full display dimensions to enhance the ability of a passive user 112 to view content, whereas a desktop computer's viewport may be much smaller than a desktop computer's display. It allows the passive user 112 to still see well enough.

In other implementations, rather than selecting the largest portion within the content (eg, image 204 ) as a factor of interest or criterion, the user may pre-identify the factor of interest and/or criterion. A user may select a particular portion within the content (eg, an image) to remain within the passive user viewport at any point in time regardless of updates by other users. Accordingly, element component 114 may be configured to allow passive users to select elements of interest and/or even reference elements. In this case, an active state for each identifiable and independent piece of content that a passive user can interact with to tag or mark that portion of content as an interest-factor and/or criterion factor. Of selectable tag objects 214 may be provided. Accordingly, any updates entered by other users will not affect the passive user viewport 118 in any way that prevents the passive user from viewing the tagged content. Tagged content can be placed within the passive user viewport 118 as the topmost element (passive user activity is below the topmost element), in the middle (passive user activity is above or below the centered element), or even It is automatically represented as the bottommost element (passive user activity is above the bottommost element).

Other ways to identify elements of interest and/or criteria include, for example, highlighting (or underlining, bolding, annotating, etc.) text strings, paragraphs or sections of text, and sections of paragraphs. Likewise, it may be to apply a commonly known editing/commenting process to the content. User input enabling such identification may be, for example, by voice command and/or input device control. If the user is (passively) interacting extensively (e.g., based on the viewer's dwell time) with a particular piece of content, this is interpreted as the user choosing to keep that content within the passive user's viewport. It can be.

3 illustrates another implementation of the system 300 of the disclosed persistent viewport architecture. In this example implementation, rather than the architecture persisting the passive user's viewport in response to updates made by the active user (eg, in a collaboration session), the architecture allows the active user (leader) to It operates in a leader-audience mode influencing the content to be viewed by passive users (audience).

Here, the leader 302 provides a viewport (not shown) of the audience users (through the leader viewport 304-L ("L" is for the leader)) of the leader computing system 312. Directs presentation virtual contents 310-L to a specific leader element 306-L of presentation content 308-L. Thus, in this case, the leader 302 (similar to the active user 120) presents the presentation content 308-L to an audience of (passive) users. Audience users may be given the flexibility to peruse the leader presentation virtual documents 310-L within an audience user viewport (not shown) during the presentation, while the leader 302 is important at that time. By directing the audience's attention to the content it deems appropriate, the reader 302 can ensure that the attention of the audience user(s) is focused on specific portions of the presentation content 308-L.

Accordingly, reader 302 may tag or simply click on a portion of the content (eg, first paragraph 208 ), which click and/or tag action may then be performed by element component 114 , on the portion or This can be interpreted to direct all audience viewports to the tagged content (e.g., first paragraph 208).

Additionally, this functionality allows the reader 302 to jump around the presentation virtual documents 310-L, so that the reader 302 instantly presents content and/or pages that audience users want to see in the audience viewport. can tate Thus, such a presentation may be realized through a user computing device (eg, smart phone, tablet, laptop, etc.) rather than a typical large screen used in front of an audience.

The update component 128 then enables the reader 302 to further update the presentation virtual documents 310-L. In response, the viewport component 132 of each audience user system moves the audience user viewport to the particular reader content location where the update was made. Alternatively, the viewport of each audience user system may be temporarily delayed (eg, several seconds) before directing the audience user viewport to the reader-specified content. This slight delay improves the user's understanding of the currently viewed content by not obstructing the user's attention to the currently viewed content.

It should be understood that in the presently disclosed architecture, certain components may be rearranged, combined, or omitted, and additional components may be included. Also, in some implementations, all or some of the components are on the client, while in other implementations, some of the components reside on a server or may be provided by a local or remote service. For example, within a client device, element component 114, update component 128, and viewport component 132 may be implemented as a single service within each client device. In a cloud implementation, one or more of these components 114, 128, 132 are implemented as a cloud service for user devices that cannot use such component(s) locally (in software and/or hardware). It can be.

In this alternative implementation, an element component configured to identify an interest-element specified by an active user (reader) within content of virtual documents associated with a presentation, wherein the interest-element is within the active user's viewport; an update component configured to process an update or tag from the active user associated with the virtual documents; and implement movement of the passive users' (eg, audience users') viewports to content associated with the active user's interest-element regardless of any positional change of the passive user's viewport by the active user. A system may be provided that includes a viewport component.

In this alternative implementation, receiving a reader-specific identification of an interest-element within the content of the virtual documents of the presentation, the interest-element specified by the reader via the reader viewport; processing the leader-specified identification via the update component and updating audience user systems with respect to the update; A method may be provided that includes moving the audience user viewports to include the interest-element regardless of any position change initiated by the audience user viewports by corresponding audience users.

The disclosed architecture may optionally include a privacy component (not shown) that allows a user to consent or not consent to revealing personal information, such as selecting or showing specific content of a virtual document. The privacy component enables authorized and secure processing of user information, such as tracking information, and personal information that may have been obtained, maintained and/or accessible. The user may be provided with notice of the collection of pieces of personal information and an opportunity to consent or disagree with this collection process. This consent can take several forms. Consent to the collection of such personal information allows users to take active steps before data is collected. In contrast, Opposing Personal Data Collection allows users to take active steps to prevent data collection before data is collected.

Included herein is a set of flow diagrams illustrating example methods for performing novel aspects of the disclosed architecture. For simplicity of explanation, while one or more methods herein, illustrated in the form of, for example, a flow chart or flow diagram, are shown and described as a series of acts, some acts may occur in a different order in such methods. It should be appreciated and understood that such methods are not limited by the order of the operations, as/or may occur concurrently with other operations than those shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all of the operations illustrated in one method are required for a new implementation.

4 illustrates a method according to the presently disclosed architecture. At 400, an interest-element is identified within the content of the virtual document. The element-of-interest is within the viewport of the virtual document presented on the passive user's system. At 402, updates to the content of the virtual document are received from the active user system. At 404, the interest-element remains within the viewport of the passive user system regardless of any positional changes of the content due to updates by the active user system.

The method may further include calculating a position of the viewport relative to the element-of-interest. The method may further include identifying a reference element within content of the viewport of the passive user system in response to the update. The method may further include identifying a top-most element in the viewport of the passive user system as a reference element.

The method may further include identifying a reference element in response to the update and adjusting an offset within the content to persist the interest-element within the viewport. The method may further include retrieving the element-of-interest within a memory storing the hash set and elements of the content. The method may further include synchronizing the update between applications of the passive user systems while maintaining the position of the element-of-interest within the corresponding viewports of the passive user systems.

The method may further include moving the position of the viewport to include the element-of-interest within the viewport. The method may further include receiving the update at a portion of the virtual document that is outside the viewport of the passive user's system. This method applies to collaborative sessions between passive users and active users updating documents under collaborative editing.

5 illustrates another method according to the presently disclosed architecture. At 500, an interest-element is identified within the content of the virtual document. The interest-element is within the viewport of the virtual document presented on the passive user's system of the collaboration session. At 502, the position of the viewport relative to the element-of-interest is calculated. At 504, a reference element is identified within the content of the passive element system's viewport. At 506, an update to the content of the virtual document is received from the active user system of the collaboration session. At 508, updates by the active user system maintain the viewport such that the interest-element is contained within the viewport of the passive user system regardless of any change in position of the content.

The method may further include identifying a topmost element within the viewport of the passive user system as a reference element. The method may further comprise adjusting the viewport according to the offset to keep the interest-element within the viewport. The method may further include synchronizing the update between applications of the passive user systems as part of a collaboration session, while maintaining the location of the interest-element within the corresponding collaboration viewports of the passive user system.

6 also illustrates another alternative method according to the presently disclosed architecture. At 600, a reader-specific identification of an interest-element within the content of the virtual documents of the presentation is received. Interest-elements are designated by the reader through the reader viewport. At 602, the leader-specific identification is processed via an update component and audience user systems are updated according to the update. At 604, the audience user viewports are moved to include the interest-element regardless of any position change initiated by the audience user viewports by the audience users in question.

As used herein, the term “component” refers to a computer-related entity, hardware, software and a combination of tangible hardware, software or software in execution. For example, components include, but are not limited to, one or more microprocessors, chip memory, mass storage devices (eg, optical drives, solid-state drives, magnetic storage media drives, etc.), computers, and portable computing and computing- It may be a tangible component such as possible devices (eg, mobile phone, tablet, smartphone, etc.). A software component is a program that runs on a microprocessor, objects (software objects that use methods to maintain the state of variables and operations), executable data structures (stored on volatile or nonvolatile storage media), modules (parts of a program). , a thread of execution (a minimal sequence of instructions that can be independently managed) and/or a program.

By way of example, both the server and the application running on the server may be components. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. The word "exemplary" may be used herein to mean serving as an example, example, or illustration. Any aspect or design described herein as “exemplary” should not be construed as necessarily preferred or advantageous over other aspects or designs.

Referring now to FIG. 7 , a block diagram of a computing system 700 implementing a persistent viewport in accordance with the presently disclosed architecture is shown. Alternatively or additionally, the functions described herein may be performed, at least in part, by one or more hardware logic components. By way of example and not limitation, example types of hardware logic components that may be used include Field-Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Products (ASSPs), System Systems (SOCs) -on-a-Chip), Complex Programmable Logic Devices (CPLDs), etc., in these components, digital and/or mixed signal and other functions may be implemented on the board.

To provide additional context for various aspects of the present invention, FIG. 7 and the discussion below are intended to provide a brief and general description of a suitable computing system 700 in which various aspects may be implemented. While the above description has been made in the general context of computer-executable instructions that can be executed on one or more computers, one skilled in the art will appreciate that new implementations may also be realized in combination with other program modules and/or as a combination of hardware and software. will recognize

Computing system 700 for implementing various aspects includes microprocessing unit(s) 704 (also referred to as microprocessor(s) and processor(s)), such as system memory 706 (on which Computer-readable storage medium (which is any physical device or material on which data can be stored and retrieved electronically and/or optically) (also referred to as magnetic disks, optical disks, solid-state drives, external memory system and flash memory drives), and a computer 702 having a system bus 708. Microprocessing unit(s) 704 may be any of a variety of commercially available microprocessors, such as single processors, multi-processors, single-core units, and multi-core units of processing and/or storage circuits. In addition, those skilled in the art will understand that the present novel systems and methods can be applied to minicomputers, mainframe computers as well as personal computers (eg, desktops, laptops, tablet PCs, etc.), handheld computing devices, microprocessor-based or programmable consumer It will be appreciated that implementations may be implemented using other computer system configurations, including electronic devices and the like, each of which may be operatively connected to one or more related devices.

Computer 702 is a data center and/or computing resource (hardware and/or software). Cloud computing services include, but are not limited to, Infrastructure as a Service (IaaS), Platform as a Service (PasS), Software as a Service (SasS), Storage as a Service (SasS), Desktop as a Service (DasS), and Data as a Service (DaaS). ), security-as-a-service (SaaS) and API-as-a-service (eg, application program interfaces) (AasS).

System memory 706 includes volatile (VOL) memory 710 (e.g., random access memory (RAM)) and non-volatile memory (NON-VOL) 712 (ROM, EPROM, EEPROM, etc.) A readable storage medium may be included. A basic input/output system (BIOS) may be stored in non-volatile memory 712 and contains basic routines that enable communication of data and signals between components within computer 702, for example, during startup. Volatile memory 710 may also include high-speed RAM, such as static RAM, for caching data.

System bus 708 provides an interface connecting system components including, but not limited to, system memory 706 to microprocessor(s) 704 . The system bus 708 can be a memory bus (with or without a memory controller) and a peripheral bus (e.g., PCI, PCIe, AGP, LPC, etc.) using any of a variety of commercially available bus architectures. ) can be any of several types of bus structures that can be further interconnected.

The computer 702 has a machine-readable storage subsystem(s) 714 and a storage interface for interfacing the storage subsystem(s) 714 to a system bus 708 and other desired computer components and circuits ( s) 716 are further included. The storage subsystem 714(s) (physical storage media) may include, for example, hard disk drives (HDDs), magnetic floppy disk drives (FDDs), solid state drives (SSDs), flash drives, and/or optical disk storage drives. (eg, a CD-ROM drive or a DVD drive). Storage interface(s) 716 may include interface technologies such as EIDE, ATA, SATA, and IEEE 1394, for example.

One or more programs and data may be stored in memory subsystem 706, machine readable and removable memory subsystem 718 (eg, flash drive form factor technology) and/or storage subsystem(s) 714 (eg, eg, optical, magnetic, solid state), the one or more programs and data may include an operating system 720, one or more application programs 722, other program modules 724 and program data 726. do.

Operating system 720, one or more application programs 722, other program modules 724, and/or program data 726 may be, for example, items and components of system 100 of FIG. It may include the items and components of diagram 200, the items and components of system 300 of FIG. 3, and the methods represented by the flowcharts of FIGS. 4-6.

Generally, a program includes routines, methods, data structures, other software components, etc. that perform particular tasks, functions, or implement particular abstract data types. All or a portion of operating system 720, applications 722, modules 724, and/or data 726 may also reside within memory, such as, for example, volatile memory 710 and/or non-volatile memory. can be cached. It should be understood that the disclosed architecture may be implemented with a variety of commercially available operating systems or combinations of operating systems (eg, virtual machines).

Storage subsystem(s) 714 and memory subsystems 706 and 718 serve as computer readable media for volatile and nonvolatile storage of data, data structures, computer executable instructions, and the like. When executed by a computer or other machine, these instructions may cause the computer or other machine to perform one or more operations of the method. Computer-executable instructions include, for example, instructions and data that cause a general purpose computer, special purpose computer, or special purpose microprocessor device(s) to perform a particular function or group of functions. Computer executable instructions may be, for example, binary intermediate format instructions such as assembly language or even source code. Instructions for performing operations may be stored on one medium or may be stored across multiple mediums, whereby the instructions may be stored on one or more computer readable storage mediums, whether or not all such instructions are on the same medium. /appears collectively on media.

Computer-readable storage media (medium), excluding the propagated signal itself, can be accessed by computer 702, volatile and non-volatile media and/or external media that can be removable and/or non-removable. includes For computer 702, various types of storage media store data in any suitable digital format. Those of ordinary skill in the art may consider other types of computer-readable media for storing computer-executable instructions for performing the novel methods (operations) of the presently disclosed architecture, such as zip drives, solid-state drives, magnetic tape, and flash. It should be understood that memory cards, flash drives, cartridges, and the like may be used.

A user may interact with the computer 702, programs, and data using external user input devices 728, such as a keyboard and mouse, as well as by voice commands realized by voice recognition. Other external user input devices 728 include a microphone, IR (infrared) remote controller, joystick, game pad, camera recognition system, stylus pen, touch screen, gesture system (e.g., eye movement, hand(s), finger body poses as they relate to (s), arm(s), head, etc.), and the like. A user may interact with the computer 702, programs and data using an onboard user input device 730, such as a touchpad, microphone, keyboard, etc., for example if the computer 702 is a portable computer.

These and other input devices are connected to the microprocessing unit(s) 704 through an input/output (I/O) device interface(s) 732 via the system bus 708, but through a parallel port, IEEE 1394 serial It may be connected by other interfaces, such as ports, game ports, USB ports, IR interfaces, short range wireless communications (eg Bluetooth) and other personal area network (PAN) technologies. The I/O device interface(s) 732 may also have a sound card and/or on-board audio processing capabilities to enable the use of output peripherals 734 such as printers, audio devices, camera devices, and the like.

One or more graphics interface(s) 736 (commonly referred to as a graphics processing unit (GPU)) may be connected to the computer 702 and an external display(s) 738 (e.g., LCD, plasma display) and/or onboard Provides graphics and video signals between displays 740 (eg, in a portable computer case). Graphics interface(s) 736 may also be fabricated as part of a computer system board.

Computer 702 may operate in a networked environment (eg, IP-based) using one or more networks and/or logical connections through wired/wireless communication subsystem 742 to other computers. Other computers may include workstations, servers, routers, personal computers, microprocessor-based entertainment devices, peer devices, or other common network nodes, elements typically described in connection with computer 702. may include all or part of it. The logical connection may include a wireless/wired connection to a local area network (LAN), wide area network (WAN), hotspot, and the like. LAN and WAN networking environments are commonplace in offices and corporations and realize enterprise-wide computer networks such as intranets, all of which can be connected to global communication networks such as the Internet.

When used in a networking environment, computer 702 is connected to a network via a wired/wireless communication subsystem 742 (eg, network interface adapter, on-board transceiver subsystem, etc.) It can communicate with a wireless printer, a wired/wireless input device 744, and the like. Computer 702 may include a modem or other means for establishing communications over a network. In a network environment, programs and data associated with computer 702 may be stored in remote memory/storage devices, such as those associated with distributed systems. It will be appreciated that the network connections shown are exemplary and other means for establishing communication links between computers may be used.

Computer 702 communicates with a wired/wireless device or entity that uses a wireless technology, such as the IEEE 802.xx family of standards, such as a wireless device operably deployed in a wireless communication environment (e.g., IEEE 802.11 over-the-air modulation techniques). capable of communicating, such devices may be, for example, printers, scanners, desktop and/or portable computers, personal digital assistants (PDAs), communications satellites, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, a newspaper stands, toilets) and telephones. The communications include at least Wi-Fi™ for hotspots (used to authenticate interoperability of wireless computer networking devices), WiMax, and Bluetooth™ wireless technologies. Accordingly, such communication may be a predefined structure with a conventional network, or may simply be an ad hoc communication between at least two devices. Wi-Fi networks use a radio technology called IEEE 802.1x (a, b, g, etc.) to provide secure, reliable, and fast wireless connections. A Wi-Fi network can be used to connect computers to each other, to the Internet, or to a wired network (which uses IEEE 802.3-related technologies and features).

The persistent viewport architecture includes means for identifying an element of interest within the content of a virtual document, the element of interest being present in a viewport of the virtual document displayed on a passive user system of a collaboration session; means for receiving updates about the content of the virtual document from an active user system of the collaboration session; and means for maintaining the interest-element within the viewport of the passive user system regardless of any position change of the content due to the update by the active user system.

The persistent viewport architecture includes means for identifying an element of interest within the content of a virtual document, the element of interest being present in a viewport of the virtual document displayed on a passive user system of a collaboration session; means for calculating the position of the viewport relative to the interest-element; means for identifying a reference element within the content of the viewport of the passive user system; means for receiving updates about the content of the virtual document from an active user system of the collaboration session; and means for maintaining the viewport such that the element of interest is included within the viewport of the passive user system regardless of any change in position of the content due to the update by the active user system. can

In another implementation, the present persistent viewport architecture is a means for receiving a reader-specific identification of an element of interest within the content of virtual documents of a presentation, the element of interest to a reader via a reader viewport. designated by the means; means for processing the leader-specific identification via the update component and updating audience user systems according to the update; and means for moving the audience user viewports such that they contain the interest-factor regardless of any position change initiated by the audience user viewports by the corresponding audience users. .

What has been described above includes examples of the disclosed architecture. Of course, it is not possible to describe every conceivable combination of components and/or methods, but one skilled in the art may recognize that many other combinations and variations are possible. Accordingly, this novel architecture is intended to embrace all such changes, modifications and substitutions that fall within the spirit and scope of the appended claims. Also, so long as the term "comprises" is used in the description or claims, such terms are to be interpreted non-exclusively, such that "comprising" is a transitional word between the preamble and the body of a claim. Even when used as

Claims (20)

A method in which each step is performed by a computing system,
identifying an element of interest in the content of the virtual document, the element of interest being present in a viewport of the virtual document being presented on a passive user system;
receiving updates about the content of the virtual document from an active user system;
determining whether the update changes the position of the element-of-interest in the viewport on the passive user system and whether the position of the viewport must be adjusted in order for the element-of-interest to remain within the viewport;
Based on determining that the update will change the position of the element-of-interest in the viewport on the passive user system, and that the position of the viewport must be adjusted in order for the element-of-interest to remain within the viewport, the passive user system causing an update indication to be displayed, the update indication providing an option to delay inclusion of the update in the virtual document presented to the passive user system;
receiving a selection in response to the update indication;
in response to receiving the selection, causing the passive user system to delay input of the update and queue the update for input to the virtual document presented on the passive user system.
method.
According to claim 1,
further comprising calculating the position of the viewport relative to the element-of-interest.
method.
According to claim 1,
identifying a reference element within the content of the viewport of the passive user system in response to the update.
method.
According to claim 3,
identifying a topmost element within the viewport of the passive user system as the reference element.
method.
According to claim 1,
identifying a reference element in response to the update and adjusting the offset in the content to keep the interest-element within the viewport.
method.
According to claim 1,
further comprising retrieving the interest-element in a memory that stores a hashset and content elements.
method.
According to claim 1,
synchronizing the update between applications of the passive user system while maintaining the position of the element-of-interest within a corresponding viewport of the passive user system.
method.
According to claim 1,
further comprising displacing the position of the viewport so that the element-of-interest is included within the viewport.
method.
According to claim 1,
receiving the update at a portion of the virtual document that is outside the viewport of the passive user system.
method.
A method in which each step is performed by a computing system,
identifying an element of interest in the content of the virtual document, the element of interest being present in a viewport of the virtual document being presented on a passive user system of a collaboration session;
calculating the position of the viewport relative to the interest-element;
identifying a reference element in the content of the viewport of the passive user system;
receiving updates about the content of the virtual document from an active user system of the collaboration session;
determining whether the update changes the position of the element-of-interest in the viewport on the passive user system and whether the position of the viewport must be adjusted in order for the element-of-interest to remain within the viewport;
Based on determining that the update will change the position of the element-of-interest in the viewport on the passive user system, and that the position of the viewport must be adjusted in order for the element-of-interest to remain within the viewport, the passive user system causing an update indication to be displayed, the update indication providing an option to delay inclusion of the update in the virtual document presented to the passive user system;
receiving a selection in response to the update indication;
in response to receiving the selection, causing the passive user system to delay input of the update and queue the update for input to the virtual document presented on the passive user system.
method.
According to claim 10,
identifying a topmost element within the viewport of the passive user system as the reference element.
method.
According to claim 10,
further comprising adjusting the viewport according to the offset to keep the interest-element within the viewport.
method.
According to claim 10,
synchronizing the updates between applications of the passive user system as part of the collaboration session while maintaining the position of the interest-element within a corresponding collaboration viewport of the passive user system.
method.
As a system,
at least one processor;
a memory operatively connected to the at least one processor and having stored therein instructions which, when executed by the at least one processor, cause the system to perform a method;
The method,
identifying an element of interest in the content of the virtual document, the element of interest being present in a viewport of the virtual document being presented on a passive user system;
receiving updates about the content of the virtual document from an active user system;
determining whether the update changes the position of the element-of-interest in the viewport on the passive user system and whether the position of the viewport must be adjusted in order for the element-of-interest to remain within the viewport;
Based on determining that the update will change the position of the element-of-interest in the viewport on the passive user system, and that the position of the viewport must be adjusted in order for the element-of-interest to remain within the viewport, the passive user system causing an update indication to be displayed, the update indication providing an option to delay inclusion of the update in the virtual document presented to the passive user system;
receiving a selection in response to the update indication;
In response to receiving the selection, cause the viewport of the passive user system to the passive user system to delay input of the update and queue the update for input to the virtual document presented on the passive user system. Including the steps of
system.
According to claim 14,
The method further comprises calculating the position of the viewport relative to the interest-element.
system.
According to claim 14,
the method further comprising identifying a reference element within the content of the viewport of the passive user system in response to the update.
system.
According to claim 16,
The method further comprises identifying a topmost element within the viewport of the passive user system as the reference element.
system.
According to claim 16,
the method further comprising identifying the reference element in response to the update and adjusting an offset in the content to maintain the interest-element within the viewport.
system.
According to claim 14,
The method further comprises retrieving the interest-element in a memory storing a hash set and content elements.
system.
According to claim 14,
the method further comprising synchronizing the update between applications of the passive user system while maintaining the location of the element-of-interest within a corresponding viewport of the passive user system.
system.

Images