By Tim Dexter on Apr 09, 2008
We have a little known API that is really very powerful - the fact that its little known is my fault. The documentation is light to say the least and I promised Leslie that I would have a white paper out a long time ago to walk folks through some examples. Its not a paper yet cos I can be lazee and irreverent here on the blog and get information out much more quickly. It will be a paper eventually I promise, mybe even get into the documentation so you are not trawling all over the place for information.
So, what is it? How many of you are involved in pulling together multiple documents or maybe coming up with a programmatic way of pulling them together? Maybe, quarter end financial numbers for a management briefing book that come from multiple systems. How about shipping documents? You have an invoice, delivery instructions, picking slip, customer letters - 'shipping documents' covers a multitude of potential documents depending on what your shipping - but again they may come from different systems or at least separate reports from the same system.
From the graphic you can see that Publisher can take disperate PDF outputs and merge them together into a single document. No great shakes on the surface, plenty of applications can merge reports. We have the simpler APIs to do simpler merging but the Bookbinder API takes things to a whole new level.
Imagine being able to take those disperate documents and apply another template over the top of them during the merging process. We allow you to add common layout objects, page numbering (chapter and master), chapter start and end pages, table of contents, cross references, you can even split a big result document into a series of volumes for easier loading through the Adobe interface.
In the next few articles I'll cover working from a simple merge all the way through to an all singing all dancing book binding spectacular! If you have made a start with the APIs and want to get stuck in to the examples you can get them here.