On Sep 3, 2007, at 11:21, Christiaan Hofman wrote: > It looks and feels pretty neat!
Thanks! That's been keeping me from adding more bugs to BD lately ;). > On 3 Sep 2007, at 7:58 PM, Niels Kobschätzki wrote: > >> On Sep 3, 2007, at 7:40 PM, Adam R. Maxwell wrote: >> >> I can drag a pdf onto another pdf and the first one is replaced in >> the view by the dropped one. >> And it would be cool if I draw a folder on the app that the content >> (the pdfs in the folder and its sub-folders) are shown as thumbnails >> and not the folder itself >> Right now I'm unfortunately not seeing really the use of the app or >> the integration of it into Bibdesk because most of my PDFs are from >> JSTOR or some other stuff that doesn't have a cover and is text only >> (especially on the first page) and therefore a thumbnail isn't really >> useful. >> >> Niels > > Should there perhaps be a file icon badge or something? Not sure what you mean there? > Deleting an item (dragging to trash) does not remove the item, it > just empties it (giving me a question mark). i think the item should > be removed. Yeah, that's a case where the controller object in this case just returns [NSNull null] after the view tells it to delete the file. > Also there should be some more direct way to delete (menu > item, hitting Delete, delete: action, in combination with selection) I've avoided doing that because it means adding selection semantics, but I think you're right. It looks too Finder-like for that not to work. I'm not happy with the text display, either; I need multiple lines with truncating in the middle, and Cocoa doesn't seem to offer that. > How did you think to manage the set of items and the counter for the > name? Should the items be reassigned when an item is removed? Perhaps > we should just have an array of items, and determine the field name > when saving only. Right now the view just displays in whatever order the datasource provides, like a tableview. So a delete action sends the datasource a message to remove a given item by index, and then it can handle that by doing whatever it wants. I'd thought about displaying a count bubble on each icon, so there'd be some notion of order, since scripting could access items by index. > The slider should follow the actual zoom (if you use the zoom menu > items). > > And the minimum size should not be zero. Minimum size is 0.1, I think, but it's definitely too small to be useful. I'm surprised the slider doesn't update when the zoom changes; I'll check that. > I just had a crash: > 1. close the window > 2. quit Hopefully that's a Tiger bug in binding to a slider. I ran into that on my work machine and forgot to fix it here. thanks, adam ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
