US20140111521A1 - Rendering source content for display - Google Patents
Rendering source content for display Download PDFInfo
- Publication number
- US20140111521A1 US20140111521A1 US14/083,014 US201314083014A US2014111521A1 US 20140111521 A1 US20140111521 A1 US 20140111521A1 US 201314083014 A US201314083014 A US 201314083014A US 2014111521 A1 US2014111521 A1 US 2014111521A1
- Authority
- US
- United States
- Prior art keywords
- rendering
- source content
- drawing operations
- predefined
- calls
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
- G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T11/00—2D [Two Dimensional] image generation
- G06T11/20—Drawing from basic elements, e.g. lines or circles
Definitions
- a fixed-document file preserves document fidelity and appearance regardless of the type of device on which the document is presented.
- a fixed-document file includes markup language or objects that define the layout and visual appearance of each page of the document as well as rules that describe the processing, rendering, and printing intent of the document.
- the manner in which these rules are implemented may allow for great flexibility in the manner in which a document is rendered to accommodate differences in functionality of different rendering engines.
- differences in rendering engines may cause some rendering engines to render a fixed document file with sub-optimal rendering fidelity, rendering time, memory usage, and/or output file size. This may result in decreased quality of output, resulting in decreased user satisfaction.
- a method for rendering source content for display in a destination figure may include receiving the source content, replicating the source content in a region surrounding the source content, such that replicated source content is aligned with the source content, extracting an axis-aligned rectangular tile containing the source content from the region, and rendering the axis-aligned rectangular tile onto the destination figure.
- FIG. 1 is an architecture diagram of an embodiment of a rendering system.
- FIG. 2 is a flow diagram of an embodiment of a method for rendering source content for display on a destination figure.
- FIG. 3 is an example implementation of the flow diagram of FIG. 2 for rendering source content for display on a destination figure.
- FIG. 4 is a flow diagram of another embodiment of a method for rendering source content for display on a destination figure.
- FIG. 5 is a schematic diagram of an embodiment of a computing device on which the rendering system of FIG. 1 may be implemented.
- FIG. 1 illustrates a system 100 for rendering source content for display. More particularly, system 100 may operate in the context of rendering source content formatted according to XML Paper Specification (XPS) for display.
- Source content of XPS rendered by system 100 may be displayed on a display device or printed for display on another medium, such as paper.
- Source content of XPS may be contained in files, streamed to a destination, generated in-place, or sent across a network.
- System 100 may include a WINDOWS® Presentation Foundation (WPF) application 102 .
- WPF application 102 may be deployed as a programming model to unify a variety of application services related to visual aspects of the WINDOWS® operating system, such as fixed document rendering.
- WPF WINDOWS® Presentation Foundation
- WPF application 102 may generate an XPS container 106 which may be a fixed document file or other source containing source content.
- XPS application 104 may call XPS serialization module 112 to read Extensible Application Markup Language (XAML) code from WPF application 102 and create corresponding parts in the XPS document. Operation of XPS application 104 may affect rendering of source content in XPS container 106 .
- XAML Extensible Application Markup Language
- the print path to render the source content begins by XPS application 104 and WPF application 102 calling spooler/filter pipeline 108 to read XPS container 106 to identify source content to be rendered.
- XPS application 104 may call XPS print application programming interface (API) 110 to request print services to render the source content.
- XPS print API 110 may call Open Packaging Conventions (OPC) services 122 which may generate an XPS OM object 114 that may be used by an XPS-to-GDI Conversion (XGC) light module 116 to convert the XPS formatted source content and corresponding print instructions into a Graphics Device Interface (GDI) format for rendering.
- OPC Open Packaging Conventions
- XGC light module 116 may be alternately referred to as a source content conversion module since the module may convert XPS formatted source content into a GDI compatible format for rendering.
- XGC-light module 116 may send the converted source content to DirectWrite rendering engine 128 and DIRECT2D rendering engine 130 to be rendered for display. Further, XGC light module 116 may send the converted source content to GDI exporter 124 to package the source content for rendering by GDI rendering engine 132 .
- XGC light module 116 may also use Print Ticket Services (PRNTVPT) module 134 , and Windows Imaging Component (WIC) 126 to render source content
- PRNTVPT Print Ticket Services
- WIC Windows Imaging Component
- spooler/filter pipeline 108 may host rasterization filter module 120 which may use XPS OM object 114 and OPC services 122 to filter or identify XPS source content to be converted into raster image instructions by XPS rasterizer module 118 for rendering by a rendering engine such as DIRECT2D rendering engine 130 or DirectWrite rendering engine 128 .
- XPS rasterizer module 118 may be called by XPS serialization module 112 and may receive XPS formatted parts that may be utilized to rasterize the source content. Further, XPS serialization module 112 may send XPS formatted parts or instructions to WIC 126 to facilitate rendering of the XPS source content.
- the format of source content of an XPS document may be unchanged throughout the printing process, and thus may retain the original quality and fidelity of the document all the way through the end of the print path.
- the XPS print path supports a modular, filter-based architecture that allows for print rendering functions to be moved out of the application and into the print path. As such, rendering of XPS source content may be more efficiently leveraged by other applications.
- FIG. 2 illustrates a method 200 of rendering source content for display in a destination figure.
- method 200 prescribes a way of generating GDI-compatible rectangular tiles that include the source content which may be applied to a bitmap created by the GDI rendering engine during the print process.
- Method 200 may be particularly applicable to source content that is not axis aligned or otherwise easily rasterized.
- Method 200 may include, at 202 receiving source content.
- the source content may be contained in an XPS container 106 that may be read by spooler/filter pipeline 108 as called by XPS application 104 of system 100 .
- source content may be received from across a network, or more particularly from a stream.
- the method may include replicating the source content in a region surrounding the source content, such that replicated source content is aligned with the source content.
- the source content may be replicated such that the replicated source content is aligned on all sides of the source content to form a surrounding region.
- the surrounding region is defined by an outer perimeter of the replicated source content.
- replication of the source content may be achieved by performing flipping operations of the source content. Flipping operations may be performed based on a tile-mode of a brush for printing the source content.
- the tile mode may be set to one or more of a variety of flipping operations that may be performed when replicating the source content, such as flipping about the X-axis, flipping about the Y-axis, and flipping about both the X-axis and the Y-axis.
- the method may include extracting an axis-aligned rectangular tile containing the source content from the region. Since the replicated source content is aligned with the original source content as a result of the flipping operation, there is no distortion and the axis-aligned rectangular tile is an accurate representation of the source content.
- the axis-aligned tile is GDI-compatible for printing of the source content on a destination figure. Specifically, the rectangular tile may be easily rasterized since the dimensions of the tile are axis aligned.
- the method may include rendering the axis-aligned rectangular tile onto the destination figure.
- a region that fully includes the source content may be created from which an axis-aligned rectangular tile may be extracted. Since the axis-aligned rectangular tile is GDI-compatible, the source content may be rendered utilizing GDI while avoiding resource intensive clipping operations. Accordingly, rendering of source content using GDI may be performed in quicker and more resource efficient manner.
- method 200 may be implemented using the hardware and software of system 100 described above, or via other suitable hardware and software, to render source content of a fixed document file such as an XPS file or from another source for display.
- receiving, extracting, and replicating are performed by XPS-to-GDI conversion module 116 of XPS rendering system 100 and rendering the source content is performed by GDI rendering engine 132 of system 100 .
- method 200 may be utilized in the rendering of source content by rendering engines other than a GDI rendering engine.
- FIG. 3 shows an example implementation of method 200 as described above that may be used in the rendering of source content 302 by a GDI rendering engine.
- source content 302 (indicated by solid lines) is a parallelogram that is not axis aligned.
- the source content is processed to be axis aligned.
- axis alignment of the source content facilitates rasterization performed by the GDI rendering engine.
- a replication (in some cases flipping) operation is performed on the source content 302 to create replicated source content 304 (indicated by dotted lines).
- the replicated source content 304 are parallelograms that are not axis aligned, but are aligned with source content 302 on all four sides of source content 302 .
- the source content 302 in combination with replicated source content 304 create a region 306 of source content that is neither shifted nor distorted.
- the region 306 may be large enough to extract an axis-aligned rectangular tile 308 (indicated by dot-dashed lines) that includes an accurate representation of the source content that can be rendered by the GDI rendering engine.
- Method 200 provides an alternative to performing clipping operations, which can result in quicker rendering of source content while freeing up resources for other computing tasks.
- FIG. 4 illustrates a method 400 of rendering source content for display in a destination figure.
- method 400 prescribes a way of providing source content that includes rendering code-paths that are optimized for a specified rendering engine (e.g., a GDI rendering engine).
- Method 400 may include, at 402 receiving source content.
- the file may be XPS container 106 that may be read by spooler/filter pipeline 108 as called by XPS application 104 of system 100 .
- the method may include identifying multiple drawing operations to print the source content.
- the drawing operations may include associated rendering primitives.
- the drawing operations may include stroking, filling, line segments, and cubic Bezier segments, as well as other curve segments (e.g., quadratic Bezier segments).
- the method may include determining if all drawing operations of the source content have been identified. By delaying drawing of the drawing operation until all drawing operations of the source content have been identified, the type and number of geometry figures and other drawing operations for printing the source content may be tracked and considered for combination into a predefined rendering call when possible. If all drawing operations have been identified, the method moves to 408 . Otherwise, all drawing operations have not been identified, and the method returns to 404 to continue identifying drawing operations for printing the source content. It will be appreciated in other embodiments, instead of determining if all drawing operations have been identified, the method may include at 406 determining if a threshold subset of drawings operations have been identified sufficient to enable selection of predefined rendering calls at 408 .
- the method may include, upon identifying all or a threshold subset of the drawing operations, selecting predefined rendering calls for a specified rendering engine. At least some of the predefined rendering calls for the specified rendering engine may be selected to include a plurality of the identified drawing operations.
- the predefined rendering calls are selected to include a plurality of the multiple drawing operations whenever possible.
- the predefined rendering calls may be selected in order to minimize the number and/or size of the associated rendering primitives generated by the specified rendering engine.
- the predefined rendering calls may include geometric figures (e.g., Polydraw). For example, a plurality of line-segment type drawing primitives may be identified as being positioned to form a square geometry. A predefined rendering call to print the square may be selected in place of each individual line-segment type drawing primitive. By replacing the four line segment drawing primitives with a predefined square geometry rendering call, the length of the rendering output file may be reduced.
- the predefined rendering calls may include collections of geometric figures (e.g., PolyPolygon).
- the predefined rendering calls that are selected may vary depending on the rendering engine that is specified, since different rendering engines may be capable of executing different predefined rendering calls.
- a GDI rendering engine may support rendering calls for drawing geometries comprised of line-segments and cubic Bezier segments.
- the GDI rendering engine in particular, also provides optimized code-paths for common cases like polygons, collections of polygons (with no Beziers), stroking without filling, filling without stroking, etc.
- the method may include rendering the source content utilizing the selected predefined rendering calls via the specified rendering engine.
- appropriate rendering calls may be selected in which drawing operations may be combined in predefined rendering calls that are optimized for the specified rendering engine. Accordingly, the code-path optimization can result in quicker rendering times and reduced output file size for the source content.
- method 400 may be implemented using the hardware and software described above, or via other suitable hardware and software to render source content of a fixed document file such as an XPS file or from another source for display.
- receiving, identifying, and selecting are performed by XPS-to-GDI conversion module 116 of XPS rendering system 100 and rendering the source content is performed by GDI rendering engine 132 of system 100 .
- method 400 may be utilized in the rendering of source content by rendering engines other than a GDI rendering engine.
- FIG. 5 is a schematic diagram of an embodiment of a computing device 500 on which system 100 may be implemented.
- Computing device 500 may be virtually any suitable computing device including a mainframe computer, personal computer, laptop computer, portable data assistant (PDA), computer-enabled wireless telephone, networked computing device, printing device, or other suitable computing device.
- Computing device may be optionally connected to other computing devices via computer networks 512 , such as the Internet.
- Computing device 500 may include a processing subsystem 502 , volatile and non-volatile memory represented as data storage 504 which may communicate via communication subsystem (e.g., computer bus) 506 .
- Computing device 500 may be configured to execute programs stored in data storage 504 or a different remote storage device using processing subsystem 502 .
- computing device 500 may include a display subsystem 508 .
- display subsystem 508 may be used to present a visual representation of data held by data storage 504 .
- a printer device 510 may be in communication with computing device 500 via communication subsystem 506 or otherwise incorporated with computing device 500 .
- printer device 510 may print a visual representation of data held by data storage 504 for display on a tangible medium, such as paper.
- the herein described methods and processes change the data held by the data storage 504 , and thus transform the state of the data storage 504 .
- the state of display subsystem 508 may likewise be transformed to visually represent changes in the underlying data.
- printer device 510 may print visual representations of the transformations of the underlying data to paper or other tangible medium.
- program refers to software or firmware components that may be executed by, or utilized by, one or more computing devices described herein, and is meant to encompass individual or groups of executable files, data files, libraries, drivers, scripts, database records, etc. It will be appreciated that computer-readable media may be provided having program instructions stored thereon, which upon execution by a computing device, cause the computing device to execute the methods described above and cause operation of the systems described above.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- General Engineering & Computer Science (AREA)
- Processing Or Creating Images (AREA)
Abstract
A method for rendering source content for display in a destination figure is provided. The method may include receiving the source content of the file, replicating the source content in a region surrounding the source content, such that replicated source content is aligned with the source content, extracting an axis-aligned rectangular tile containing the source content from the region, and rendering the axis-aligned rectangular tile onto the destination figure.
Description
- This application is a divisional of U.S. patent application Ser. No. 12/333,330, titled RENDERING SOURCE CONTENT FOR DISPLAY and filed Dec. 12, 2008, the entire disclosure of which is hereby incorporated by reference.
- A fixed-document file preserves document fidelity and appearance regardless of the type of device on which the document is presented. In order to preserve the fidelity of a document, a fixed-document file includes markup language or objects that define the layout and visual appearance of each page of the document as well as rules that describe the processing, rendering, and printing intent of the document. The manner in which these rules are implemented may allow for great flexibility in the manner in which a document is rendered to accommodate differences in functionality of different rendering engines. However, differences in rendering engines may cause some rendering engines to render a fixed document file with sub-optimal rendering fidelity, rendering time, memory usage, and/or output file size. This may result in decreased quality of output, resulting in decreased user satisfaction.
- A method for rendering source content for display in a destination figure is provided. The method may include receiving the source content, replicating the source content in a region surrounding the source content, such that replicated source content is aligned with the source content, extracting an axis-aligned rectangular tile containing the source content from the region, and rendering the axis-aligned rectangular tile onto the destination figure.
- 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 to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
-
FIG. 1 is an architecture diagram of an embodiment of a rendering system. -
FIG. 2 is a flow diagram of an embodiment of a method for rendering source content for display on a destination figure. -
FIG. 3 is an example implementation of the flow diagram ofFIG. 2 for rendering source content for display on a destination figure. -
FIG. 4 is a flow diagram of another embodiment of a method for rendering source content for display on a destination figure. -
FIG. 5 is a schematic diagram of an embodiment of a computing device on which the rendering system ofFIG. 1 may be implemented. -
FIG. 1 illustrates asystem 100 for rendering source content for display. More particularly,system 100 may operate in the context of rendering source content formatted according to XML Paper Specification (XPS) for display. Source content of XPS rendered bysystem 100 may be displayed on a display device or printed for display on another medium, such as paper. Source content of XPS may be contained in files, streamed to a destination, generated in-place, or sent across a network.System 100 may include a WINDOWS® Presentation Foundation (WPF)application 102. WPFapplication 102 may be deployed as a programming model to unify a variety of application services related to visual aspects of the WINDOWS® operating system, such as fixed document rendering. WPFapplication 102 may generate anXPS container 106 which may be a fixed document file or other source containing source content.XPS application 104 may callXPS serialization module 112 to read Extensible Application Markup Language (XAML) code fromWPF application 102 and create corresponding parts in the XPS document. Operation ofXPS application 104 may affect rendering of source content inXPS container 106. - The print path to render the source content begins by
XPS application 104 andWPF application 102 calling spooler/filter pipeline 108 to readXPS container 106 to identify source content to be rendered.XPS application 104 may call XPS print application programming interface (API) 110 to request print services to render the source content. XPSprint API 110 may call Open Packaging Conventions (OPC)services 122 which may generate an XPSOM object 114 that may be used by an XPS-to-GDI Conversion (XGC)light module 116 to convert the XPS formatted source content and corresponding print instructions into a Graphics Device Interface (GDI) format for rendering. XGClight module 116 may be alternately referred to as a source content conversion module since the module may convert XPS formatted source content into a GDI compatible format for rendering. XGC-light module 116 may send the converted source content to DirectWriterendering engine 128 and DIRECT2Drendering engine 130 to be rendered for display. Further, XGClight module 116 may send the converted source content to GDIexporter 124 to package the source content for rendering by GDIrendering engine 132. XGClight module 116 may also use Print Ticket Services (PRNTVPT)module 134, and Windows Imaging Component (WIC) 126 to render source content - Continuing with
FIG. 1 , spooler/filter pipeline 108 may hostrasterization filter module 120 which may use XPS OMobject 114 andOPC services 122 to filter or identify XPS source content to be converted into raster image instructions by XPSrasterizer module 118 for rendering by a rendering engine such as DIRECT2Drendering engine 130 or DirectWriterendering engine 128. XPSrasterizer module 118 may be called byXPS serialization module 112 and may receive XPS formatted parts that may be utilized to rasterize the source content. Further,XPS serialization module 112 may send XPS formatted parts or instructions to WIC 126 to facilitate rendering of the XPS source content. By converting various parts and print instructions to XPS format, the format of source content of an XPS document may be unchanged throughout the printing process, and thus may retain the original quality and fidelity of the document all the way through the end of the print path. Further, the XPS print path supports a modular, filter-based architecture that allows for print rendering functions to be moved out of the application and into the print path. As such, rendering of XPS source content may be more efficiently leveraged by other applications. - Within the context of the
system 100 described above, several methods for rendering source content may be practiced, as described below with reference toFIGS. 2 and 4 . As one example,FIG. 2 illustrates amethod 200 of rendering source content for display in a destination figure. In particular,method 200 prescribes a way of generating GDI-compatible rectangular tiles that include the source content which may be applied to a bitmap created by the GDI rendering engine during the print process.Method 200 may be particularly applicable to source content that is not axis aligned or otherwise easily rasterized.Method 200 may include, at 202 receiving source content. As discussed above, in one embodiment, the source content may be contained in anXPS container 106 that may be read by spooler/filter pipeline 108 as called byXPS application 104 ofsystem 100. In some cases, source content may be received from across a network, or more particularly from a stream. - At 204, the method may include replicating the source content in a region surrounding the source content, such that replicated source content is aligned with the source content. In particular, the source content may be replicated such that the replicated source content is aligned on all sides of the source content to form a surrounding region. In some cases, the surrounding region is defined by an outer perimeter of the replicated source content. In some cases, replication of the source content may be achieved by performing flipping operations of the source content. Flipping operations may be performed based on a tile-mode of a brush for printing the source content. For example, the tile mode may be set to one or more of a variety of flipping operations that may be performed when replicating the source content, such as flipping about the X-axis, flipping about the Y-axis, and flipping about both the X-axis and the Y-axis.
- At 206, the method may include extracting an axis-aligned rectangular tile containing the source content from the region. Since the replicated source content is aligned with the original source content as a result of the flipping operation, there is no distortion and the axis-aligned rectangular tile is an accurate representation of the source content. The axis-aligned tile is GDI-compatible for printing of the source content on a destination figure. Specifically, the rectangular tile may be easily rasterized since the dimensions of the tile are axis aligned. At 208, the method may include rendering the axis-aligned rectangular tile onto the destination figure.
- By replicating the source content, a region that fully includes the source content may be created from which an axis-aligned rectangular tile may be extracted. Since the axis-aligned rectangular tile is GDI-compatible, the source content may be rendered utilizing GDI while avoiding resource intensive clipping operations. Accordingly, rendering of source content using GDI may be performed in quicker and more resource efficient manner.
- It will be appreciated that
method 200 may be implemented using the hardware and software ofsystem 100 described above, or via other suitable hardware and software, to render source content of a fixed document file such as an XPS file or from another source for display. In one example, receiving, extracting, and replicating are performed by XPS-to-GDI conversion module 116 ofXPS rendering system 100 and rendering the source content is performed byGDI rendering engine 132 ofsystem 100. It will be appreciated thatmethod 200 may be utilized in the rendering of source content by rendering engines other than a GDI rendering engine. -
FIG. 3 shows an example implementation ofmethod 200 as described above that may be used in the rendering ofsource content 302 by a GDI rendering engine. In the illustrated example, source content 302 (indicated by solid lines) is a parallelogram that is not axis aligned. In order to rendersource content 302 via the GDI rendering engine, the source content is processed to be axis aligned. In particular, axis alignment of the source content facilitates rasterization performed by the GDI rendering engine. Thus, a replication (in some cases flipping) operation is performed on thesource content 302 to create replicated source content 304 (indicated by dotted lines). The replicatedsource content 304 are parallelograms that are not axis aligned, but are aligned withsource content 302 on all four sides ofsource content 302. Thesource content 302 in combination with replicatedsource content 304 create aregion 306 of source content that is neither shifted nor distorted. Theregion 306 may be large enough to extract an axis-aligned rectangular tile 308 (indicated by dot-dashed lines) that includes an accurate representation of the source content that can be rendered by the GDI rendering engine. - In previous operations utilizing a GDI rendering engine, source content that was not axis-aligned would have to be replicated and clipped to create source content that is axis aligned for rasterization. The clipping operations can be resource expensive, consuming valuable processor time, and resulting in slower rendering.
Method 200 provides an alternative to performing clipping operations, which can result in quicker rendering of source content while freeing up resources for other computing tasks. -
FIG. 4 illustrates amethod 400 of rendering source content for display in a destination figure. In particular,method 400 prescribes a way of providing source content that includes rendering code-paths that are optimized for a specified rendering engine (e.g., a GDI rendering engine).Method 400 may include, at 402 receiving source content. As discussed above, in one embodiment, the file may beXPS container 106 that may be read by spooler/filter pipeline 108 as called byXPS application 104 ofsystem 100. - At 404, the method may include identifying multiple drawing operations to print the source content. The drawing operations may include associated rendering primitives. For example, the drawing operations may include stroking, filling, line segments, and cubic Bezier segments, as well as other curve segments (e.g., quadratic Bezier segments).
- At 406, the method may include determining if all drawing operations of the source content have been identified. By delaying drawing of the drawing operation until all drawing operations of the source content have been identified, the type and number of geometry figures and other drawing operations for printing the source content may be tracked and considered for combination into a predefined rendering call when possible. If all drawing operations have been identified, the method moves to 408. Otherwise, all drawing operations have not been identified, and the method returns to 404 to continue identifying drawing operations for printing the source content. It will be appreciated in other embodiments, instead of determining if all drawing operations have been identified, the method may include at 406 determining if a threshold subset of drawings operations have been identified sufficient to enable selection of predefined rendering calls at 408.
- At 408, the method may include, upon identifying all or a threshold subset of the drawing operations, selecting predefined rendering calls for a specified rendering engine. At least some of the predefined rendering calls for the specified rendering engine may be selected to include a plurality of the identified drawing operations.
- In some embodiments, the predefined rendering calls are selected to include a plurality of the multiple drawing operations whenever possible. Thus, the predefined rendering calls may be selected in order to minimize the number and/or size of the associated rendering primitives generated by the specified rendering engine. In some cases, the predefined rendering calls may include geometric figures (e.g., Polydraw). For example, a plurality of line-segment type drawing primitives may be identified as being positioned to form a square geometry. A predefined rendering call to print the square may be selected in place of each individual line-segment type drawing primitive. By replacing the four line segment drawing primitives with a predefined square geometry rendering call, the length of the rendering output file may be reduced. Further, in some cases, the predefined rendering calls may include collections of geometric figures (e.g., PolyPolygon).
- The predefined rendering calls that are selected may vary depending on the rendering engine that is specified, since different rendering engines may be capable of executing different predefined rendering calls. For example, a GDI rendering engine may support rendering calls for drawing geometries comprised of line-segments and cubic Bezier segments. The GDI rendering engine, in particular, also provides optimized code-paths for common cases like polygons, collections of polygons (with no Beziers), stroking without filling, filling without stroking, etc.
- At 410, the method may include rendering the source content utilizing the selected predefined rendering calls via the specified rendering engine. By delaying drawing of each of the drawing operations to identify the entire geometry of the source content, appropriate rendering calls may be selected in which drawing operations may be combined in predefined rendering calls that are optimized for the specified rendering engine. Accordingly, the code-path optimization can result in quicker rendering times and reduced output file size for the source content.
- It will be appreciated that
method 400 may be implemented using the hardware and software described above, or via other suitable hardware and software to render source content of a fixed document file such as an XPS file or from another source for display. In one example, receiving, identifying, and selecting are performed by XPS-to-GDI conversion module 116 ofXPS rendering system 100 and rendering the source content is performed byGDI rendering engine 132 ofsystem 100. It will be appreciated thatmethod 400 may be utilized in the rendering of source content by rendering engines other than a GDI rendering engine. - It will be appreciated that the modules of
system 100, which may perform at least some part of the above described methods, may be executed by a computing device.FIG. 5 is a schematic diagram of an embodiment of acomputing device 500 on whichsystem 100 may be implemented.Computing device 500 may be virtually any suitable computing device including a mainframe computer, personal computer, laptop computer, portable data assistant (PDA), computer-enabled wireless telephone, networked computing device, printing device, or other suitable computing device. Computing device may be optionally connected to other computing devices viacomputer networks 512, such as the Internet.Computing device 500 may include aprocessing subsystem 502, volatile and non-volatile memory represented asdata storage 504 which may communicate via communication subsystem (e.g., computer bus) 506.Computing device 500 may be configured to execute programs stored indata storage 504 or a different remote storage device usingprocessing subsystem 502. - In some embodiments,
computing device 500 may include adisplay subsystem 508. When included,display subsystem 508 may be used to present a visual representation of data held bydata storage 504. In some embodiments, aprinter device 510 may be in communication withcomputing device 500 viacommunication subsystem 506 or otherwise incorporated withcomputing device 500. When included,printer device 510 may print a visual representation of data held bydata storage 504 for display on a tangible medium, such as paper. The herein described methods and processes change the data held by thedata storage 504, and thus transform the state of thedata storage 504. The state ofdisplay subsystem 508 may likewise be transformed to visually represent changes in the underlying data. Further,printer device 510 may print visual representations of the transformations of the underlying data to paper or other tangible medium. - As used herein, the term “program” refers to software or firmware components that may be executed by, or utilized by, one or more computing devices described herein, and is meant to encompass individual or groups of executable files, data files, libraries, drivers, scripts, database records, etc. It will be appreciated that computer-readable media may be provided having program instructions stored thereon, which upon execution by a computing device, cause the computing device to execute the methods described above and cause operation of the systems described above.
- It should be understood that the embodiments herein are illustrative and not restrictive, since the scope of the invention is defined by the appended claims rather than by the description preceding them, and all changes that fall within metes and bounds of the claims, or equivalence of such metes and bounds thereof are therefore intended to be embraced by the claims.
Claims (20)
1. A method for rendering source content for display in a destination figure comprising:
receiving source content in a file;
identifying multiple drawing operations in the file to print the source content;
upon identifying the drawing operations, selecting one or more predefined rendering calls for a specified rendering engine, wherein at least some of the predefined rendering calls are selected to include a plurality of the drawing operations; and
rendering the source content to the destination figure utilizing the selected predefined rendering calls via the specified rendering engine.
2. The method of claim 1 , wherein the drawing operations include associated rendering primitives.
3. The method of claim 1 , wherein the predefined rendering calls are selected such that a number and/or size of the associated rendering primitives generated by the specified rendering engine is minimized.
4. The method of claim 1 , wherein identifying the drawing operations includes identifying all of the drawing operations to print the source content; and
wherein selecting is performed upon identifying all of the drawing operations, and the predefined rendering calls are selected to include a plurality of the drawing operations when possible.
5. The method of claim 1 , wherein the predefined rendering calls include geometric figures or collections of geometric figures.
6. The method of claim 1 , wherein the drawing operations include line segments, and cubic Bezier segments.
7. The method of claim 1 , wherein the file is a fixed document file.
8. The method of claim 7 , wherein the fixed document file is a XML Paper Specification (XPS) file.
9. The method of claim 8 , wherein the rendering engine is a graphics device interface (GDI) rendering engine of an XPS rendering system.
10. The method of claim 9 , wherein receiving, identifying, and selecting are performed by a XPS-to-GDI conversion module of the XPS rendering system.
11. A computing system comprising:
a processing subsystem; and
a data storage device holding instructions that when executed by the processing subsystem:
receive source content in a file;
identify multiple drawing operations in the file to print the source content;
upon identifying the drawing operations, select one or more predefined rendering calls for a specified rendering engine, wherein at least some of the predefined rendering calls are selected to include a plurality of the drawing operations; and
render the source content to a destination figure utilizing the selected predefined rendering calls via the specified rendering engine.
12. The computing system of claim 11 , wherein the drawing operations include associated rendering primitives.
13. The computing system of claim 11 , wherein the predefined rendering calls are selected such that a number and/or size of the associated rendering primitives generated by the specified rendering engine is minimized.
14. The computing system of claim 11 , wherein identifying the drawing operations includes identifying all of the drawing operations to print the source content; and
wherein selecting is performed upon identifying all of the drawing operations, and the predefined rendering calls are selected to include a plurality of the drawing operations when possible.
15. The computing system of claim 11 , wherein the predefined rendering calls include geometric figures or collections of geometric figures.
16. The computing system of claim 11 , wherein the drawing operations include line segments, and cubic Bezier segments.
17. The computing system of claim 11 , wherein the file is a fixed document file.
18. The computing system of claim 17 , wherein the fixed document file is a XML Paper Specification (XPS) file, and wherein the rendering engine is a graphics device interface (GDI) rendering engine of an XPS rendering system.
19. A method for rendering source content for display in a destination figure comprising:
receiving source content in a file;
identifying multiple drawing operations to print the source content;
upon identifying a number of drawing operations greater than a threshold number, selecting one or more predefined rendering calls for a specified rendering engine, wherein at least some of the predefined rendering calls are selected to include a plurality of the drawing operations, and wherein the threshold number of drawing operations is sufficiently large enough to enable selection of the predefined rendering calls; and
rendering the source content to the destination figure utilizing the selected predefined rendering calls via the specified rendering engine.
20. The method of claim 19 , wherein the threshold number of drawing operations is the total number of drawing operations for printing the source content.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/083,014 US20140111521A1 (en) | 2008-12-12 | 2013-11-18 | Rendering source content for display |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/333,330 US8587610B2 (en) | 2008-12-12 | 2008-12-12 | Rendering source content for display |
US14/083,014 US20140111521A1 (en) | 2008-12-12 | 2013-11-18 | Rendering source content for display |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/333,330 Division US8587610B2 (en) | 2008-12-12 | 2008-12-12 | Rendering source content for display |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140111521A1 true US20140111521A1 (en) | 2014-04-24 |
Family
ID=42242063
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/333,330 Active 2030-04-15 US8587610B2 (en) | 2008-12-12 | 2008-12-12 | Rendering source content for display |
US14/083,014 Abandoned US20140111521A1 (en) | 2008-12-12 | 2013-11-18 | Rendering source content for display |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/333,330 Active 2030-04-15 US8587610B2 (en) | 2008-12-12 | 2008-12-12 | Rendering source content for display |
Country Status (1)
Country | Link |
---|---|
US (2) | US8587610B2 (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9183186B2 (en) * | 2011-07-08 | 2015-11-10 | Microsoft Technology Licensing, Llc. | Conversion tool for XPS and OpenXPS documents |
US20130173386A1 (en) * | 2011-12-29 | 2013-07-04 | Chegg, Inc. | Providing Advertisements in a Digital Reading Platform |
CN102968807B (en) * | 2012-10-29 | 2015-12-16 | 广东威创视讯科技股份有限公司 | image automatic generation method and system |
RU2608883C2 (en) * | 2014-12-26 | 2017-01-25 | Общество С Ограниченной Ответственностью "Яндекс" | Image processing method and electronic device |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070146378A1 (en) * | 2005-11-05 | 2007-06-28 | Arm Norway As | Method of and apparatus for processing graphics |
US20080005212A1 (en) * | 2006-05-22 | 2008-01-03 | Levien Raphael L | Method and apparatus for interactive curve generation |
US20080007559A1 (en) * | 2006-06-30 | 2008-01-10 | Nokia Corporation | Apparatus, method and a computer program product for providing a unified graphics pipeline for stereoscopic rendering |
US20090110307A1 (en) * | 2007-10-29 | 2009-04-30 | Markowitz Moshe Itzhak | Method and system for efficient transmission of rich three-dimensional geometry and animation content over narrow band communication networks |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5751293A (en) * | 1994-08-24 | 1998-05-12 | Nippon Telegraph And Telephone Corp. | Pattern generation method and apparatus for automatic generation of continuous tile patterns along any arbitrary side |
EP0769761A1 (en) * | 1995-10-12 | 1997-04-23 | Schablonentechnik Kufstein Aktiengesellschaft | Method for generating patterns |
US6191800B1 (en) * | 1998-08-11 | 2001-02-20 | International Business Machines Corporation | Dynamic balancing of graphics workloads using a tiling strategy |
US7259766B1 (en) * | 1998-10-30 | 2007-08-21 | Autodesk, Inc. | Aperiodic tiling of textured images |
AUPQ995700A0 (en) * | 2000-09-07 | 2000-09-28 | Canon Kabushiki Kaisha | Method and apparatus for printing computer generated images |
US7417645B2 (en) * | 2003-03-27 | 2008-08-26 | Microsoft Corporation | Markup language and object model for vector graphics |
GB0307095D0 (en) * | 2003-03-27 | 2003-04-30 | Imagination Tech Ltd | Improvements to a tiling system for 3d rendered graphics |
GB2404546B (en) * | 2003-07-25 | 2005-12-14 | Purple Interactive Ltd | A method of organising and displaying material content on a display to a viewer |
US7511718B2 (en) * | 2003-10-23 | 2009-03-31 | Microsoft Corporation | Media integration layer |
US20050259108A1 (en) * | 2004-05-21 | 2005-11-24 | Brett Chladny | System and method for dynamically generating images using repeatable textures |
US7813562B2 (en) | 2004-09-27 | 2010-10-12 | Intel Corporation | Low-latency remote display rendering using tile-based rendering systems |
US20070013723A1 (en) * | 2005-07-12 | 2007-01-18 | Microsoft Corporation | Magnification engine and interface for computers |
JP4785580B2 (en) * | 2006-03-17 | 2011-10-05 | キヤノン株式会社 | Image forming apparatus, control method therefor, and program |
JP4667280B2 (en) * | 2006-03-17 | 2011-04-06 | キヤノン株式会社 | Information processing apparatus, control method therefor, and program |
US7734412B2 (en) * | 2006-11-02 | 2010-06-08 | Yahoo! Inc. | Method of client side map rendering with tiled vector data |
US8471862B2 (en) * | 2007-03-09 | 2013-06-25 | Ati Technologies Ulc | Offset tiles in vector graphics |
GB0723537D0 (en) | 2007-11-30 | 2008-01-09 | Multi-core rasterisation in a tile based rendering system7743180001 | |
US8059119B2 (en) * | 2007-12-05 | 2011-11-15 | Stmicroelectronics S.R.L. | Method for detecting border tiles or border pixels of a primitive for tile-based rendering |
-
2008
- 2008-12-12 US US12/333,330 patent/US8587610B2/en active Active
-
2013
- 2013-11-18 US US14/083,014 patent/US20140111521A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070146378A1 (en) * | 2005-11-05 | 2007-06-28 | Arm Norway As | Method of and apparatus for processing graphics |
US20080005212A1 (en) * | 2006-05-22 | 2008-01-03 | Levien Raphael L | Method and apparatus for interactive curve generation |
US20080007559A1 (en) * | 2006-06-30 | 2008-01-10 | Nokia Corporation | Apparatus, method and a computer program product for providing a unified graphics pipeline for stereoscopic rendering |
US20090110307A1 (en) * | 2007-10-29 | 2009-04-30 | Markowitz Moshe Itzhak | Method and system for efficient transmission of rich three-dimensional geometry and animation content over narrow band communication networks |
Also Published As
Publication number | Publication date |
---|---|
US8587610B2 (en) | 2013-11-19 |
US20100153842A1 (en) | 2010-06-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9753677B2 (en) | Apparatus and methods for image processing optimization for variable data printing | |
US7583410B1 (en) | System to create image transparency in a file generated utilizing a print stream | |
CN101452533B (en) | Rendering apparatus, rendering method and printing device | |
KR20060048511A (en) | Common charting using shapes | |
US20030076535A1 (en) | Banded compositor for variable data | |
JP2009193573A (en) | System and method for print resource management | |
JP2019537807A (en) | System and method for automatically reformatting a publication | |
US20140111521A1 (en) | Rendering source content for display | |
US9977771B2 (en) | System and method for printable document viewer optimization | |
US20020191199A1 (en) | Printing system | |
CN109815451B (en) | PDF (Portable document Format) generation method, device and equipment | |
US8169625B2 (en) | Handling unhandled raster operations in a document conversion | |
US20210125386A1 (en) | Systems and methods for clipping images | |
US10657427B2 (en) | Information processing apparatus, information processing method and storage medium | |
JP2011175629A (en) | System and method for rendering of printable data | |
US20100079474A1 (en) | Methods for rendering source content of a file for display on a destination figure | |
US7710602B2 (en) | Systems and methods for context-based adaptive image processing using segmentation | |
US8159688B2 (en) | Automated systems and methods for prepress workflow processing | |
US8243313B2 (en) | Cache optimization mechanism | |
US8762830B2 (en) | Rendering data in the correct z-order | |
JP2017097463A (en) | Print control system, print control device, and program | |
US20140240787A1 (en) | Mechanism for Applying Marks After Rasterization | |
EP2293180B1 (en) | PDL data processing device and PDL data creating device | |
US20100103446A1 (en) | Methods and systems for printing documents with semi-transparent graphical elements | |
JP2013121674A (en) | Apparatus, and method for processing image, and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034747/0417 Effective date: 20141014 Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:039025/0454 Effective date: 20141014 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |