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.
>
> > 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.
>
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. Though it I can't get complex string editing to
work.
Christiaan
>
> > If you and other developers prefer the form for function/
> > aesthetics, though, I'll leave it alone. Users are going to
> > complain no matter what, so I figured this was a good time for
> > massive change :).
> >
> >> Also I'm not sure how the crossref arrow button and complex
> >> string editing work all properly.
> >
> > I thought the text import sheet tableview had complex string
> > editing? I had both working in my outline view test, though that
> > code is really dated. The arrow button should be pretty easy as
> > well using BDSKFormCell or a similar class. Incidentally, Apple
> > now provides an arrow button via NSImage, although the background
> > is black.
> >
>
>
> So its more that I remember having trouble to get all the
> requirements we would like into the table setup. I think that should be:
> 1. complex string editing
> 2. arrow buttons
> 3. 1-click edit
>
> Indeed, complex string editing works. But I seem to recall that
> having all of it can be a pain. NSTextFieldCell has a lot of bugs
> when you don't stick exactly to the standard use.
>
> 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
