Re: [Bibdesk-develop] Mockup of how to cram lots of detail into editing pane for BD2

[Christiaan H. <chr...@we...>]

I think that basically looks nice. The buttons to choose the detail  
(like abstract, notes, refs, citation, other fields) solve some space  
problem. I prefer them above the detail scrollView, as they are  
related to that. And it gives more horizontal space for the little  
tables. I have to see if it doesn't interfere to much with the  
workflow (we might want key shortcuts for them, like Cmd-1 etc).

And we should make the important info at the top (like title.  
venue, ...) editable. It would be nice if we could generate an  
address book/iTunes like editing textfield there (without the edit  
button of course). Is there some example code around?

Venue is a separate entity, so it probably should give you a separate  
editor window, maybe with a table to choose from. How do you call it,  
by double clicking the Venue field below the title?

As for the multiple files, I am not sure. Maybe small up/down buttons  
to switch between them, but then we need an identifier for them  
showing somewhere. Is there space? Or maybe another table in the  
detail view.
And below the icon button there should probably also be a web button.

And what precisely are tags? Can they be shared by different items?
My idea was to have just a tag inspector as a separate window, not  
directly in the detail view. Also as they are more general (ie for  
other entities). It depends on how important we find them.

I have similar remarks/questions for notes. Also there seems to be  
only place for a single note. Do we actually want a to-many  
relationship?

So this is supposed to be for publications only? That makes things  
easier.

Note that still there should be the master table at the top. How does  
it fit (especially on a 12 inch screen)?

And then the other editing views (for persons, institutions, venues).  
They are probably much easier, and closer to what we have.

Christiaan

On 7 Feb 2006, at 2:27 AM, Michael McCracken wrote:

> OK, here's a quick mockup of what I was talking about in previous  
> messages about how to design the UI for the  
> publicationDisplaycontroller. I was inspired by the ACM webpage for  
> papers listings, that although it has design problems, works pretty  
> well. For example, see http://doi.acm.org/10.1145/1113316.1113320.
>
> In general I think that there is some very important info that you  
> need to always see but rarely edit - title, date, venue, authors,  
> etc. Then there's some metadata that you'll want to edit  
> frequently, like checkbox fields (Read, etc) and ratings, and tags.  
> Then there's everything else, which can be sometimes hidden for  
> other things - like notes, abstract, etc. But you want quick access  
> to those things, so we give you shortcuts. ACM uses links, maybe  
> we'd use iTunes store style linkbuttons (only try to do it without  
> the drawbacks of those, so you know you can click on them, maybe  
> use the arrows.)
>
> The icon button could be the same as it was in bibeditor - except  
> there might be more than one file, and how do we want to view  
> these? I suggest separate windows, although we could also consider  
> a third horizontal pane that'd squash the top tableview when we  
> were viewing what was drawer content in bibeditor.
> Or we could keep the drawer (although I don't love drawers)
>
> I also attached a screengrab of the current  
> BDSKPublicationDisplayController view I had going in IB, to show  
> another view of what I'm talking about - the lower scroll pane is  
> not implemented yet, there's a lot of NSView work to get that done  
> and I wanted to get feedback before I dove in.
>
> Comments? I've included the omnigraffle file in case someone wants  
> to make another version.
>
> -mike
>
> <bd2mockupNew.graffle.pdf>
>
> <pastedGraphic1.tiff>
>
>
> <bd2mockupNew.graffle>
>
> --
>     Michael McCracken
>     mic...@ma...
>     http://michael-mccracken.net/