Hi Wishad,

DSI PrintManager does a few things, and does them well.

First, it provides a simple, WYSIWYG graphic user interface for creating printable documents. The size of the document in the PagePanel is the size of the document to be printed.

Second, PrintElements can be moved and resized by dragging and dropping with a mouse. Even images can be resized in the same way.

Third, there are no grids, sections, or any sort of difficult interface items to deal with. What you see is truly what you get. If you put a table of data into the PrinterDocument, it simply goes where you put it. It may jump or resize itself to fit inside the margins of the page, but that's it. If you want to add a header, you simply add other PrintElements above the table. The application is smart enough to know that if it's above the top of the table, it's part of the header. Of course, you need to specify whether these PrintElements are to be repeated on all pages. But that's about the size of it.

Fourth, it provides a completely extensible .Net programming interface, which means that it can be used with or without the GUI, in applications you write with the Microsoft .Net Framework. In addition, you can create your own extensions using the base PrintElement and PrintElementData classes.

Finally, your documents can be saved to an XML file format (with a .pdd extension). The XML includes everything, including images and database data, and can be transformed using XSL to any other document format you wish. At present, support for transforming to HTML is already built into the application. We hope to add Microsoft Word to the list of transforms next.

How does it work? Well, Printing from computers today is not what it used to be. Back in the day, printers supplied fonts and all sorts of other necessary software to create printed documents. But today, printers essentially print images. What your word processing software or whatever other software you use sends to the printer is an image.

An image is a rectangle with something drawn or "painted" inside it. In addition, like an HTML page (such as this one), it may contain other smaller rectangles with different things drawn in them. Sometimes they overlap. So, they can be stacked.

DSI PrintManager uses 2 base classes, PrintElementData and PrintElement, to create these rectangles. The PrintElementData class is the class which holds all the information about what to draw and how to draw it. The PrintElement class is a container for a PrintElementData class instance, and provides a user interface for interacting with it.

There are 6 current PrintElement/PrintElementData classes currently:


TextPrintElement creates a rectangle with text in it.
LinePrintElement creates a horizontal or vertical line.
BoxPrintElement creates a box.
ImagePrintElement creates an image.
TablePrintElement creates a table from a database.
LabelPrintElement creates sheets of labels.


These 6 PrintElement classes provide all the basic functionality needed to create printable documents. In fact, the ImagePrintElement can hold any kind of image, so it draw anything that fits in a single page.

As for your question about databases other than SQL Server, well, believe me, that is definitely high on our list of capabilities to add! It's not so much a problem of handling the data; it's just a matter of the time involved in building the various supporting Control interfaces to do it. I realize this is important, and appreciate your input.

In any case, it can create other printable documents without SQL Server, just not database reports. The classes that it runs on are included in the Miradyne Component Library, and these classes can make printing from an application much easier. I would recommend trying them out, and continuing to give us your feedback.

Thanks again!