Patent Application
20070168858
Diagrams that graphically present relations between objects are used in many applications including, but not limited to, word processing applications, presentation applications, spreadsheet applications, and the like. Organizational structures, network structures, and the like may be visually represented by a diagram. Diagrams may include simple or complex objects and connect those objects in many different ways. Traditional systems for applying style to a complex object may not allow developers or advanced users to add style descriptions to the application during use. Some applications may allow for adding styles to existing charts or layouts during setup, but those still do not allow adding styles for future layouts that do not exist at the time of the creation of the style.
Style extensibility is provided to shapes in a diagram by editing text files. A structured data model may be used to render the diagram representing items and their relationships provided by a user in a semantic model. Style properties are assigned to key shapes of the diagram through style labels. Style definitions may also assign color scheme(s) through the style labels. Layout definitions based on user input and default parameters along with style labels are employed to render a presentation model from a semantic model.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Embodiments of the present disclosure now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific exemplary embodiments for practicing the invention. This disclosure may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope to those skilled in the art. Among other things, the present disclosure may be embodied as methods or devices. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.
Illustrative Operating Environment
Referring to
In addition to program modules 106, diagram application 120 may also be executed within operating system 105. Diagram application 120 may include a word processing application, a presentation application, a spreadsheet application, an electronic mail application, and the like, with diagram capability. Diagram capability refers to a feature of the application providing a diagram independently or as part of another document such as a text-document based on user input.
Diagram application 120 may include style engine 122, a layout engine (not shown) and other modules that interact in order to determine style and other properties of diagram elements (e.g. objects and connectors) and lay out the diagram. To perform the actions described above, diagram application 120 may include and/or interact with other computing devices, applications, and application interfaces (APIs) residing in other applications.
Computing device 100 may have additional features or functionality. For example, computing device 100 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
System memory 104, removable storage 109 and non-removable storage 110 are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 100. Any such computer storage media may be part of device 100. Computing device 100 may also have input device(s) 112 such as retail devices, keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 114 such as a display, speakers, printer, etc. may also be included. To execute an inking application computing device 100 typically includes a touch-sensitive display that detects ink strokes from an inking pen or stylus, essentially acting as an input device.
Computing device 100 also contains communication connections 116 that allow the device to communicate with other computing devices 118, such as over a network. Communication connections 116 are one example of communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
Diagram application 220 may be executed on computing device 202 providing a diagram based on user input. Diagram application 220 may be run centrally on computing device 202 or in a distributed manner over several computing devices managed by one or more servers (e.g. server 232). Computing device 202 may communicate with other computing devices such as laptop PC 236, desktop PC 238, and the like, over network 210 as part of the operation of diagram application 220.
Moreover, any computing device associated with the diagram application may store data at or receive data from data store 234. In an example embodiment, diagram application 220 may include style engine 224 and layout engine 226 that interact in assigning style labels and color schemes to key shapes of a diagram. Style elements, color elements, and other information may be stored in and retrieved from data model store 222. In another embodiment, diagram application 220 may be executed in a distributed manner and data model and other elements may be stored in data store 234.
Network 210 may be a secure network such as an enterprise network, or an unsecure network such as a wireless open network. Network 210 provides communication between the nodes described above. By way of example, and not limitation, network 210 may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
Many other configurations of computing devices, applications, data sources, and systems may be employed to implement style extensibility applied to a group of shapes by editing text files.
A method and data model according to aspects described herein enables a user or a programmer to create a style definition for a layout definition, as long as the layout definition and the style definitions follow a set of rules. Using the set of rules ensures any new or existing style definition's compatibility with any new or existing layout definition. A consistent look-and-feel between possible layouts is also provided.
The layout and style definitions are based on a data model that ensures that the underlying layout is built upon data that is structured. The structure of the data is hierarchical and directional.
The layout definitions may contain variables called style labels, which are used to identify key shapes in a layout that are then matched and specified by the style definition. The use of the style labels is consistent with the use of the style labels in the style definition.
Referring to
A style, size, and direction of the connectors along with a size, shape, and positioning of the objects represents the relationship between the elements of the diagram. For example, in an organizational structure diagram, size and direction of connectors may indicate a hierarchy and type of relationship between members, while size, shape, and positioning of the objects may further indicate a position of each member in the organizational hierarchy.
As mentioned previously, a user may be provided the ability to select a style and color scheme for the diagram. By assigning style labels that define certain properties and color schemes of the shapes independently from the layout definition, a look-and-feel of the diagram may be preserved while changing to a different presentation.
Diagram 320 is a different style representation of diagram 310. Objects in diagram 320 (e.g. object 322) are in 3D form as well as connectors (e.g. connector 324). Font type of text (e.g. content 326) is preserved while a different color scheme is used for the objects, connectors and content.
Diagram 330 is yet another style representation of diagram 310. The objects (e.g. object 332) and the connectors (e.g. connector 334) are in button style (concave 3D with contours). Select attributes of shapes, connectors, and content, such as font type, shadowing, 3D/2D presentation, outlining, and the like may be determined by the style definition independent of the layout definition.
Diagram 340 shows a further style representation of diagram 310 with objects and connectors (e.g. object 324 and connector 344) in convex 3D style. A different color scheme is also used. While text is shown in light color in all of the objects, a different color scheme may also be selected for the text (e.g. content 346).
Different styles are implemented in each diagram with varying color schemes 2D or 3D effects, and outlining techniques. While
As shown in diagram 500, semantic model 502 defines hierarchical relationships between the elements of the diagram. There may be various ways of providing that hierarchy information. According to one embodiment, the user enters the information in a text-based form such as a bulleted list. Each line in the list indicates an object to the placed on the diagram, whereas tabs in each line determine a hierarchical status of each object. For example, semantic model 502 includes four elements with three tab levels (the last two elements being at the same tab level). In a tree-style diagram, such as presentation model 506, each tab level may correspond to a branch level.
Layout definition 504 includes information associated with converting the semantic model to a presentation model. Such information may include shapes to be assigned to text entries in the semantic model, diagram type (e.g. radial, tree, circular), connection types (e.g. arrows), color scheme, and style of the elements.
Once a layout engine (part of the diagram application) applies the layout definition, presentation model 506 is created. In the example diagram, presentation model 506 is in tree style. Accordingly, first entry “Trees” is assigned to a top level shape (object 512), second entry “Firs” is assigned to a second level shape (object 514), and third and fourth entries “Douglas” and “Noble” are assigned to objects 516 and 518 at the third hierarchical level.
In rendering the presentation model from the semantic model, the layout engine interacts with a style engine receiving information associated with style and color of the elements. By rendering the style and color properties independent from the layout definitions, a consistent look-and-feel between possible layouts may be provided. Furthermore, style definitions and color schemes may be modified at any time independent of the rendering of the diagram. New style definitions and color schemes may even be added.
Diagram 600 shows how key shapes are assigned identifiers (style labels) that are used to decouple layout definitions and style definitions. Layout definition 604 is still employed to render presentation model 606. But in this case, objects at each hierarchy level are assigned a style label. For example, object 612 at the top level is node 0, object 614 at the second level is node 2, objects 614 and 616 at the third level are assigned style label node 3.
The style labels are used to associate the key shapes with specific style definitions independent of the layout definition. Once the style labels are assigned, a look-and-feel of the presentation of the objects may be preserved even if the layout is modified, as shown in
Style labels may be assigned to any element of a diagram including, but not limited to, objects, connectors, and content. Moreover, embodiments are not limited to the example presentation model shown in
Objects 712, 714, 716, and 718 that were identified as node 0, node 2, and nodes 3, are assigned style properties through the style labels in style definition 720. In one embodiment, each style label may correspond to a number of properties (e.g. line, fill, and effect for objects, font, attribute, and effect for text, etc.) in a style sheet 730. For example, style label “node 0” is assigned style properties group 3 in style sheet 730. Similarly, style label “node 2” is assigned to style properties group 0 in style sheet 730. Style properties may be provided in other forms as well. Embodiments are not restricted to style sheets.
In diagram 800, color transform definition 840 is used to illustrate how objects such as object 812 are assigned a color within a color scheme (850) as part of the style label. Objects may be assigned single color, multiple colors, and different combinations of color schemes. Style labels enable preservation of color schemes independently from layout definition such that a look-and-feel of the style is maintained when layout is modified.
Furthermore, color schemes may be modified after the diagram is rendered. New color schemes may be added at any point by the user.
While example diagrams and style and color scheme definitions are shown in the above figures with limited elements, other implementations may include additional elements. Other properties, shapes, assignment types, and labels may be implemented using the principles described herein.
Process 900 begins at operation 902, where a semantic model is received. Relationships in a connected diagram such as a state diagram, an organizational structure diagram, and the like, may be defined in many ways. According to one embodiment, elements (objects) of the diagram and their hierarchical relationships are defined by a user employing a text-based entry method. For example, the user may enter content text for each object on a single line in a text editor. Tabs may be used to indicate hierarchical status of each entry. Connections may be based on proximity of the text-based entries (e.g. text entries in adjacent lines indicate connected objects in the diagram). Processing moves from operation 902 to operation 904.
An integral part of the diagram is the style defining how objects, connectors, and their content is presented. According to embodiments, a layout engine interacts with a style engine, which retrieves style definitions at operation 904. Processing advances from operation 904 to operation 906, where style information is provided for style labels assigned key shapes identified in the presentation model.
As described previously, the style labels are independent from the layout definition and are assigned to key shapes. The style definitions called by the style labels provide information for style properties including, but not limited to, font type, font attribute (bold, italic, underlined, etc.), shadowing, 2D/3D presentation, outlining. While a style definition may include size information for all shapes or their content for general presentation, shape-specific size information is typically included in the layout (or diagram) definition. The reason for reserving shape and content size for individual objects to the layout diagram is the size of those representing hierarchical placement of the objects in the diagram (e.g. smaller size may indicate lesser significance).
Processing advances from operation 906 to operation 908, where the color scheme is determined and provided to the layout engine. In addition to the above described example properties, style definition may also include color information for the objects (or the whole diagram). Color information may be determined by the style labels or by a separate color scheme definition. As explained in conjunction with
At operation 910, layout definition is determined. The layout engine of a diagram application determines layout definitions from text-based entries described above and default parameters associated with specific diagram and object types. For example, the hierarchical structure defined by the text-based user input may result in a number of different layouts depending on diagram type, such as radial, circular, tree-style, and the like. Processing advances from operation 910 to operation 912.
At operation 912, the diagram is rendered. The layout engine places objects and connectors on a canvas based on the layout (or diagram) definition(s) and user input generating a presentation model. The style and color scheme for the presentation model are implemented as provided by the style engine.
In some embodiments, the user may be provided with an opportunity to modify elements or whole style definitions. The user may even be provided with an opportunity to create their own style and apply to the diagram, because the style definitions are independent from the layout definitions. After operation 912, processing moves to a calling process for further actions.
The operations included in process 900 are for illustration purposes. Providing style extensibility to a group of shapes by editing text files may be implemented by a similar process with fewer or additional steps, as well as in different order of operations.
The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments.
