I absolutely agree that it's possible to moderately easily set up a view hierarchy that will allow for automatic pagination etc and work with object oriented methodologies to accomplish the goal, but there is a certain amount of grunt work in doing this, and the whole point of having frameworks is to handle the common repeatable cases like printing tables.
After all, they are always automatically going to be row based, so with a little bit of work on Apple's part, it would be easy enough to have a configuration item to say for it to print with or without the header, and maybe a callback to find out whether it can split a particular row, and if so, where. Then everyone would automatically get the printing capabilities without everyone having to reinvent the wheel. And besides this, you have already got a component optimised for retrieving the data and displaying it in a table, so it makes sense to be using that for the user interface. So I don't want to have to be building a separate mechanism just to print it - it's like doubling the work, and from the user's perspective, they can work within the mental framework of getting the table the way they want it (showing the right columns at the right size in the right order), and then saying "print *this*" i.e. wysiwyg. Even if the reinvention process isn't too onerous, when repeated across all the projects where people want to print tables, it adds up to a lot of developer hours that could be saved through having it in the framework. Gideon On 21/07/2010, at 9:41 AM, Matt Neuburg wrote: > On or about 7/20/10 4:19 PM, thus spake "Gideon King" <[email protected]>: > >> It's a real shame that printing >> support isn't there nicely for table views... > > I don't really understand this kind of complaint. If you organize a > hierarchy of intelligent self-printing views, printing is a snap, as I've > said before: > > http://www.cocoabuilder.com/archive/cocoa/181559-printing-database-report.ht > ml#181739 > > http://www.cocoabuilder.com/archive/cocoa/175898-trouble-with-knowspagerank. > html#175913 > > http://www.cocoabuilder.com/archive/cocoa/115096-building-and-printing-table > s.html#115128 > > It is reasonable to ask for a "report writer" module; that's a FAQ, so check > the archives. But I find that once you actually understand the printing > architecture, and start thinking in terms of views and subviews, nibs, and > so forth, printing becomes object-oriented and all the pieces of the view > effectively print themselves. m. _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
