Patent Publication Number: US-9418454-B1

Title: Generating markup encodings for the compact rendering of curves in interactive graphical designs

Description:
BACKGROUND 
     Design programs for interactive graphical designs, such as web sites, allow users to specify designs while the designs are being rendered in a design environment. The underlying data structure used to render the editable version of the design in the design environment is generally in a different format than the underlying data structure that will be used to render the design itself in a player, such as a web browser. One basic reason that the formats differ is that the editable version of the design and the design itself expose different kinds of interactivity to the user: the editable version exposes interactivity that allows the user to specify and edit the design; and the design itself exposes interactivity to allow the user to interact with the design. For example, selecting a button in the editable version of a design (e.g., via the design environment) will move the focus of the design tool to the button in order to move the button or change its style, while selecting the same button in the rendered version of the design (e.g., via the player) will load a different page of the design. Another reason that the formats differ is that design environments are often proprietary tools while the designs created in said design environments are meant to be distributed widely to numerous potential players. As such, designs are often generated or exported from design environments in standard formats such as via code in a hypertext markup language. 
     Issues arise when designs are transferred back and forth between a design environment and player during production because certain aspects of the design are for production purposes only and might interfere with the interactivity of the design. For example, design annotations used to communicate potential changes to the design between members of a team that are collaborating on the design can be difficult to implement in the format of the exported design without interfering with the interactivity of the design. Annotations are particularly challenging in situations where the exported design is rendered using a markup language encoding because of the way standard players render markup language designs. Annotations are usually drawn over a design, but because of the way standard players render markup language designs, the annotations effectively block the interactivity of the design. In particular, hypertext markup language does not support interacting with portions of a design that have overlapping elements or containers. As a result, the production design either doesn&#39;t provide adequate room for annotations or doesn&#39;t allow full interactivity with the design. 
       FIG. 1  illustrates rendering  101  of an interactive graphical design being rendered in a player  100  such as a web browser. The interactive graphical design includes several design elements such as a hero image  102 , a menu of links  103 , and a member login form  104 . These elements could have been laid out in a graphical design environment by a designer using a drag and drop paradigm. Once the designer has completed the design, another member of the design team could review and annotate the design with annotation  105 . Unfortunately, when annotation  105  is exported from the design environment as HTML for rendering in a browser, the curve of annotation  105  will be rendered as element  106 , which has a footprint on the page as illustrated in  FIG. 1  by a dashed line. Due to the limitations of rendering markup-coded representations of a design in standard browsers, the resulting element will cover button  108 , and selection of button  108  will no longer be possible when annotation  105  is rendered with the design. As a result, the rendering of annotation  105  results in a loss of design interactivity which will hinder further review. 
     SUMMARY 
     In one embodiment a method is provided. The method comprises providing an interactive graphical design to a memory. The method also comprises parsing the interactive graphical design to identify a curve having graphical information. The method also comprises decomposing the curve into a set of at least two curve components. The method also comprises generating a markup-coded representation of the interactive graphical design that includes a set of independent elements for rendering the curve, wherein each of the independent elements in the set of independent elements uniquely corresponds to a curve component in the set of at least two curve components. 
     In another embodiment another method is provided. The method comprises receiving a user input via an interactive graphical design environment. The user input defines a graphical curve for an interactive graphical design. The method also comprises exporting the interactive graphical design from the interactive graphical design environment. The method also comprises decomposing the graphical curve into a set of at least two curve components. The method also comprises generating a coded representation of the interactive graphical design that includes a set of independent elements for rendering the curve. Each of the independent elements in the set of independent elements uniquely corresponds to a curve component in the set of at least two curve components. The method also comprises rendering the interactive graphical design in a player using the coded representation. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  illustrates the rendering of an annotation on a design using a markup-coded representation of the design and a web browser. 
         FIG. 2  is a flow chart that illustrates a set of methods for generating markup encodings for the compact rendering of curves in interactive graphical designs. 
         FIG. 3  illustrates the compact rendering of an annotation on a design using a markup-coded representation of the design and a web browser. 
         FIG. 4  includes a flow chart that illustrates a set of methods for decomposing a graphical curve into a set of Bezier curves and an illustration of the decomposition of a graphical curve into a set of quadratic Bezier curves. 
         FIG. 5  includes a flow chart that illustrates a set of methods for decomposing a graphical curve into a set of curves components and an illustration of the decomposition of a graphical curve into a set of curve components having minimum bounding rectangles of a predefined width. 
         FIG. 6  illustrates the compact rendering of an annotation on a design using a web browser and a markup-coded representation of the design where the independent elements of the rendered curve include a “rotate” element. 
         FIG. 7  is a block diagram of a computer system that can be used in accordance with embodiments described herein. 
     
    
    
     DETAILED DESCRIPTION 
     Reference now will be made in detail to embodiments of the disclosed invention, one or more examples of which are illustrated in the accompanying drawings. Each example is provided by way of explanation of the present technology, not as a limitation of the present technology. In fact, it will be apparent to those skilled in the art that modifications and variations can be made in the present technology without departing from the spirit and scope thereof. For instance, features illustrated or described as part of one embodiment may be used with another embodiment to yield a still further embodiment. Thus, it is intended that the present subject matter covers all such modifications and variations within the scope of the appended claims and their equivalents. 
     The following detailed description describes various systems and approaches for generating encodings for the compact rendering of curves in interactive graphical designs. Some of these approaches involve decomposing a curve into a set of curve components and generating a markup-coded representation of the interactive graphical design and the set of curve components. The curve components can be rendered using independent elements in the markup-coded representation of the interactive graphical design. The independent elements can be generated upon export of the design from a graphical design environment for rendering in an external player. The independent elements can be components of a proprietary model that is recognized by a specialized software element of the external player such as a plug-in or add-on to a standard web browser. The generation of the markup-coded representation can include formatting the set of independent elements for injection into a document object model (DOM) of the interactive graphical design. The generated markup-coded representation can thereby be parsed by a standard web browser such that the independent elements are recognized by and injected into the DOM. The DOM is recognized and utilized by a standard web browser to render the design and the independent elements. As used herein, the term “DOM” has its plain meaning to those of ordinary skill in the art of web browsers, and refers to a representation of the document as a structured group of elements that have properties and methods. The type of element and its properties determine whether and how it is rendered. The elements can also have event handlers to provide interactivity. 
     The described approaches can be utilized for the compact rendering of annotations on an interactive graphical design. In this case, the curves could be annotations on the interactive graphical design such as a line drawn across the design to bring attention to a particular design component or to illustrate a desired modification of the design or desired interactivity. When marking up a design with annotations, the reviewer making the annotations will thereby not need to be conscious of preserving the interactivity of the design. As such, when the design is rendered in a player, an annotation whose rendering might have otherwise obscured an interactive portion of the interactive graphical design will not do so. In other words, the annotation will be compactly rendered to expose an interactive portion of the interactive graphical design beneath the annotation. 
     The described approaches can also be utilized for the compact rendering of curves that are part of the graphical content of the interactive graphical design itself. Conventionally, curves in an interactive graphical design would be rendered as parts of the images in which they appear and would be blocked off from interactive elements for that reason. When a designer specifies the content of a page, the location of the curve relative to the interactive element would only need to be considered to the extent that the relative location of separate blocks of content were considered when laying out the overall page. However, if the design is specified in a graphical design environment that includes sketching tools, the designer may specify the design without any reference to the underlying markup language that will render the design. As such, if markup language code is automatically generated from the individual elements of the design, the potential for the overlap of elements as described with reference to  FIG. 1  becomes a real possibility in the absence of additional processing steps. The approaches described herein also alleviate this concern and can serve as the additional processing steps needed to avoid the overlap of free form curves and other content that was separately specified for an interactive graphical design. By compactly rendering the curves of the design, the graphical design environment does not need to engage in complex determinations as to what elements of a design need to be grouped for non-overlapping rendering, and the code for rendering the curves of a design without interfering with the interactivity of the design can be efficiently generated. 
     A set of methods for generating markup encodings for the compact rendering of curves in interactive graphical designs can be described with reference to flow chart  200  in  FIG. 2 . Further variations and specific implementations of these methods are provided with reference to  FIGS. 3-6 . The approaches described below include different algorithms for decomposing the curve into curve components, different implementations of the independent elements in the markup-coded representation of the design, and different algorithms for generating the markup-coded representation of the design given a set of curve components and target type of independent element for the markup-coded representation. 
     Flow chart  200  includes step  201 , in which inputs  207  are received from a user via a graphical design environment. Input  207  refers to electronic signals received by a machine via human-machine interfaces such as a keyboard, mouse, gesture recognition device, or surface pen. The user can be a designer or other collaborator working on an interactive graphical design in the graphical design environment. The user input can define a graphical curve for an interactive graphical design. As an example, a user can use a mouse directed two-click-and-bend curve generation tool or a free form mouse-down-and-drag, curve generation tool. As another example, the user input can be an electronic signal received via a surface pen and processed by the graphical design environment back end software to encode the desired signal. This encoding of the graphical curve can be used to display the graphical curve back to the user as part of the design in the graphical design environment. The encoding can also be exposed for modification by additional user inputs to change the color, shape, position, and style of the graphical curve. The graphical curve can be an annotation placed on the design from within the graphical design environment. As another example, the user input can be an electronic signal received via a surface pen and processed by a player&#39;s back end software to encode the desired signal. The back end software could be a portion of a proprietary player or a plug-in on a standard player such as a web browser. This encoding of the graphical curve could be used to display the graphical curve back to the user as part of the design in the player. The encoding can also be exposed for modification by additional user inputs to change the color, shape, position, and style of the graphical curve. 
     Flow chart  200  also includes step  202 , in which the interactive graphical design is provided to a memory. Once stored in memory, the interactive graphical design can be used to generate a markup-coded representation of the interactive graphical design, As such, the interactive graphical design can be considered the input to a method comprising variations of steps  203 - 205  wherein the output of such a method is the aforementioned markup-coded representation of the interactive graphical design. The design can be continuously provided to memory as the user is editing and specifying the design by the state machine that is instantiating the interactive graphical design environment. Alternatively, the design can be provided to memory from an external software system during an import process, such as when an interactive graphical design has been edited in an external tool and is being brought back into the graphical design environment. 
     Flow chart  200  also includes optional step  203 , in which the interactive graphical design is parsed to identify a curve having graphical information. Step  203  is optional because its execution depends on the format in which the design is provided to memory and the operation of the back end software for the interactive graphical design environment. In particular, specific types of curves on which the design will operate may have already been tagged with a unique identifier that marks them as requiring the operation of a particular software element that will execute steps  204  and  205 . However, in other approaches, the design will be parsed to identify graphical curves for which the rendering in compact format would provide a benefit to the design. As an example, the parsing action could involve a compiler conducting a specific process involving selecting only curves with an unprocessed area above a threshold and then further narrowing the selection to curves that cover interactive elements. 
     Flow chart  200  also includes steps  204  and  205 , in which the graphical curve is decomposed into a set of at least two curve components and a markup-coded representation of the interactive design is generated, respectively. Steps  203 ,  204 , and  205  can all be a part of an export process  209  for exporting the interactive graphical design from the graphical design environment. In some approaches, the at least two curve components will have the same graphical information as the original graphical curve such that the original curve can be rendered graphically in its entirety with access to the data represented by the curve components. In some approaches, the at least two curve components will have sufficient graphical information from the original graphical curve such that the semantic content of the original curve can be rendered graphically with access to the data represented by the curve components. Depending upon the specific implementation applied to decompose the curve in step  204 , and the complexity of the curve itself, the number of curve components can be much greater than two. However, benefits accruing to the compact rendering of a curve using a markup language encoding will attach even when the number of curve components is limited to two. The curve components are each uniquely identifiable and editable data structures that can be operated upon by the compiler that is used to generate the markup-coded representation in step  205 . 
     The markup-coded representation of the interactive graphical design that is generated in step  205  will include a set of independent elements for rendering the curve. These independent elements will each uniquely correspond to a curve component in the set of curve components to which the curve was decomposed in step  204 . As the most basic example, two independent elements of the markup-coded representation that are used to render the graphical curve in a player will individually and uniquely correspond to two curve components into which the curve was decomposed in step  204 . The independent elements can be separately enumerated HTML elements, such as &lt;div&gt;, &lt;img&gt;, or &lt;canvas&gt; elements or their equivalents in any markup language. 
     Flow chart  200  also includes step  206  in which the design is rendered in a player. The player can be a component of the interactive graphical design environment (e.g., for previewing designs), a standard web browser, or a proprietary player. In the case of a standard web browser, the player may include an add-on or plug-in used to accept annotations on the design or other input from reviewers. However, benefits accrue to situations in which the player is a standard web browser which thereby does not require any specialized add-on to render the design besides recognition of and adherence to the DOM. 
       FIG. 3  illustrates the same interactive graphical design that is being rendered in web browser  100  in  FIG. 1 . However, rendering  300  of the interactive graphical design in  FIG. 3  is being rendered from a markup-coded representation of the interactive design that was generated according to a method that is within the set of methods represented by flow chart  200 . As a result, the curve of annotation  105  was decomposed into two curve components and is being rendered through the use of two independent elements in the markup-coded representation used to produce rendering  300 . The curve components represented by these independent elements have the same graphical information as the original curve such that there is no change in the appearance of rendering  300  as compared to rendering  101 . However, the footprint of these individual elements in the rendering, as represented by dashed areas  301  and  302 , is far less that the footprint of the curve in rendering  101 . As a result, the rendering of annotation  105  does not interfere with the interactivity provided by button  108  such that the graphical information provided by the annotation and the full interactivity of the design are both available to a reviewer. 
     Different specific approaches for conducting step  204  can be explained with reference to the illustrations and flow charts of  FIGS. 4 and 5 . In general, a graphical curve can be decomposed into curve components such that the sum of the area consumed by the minimum bounding rectangle (MBR) of each curve component is less than the area consumed by the MBR of the original curve. For example, the graphical curve can be decomposed by deriving a minimal set of Bezier curves that replicate the curve. Once the curve has been decomposed, each Bezier curve in the minimal set of Bezier curves will then uniquely corresponds to a curve component that is generated in the marked-coded representation of the design. As another example, the graphical curve can be decomposed by deriving a minimal set of paths having an MBR less than a predefined width that still cover the original curve. 
       FIG. 4  illustrates a set of methods for decomposing a graphical curve into a minimal set of Bezier curves with reference to flow chart  400  and illustrations  401 ,  402 , and  403 . In step  404 , a description of the graphical curve is provided to memory. In step  405 , a path order is provided to memory. With this data available, the curve can then be decomposed in step  406  by fitting the maximum distance curve of the given order along the original curve starting from the beginning end of the curve. The fit can be derived on an iterative basis by extending the end point of the curve component and determining where it is no longer possible to derive a Bezier curve of the given order to fit the original curve. This process is illustrated in a comparison of illustrations  401  and  402  where  401  illustrates the original curve and  402  illustrates the maximum quadratic Bezier curve that can adequately fit the original curve in step  406 . Flow chart  400  ends with step  407 , in which a check is run to determine if the end point of the original curve is the end point of the last curve component derived in step  406 . If the end point has not been reached, the flow chart proceeds back to step  406  and continues to iterate between steps  406  and  407  until the end point of the curve has been reached. A full decomposition of the graphical curve from illustration  401  into curve components comprising quadratic Bezier curves is shown in illustration  403 . 
     The path order selected in step  405  sets the order of the Bezier curves that will serve as the curve components of the decomposed curve. The order can be pulled from the source code of the graphical design environment, be determined by the user of the graphical design environment and pulled from a temporary storage location, or it can be derived through a script run on the curve description to determine the optimal value for the order. Increasing the order of the Bezier curves tends to degrade the benefit of later steps in the overall process of flow chart  200  as the MBR will include space that could have been optimized out of the overall footprint of the final derived curve. Although decreasing the order of the Bezier curves results in a larger number of curve components and a slightly larger number of independent elements that need to be derived, the increase in the data volume of the design and its correspondingly increased rendering and generating time is generally minimal compared to the benefit of decreasing the footprint of the annotation. Generally, a quadratic or cubic order will suffice for sufficiently compact rendering and the expedient generation of efficient code. 
     In other implementations, the path order from step  405  is a maximum value used to provide one limit to the curve fit step. The curve fit step of  406  could use the minimum order to fit a given curve and continue to increase in length and order until either the maximum value was reached or a given curve length was reached. The total area of the MBR could be an alternative limit for this approach in which, when the MBR was exceeded, a higher order was used for the Bezier curve until the MBR area decreased below a predetermined value. 
       FIG. 5  illustrates a set of methods for decomposing a graphical curve into a minimal set of curve components where each component has an MBR with a width that is less than a predefined width, with reference to flow chart  500  and illustrations  501 ,  502 , and  503 . In step  504 , a description of the graphical curve is provided to memory. In step  505 , a predefined MBR width is provided to memory. With this data available, the curve can then be decomposed by fitting the maximum distance curve that will have a MBR less than the predefined MBR width and extending along the original curve starting from the beginning of the curve. This process can be conducted in step  506 , which may involve taking the derivative of the curve utilizing the tangent of the curve at its starting point as a frame of reference. Alternatively, the process can include an iterative sub-process in which the length of the MBR is extended and the MBR is rotated through various angles until the curve component can no longer fit within its width. This process is illustrated in a comparison of illustrations  501  and  502  where  501  illustrates the original curve and  502  illustrates the maximum length MBR with a predetermined width that can adequately cover the first segment of the original curve in step  506 . Flow chart  500  ends with step  507 , in which a check is run to determine if the end point of the original curve is the end point of the last curve component derived in step  506 . If the end point has not been reached, the flow chart proceeds back to step  506  and continues to iterate between steps  506  and  507  until the end point of the curve has been reached. A full decomposition of the graphical curve from illustration  501  into curve components comprising maximum length MBRs with a predetermined width is shown in illustration  503 . 
     The target MBR width selected in step  505  can be specified in pixels or in accordance with any scaling scheme utilized within the graphical design environment. The width can be pulled from the source code of the graphical design environment, be determined by the user of the graphical design environment and pulled from a temporary storage location, or it can be derived through a script run on the curve description to determine the optimal value for the width. The optimal value can be derived based on minimizing the overall area of the component&#39;s MBRs counterbalanced with a desire to minimize the number of components as described above. The frontier of this optimization problem can be selected by a developer of the graphical design environment. For example, the frontier could be first order linear such that an increase in total MBR of 1,000 pixels was equivalent to the addition of another curve component. However, other frontiers could be selected including higher order frontiers and first order frontiers with different slopes such as 500-10,000 pixels. 
     An additional aspect of the decomposition process involves the treatment of line ends such as arrow heads and other symbols. Line ends can be automatically provided as a feature in the graphical design environment or may be entered manually by the person specifying the curve. For example, a user could apply an arrow head style to a line through a menu option, or manually draw in two additional lines at the end of the main line. The graphical design environment can tag the line ends as elements of the design that require their own independent elements for rendering. In this case, as long as the system keeps track of the line ends until their corresponding independent components are injected into the markup-coded representation, the line ends may be ignored during the decomposition process. 
     Once the decomposition process has been conducted, the result of that process can be utilized for the generation of a mark-up coded representation of the curve and the interactive design. The decomposed curve components can be used to generate a rendering that will utilize a proprietary model. For example, the curve components could be rendered using ActiveX, Silverlight, Adobe Flash, or other plug-in application frameworks. The generation of these renderings can render the curves as if they were on a separate level from the design itself. In some cases, this can involve the ability to interact with the design even if the area of interactivity is located below a curved segment of an annotation. In effect, the presence of the annotation on the design can be simulated and kept separate from the user&#39;s interaction with the design via the core of the web browser. In keeping with this approach, the plug-in could simulate the presence of the cursor over the design, intercept mouse clicks, and interact with the design indirectly by keeping track of what that mouse click would have done in the absence of the rendered curves. Although these approaches would facilitate the separation of interactivity from rendering of the curves in the design, there are certain benefits that accrue to approaches in which the curves are rendered using a DOM and not utilizing a separate semantic framework. 
     The markup-coded representation of the interactive design can be generated by leveraging a DOM such that the curves are rendered as if they were part of the interactive design. The generating can include injecting the set of independent elements into a DOM of the interactive graphical design. In the situation where the markup-coded representation is coded using HTML, this could involve creating independent HTML elements for each of the curve components into which the curve was decomposed. The generating can also involve generating a DOM element for each of the independent elements. For example, the generated markup-coded representation could include a &lt;div&gt; element to serve as a container in which each curve component was rendered. The &lt;div&gt; element, upon being recognized by the DOM, would be rendered at a specific location in a browser window as determined by the encoding and the DOM. Therefore, the curve components would be rendered as if they were part of the design itself, rather than being rendered on a separate layer or through the use of an alternative semantic platform. 
     Injecting the independent elements into the DOM provides benefits in terms of both efficiency and additional functionality, as the associated approaches both reduce the software requirements necessary to collaborate on a design and afford additional flexibility in terms of where annotations can be placed. Injecting the independent elements used to render the curve into the DOM reduces the software requirements necessary for collaborative efforts because the DOM is recognized by standard web browsers such that additional software is not required to review the design along with the associated annotations. As such, there is no need for reviewers to download and install additional software in order to review designs as they move through the production process. In addition, there is no need to maintain the add-ons so that they continue to function as standard web browsers evolve. Injecting the elements into the DOM also provides additional functionality in that the annotations can appear or disappear when elements of the design are dynamically shown or hidden. For example, if a design displayed either a log in interface or an account information interface, injecting annotations about each element into the encoding to appear on each of those interfaces would result in the annotations being displayed when those different interfaces were displayed. This allows reviewers to comment on and annotate different dynamic portions of a design. In contrast, if the annotations and design were kept on entirely separate layers, the annotations would not change when the state of the panel was modified and, as a result, it would not be possible to separately comment on the two panel states. 
     The independent elements in the generated representation of step  205  can be separate hypertext markup language elements having at least one hypertext markup language tag. The independent elements could consume a rectangular portion of a rendering space upon being rendered. The independent elements could include an attribute that rotates the independent elements for rendering. In one example, this attribute would be the HTML 5 “transform: rotate(X)” attribute. With reference to  FIG. 5 , it should be noted that the minimum width MBR decomposition method primes the compiler for the generation of these elements since the curve component derivation includes information on the degree of rotation and the alignment of that element to the curve. If instead a Bezier curve based decomposition method is used, the compiler will need to derive the MBR for each curve component in order to properly specify the size and degree of rotation of the independent elements used to render the curve components. However, this is a less intensive task than for the procedure in  FIG. 5  because the length of each curve component is already known. 
     The separate hypertext markup language elements that can be used for rendering the curve include any element capable of referencing image data or graphical data more generally. For example, the independent elements could be image elements specified as &lt;img src=′X′&gt;, where “X” is a referenced image file that includes a graphical representation of the curve component for that independent element. The independent elements could also be canvas elements specified as:
         &lt;canvas id=“curveCanvas” width=“200” height=“200”&gt;&lt;/canvas&gt;   &lt;script&gt;   var canvas=document.getElementByld(‘curveCanvas’);   var context=canvas.getContext(‘2d’);   contextbeginPath( )   context.moveTo(5, 5);   context.bezierCurveTo(140, 10, 180, 10, 180, 170);   context.lineWidth=5;   context.strokeStyle=‘black’;   context.stroke( );   &lt;/script&gt;       

     In this example, the JavaScript referenced by the &lt;canvas&gt; element renders the curve component in a rendering spaced defined by the &lt;canvas&gt; element. One potential benefit of this approach is that the curve could be dynamically altered using JavaScript in the player. For example, the color of the curve could be configured while rendering the design in the player. As another example, the independent elements could be container elements, such as a &lt;div&gt; element specified as &lt;div style=“width:200 px; height:200 px; background-image: url(“curve.gif”); background-position: 50 px 100 px;”&gt;. In this example, the cascading style sheet property of the element defines a portion of a background image for rendering in a rendering space defined by the container element. This approach is beneficial in that a single image file representing all of the various curve components is all that is needed for the markup-coded representation, which increases the speed at which the markup-coded representation can be transmitted through the Internet and rendered by a web browser. 
       FIG. 6  illustrates another rendering  600  of the same design and curve shown in  FIGS. 1 and 3 . As illustrated, the curve of annotation  105  is being rendered in accordance with a particular combination of the approaches described above. Specifically, the curve had been decomposed into minimum width MBR components  601  and  602  and is being rendered as &lt;div&gt; elements with a rotation element specified to minimize the footprint of each individual element. In addition, the curve end, which in this case is an arrow head, is being rendered as a separate div element  603 . A comparison of the overall footprint of the curve in  FIG. 1  and  FIG. 6  illustrates that the curve rendering process could be applied to render a curve even if it were part of a highly interactive design with a high concentration of interactive points in the rendering space. 
     Although examples discussed above were directed to the generation of a markup-coded representation of a curve via the exporting of that graphical design and annotation from a graphical design environment, the approaches described herein are broadly applicable for the rendering of compact curves in any markup-coded representation of a graphical design regardless of where or how the curve was added to the design. For example, as introduced previously with respect to step  201  in flow chart  200 , the curve could be an annotation added to a design in a specialized player that provides reviewers with the ability to markup or add annotations to a design, where the design is then subsequently imported along with those annotations into a graphical design environment. The annotation could be compactly generated in a markup-coded representation as part of the design during the import process, either after the player receives the annotation input and adds the annotation to the design in the player, or during a subsequent export of the design from the graphical design environment at a later time. 
     Although examples discussed above were directed to the generation of a markup coded representation of an annotation on a graphical design, the approaches described herein are broadly applicable for the rendering of compact curves regardless of what the semantic content of the curve happens to be. For example, the curve does not have to be an annotation but can also be a curve whose semantic content is a part of the actual design itself. For example, the curve could be an illustration added to the design by a graphical designer adding additional artistic elements to a design after the interactivity was specified by a different user. Due to the ability of the described approaches to compactly render this curve, the work of the graphical designer and the user interface designer working on the interactivity of the design can be conducted in a more flexible manner without each of them having to make adjustments for the other&#39;s efforts, thereby facilitating a more liquid collaborative effort for the production of the overall interactive graphical design. 
     Any of the methods described herein can be conducted through the use of a computer system  700  as shown in  FIG. 7 . For example, the design environment could be provided by a processing system  701  acting in tandem with a memory  702 . A user  703  would be able to access the design environment through the use of a routing system  704  and a user interface system  705 . Any method steps involving providing or accepting things to and from a user can be conducted using interface system  705 . Any method steps involving executing an action can be conducted using processing system  701  alone or in combination with memory  702 .  FIG. 7  is only an illustrative computer system that is amenable to operation in accordance with embodiments of the present invention and variant computer system topologies may be used in its stead. Nothing in this description should limit the processor of processing system  701  to a single processor, as the function of this block can be accomplished by multiple physical processors located either on a single work station or server, or distributed through a network. It is not essential for memory  702  to be physically distinguishable from processing system  701 , as they are merely illustrated as separate blocks for purposes of invoking common conceptions of how computing systems operate. Routing system  704  could be the internal routing system of a single work station, a LAN, a WAN, a wired or wireless network, the Internet, or any other system capable of routing signals. User interface system  705  could be a work station, a computer, a mobile phone or other mobile device, or any computing device or group of computing devices capable of receiving inputs from a single user or group of users.  FIG. 7  should also not be taken to indicate that the invention can only involve design environments or design programs that may only be accessed by one user as there could be multiple users  703  and that group of multiple users  703  could access the design environment using any number of routing systems  704 . Those users could also access the design environment simultaneously. The steps of the various flow charts in the examples above can be executed by the processing system of  FIG. 7  executing instructions to implement the objectives of those steps. The instructions can be encoded and stored on a non-transitory computer readable storage medium. Non-limiting examples of such non-transitory computer readable storage media include binary computer code stored in CD-ROM, hard disk drives, flash drives, or any computerized RAM. The code could be stored as a .exe or .dmg file. Non-transitory computer readable storage media can also include any file that is stored on a server in volatile or non-volatile memory and prepared for transmission via FTP, HTTP, or HTTPS. 
     While the specification has been described in detail with respect to specific embodiments of the invention, it will be appreciated that those skilled in the art, upon attaining an understanding of the foregoing, may readily conceive of alterations to, variations of, and equivalents to these embodiments. These and other modifications and variations to the present invention may be practiced by those skilled in the art, without departing from the scope of the present invention, which is more particularly set forth in the appended claims.