Hi Todd, > 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. I'm sorry but probably this thread was misunderstood, at the beginning I ask to others if someone has used the print feature and if some problem/trick has been found to do the stuff, like a sort of "Best Practices for Printing in Pivot". After then some trick appeared, but that's all, also the proposal for a ticket for the 1.5, but just as reminder, an idea for a future work (could be little, or much, now it's a detail), so this discussion is what I think as a constructive feedback from others, like a rough analysis of the feature. Could also be dropped, no problem with it.
But from here to have a proposal API I am very far ... before wasting time and coding something that is not interesting or not wanted I prefer to discuss with all, and only after (if it's the case) proceed and study better the problem and maybe the implementation (the test prototype that I should make has been cancelled, so I've no more this requirement now, but could be useful to someone). Without this it's difficult to write something really integrated in the platform and really useful, at least for committers like me that doesn't have a full coverage of the platform. Comments ? Sandro
