On 8 Dec 2007, at 4:15 AM, Adam R. Maxwell wrote: > > On Dec 7, 2007, at 2:14 PM, Christiaan Hofman wrote: > >> >> >> On Dec 7, 2007 10:46 PM, Christiaan Hofman <[EMAIL PROTECTED]> >> wrote: >> >> On 7 Dec 2007, at 10:23 PM, Adam R. Maxwell wrote: >> >>> >>> On Friday, December 07, 2007, at 01:03PM, "Christiaan Hofman" >>> <[EMAIL PROTECTED] > wrote: >>>> >>>> On 7 Dec 2007, at 9:53 PM, Adam R. Maxwell wrote: >>>> >>>>> Since we're messing about with the editor and bibitem, should we >>>>> try replacing the NSForm with an NSTableView? Now that file drag- >>>>> and-drop is out of the form, that should be easier. Opinions? >>>> >>>> I think the main reason people had problems with a tableview is >> that >>>> you have to double click to edit. And without thta there are some >>>> problems. >>> >>> That's no longer an issue on Leopard, which now uses single-click >>> table editing. >> >> But that would make it Leopard only. I don't like that just yet. > > I wasn't suggesting to go Leopard-only, just that it will be expected > behavior in future. > >>> The people who complained about that were also under the (mistaken) >>> impression that you couldn't use tab-navigation with a tableview, >>> IIRC, and thought you'd have to double-click each row to edit it >>> (which I agree would be tedious). >>> >>> I won't bother restating all of my dislikes for the form; I'd like >>> something that looks more modern and is amenable to dynamic content >>> without hacking it to death. >> >> I also don't like the form. But with a little test app I had (that >> also had single edit with some subclassing) somehow the bezeled look >> like the form looked better than the standard tableview look. I'm not >> sure why, perhaps the distinction between the field names and the >> edits, and the separation of the fields. > > That's a good point; I agree that some distinction between the rows/ > names is good. I also don't like alternating-color rows in the > editor, so that's not a good option. > >> I've put the test app in the bibdesk directory if you want to have a >> look at it. With the bezel style it seems to work, the normal style >> and bordered style don't work properly. > > What doesn't work in the normal/bordered styles? Editing seemed to > work ok for me.
The field editor covers the arrow/file button (apart from about 1 px). Also the focus ring is cut off in an ugly way. > The bezel style looks most familiar. A grid doesn't > look so bad either (better than the bordered style cells, I think). I > wonder if some sort of custom bezel would look good---maybe a round- > rect or something... > A round rect is associated to search fields. >> Though it I can't get complex string editing to work, so that's >> not a good option. > > It works if you use > > if ([self isWindowLoaded] && [[self window] isVisible] == NO) > [self attachWindow]; > > in MacroTextFieldWindowController. BibDesk only checks for -isVisible > == NO right now. > > -- > adam Thanks, I thought I did something wrong. I put a new version of the test project. It now seems to work in all cases, including the drawing in bordered and normal style (with some fixes). Christiaan ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
