If I may, I'd like to give some constructive feedback on these types of discussions. I'd be easier to discuss if you were to suggest specific API changes or additions you'd like to make. Saying that we should address a shortcoming in without specifying exactly what the shortcoming is or how we should address it (yet targeting a specific version) doesn't tend to focus the discussion.
Just my 2c (I don't know much about the printing API, so I can't lend anything useful there). -T On Thu, Nov 26, 2009 at 8:22 AM, Sandro Martini <[email protected]>wrote: > Hi Greg, > > > As we have said before, we don't want to reinvent the wheel where it is > not necessary. If the existing print functionality provided by AWT is > sufficient, I don't see any reason to build specific printing support into > Pivot. However, if your investigations reveal potential shortcomings that > could be easily addressed by Pivot, it might make more sense to consider it. > Ok, I'll try to see what happens. > > Bye, > Sandro >
