From: <bm...@ca...> - 2007-10-04 14:16:52
|
> I'm trying to work with you guy here :) Benny says that he doesn't like > probably-alive in the sidebar filter and Don doesn't like an alive-in-year > column in the People View. I've been told: "these should be quick > reports". Ok, I'll try that. But, as you say, reports are much less useful > than the rest of the interface, because they aren't part of the > "interface". They are just reports. Ok, this is not directly related to the original subject, but I feel obliged to react. I understand your gripe. However, as I remember the discussion: for probably alive you need a year: 'Probably alive in <year>'. A quick report has no interaction before construction, so you cannot set the year, so a quick report is out. You can do a report where year is an option, or a custom filter where year is the input. The advantage of a report: you can give more info, so not only that a person was alive, but his age. I can understand that you want to run such a report on the textbuf, as it is lookup and throw away. However, the gtk printpreview can serve the same function, and print is a click away. We rejected derived columns for the views for several reasons. I didn't want to add extra boxes to the filter sidebar as a general solution to quickly edit custom filters is needed, instead of cluttering the filter view. I do have an idea on how to realize the quick edit of a filter, but not the time to implement. I try to get 3.0 finished up and 2.2.8 bugfree. About the interactive TextBuf, I suppose you can implement a derived class for this, that specific reports could use. We plan to implement active objects for all primary objects for 3.0, which would be usefull for this. Benny ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |