Enhanced design collaboration using design-based feedback

Abstract

Embodiments of the present disclosure relate to enhanced design collaboration using design-based feedback. Methods and systems for enhancing design collaboration using design-based feedback are provided. In an embodiment, an indication to provide feedback based on a graphic design element within a document is received. Text-based feedback related to the graphic design element within the document is obtained, and design-based feedback that manipulates the graphic design element within the document is obtained. Thereafter, a feedback indicator is generated that indicates the text-based feedback and the design-based feedback related to the graphic design element. The feedback indicator is provided (e.g., to a server) for presentation (e.g., via a user device) to one or more collaborators of the document, such that the document with the text-based feedback and the design-based feedback is visible to the one or more collaborators.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of document design, and more particularly to enhanced design collaboration. Background Art

[0002] Often, users desire to collaborate in creating a document. For example, input from several collaborators may be required to generate a document. Generally, in order to provide feedback, collaborators typically provide text comments associated with the document. In this regard, a user can select a portion of a document and insert a text comment to express comments, suggestions, or ideas.

[0003] In some cases, a portion of a document that is annotated is related to a visual aspect of the document. In this case, a user may attempt to provide feedback via a text annotation. For example, a collaborator may suggest moving an image to the left or reducing the size of an image. It may be difficult to express and / or provide feedback related to the visual features of a document via text. It may also be difficult for another collaborator to interpret such feedback. Continuing with the above example, it may be difficult to express and / or explain how far a collaborator expects an image to be moved in a given direction or how much a collaborator expects the size of an image to be changed. Therefore, in order to modify the visual aspects of a document using text-based feedback, there may be multiple rounds of revisions, resulting in unnecessary time spent on revising the document. Summary of the invention

[0004] Embodiments of the present disclosure relate to promoting enhanced design collaboration using design-based feedback. Design-based feedback generally refers to non-textual feedback provided relative to the design of a document. In this regard, design-based feedback may include any of several manipulations applied to graphic design elements. For example, design-based feedback may include modifications to the position, size, format, style, etc. associated with a graphic design element within a document. After obtaining design-based feedback, the design-based feedback and in some cases associated text-based feedback may be provided to other document collaborators so that the provided feedback can be previewed in a visual manner. Advantageously, previewing design-based feedback enables other collaborators to more accurately understand the perspective of the collaborator providing design-based feedback. Therefore, visual or aesthetic modifications may be more easily evaluated and / or adopted, resulting in reduced iterations and time required to generate a final document. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 depicts example configurations of operating environments in which some implementations of the present disclosure may be employed in accordance with various embodiments of the present disclosure;

[0006] Figure 2depicts an exemplary flow chart for facilitating enhanced design collaboration using design-based feedback in accordance with various embodiments of the present disclosure;

[0007] FIG. 3A to FIG. 3E An example graphical user interface according to embodiments described herein is provided;

[0008] Figure 4 A method for enhancing design collaboration using design-based feedback according to various embodiments of the present disclosure is provided;

[0009] Figure 5 Another method for enhancing design collaboration using design-based feedback according to various embodiments of the present disclosure is provided;

[0010] Figure 6 Another method for enhancing design collaboration using design-based feedback according to various embodiments of the present disclosure is provided; and

[0011] Figure 7 is a block diagram of an example computing device in which embodiments of the present disclosure may be employed. DETAILED DESCRIPTION

[0012] Individuals typically collaborate to produce a final document. In particular, an initial document may be created, and multiple individuals or entities may contribute input to arrive at a final work product. Such contributed input is typically provided as text, such as in the form of comments added to the document. By way of example only, assume that a campaign professional creates a new poster and solicits input from various entities, some of which may annotate the content of the poster, while some may annotate the aesthetic of the poster. In this case, the various entities provide comments in text form indicating recommendations, preferences, and the like. For example, a comment may state a desire to "move the image to the right."

[0013] However, feedback about the design or aesthetic associated with a document may be difficult to convey via text. Although a reviewer or collaborator of a document may generally be able to express comments in text about the design of the document, it is often difficult to effectively convey such details. For example, in some cases, it is difficult to specify a reviewer's visual perspective in text. In other cases, text provided by a reviewer that describes the visual appearance of a document may be difficult to interpret by another participant.

[0014] Failure to specify and / or explain text annotations related to the visual aspects of a document can lead to a large number of editing iterations, thereby increasing the time and effort used to obtain the desired or final document. For example, assume that a reviewer provides a text annotation that specifies that "text spacing is too crowded." Based on the provided annotation, in a first editing iteration, the document creator may modify the font style or type to increase the spacing between characters in the text. Based on the modified document, the reviewer may clarify the intention of increasing the spacing between words via another text annotation. In a second editing iteration, the document creator may revert to the original font and increase the spacing between words in the text. While reviewing, the reviewer may provide another textual explanation of the intention to increase the spacing between words and images. As a result, a third editing iteration may be applied to increase the spacing between words and images. In this way, multiple editing iterations may be performed in order to accurately interpret the text annotations provided by the reviewer.

[0015] Therefore, embodiments of the present disclosure relate to promoting enhanced design collaboration using design-based feedback. Design-based feedback generally refers to non-textual feedback provided relative to the design of a document. In this regard, design-based feedback may include any of several manipulations applied to graphic design elements. For example, design-based feedback may include modifications to the position, size, format, style, etc. associated with a graphic design element within a document. After obtaining design-based feedback, the design-based feedback, and in some cases associated text-based feedback, may be provided to other document collaborators so that the provided feedback may be previewed visually. Advantageously, previewing the design-based feedback enables other collaborators to more accurately understand the perspective of the collaborator providing the design-based feedback. Therefore, visual or aesthetic modifications may be more easily evaluated and / or adopted, resulting in reduced iterations and time required to generate the final document.

[0016] In operation, and at a high level, based on reviewing a document, a user may choose to provide feedback on the design of a document or a portion thereof. For example, a user may desire to modify a specific graphic design element (e.g., image, text, icon, table, etc.) within a document, and therefore, select a feedback element via a graphical user interface to initiate feedback provision. A user may provide text-based feedback and / or design-based feedback associated with a desired portion or graphic design element within a document. By way of example, a user may provide text via a comment box and design modifications (e.g., to modify the position, scale, size, font, type, style, etc. associated with a specific graphic design element) via various design editing tools. In this way, the visual context of the design may correspond to the text-based feedback provided in the comment box, thereby increasing visibility of the desired design modifications and improving collaborative workflows.

[0017] After feedback is entered, the feedback can be provided to other users or document collaborators so that the feedback can be reviewed and included in the document as needed. In some cases, feedback can be automatically presented to collaborators (e.g., upon reviewing the document). In other cases, feedback can be presented based on user selection. For example, a user can choose to review or preview feedback entered by a collaborator or a group of collaborators. In still other cases, text-based feedback can be automatically presented (e.g., upon reviewing the document), and design-based feedback can be previewed based on user selection.

[0018] By way of example only, and with brief reference to Figure 3C , in addition to providing text-based annotations via the comment box, the feedback provider may also modify the document content to provide design-based feedback. In this particular example, the feedback provider modifies the design graphic element 310 by moving the design graphic element down on the document to distribute the content. When the feedback provider has modified the graphic design element 310 as desired, the feedback provider may click a "Publish" button 312. According to some embodiments, selection of such a "Publish" button may initiate the capture of the annotations and / or content differences of the changes and send such feedback to the server to provide to other collaborators of the document.

[0019] Now refer to Figure 1 , Figure 1 Depicted are example configurations of operating environments in which some implementations of the present disclosure may be employed in accordance with various embodiments of the present disclosure. It should be understood that this and other arrangements described herein are set forth as examples only. Other arrangements and elements (e.g., machines, interfaces, functions, commands, and functional groupings, etc.) may be used in addition to or in place of those arrangements and elements shown, and some elements may be omitted entirely for clarity. In addition, many of the elements described herein are functional entities that may be implemented as discrete or distributed components or in combination with other components in any suitable combination and position. The various functions described herein as performed by one or more entities may be implemented by hardware, firmware, and / or software. For example, some functions may be implemented by a processor that executes commands stored in a computer program program such as a computer program program described in reference to a computer program program. Figure 7 The instructions in the memory are further described.

[0020] It should be understood that Figure 1 The operating environment 100 shown in FIG. 1 is an example of a suitable operating environment. Among other components not shown, the operating environment 100 includes a number of user or collaborator devices 102A and 102B through 102N (which may be referred to herein as user devices 102 or collaborator devices), a network 106, and (multiple) servers 108. For example, the operating environment 100 may be accessed via any type of computing device (such as a computer system in conjunction with a processor). Figure 7 One or more of the computing devices 700 described herein) are implemented Figure 1 Each component shown in . These components can communicate with each other via network 106, which can be wired, wireless or both. Network 106 may include multiple networks or networks in a network, but is shown in a simple form so as not to obscure the various aspects of the present disclosure. By way of example, network 106 may include one or more wide area networks (WANs), one or more local area networks (LANs), one or more public networks (such as the Internet) and / or one or more private networks. In the case where network 106 includes a wireless telecommunications network, components (such as base stations, communication towers or even access points (and other components)) may provide wireless connectivity. Networked environments are common in offices, enterprise-wide computer networks, intranets, and the Internet. Therefore, network 106 is not described in detail.

[0021] It should be understood that within the scope of the present disclosure, any number of user devices, servers, and other components may be employed within operating environment 100. Each device may include a single device or multiple devices cooperating in a distributed environment.

[0022] The user device 102 (also referred to herein as a collaborator device) can be any type of computing device capable of being operated by a user or a collaborator. For example, in some implementations, the user device 102 is a Figure 7 Type of computing device described. By way of example and not limitation, the user device may be implemented as a personal computer (PC), a laptop computer, a mobile device, a smart phone, a tablet computer, a smart watch, a wearable computer, a personal digital assistant (PDA), an MP3 player, a global positioning system (GPS) or device, a video player, a handheld communication device, a gaming device or system, an entertainment system, a vehicle computer system, an embedded system controller, a remote control, an appliance, a consumer electronic device, a workstation, any combination of these described devices, or any other suitable device.

[0023] The user equipment may include one or more processors and one or more computer-readable media. The computer-readable media may include computer-readable instructions executable by the one or more processors. The instructions may be executed by one or more applications (such as Figure 1 1 (applications 110A and 110B to 110N)). For simplicity, application 110 is referred to as a single application, but in fact its functionality may be implemented by one or more applications. It will be appreciated that applications 110A and 110B to 110N may be applications of the same type, although not necessarily the same version or even the same application running on various user devices. For example, each application 110 may be an application that provides document design functionality (e.g., XD). Generally, applications 110A and 110B to 110N enable users to collaborate in creating and editing documents. Although document collaboration is generally described as being performed via a server, it is understood that other embodiments may not employ a server to implement document collaboration functionality (e.g., via a peer-to-peer network). In this case, the functionality described herein associated with the server may be performed at other devices (such as user device 102).

[0024] As described more fully below, the user device 102 can be operated by various users or collaborators of the document collaboration application. For the purpose of conveying various aspects of the present technology, the various users or collaborators can be described as document creators and feedback providers. A document creator generally refers to a user who creates a document (initial document). A feedback provider generally refers to a user who provides feedback about a document. Figure 1 , for illustrative purposes, user device 102A is operated by feedback provider 104A, and user device 102B is operated by document creator 104B. Although illustrated in this manner, any one of user devices 102 is typically operated by a user or a collaborator, either of whom can create documents, provide feedback, and / or view documents and feedback.

[0025] The application 110 operating on the user device 102 can generally be any application that can facilitate the exchange of information between the user device and the server 108 (in some embodiments) to perform enhanced design collaboration. In some implementations, the (multiple) application includes a web application that can run in a web browser and can be hosted at least in part on the server side of the environment 100. In addition or alternatively, the (multiple) application can include a dedicated application, such as an application with document design functionality. In some cases, the application is integrated into the operating system (e.g., integrated as a service). Therefore, it is intended that "application" be interpreted broadly herein.

[0026] According to embodiments herein, an application may use design-based feedback and previews thereof to facilitate enhanced design collaboration. Enhanced design collaboration typically supports collaboration related to the design of a document provided in a non-textual manner. To this end, graphic design elements within a design document may be manipulated and provided as visual feedback. Based on the design-based feedback, a preview of this feedback may be presented to other collaborators so that other collaborators may visually view the design intent of the reviewer providing the feedback.

[0027] To provide feedback about the document, an application (such as application 110A on user device 102A) can access the design document. As described herein, a design document can refer to any type of electronic document on which a graphic design can be created or created. As an example, via The document created by XD can be a type of design document on which a creator (such as document creator 104B operating user device 102B) can use one or more graphic elements to create a graphic design. The graphic elements may include images, icons, tables, charts, text, or other graphic elements. In some embodiments, the graphic elements on the design document include at least one non-text graphic element, such as, for example, an image, icon, table, chart, diagram, etc.

[0028] The design document being accessed may, for example, be created by another collaborator or user. For example, as described, a document creator (such as document creator 104B operating user device 102B) may create a design document via application 110B. To create the graphic design within the document, the document creator may use any graphic design techniques and functionality. For example, a user may enter text into a document, select an image for the document, position or place a graphic element with the document, resize a graphic element, etc. The graphic design techniques used to create the document are not intended to be limited herein.

[0029] After the user or document creator 104B creates the graphic design within the design document, the design document may be shared with other users or collaborators (such as users 104A and 104N) via the user device 102B. For example, in some cases, a document share button may be selected via the graphical user interface to initiate sharing of the design document with other document collaborators. For example, the document creator 104B may select the document share button. Upon selecting the document share button, the design document and / or document data (data associated with the design document) may be provided to a server (e.g., server 108) for sharing with other collaborators so that other user devices may access the design document.

[0030] The design document may be stored, for example, in a data repository 130 and may be accessed by the server(s) 108 and various user devices of the document collaboration environment. The user devices may access the design document in any number of ways. For example, a link may be generated and provided (e.g., via email) to a user device (such as user devices 102B and 102N) for a collaborator or reviewer to access the design document. In other examples, a user may open an application 110 and be provided access to the design document (e.g., automatically or upon user selection).

[0031] After accessing the design document, the application 110 executed on the user device can present the design document to support enhanced design collaboration. In this way, users (such as feedback providers (or reviewers)) can view the design document and provide feedback related to the design document.

[0032] As shown, application 110 (such as application 110A on user device 102A) can include feedback manager 120, so that users can provide feedback on design documents, thereby enhancing design collaboration. It is understood that each user device 102 may include feedback manager 120. As described throughout this disclosure, feedback manager 120 enables users to provide design-based feedback and / or text-based feedback. In order to promote enhanced design collaboration, after creating a design document (such as a design document created by document creator 104B of user device 102B), the design document can be accessed by feedback provider 104A via user device 102A, and the design document can be manipulated to provide feedback related to the design of the document. In some cases, enhanced design collaboration can be automatically implemented in association with application 110 (e.g., as a default setting). In other cases, users can choose to initiate enhanced design collaboration. In this regard, users can choose to enable design-based feedback.

[0033] The feedback manager 120 typically manages feedback about a design document, such as design-based feedback and / or text-based feedback. Typically, feedback or design document feedback refers to feedback provided on or for a design document. Design document feedback may include text-based feedback and design-based feedback. Text-based feedback refers to feedback or comments provided in text (e.g., by a feedback provider or reviewer). Thus, a feedback provider may provide text comments associated with various aspects of a design document. For example, a feedback provider may provide text-based feedback on text content in a document, a design layout of a document, images within a document, and the like.

[0034] Design-based feedback generally refers to non-textual feedback on a graphic design element within a design document. In other words, design-based feedback refers to a modification of the design (e.g., layout) of (multiple) graphic design elements within a design document. Design-based feedback may include, for example, a modification of the size, position, placement, type, etc. of a graphic design element within a design document.

[0035] In this regard, a user may interact with the application 110 via a graphical user interface to modify or manipulate graphical design elements within a design document. Design-based feedback may be performed using, for example, any of a variety of graphical design tools and functionality provided in association with the application 110. By way of example only, a user (such as the feedback provider 104A of the user device 102A) may utilize a design editing tool to modify the position, size, scale, shape, style, format, etc. associated with a graphical design element.

[0036] In some implementations, to provide design document feedback, a feedback provider or reviewer may choose to provide design document feedback via selection of a feedback element, which is presented via a graphical user interface. A feedback element generally refers to a tool or component presented via a graphical user interface that enables a user to provide design document feedback (e.g., design-based feedback and / or text-based feedback). A feedback element may be visually represented via a graphical user interface in any number of ways, such as, for example, an icon or button. By selecting a feedback element, text-based comments and / or design modifications may be provided by the reviewer.

[0037] Feedback can be provided by the user in any number of ways. In some embodiments, the user can select the graphic display element of the document to provide feedback for the graphic display element. For example, the user can highlight or select a specific graphic display element corresponding to the feedback to be provided. According to the selection of the graphic display element, the user can provide text-based feedback and / or design-based feedback. In some cases, a comment box can be presented to obtain text-based feedback. For example, after selecting a specific graphic display element, a comment box can be presented. Then, the user can provide text-based feedback in the comment box. In order to provide design-based feedback, the user can manipulate the selected graphic display element in any number of ways. For example, the user can modify the position, proportion, size, color, format, style, etc. associated with the image display element using one or more design editing tools. Although various embodiments describe inputting both text-based feedback and design-based feedback in association with the graphic display element, it is understood that both types of feedback are not necessary.

[0038] In operation, and based on feedback input by a user (e.g., text-based feedback and design-based feedback), the feedback manager 120 may obtain, detect or identify feedback and generate a feedback indicator. A feedback indicator refers to an indication of feedback provided by a user. Thus, a feedback indicator may indicate text-based feedback and / or design-based feedback. A feedback indicator may be or include metadata. Such metadata may be embedded in a document file or separate from the document file. To generate a feedback indicator, the application 110 or a portion thereof (e.g., the feedback manager 120) may identify (a plurality of) graphical design elements (for which feedback may be provided), text-based feedback, design-based feedback, feedback providers, and the like. To identify design-based feedback, the application or feedback manager 120 may identify differences in a document or portion thereof (e.g., a graphical design element) based on the provided design-based feedback. For example, the feedback manager 120 or application 110 may compare differences (e.g., graphical or visual differences) between two files or documents (e.g., a modified version and a previous or original version) and create a "content difference" or comparison for indicating differences (e.g., design-based differences) in the document. The following is an example of a feedback indicator:

[0039] {"id": 21323, "creator": {"email": "bpb@xyz.com", "name": "BOB"}, "captiontext": Moce the plane to the UP", "content_diff: "<binary diff> ", "boundingbox": [276.028961, 621.649414, 356.142303, 647.793884]}.

[0040] In this example, the "captiontext" component of the feedback indicator indicates text-based feedback, while the "content_diff" component of the feedback indicator indicates design-based feedback. Content differences can be represented in any number of ways, one of which is via the use of binary data. In addition, as shown in this example, the "boundingbox" component of the feedback indicator indicates a portion of a graphic design element or document associated with text-based feedback and design-based feedback. The example provides the coordinates of a bounding box associated with feedback, but a graphic design element can be indicated or specified in any number of other ways for providing feedback to the graphic design element. Although the example feedback indicator provides an indication of both text-based feedback and design-based feedback, it is understood that such information can be provided via a separate indicator. For example, a text feedback indicator can provide an indication of text-based feedback, while a separate design feedback indicator can provide an indication of design-based feedback. In addition, as described herein, in some cases, only text-based feedback or design-based feedback is provided. In this case, only such information can be conveyed in the feedback indicator.

[0041] In some cases, a feedback indicator may be generated and / or provided when a user inputs feedback (such as text-based feedback and / or design-based feedback). In other cases, a feedback indicator may be generated and / or provided when a user chooses to publish input feedback so that other users can view the feedback. For example, via application 110 or another application operating on user device 102A, a feedback provider may choose to publish input feedback, the publication or accessibility of which to other collaborators is desired. As an example, a user may select a "publish" button or icon to initiate publication or accessibility of the input feedback to other collaborators of a design document. In this way, feedback contributed by a collaborator may be captured and made accessible to other collaborators so that other collaborators can view the provided feedback. By way of example only, when text-based feedback and design-based feedback are entered in association with (multiple) specific graphic design elements, a user may select "publish" feedback. Therefore, a feedback indicator containing an indication of text-based feedback and design-based feedback may be provided to server 108 to enable publication or accessibility of feedback to other collaborators of a design document.

[0042] Continue to refer to Figure 1As described herein, the server 108 can use design-based feedback to promote enhanced collaboration via the collaboration manager 122. The server 108 includes one or more processors and one or more computer-readable media. The computer-readable medium includes computer-readable instructions executable by the one or more processors. The instructions can optionally implement one or more components of the collaboration manager 122 that will be described in additional detail below. It will be appreciated that various aspects of the collaboration manager 122 can be executed via the feedback manager 120, and vice versa. For example, in a peer-to-peer environment, the feedback manager 120 on (multiple) user devices can perform the functions described in association with the collaboration manager 122 herein.

[0043] At a high level, the collaboration manager 122 can generally manage user collaboration related to a design document. In particular, according to embodiments described herein, the collaboration manager 122 can facilitate sharing of design document feedback provided by feedback providers or reviewers.

[0044] The data storage 130 accessible by the collaboration manager 122 can store computer instructions (e.g., software program instructions, routines, or services) and data used in the embodiments described herein. In some implementations, the data repository 130 stores information or data received via the user device 102, and provides access to the information or data to the user device 102 as needed. Although described as a single component, the data repository 130 can be implemented as one or more data repositories. In addition, the information in the data repository 130 can be distributed in one or more data repositories for storage (which can be hosted externally) in any suitable manner. In an embodiment, the data stored in the data repository 130 includes documents, feedback indicators, data associated therewith, and the like.

[0045] The collaboration manager 122 may receive (multiple) feedback indicators via the user device. For example, as described, after the user provides feedback, a feedback indicator indicating the feedback may be generated and provided to the server. The feedback indicator may be stored, for example, via the data repository 130 in association with the corresponding design document.

[0046] In an embodiment, to facilitate feedback sharing, the collaboration manager 122 may enable other users or collaborators (including the user providing the feedback) to view the feedback. In some cases, the collaboration manager 122 may provide a notification of new feedback. For example, the collaboration manager 122 may transmit an email indicating that new feedback has been received for a particular design document. As another example, the collaboration manager 122 may provide a notification to the application 110 so that when the design document is accessed via the application 110 on the user device, a notification appears within the design document indicating new feedback associated with the design document. It will be appreciated that the notification may include any type of information, such as an identifier of the feedback provider (e.g., a user name), an identifier of the graphical design element(s) for which feedback was provided, an indication of the time at which the feedback was provided, and the like.

[0047] The collaboration manager 122 can provide the design document with the corresponding feedback to various user devices. In this regard, the user device 102 can access and / or open the design document and the corresponding feedback provided by one or more feedback providers via the application 110. Thus, the application 110 operating on the user device 102 can facilitate viewing of the design document and the corresponding feedback.

[0048] Design documents and feedback may be provided to the collaboration manager in any number of ways. As an example, a feedback indicator may be provided to a user device along with the document so that a user device application may read or implement the feedback (e.g., via a design modification) into the document. As another example, the server 108 or a portion thereof may read the feedback indicator and create a document containing the feedback (e.g., via a design modification), and then send the modified document with the contained feedback to the user device(s). As yet another example, a call returned to the server 108 for accessing the feedback information may be used to transmit the document to the user device(s). For example, for a particular feedback (e.g., design-based feedback), a call may be made to the server to obtain the design-based feedback. In some cases, a separate server call may be triggered for each feedback (e.g., design-based feedback) to obtain the corresponding feedback indicator or portion thereof (e.g., content-diff).

[0049] Design document feedback, such as design-based feedback and text-based feedback, may be presented in any number of ways via the application 110 of the user device. In one implementation, the design document feedback may be automatically presented via a graphical user interface. In such an implementation, design document feedback, such as design-based feedback and text-based feedback, may be automatically presented in association with the presentation of the design document (e.g., included in the document, displayed simultaneously in the margin of a document or application view, etc.) when the design document is opened or viewed or when feedback is obtained.

[0050] In another implementation, design document feedback may be presented based on a user selection to view design document feedback provided by any feedback provider or a selected set of feedback providers. In such an implementation, a user may select an icon to view or preview feedback when opening or viewing a design document or when obtaining feedback. In response to such a user selection, the feedback may be presented (e.g., in a comment box and / or visually within the document to illustrate the design modifications). It will be appreciated that a user may select to view all feedback, feedback from a particular user or set of users, feedback associated with a particular graphical display element or set of graphical display elements, etc.

[0051] In yet another implementation, one feedback type may be automatically presented, while another feedback type may be presented upon user selection. For example, text-based annotations may be automatically presented via a graphical user interface, while design-based feedback is provided based on a user selection to view design-based feedback. By way of example, when presenting a design document, the annotation text may be automatically presented along with a design feedback preview button. Selection of the design feedback preview button enables the user to select to view design modifications made by the reviewer. In some cases, upon selection of the preview button, the design modifications may be applied to a copy (e.g., a local copy) of the design document file, such that the user can view the design modifications made by the feedback provider, e.g., as indicated by a "content_diff" component within the feedback indicator.

[0052] In some cases, the design feedback preview button may be a global button that, when selected, provides all design modifications provided by a user or a group of users. In other cases, the design feedback preview button may be a local button that is presented in association with a particular graphic design element or text-based annotation. In this regard, when a user selects a local button associated with a particular graphic design element or text-based annotation, the user may preview the design modifications associated with the particular graphic design element or text-based annotation.

[0053] In some cases, because the presented design-based feedback can be presented in a preview mode, a user (such as document creator 104B) can select whether to include the design modifications provided via the design-based feedback in an updated version of the design document. Where design-based feedback is desired, an updated version of the design document can be created and stored, for example, at data repository 130.

[0054] For a cloud-based implementation, instructions on the server 108 may implement one or more components of the collaboration manager 122, and the application 110 may be utilized by the user to interface with the functionality implemented on the server(s) 108. In some cases, the application 110 includes a web browser. In other cases, the server 108 may not be required. For example, the components of the collaboration manager 122 may be implemented entirely on a user device or a group of user devices (such as the user device 102). In this case, the collaboration manager 122 may be implemented at least in part by instructions corresponding to the application 110.

[0055] It should be understood that the collaboration manager 122 can be provided via multiple devices arranged in a distributed environment, which together provide the functionality described herein. Additionally, other components not shown can also be included in the distributed environment. Additionally or alternatively, the collaboration manager 122 can be at least partially integrated into a user device (such as the user device 102). Furthermore, the collaboration manager 122 can be implemented at least in part as a cloud computing service.

[0056] Figure 2 An exemplary flow chart 200 for promoting enhanced design collaboration using design-based feedback is provided. In the flow chart 200, a document creator 202 initially creates a design document 204. Such a design document may include any number of graphic design elements. When the document creator 202 has prepared a design document 204 that he / she likes, the design document may be shared with other collaborators of the design document. In this regard, the design document 204 may be provided to a server 206, and a feedback provider 208 may access and view the design document 204. Assume that the feedback provider 208 views the design document 204 and desires to provide feedback on the design of (multiple) graphic design elements within the document. In this case, it is assumed that the feedback provider 208 provides feedback in the form of text and design modification or manipulation. In this regard, the feedback provider 208 may select a feedback element via a graphical user interface and input both text-based feedback and design-based feedback. This is illustrated at box 210.

[0057] After completing the feedback, the feedback provider 208 may indicate the completion of the feedback (e.g., via a "Publish" button). Thereafter, as shown in box 212, the application may identify the graphic design element manipulation or modification and create a feedback indicator including a content_diff indicating the difference in the graphic design element (e.g., the difference from the original version and the edited version). The feedback indicator 214 may be transmitted to the server 206 (e.g., via a network). The server 206 may generate a notification indicating the new feedback, which may be communicated to the document creator 202 (among other collaborators). The document creator 202 may then access the design document, which has access rights to the new feedback. In some cases, the design document may be opened. In other cases, the design document may already be opened, where the new feedback is accessible or viewable. In this example, it is assumed that the document creator 202 opens the reviewed document. In this case, in box 216, the reviewed document is opened and presented with text-based feedback displayed and a preview button displayed. When the preview button is selected, in box 218, the application can apply content_diff on the document and present a preview of the design-based feedback provided by the feedback provider 208. Thereafter, as indicated in box 220, the document creator 202 can review the feedback and apply appropriate actions based on the reviewed feedback. For example, the document creator 202 can agree with the design-based feedback and choose to include or implement such changes. As another example, the document creator 202 can review the feedback and have additional feedback to provide. For example, the document creator 202 can add a text-based comment to agree or disagree with the feedback provided by the feedback provider. Additionally or alternatively, the document creator 202 can provide a design-based modification that modifies the original design of the document or the document to which the design-based feedback is applied. For example, the document creator 202 can adjust the design feedback provided by the feedback provider. This design-based feedback can then be provided to other collaborators for their review. Any such feedback or modifications made to the design document can be provided to the server 206 for provision to other collaborators of the design document.

[0058] Return to reference FIG. 3A to FIG. 3E , FIG. 3A to FIG. 3E Exemplary graphical user interfaces for implementing the embodiments described herein are provided. These exemplary graphical user interfaces are illustrative graphical user interfaces and are not intended to limit the scope of the embodiments described herein. Figure 3A, assume that a document creator creates document 302 and sends document 302 to a feedback provider for review. The feedback provider may open document 302 so that document 302 can be presented via a graphical user interface. In some cases, the feedback provider may receive an email notification regarding the document and thereafter open document 302. Further assume that, while reviewing document 302, the feedback provider wishes to provide feedback regarding document 302. Thus, if Figure 3A As shown in FIG. 3 , a feedback provider may select a feedback tool 304 to initiate providing feedback. Figure 3B As shown in FIG. 3 , after selecting the feedback tool 304, the document 302 may be opened in an edit mode 306. Figure 3B , a comment box 308 is presented (e.g., in a margin associated with an application). The feedback provider can provide text-based feedback via the comment box 308. In this example, the feedback provider provides the following comment in the comment box 308: "The text looks messy. There is a lot of white space in the poster. Let's distribute the content more evenly (as shown)."

[0059] like Figure 3C , in addition to providing text-based annotations via comment box 308, the feedback provider also modifies the document content to provide design-based feedback. In this particular example, the feedback provider modifies the design graphic element 310 by moving the design graphic element downward on the document to distribute the content. When the feedback provider modifies the graphic design element 310 as desired, the feedback provider can click a "publish" button 312. According to some embodiments, selection of such a "publish" button can initiate the capture of the annotations and / or content differences of the changes and send such feedback to the server to provide to other collaborators of the document.

[0060] Now refer to Figure 3D , assume that another document collaborator receives an email notification about new feedback. In this case, the collaborator can open the document and view the text-based annotations 314 provided by the feedback provider. Figure 3D As shown in FIG. 3 , a comment box with a text-based comment 314 may also be presented with an option to preview the design changes or modifications via a preview button 318. Although a preview button 318 is provided within the comment box 316, it is understood that such a preview button 318 may be presented based on various aspects of the document. Assume that a collaborator viewing the document desires to preview the design changes. In this case, the collaborator may select the preview button 318. Figure 3E As shown in FIG. 1 , in response to selecting the preview button 318, the Figure 3CThe provided design-based feedback is applied to the document and presented to the collaborator. In particular, the design graphic element 310 is moved down on the document with a specific placement to illustrate how the feedback provider envisions distributing the content. The collaborator reviewing the feedback now has the best understanding of the requested changes indicated in the comment box.

[0061] Reference Figures 4 to 6 , Figures 4 to 6 An exemplary process flow according to various embodiments described herein is illustrated. This process flow supports enhanced design collaboration using design-based feedback.

[0062] First refer to Figure 4 , Figure 4 A method 400 for enhancing design collaboration using design-based feedback is provided. The method 400 may be performed, for example, by a user device such as Figure 1 The user device 102A of the document is executed. In box 402, an indication of providing feedback is received according to a graphic design element in the document. In this regard, a user (such as a feedback provider) can choose to provide feedback related to a specific graphic design element (e.g., text-based feedback and / or design-based feedback). In box 404, text-based feedback related to the graphic design element in the document is obtained. For example, a comment box can be presented, and the user can provide a text comment in the comment box. In box 406, design-based feedback for manipulating the graphic design element in the document is obtained. For example, the user can modify the position, size, scale, style, etc. of the graphic design element in the document. In box 408, a feedback indicator (or a set of metadata) is generated, which indicates text-based feedback and design-based feedback related to the graphic design element. Such feedback indicators may include indications of text-based feedback, design-based feedback (e.g., via content differences), specific graphic design elements, users providing feedback, etc. The feedback indicator may be provided to another device (e.g., a server and / or a user device), which is embedded in the document or independent of the document to which it corresponds. Thereafter, in block 410, a feedback indicator is provided for presentation to one or more collaborators of the document, such that the document with the text-based feedback and the design-based feedback is visible to the one or more collaborators. The feedback indicator may be provided to a server for facilitating distribution to a user device so that other collaborators may view the feedback.

[0063] Reference Figure 5 , Figure 5 The diagram shows another process flow of a method 500 for enhancing design collaboration using design-based feedback. The method 500 may be performed by, for example, a server such as Figure 1The server 108 of the embodiment of the present invention is executed. First, in box 502, a feedback indicator is received from a first user device, which indicates design-based feedback related to a graphic design element in a document. Design-based feedback may include non-text manipulation of a graphic design element in a document. The feedback indicator may also include text-based feedback, an indication of a feedback provider, a time to provide feedback, etc. In box 504, a feedback notification indicating that feedback has been provided is provided to a second user device according to the received feedback indicator. Such feedback notification may be provided via email, via an application, etc. Thereafter, in box 506, in response to a request from a second user device to view design-based feedback, design-based feedback is provided to the second user device so as to present design-based feedback in the document. In this regard, a user of the second user device may request to view design-based feedback. This may be performed in a variety of ways, such as opening a document or selecting a preview button or icon associated with design-based feedback. In some cases, the server may include design-based feedback in a document and then provide the modified document to the second user device. In other cases, the server may provide the document in association with the design-based feedback (e.g., via content differences) so that the second user device may include the design-based feedback in the document. In still other cases, the server may provide (e.g., via server calls) the design-based feedback separately from the document (e.g., via content differences).

[0064] Relative to Figure 6 , Figure 6 FIG. 6 is another process flow diagram illustrating a method 600 for enhancing design collaboration using design-based feedback. The method 600 may be performed, for example, by a user device such as Figure 1 The user device 102B of the embodiment of the present invention is executed. First, in box 602, a document is presented in association with a comment box having text-based feedback and a design-based feedback preview element, the design-based feedback preview element being configured to enable previewing of design-based feedback provided by a first collaborator of the document. In some embodiments, when a document is opened or accessed, the document and the comment box can be automatically presented together with the design-based feedback preview element. In box 604, a selection of a design-based feedback preview element is received. For example, a user can select a design-based feedback preview element. In box 606, based on the selection of the design-based feedback preview element, design-based feedback is applied to the document, the design-based feedback including non-text manipulation of graphic design elements within the document. For example, after selecting the design-based feedback preview element, content differences can be accessed (e.g., locally or via a server call), and the content differences are used to modify the document to include design-based feedback. In box 608, a preview of the document with design-based feedback is presented, thereby making the document with design-based feedback visible to the second collaborator of the document.

[0065] Having described the embodiments of the present invention, Figure 7 An example of a computing device in which embodiments of the present invention may be employed is provided. Computing device 700 includes bus 710 that directly or indirectly couples memory 712, one or more processors 714, one or more presentation components 716, input / output (I / O) ports 718, input / output components 720, and an illustrative power supply 722. Bus 710 represents an object that may be one or more buses, such as an address bus, a data bus, or a combination thereof. Although shown with lines for clarity, Figure 7 , but in reality, it is not very clear to depict the various components, and metaphorically, the lines would more accurately be gray and fuzzy. For example, a presentation component (such as a display device) can be considered an I / O component. In addition, a processor has memory. The inventors recognize that this is the nature of the art and reiterate that Figure 7 The illustrations are merely illustrative of exemplary computing devices that may be used in conjunction with one or more embodiments of the present invention. No distinction is made between categories such as "workstation," "server," "laptop," "handheld device," etc., since all devices are expected to be in the same Figure 7 and refer to “computing equipment”.

[0066] The computing device 700 generally includes various computer-readable media. Computer-readable media can be any available media that can be accessed by the computing device 700 and includes volatile media and non-volatile media, removable media and non-removable media. By way of example and not limitation, computer-readable media can include computer storage media and communication media. Computer storage media include volatile and non-volatile removable and non-removable media implemented in accordance with any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. Computer storage media include, but are not limited to: RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage device, cassette, tape, disk storage device or other magnetic storage device, or any other medium that can be used to store desired information and can be accessed by the computing device 700. Computer storage media do not include the signal itself. Communication media generally implement computer-readable instructions, data structures, program modules or other data in modulated data signals (such as carriers or other transport mechanisms), and include any information delivery media. The term "modulated data signal" means one or more of its characteristics are set or changed in such a way as to encode the information in the signal. By way of example and not limitation, communication media include wired media such as a wired network or direct wired connection; and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above media should also be included within the scope of computer-readable media.

[0067] Memory 712 includes computer storage media in the form of volatile and / or non-volatile memory. As depicted, memory 712 includes instructions 724. Instructions 724 are configured to cause the computing device to perform any operation described herein or implement any program module described herein with reference to the drawings discussed above when executed by (multiple) processors 714. The memory may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard drives, optical drives, etc. Computing device 700 includes one or more processors that read data from various entities (such as memory 712 or I / O components 720). (Multiple) presentation components 716 present data indications to users or other devices. Exemplary presentation components include display devices, speakers, printing components, vibration components, etc.

[0068] I / O port 718 allows computing device 700 to be logically coupled to other devices including I / O component 720, some of which may be built-in. Illustrative components include microphones, joysticks, game controllers, satellite dishes, scanners, printers, wireless devices, etc. I / O component 720 may provide a natural user interface (NUI) that processes air gestures, voice, or other physiological inputs generated by a user. In some instances, the input may be transmitted to an appropriate network element for further processing. NUI may implement any combination of voice recognition, touch and stylus recognition, facial recognition, biometrics, gesture recognition on and adjacent to the screen, air gestures, head and eye tracking, and touch recognition associated with the display on computing device 700. Computing device 700 may be equipped with a depth camera, such as a stereo camera system, an infrared camera system, an RGB camera system, and a combination of these, for gesture detection and recognition. Additionally, computing device 700 may be equipped with an accelerometer or gyroscope that supports motion detection. The output of the accelerometer or gyroscope may be provided to a display of computing device 700 to render immersive augmented reality or virtual reality.

[0069] The embodiments presented herein have been described with respect to specific embodiments, which are intended in all respects to be illustrative rather than restrictive. For those of ordinary skill in the art to which the present disclosure pertains, alternative embodiments will become apparent without departing from the scope of the present disclosure.

[0070] Various aspects of the illustrative embodiments have been described using terms commonly used by those skilled in the art to convey the substance of their work to others skilled in the art. However, it is apparent to those skilled in the art that alternative embodiments may be practiced utilizing only some of the described aspects. For purposes of explanation, specific numbers, materials, and configurations are set forth to provide a thorough understanding of the illustrative embodiments. However, it is apparent to those skilled in the art that alternative embodiments may be practiced without the specific details. In other instances, well-known features have been omitted or simplified to avoid obscuring the illustrative embodiments.

[0071] Various operations have been described as multiple discrete operations in a manner that is most helpful for understanding the illustrative embodiments; however, the order of description should not be interpreted as implying that these operations must be dependent on the order. In particular, it is not necessary to perform these operations in the order presented. In addition, the description of operations as separate operations should not be interpreted as requiring the operations to be performed independently and / or by separate entities. The description of entities and / or modules as separate modules should also not be interpreted as requiring the modules to be separate and / or perform separate operations. In various embodiments, the illustrated and / or described operations, entities, data and / or modules can be merged, decomposed into other sub-parts and / or omitted.

[0072] The phrases "in one embodiment" or "in an embodiment" are used repeatedly. The phrases generally do not refer to the same embodiment, but may refer to the same embodiment. Unless the context indicates otherwise, the terms "comprising," "having," and "including" are synonymous. The phrase "A / B" means "A or B." The phrase "A and / or B" means (A), (B), or (A and B). The phrase "at least one of A, B, and C" means "(A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C)."

Claims

1. A computer-implemented method comprising: receiving an instruction to provide feedback related to a graphical design element within a document; obtaining text-based feedback related to the graphic design element within the document; obtaining design-based feedback for manipulating the graphical design elements within the document; generating a feedback indicator indicating the text-based feedback and the design-based feedback associated with the graphical design element, wherein generating the feedback indicator comprises: including within the feedback indicator an indication of data of the text-based feedback and the design-based feedback that can be used to apply the design-based feedback to the document; as well as The feedback indicator is provided via a network to support presentation of the feedback to one or more collaborators of the document, such that the document with the text-based feedback and the design-based feedback is visible to the one or more collaborators. 2 . The computer-implemented method of claim 1 , wherein receiving the indication to provide feedback related to the graphical design element comprises receiving an indication of a selection of the graphical design element.

3. The computer-implemented method of claim 1 , wherein receiving the indication to provide feedback related to the graphical design element comprises: receiving an indication of a selection of a feedback element indicating a desire to provide feedback; as well as An indication of a selection of the graphic design element is received.

4. The computer-implemented method of claim 1 , further comprising: In response to the indication to provide feedback related to the graphic design element, providing a comment box for receiving the text-based feedback, entering an edit mode for receiving the design-based feedback, and capturing graphical manipulations of the graphic design element while in the edit mode, wherein data of the graphical manipulations is included within the feedback indicator as part of the design-based feedback. 5 . The computer-implemented method of claim 1 , wherein the feedback indicator further comprises an indication of the graphical design element.

6. A computer-implemented method according to claim 1, wherein the feedback indicator indicates the design-based feedback via content differences, the content differences indicating differences in the document based on the manipulation of the graphic design element within the document, wherein the content differences include data that can be used to apply the manipulation of the graphic design element to the document.

7. The computer-implemented method of claim 1, wherein the feedback indicator is provided based on receiving an indication to share the feedback.

8. The computer-implemented method of claim 1, wherein the design-based feedback includes data corresponding to manipulation of style, size, position, scale, rotation, or a combination thereof associated with the graphical design element.

9. One or more computer-readable media having embodied thereon a plurality of executable instructions which, when executed by one or more processors, cause the one or more processors to perform a method comprising: receiving, at a server from a first user device, a feedback indicator comprising modification data of design-based feedback associated with a graphical design element within a document, the design-based feedback comprising a non-text manipulation of the graphical design element within the document, wherein the feedback indicator is separate from the document; providing, in response to receiving the feedback indicator, to the second user equipment a feedback notification indicating that feedback has been provided; as well as In response to a request from the second user device to view the design-based feedback, the modification data of the design-based feedback included in the feedback indicator is provided to the second user device to support presentation of the design-based feedback within the document.

10. The medium of claim 9, wherein the feedback indicator further indicates text-based feedback related to the graphical design element.

11. The medium of claim 9, wherein the feedback indicator indicates the design-based feedback via content differences, the content differences indicating differences in the document based on the non-textual manipulation of the graphic design element within the document, wherein the content differences include data that can be used to apply the non-textual manipulation of the graphic design element to the document.

12. The medium of claim 9, wherein the request to view the design-based feedback is received from the second user device based on a user selection to view the document.

13. The medium of claim 9, wherein the request to view the design-based feedback is received from the second user device based on a user selection to preview the design-based feedback.

14. A computing system comprising: One or more processors; as well as one or more non-transitory computer-readable storage media coupled to the one or more processors, the non-transitory computer-readable storage media having stored thereon instructions that, when executed by the one or more processors, cause the computing system to: causing presentation of a document having text-based feedback and a design-based feedback preview element configured to support preview of design-based feedback provided by a first collaborator of the document; receiving a selection of the design-based feedback preview element; based on the selection of the design-based feedback preview element, accessing a feedback indicator stored separately from the document, wherein the feedback indicator includes modification data of the design-based feedback; applying the modification data of the design-based feedback to the document, the modification data of the design-based feedback comprising data usable for applying non-text manipulation of a graphical design element to the document; as well as Causing presentation of a preview of the document with the design-based feedback so that the document with the design-based feedback is visible to a second collaborator of the document.

15. The system of claim 14, wherein the presentation of the document is caused in response to the second collaborator of the document selecting to view the document.

16. The system of claim 14, wherein the text-based feedback and the design-based feedback are provided by the first collaborator in association with the graphical design element within the document.

17. A system according to claim 14, wherein the design-based feedback is applied to the document via content differences, the content differences indicating differences in the document based on the non-textual manipulation of the graphic design elements within the document, wherein the content differences include data that can be used to apply the non-textual manipulation of the graphic design elements to the document.

18. The system of claim 14, further comprising: receiving a selection to include the design-based feedback into the document; as well as The design-based feedback is incorporated into the document.

19. The system of claim 14, wherein the design-based feedback preview element comprises an icon presented within a comment box with the text-based feedback.

20. The system of claim 14, wherein the graphical design elements include non-text elements.

Images