That's pretty slick-looking.
If the underlying representation is categorical, is/is not with a
selector for color would be fine.
[On a totally different note, has anyone thought about nested boolean
logic for smart groups (a la the 10.5 finder)?]
AppleScript would be convenient as well, but it's pretty easy just to
access the finder directly, so that's unnecessary, e.g.,
tell application "BibDesk"
set thePubs to the selection of document 1
repeat with thePub in thePubs
set linkFile2 to linked file 2 of thePub
tell application "Finder"
set theFile to linkFile2 as alias
set the label index of theFile to 2 -- red
end tell
end repeat
end tell
...sets the label of the second linked file of selected publications
to red.
On 2008-01-17, at 10:32 AM, Christiaan Hofman wrote:
> To come back to this, now that we have support for Finder labels in
> the recent nightlies. What smart group support for this would be
> useful?
>
> Note that currently you can add smart groups based on the number of
> linked files/URLs.
>
> Christiaan
>
> On 8 Jan 2008, at 5:35 AM, Alexander H. Montgomery wrote:
>
>> Actually, it's not about *visual* differentiation (which I can do),
>> but differentiation that can, say, be discerned by an AppleScript
>> or a
>> Smart Folder. (For the record, 4938 refs, 3119 single files, and
>> 304 >
>> 1 file).
>>
>> For example, I put together syllabi with an AppleScript that copies
>> references and PDFs to a separate directory for easy distribution.
>> The
>> AppleScript can't tell the difference between a local file that is
>> the
>> actual PDF and a local file that is a related PDF. But if I could tag
>> the correct local file (or, much easier, tag the incorrect ones!)
>> then
>> an AppleScript or a smart folder could do it. My current smart
>> folders
>> allow me to find articles that don't have PDFs (of the article)
>> easily; the new architecture doesn't.
>>
>> Now, I certainly don't think this needs to be in 1.3.13 (I already
>> have a workaround for my scripts through script hooks: everything
>> added to the local-url field is added automatically as a linked file,
>> and vice versa if local-url isn't yet filled in) I'm partially
>> thinking out loud about how the current metadata-in-a-file support in
>> BibDesk (Skim notes!) could be expanded to include tagging files with
>> other metadata. One way to do it would be to use Finder metadata;
>> another just to store it in xattrs on each PDF. Of course, that might
>> take forever to read in, so it might be easier (faster?) to do it
>> within BibDesk instead.
>>
>> -AHM
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bibdesk-users mailing list
> Bibdesk-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bibdesk-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bibdesk-users mailing list
Bibdesk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
