JComponent Printer

I want a utility class that can print a "tree" of JComponents. The "tree" does not refer to a JTree but rather to a conceptual ordering of the JComponents so that there is a JComponent that is the root and any JComponent can have multiple child JComponents. The parent-child relationship is conceptual and independent of the JFC/Swing containment hierarchy. Alternatively, one can think of it as the JComponent to be printed also implements interface TreeNode and the user will select the sub-tree to be printed at runtime. The printer must be able to optionally (user choice) special process JComponents that implement the Scrollable interface. The Scrollable can either be printed as it would be rendered (screen image) or in its entirety (each Scrollable fully printed). The printer must also provide the user a choice of printing a cover page, a table of contents, and adding page headers and footers. Typical user options such as adding a border to each page, centering the component in a page, scaling the component to fit the entire page, page orientation, etc. must also be provided. A print preview feature is required and prining to a PDF file or PNG image(s) would be nice. ## Deliverables Suggested approach: 1. Feature review: let's discuss the features that will be implemented. I welcome new ideas and thoughts on how the user experince can be streamlined. 2. Design review: let's brainstorm on the design. This component will be part of a larger system and I want to make sure that it will integrate well and not duplicate existing functionality. 3. Implementation timeline: this is critical so we have common expectations. 4. Test plan: again, this component is part of a larger system and a solid test harness is necessary. Optimally, we will define the test cases in step 1 --feature review. 5. Let's do it! I want to to get started as soon as possible. 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). * * *This broadcast message was sent to all bidders on Wednesday Sep 21, 2005 5:20:39 PM: I have updated the project description. Please let me know if you have any additional questions. ## Platform JDK 1.4.2