On Sep 25, 2004, at 7:10 PM, Michael McCracken wrote:
> I'm thinking of killing the multithreaded IO in favor of focusing time
> on macro support.
> I just spent a while trying to get the threading to work without dying
> when you close the window, and the best thing I can think of is to
> just force it to wait until the file is read in before the window
> closes, and that really isn't ideal.
> I'm sure there's a way to do it, and I can kill the thread
> appropriately but I can't seem to kill all the notifications still
> flying around, and that ends up crashing because they refer to dead
> What does everyone think about trying to get the macro support more
> polished, and just putting the threaded stuff on the back burner?
Frankly I don't have a use for the threaded stuff because I use fairly
small subject specific bibs so don't experience the loading times
problem. One might argue that there is an easy, if inconvenient,
workaround for slow loading which is to break one's bibs up ...
OTOH there isn't really a convenient workaround if you use Macros that
I know of ... so that points to macros.
> On Sep 19, 2004, at 5:38 PM, Adam R. Maxwell wrote:
>> On Sep 19, 2004, at 17:01, Michael McCracken wrote:
>>> On Sep 19, 2004, at 3:03 PM, Adam R.Maxwell wrote:
>>>> It's a bit confusing to see the journal name, then a \t?, then the
>>>> abbreviation in the BibEditor. What about having a choice to show
>>>> either the macro or its expanded form? This would then apply to
>>>> any field, I guess.
>>> I'm not sure what you're referring to. The editor certainly isn't
>>> done, but I thought it was displaying the expanded form until you
>>> edit it (at which point it overwrites the macro, ouch)
>> I thought I saw the expanded form, then some whitespace, then the
>> macro appended...but I was wrong.
>> - Open the test case entry Gay:1999:SAF (or another Journal entry) in
>> BibEditor, and it displays the expanded name.
>> - The preview pane in the split view (set to show everything) shows
>> the macro (j-TOMS).
>> - Click in the "Journal" form field of bibeditor, and it changes from
>> expanded to j-TOMS.
>> Is this right? I haven't fully figured out what you changed in the
>> code; the sourceforge diffs don't seem to show all the changes.
>>>> Maybe the @string entries could be edited in a text view on a
>>>> sheet, since I don't think much GUI is required for people that use
>>>> BibTeX macros. Alternately, maybe an editable table like Property
>>>> List Editor (albeit one that sucks less) with key-value...although
>>>> that would be weird for multiple lines.
>>> I think a table would be easier to do, since it'd be a pain to
>>> re-parse those things.
>> Yeah, duh, I thought of that after hitting send. You're storing the
>> field values in arrays of dictionaries, right?
>> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
>> Project Admins to receive an Apple iPod Mini FREE for your judgement
>> who ports your project to Linux PPC the best. Sponsored by IBM.
>> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
>> Bibdesk-develop mailing list
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
> Bibdesk-develop mailing list
+1 315 395 4056