You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(13) |
Nov
(42) |
Dec
(18) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(12) |
Feb
(2) |
Mar
(9) |
Apr
(3) |
May
(3) |
Jun
(5) |
Jul
(13) |
Aug
(10) |
Sep
(5) |
Oct
(39) |
Nov
(44) |
Dec
(59) |
2004 |
Jan
(15) |
Feb
(44) |
Mar
(163) |
Apr
(74) |
May
(19) |
Jun
(53) |
Jul
(110) |
Aug
(173) |
Sep
(157) |
Oct
(74) |
Nov
(243) |
Dec
(326) |
2005 |
Jan
(112) |
Feb
(274) |
Mar
(336) |
Apr
(547) |
May
(465) |
Jun
(226) |
Jul
(227) |
Aug
(348) |
Sep
(134) |
Oct
(229) |
Nov
(202) |
Dec
(127) |
2006 |
Jan
(56) |
Feb
(136) |
Mar
(113) |
Apr
(133) |
May
(149) |
Jun
(59) |
Jul
(31) |
Aug
(134) |
Sep
(47) |
Oct
(132) |
Nov
(92) |
Dec
(72) |
2007 |
Jan
(193) |
Feb
(258) |
Mar
(213) |
Apr
(103) |
May
(84) |
Jun
(27) |
Jul
(40) |
Aug
(59) |
Sep
(62) |
Oct
(64) |
Nov
(105) |
Dec
(148) |
2008 |
Jan
(262) |
Feb
(35) |
Mar
(44) |
Apr
(27) |
May
|
Jun
(37) |
Jul
(10) |
Aug
(29) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2009 |
Jan
(149) |
Feb
(53) |
Mar
(92) |
Apr
(69) |
May
(34) |
Jun
(51) |
Jul
(48) |
Aug
(44) |
Sep
(35) |
Oct
(25) |
Nov
(31) |
Dec
(14) |
2010 |
Jan
(13) |
Feb
(29) |
Mar
(2) |
Apr
(3) |
May
(9) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(4) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
(7) |
Apr
(6) |
May
(2) |
Jun
(2) |
Jul
(7) |
Aug
(10) |
Sep
(5) |
Oct
(3) |
Nov
(2) |
Dec
(5) |
2012 |
Jan
(17) |
Feb
(3) |
Mar
(11) |
Apr
(6) |
May
(23) |
Jun
(13) |
Jul
(10) |
Aug
(13) |
Sep
(5) |
Oct
(14) |
Nov
(27) |
Dec
(12) |
2013 |
Jan
(44) |
Feb
(41) |
Mar
|
Apr
(8) |
May
(5) |
Jun
(31) |
Jul
|
Aug
(11) |
Sep
(1) |
Oct
|
Nov
(16) |
Dec
(34) |
2014 |
Jan
|
Feb
|
Mar
(90) |
Apr
(57) |
May
(10) |
Jun
(5) |
Jul
(12) |
Aug
(5) |
Sep
(8) |
Oct
|
Nov
|
Dec
(1) |
2015 |
Jan
|
Feb
(8) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(2) |
Sep
|
Oct
(30) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(21) |
May
|
Jun
(3) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(10) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
(20) |
Dec
|
2019 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
2021 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2022 |
Jan
(3) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Bruce D'A. <da...@mu...> - 2002-11-06 04:47:54
|
As I've been struggling with the details of how to both present structure and flexibility in the BibEditor interface, I'm realizing that AddressBook is really well done in this area. I know you've mentioned before, Mike, that this might be useful for BibDesk and I couldn't agree more. It would be really helpful to figure out a way to do this. The combination of the small and elegant "add field" button, and the similarly small, elegant and flexible pop-up selector would be a great mechanism for things like adding authors and so forth...: |
From: Bruce D'A. <da...@mu...> - 2002-11-05 17:11:33
|
On Monday, November 4, 2002, at 02:48 PM, Michael McCracken wrote: > A possible big problem (depending on details of the XML spec and of > the bibtex spec that I don't remember) is how to map information that > appears in one format but can't easily be expressed in the other. This > could be a major design difficulty. I don't have enough info at hand > to estimate how long that might take. Hopefully there's no problem > there. Did a quick mockup of an example. There would obviously be details to work out (like 1st and 2nd authors, etc.), but you'll note that this would capture all the information needed for BibTeX, and then some. The additional data can just get mapped back to the more limited BibTeX model if needed. |
From: Bruce D'A. <da...@mu...> - 2002-11-04 21:49:57
|
On Monday, November 4, 2002, at 02:48 PM, Michael McCracken wrote: > There's no xml parsing in it now. I'll probably look into using Omni's > OmniExpat, or just Apple's corefoundation XML parser (works well, and > might be faster). There's also a Cocoa XML kit at: http://www.metaobject.com/Community.html I have no idea about the relative merits of the different approaches, though it seems to me Marcel Weiher is both a) well-respected in Cocoa circles, and b) a nice guy (so maybe could offer advice). There are also some interesting "to do" items listed in the docs... I'm a little perplexed Apple hasn't really adopted XML in Cocoa yet. The sad irony is that MS is doing a better job on this front... Bruce |
From: Alexandre E. <alexandre.enkerli@UMontreal.CA> - 2002-11-04 20:52:55
|
> cleaning up the project a little, and soon will add the omniframeworks > to the CVS version of BD, so that building will be much simplified. Great! Thanks! It's basically what I'm waiting for before I can start contributing. My programming skills are rudimentary but I'm sure I could help out if I could at least compile it... |
From: Michael M. <mic...@ma...> - 2002-11-04 19:52:42
|
In a previous post, I mentioned that I might not be able to post the omni frameworks as part of the BD CVS repository. On a second read of the copyright, I can redistribute 'modified binary code'. So, I'll be cleaning up the project a little, and soon will add the omniframeworks to the CVS version of BD, so that building will be much simplified. I should be done with this by the end of this week. I have a cross country flight this week, and I'll do the work on the plane. -mike -- Michael McCracken mic...@ma... http://disco.ucsd.edu/blog |
From: Michael M. <mic...@ma...> - 2002-11-04 19:48:44
|
Hi. On Monday, November 4, 2002, at 11:10 AM, Bruce D'Arcus wrote: > > Also, if you consolidate the "startup" and "display" pref panes into > "general" you can borrow Omni's icon! Do you have OmniOutliner? If > not, download the free demo and take a look at how they've done > preferences. Quite nice, and good a model for fixing BD's. I don't > think you need to leave room for adding the citation mode preferences > I earlier mentioned... Do you mean just the visual layout of the preferences panes? Because I'm using their code for the preference window and the pane chooser along the top. > > Also, OO is moving to a new XML file format soon. Am hoping to be > able to use it to write papers (with XSLT, I can create an XHTML file > that Word will open as if native!), and use BD to add citations to > it... That does sound nice. It'd be great to have the outliner's collapsible interface to help keep things neat while writing. A thought I had once for bibdesk was that if Omni would make an 'embeddable' version of OO, I'd have used it for the 'annote' section, which would get exported into plain text for bibtex files, and maybe OPML for XML files. But I'm not sure if they'll do it, and I don't want to have to write an outliner myself. >>> Only thing I don't like in NNW is how that app displays links in its >>> "preview panel".... >> >> What don't you like about it? Just curious. > > The colored-blue-underlined-link thing; it's so 20th century ;-) > > More seriously, though, it just doesn't look very nice, which is why > current web-designers (and Apple?) use other ways to indicate links... I agree - it's not pretty, but it is universally understood. That's why I use it for the 'view remote' link. I think the reason Brent uses it is that he uses the Cocoa frameworks' built-in HTML displaying code, which doesn't really let you change the link attributes. At least not easily. > >>> In general, tightened up spacing (BibFinder was particularly bad >>> here), in some cases switched to "small" controls (in the search >>> field pop-up, for example), or to "push buttons" (which I strongly >>> prefer to the "rounded bevel button" that is used in a lot of >>> places), and added a subtle grid to table views (don't know how to >>> do alternate-row shading; though see my post to the list). >> >> alternate row shading can't be done in IB. there's a small bit of >> code you need to do it. > > See the note I sent to the list for the sample code I found from > Apple. I just don't know where to add it, and how. I assume it'd be > trivial for you, though. it should be :) btw, I didn't mention it before, but I haven't looked at BibFinder (either the UI or the code for it) in a long long time, many versions ago. If there are any comments or improvements that should be made there, I'm open to them. The code to support searching with multiple constraints is in and works (in the service), so it's more a matter of adding a good GUI for it in BibFinder to make it much more usable. > >>> I also changed the keybindings in the main menu to have command-N >>> create a new record, and those items that were previously command-1, >>> 2, 3, and 4 because I really think these should be used in the >>> BibEditor panel to switch between tabs (though again, I don't know >>> how to define keybindings for the tabs). >> >> I agree with the command-N change, although I dislike breaking >> people's habits. If I make that change, I might try to add a bit of >> code that would pop up a warning window the first time you use a new >> version, just to check that you know it changed. > > Yes, I understand; it's not a 1.0 product yet, so maybe people will be > tolerant. good point. > More importantly, the logic of these changes is to make it easier to > do what one spends most time creating in a bib manager: references. > So...with the changes, for the most part you don't have to use the > mouse at all (except to choose the reference type). not using the mouse sold me. I'm thinking more and more that I need to pay more attention to the workflow aspect of using bibdesk. (and wish i had time to write good documentation, because i get emails a lot with feature requests that have already been implemented, or aren't necessary because faster ways are already implemented, etc...) > >> What did you change the numbered panels to? > > Don't remember; something with obvious letter counterparts (like P for > preview). be careful not to clash with standard key bindings. cmd-P is for print, and just because I haven't written printing code doesn't mean it's not intended. It's been requested a few times, but it's just a little harder than I have wanted to deal with. >> the ~.nib files are backups - submit the .nib files. Sorry again >> about slacking on responses > > Will send later today, or tomorrow. They're on my laptop, which is > not with me now. > Also two other things when you get a chance: > > 1) The XML question. What is actually involved in adding support for > the sample I earlier sent? Do you already have XML-parsing built-in > (I know Omni distributes the expat libraries for obj-c)? Or is the > existing support specific to RSS? Incidentally, I took at look at > Pybliographer, which will be moving to an XML format in the next > release. Their goals seem to be similar to mine. Hope Taco releases > his new system soon! There's no xml parsing in it now. I'll probably look into using Omni's OmniExpat, or just Apple's corefoundation XML parser (works well, and might be faster). It should be a conceptually simple job to add this in, it's essentially 'add two methods' and 'remove any dependencies on bibtex'. the first one is straightforward, but might be slow to get right. the second one could be awful. Luckily I'm taking a class right now on how to best deal with modfiying improperly modular aspects of code, and I've found out about some great tools to do that with. So I'm optimistic. A possible big problem (depending on details of the XML spec and of the bibtex spec that I don't remember) is how to map information that appears in one format but can't easily be expressed in the other. This could be a major design difficulty. I don't have enough info at hand to estimate how long that might take. Hopefully there's no problem there. > 2) Building. If there's some way to make building easier, that'd make > it easier for people like me. Like, can you send me compiled Omni > frameworks and tell me exactly what to do with them? That's not > workable in an ideal world, of course, but I can't afford to spend a > lot of time just figuring out how to build the app... I can send you the frameworks, and I will in a separate (non list) message. I'm going to ask the Omni guys if it's OK to post a compiled version on SF, but I fear the answer may be no. At any rate, I think I'll have to change how they are referenced in the PB project, to avoid confusion about 'build product relative' paths. more info about this soon. -mike > Bruce > > -- Michael McCracken mm...@ac... http://www.cs.ucsd.edu/~mmccrack/ |
From: Bruce D'A. <da...@mu...> - 2002-11-04 01:40:38
|
On the preference panes: Seems to me "startup" and "display" could be consolidated into a "general" pane. Also, there are places where text descriptions ought to just be eliminated, perhaps with some of that content placed in a tooltip. For example, here's what I've done with the font preference (borrowed from OmniOutliner): |
From: Bruce D'A. <da...@mu...> - 2002-11-02 23:15:14
|
Sorry, there's bug in Mail that changes 10pt Monoco to 8pt! Bruce |
From: Bruce D'A. <da...@mu...> - 2002-11-02 23:11:00
|
I found sample code to implement alternate-row shading here: http://developer.apple.com/samplecode/Sample_Code/Cocoa/MP3_Player/ MyTableView.m.htm The relevant code seems to be the following, but I'm not sure exactly where to put it, and how. Mike? #import "MyTableView.h" // RGB values for stripe color (light blue) #define STRIPE_RED (237.0 / 255.0) #define STRIPE_GREEN (243.0 / 255.0) #define STRIPE_BLUE (254.0 / 255.0) static NSColor *sStripeColor = nil; @implementation MyTableView [snip] // This is called after the table background is filled in, but before the cell contents are drawn. // We override it so we can do our own light-blue row stripes a la iTunes. - (void) highlightSelectionInClipRect:(NSRect)rect { [self drawStripesInRect:rect]; [super highlightSelectionInClipRect:rect]; } // This routine does the actual blue stripe drawing, filling in every other row of the table // with a blue background so you can follow the rows easier with your eyes. - (void) drawStripesInRect:(NSRect)clipRect { NSRect stripeRect; float fullRowHeight = [self rowHeight] + [self intercellSpacing].height; float clipBottom = NSMaxY(clipRect); int firstStripe = clipRect.origin.y / fullRowHeight; if (firstStripe % 2 == 0) firstStripe++; // we're only interested in drawing the stripes // set up first rect stripeRect.origin.x = clipRect.origin.x; stripeRect.origin.y = firstStripe * fullRowHeight; stripeRect.size.width = clipRect.size.width; stripeRect.size.height = fullRowHeight; // set the color if (sStripeColor == nil) sStripeColor = [[NSColor colorWithCalibratedRed:STRIPE_RED green:STRIPE_GREEN blue:STRIPE_BLUE alpha:1.0] retain]; [sStripeColor set]; // and draw the stripes while (stripeRect.origin.y < clipBottom) { NSRectFill(stripeRect); stripeRect.origin.y += fullRowHeight * 2.0; } } |
From: Bruce D'A. <da...@mu...> - 2002-11-01 15:04:04
|
On Wednesday, October 23, 2002, at 04:51 PM, Michael McCracken wrote: > Now you have a CVS working copy, but you don't care about that. If you > make changes, just submit them as patches through the patch manager: > https://sourceforge.net/tracker/> ?atid=497425&group_id=61487&func=browse Got it, but now I have a dumb question about submitting a patch: If I am submitting a nib file I made changes on, which do I submit. For example, if I have BibDocument.nib and BibDocument~.nib, do I submit both? Also (and related), what should be done about the 10.2/pre-10.2 issue? I venture to say we ought to look at 10.2-only stuff in the future. Finally, I can't figure out how to compile the app, an am getting tripped up on the Omni frameworks. Is there nothing that can be done to make this easier? Even more detailed instructions might be helpful, though I wish I didn't have to deal them at all... Bruce |
From: Bruce D'A. <da...@mu...> - 2002-11-01 02:40:55
|
OK, this is what I mean in terms of a model for the basic database view: subtle alternate-row shading, with a very light gray column grid. |
From: Bruce D'A. <da...@mu...> - 2002-10-31 17:17:09
|
FYI, some interesting conversion scripts for standard formats like BibTeX, RIS, etc., using an XML intermediate format. http://www.scripps.edu/~cdputnam/software/newbib.html Bruce |
From: Bruce D'A. <da...@mu...> - 2002-10-29 16:39:17
|
Mike, How is the RSS support implemented in BibDesk? Or more precisely, what needs to be done to add support for other XML formats? Say I have a simple example XML doc with two records like the following... <bib> <entry id="rec1" type="newspaper"> <names> <person> <firstname>John</firstname> <lastname>Smith</lastname> </person> </names> <date day="23" month="March" year="2000"/> <titles> <title>Bush pulls support</title> <subtitle>Bill Killed</subtitle> </titles> <published> <date year="2000"/> <publisher>New York Times</publisher> </published> <text type="note"> Here is the note (annote) field.</text> </entry> <entry id="rec2" type="book"> <titles> <title>The Big Red Book</title> <subtitle>Jumping Hoops</subtitle> </titles> <date year="1994"/> <published> <date year="2000"/> <publisher>ABC Publishers</publisher> </published> <words type="keywords"> <word>geography</word> <word>U.S.</word> <word>space</word> </words> </entry> </bib> Also, regarding the earlier problems with building the app, have these been fixed? Bruce |
From: Alexandre E. <alexandre.enkerli@UMontreal.CA> - 2002-10-24 20:21:04
|
Given the complexity of building BD (what with the frameworks and all), I don't think the lack of a source tarball will be a problem for anyone... |
From: Michael M. <mic...@ma...> - 2002-10-23 20:51:42
|
Just a quick note: I've decided (barring loud opposition) not to post a source tar.gz archive for non cvs savvy developers to download. This is due to a bad experience on another project of significant duplicated work and lost opportunity due to an out-of-date source archive. There is currently no reliable way that I have to automatically generate an up-to-date archive, so I will rely on CVS. Here's exactly what to type to get a version of bibdesk from the servers that is up-to-the minute: cvs -d:pserver:ano...@cv...:/cvsroot/bibdesk login (there is no password, just press 'enter') cvs -z3 -d:pserver:ano...@cv...:/cvsroot/bibdesk co bibdesk Now you have a CVS working copy, but you don't care about that. If you make changes, just submit them as patches through the patch manager: https://sourceforge.net/tracker/?atid=497425&group_id=61487&func=browse Thanks, and as always, I'm open to comments or opposition. -mike -- Michael McCracken mm...@ac... http://www.cs.ucsd.edu/~mmccrack/ |
From: Michael M. <mic...@ma...> - 2002-10-23 18:42:25
|
Hi. I think the list is subscriber only. I did that to avoid spam. On Saturday, October 19, 2002, at 09:58 AM, Kristofer Johannisson wrote: > [I sent this to the sourceforge bibdesk-developer list, but since I am > not a subscriber I am not sure my email was accepted -- hence this > duplicate copy to you] > > Hi, > > as a user of the IMHO very nice BibDesk program I was a bit annoyed by > the local-url-bug. Since it seemed as if it would be simple to fix, I > downloaded the BibDesk source. Being rather new to Projectbuilder it > took me quite a while to get the BibDesk project to build > (Omniframeworks, prebinding...), and when I finally managed this, I > discovered that the bug had already been fixed :-). Thanks for going through the effort. Now that you've got it working, maybe you'll find other things you want to fix? :) > > However, it seems as if a new bug has been introduced by this fix: > local urls with tilde ("~") in them do not seem to work. It might be > something in the fixURLs method of BibEditor, but I am not sure. It is in fixURLs. Could you provide a more detailed test of this? for instance, what is the string you're trying to use? it works on paths with tildes: ~/Papers/foo.pdf and it works on file URLS: file://localhost/Users/mike/Papers/foo.pdf did you mean file://localhost/~/Papers/foo.pdf or file://localhost/~mike/Papers/foo.pdf ? -mike > > A side note: In the BibDesk project, there was an absolute path in > Targets/Bibdesk/Settings/SimpleView/SearchPaths/Libraries which I had > to modify, maybe this should be changed? which library had the absolute path? thanks, mike > / Kristofer Johannisson > -- Michael McCracken mm...@ac... http://www.cs.ucsd.edu/~mmccrack/ |
From: Kristofer J. <kr...@cs...> - 2002-10-19 16:19:16
|
Hi, as a user of the IMHO very nice BibDesk program I was a bit annoyed by the local-url-bug. Since it seemed as if it would be simple to fix, I downloaded the BibDesk source. Being rather new to Projectbuilder it took me quite a while to get the BibDesk project to build (Omniframeworks, prebinding...), and when I finally managed this, I discovered that the bug had already been fixed :-). However, it seems as if a new bug has been introduced by this fix: local urls with tilde ("~") in them do not seem to work. It might be something in the fixURLs method of BibEditor, but I am not sure. A side note: In the BibDesk project, there was an absolute path in Targets/Bibdesk/Settings/SimpleView/SearchPaths/Libraries which I had to modify, maybe this should be changed? / Kristofer Johannisson |
From: Bruce D'A. <da...@mu...> - 2002-10-19 16:05:16
|
I changed my mind on the contextual menu. It seems to me one could just set a "citation mode" (Natbib, Harvard, ConTeXt, Docbook, etc.) in BibDesk, and use standardized keyboard (and maybe also at some point contextual menu) commands to paste them. My point is that the current "custom citation string" panel idea ought to be generalized, and rationalized. Bruce |
From: Michael M. <mic...@ma...> - 2002-10-18 07:00:07
|
I had a little free time last night, so: Checked into the CVS repository now are some changes to BibItem and BibEditor. BibItem's RTFValue method (creates the RTF you see in the preview window) now uses more and nicer fonts. BibEditor now uses file:// URLs and paths equally well for viewing the local file. This fixes bug # 611175. I also added a BibDesk Help directory for a start on online help. -mike -- Michael McCracken mic...@ma... http://disco.ucsd.edu/blog |
From: Michael M. <mmc...@cs...> - 2002-10-18 06:22:54
|
Checked into the CVS repository now are some changes to BibItem and BibEditor. BibItem's RTFValue method (creates the RTF you see in the preview window) now uses more and nicer fonts. BibEditor now uses file:// URLs and paths equally well for viewing the local file. This fixes bug # 611175. I also added a BibDesk Help directory for a start on online help. -mike -- Michael McCracken mm...@ac... http://www.cs.ucsd.edu/~mmccrack/ |
From: Bruce D'A. <da...@mu...> - 2002-10-18 02:37:16
|
Regarding earlier mention of citation preferences, I've done a simple mockup in IB of what I had in mind. This is obviously, um, forward-looking, but it seems appropriate. I don't remember the correct code for this stuff, so I left it out. |
From: Bruce D'A. <da...@mu...> - 2002-10-16 20:24:21
|
On Wednesday, October 16, 2002, at 03:23 PM, Michael McCracken wrote: > Also, I have two 8 hour flights coming up this weekend, and I'm > thinking I'll spend some of that time hacking on BD. I'll probably > start with some of the small bugs, and move on to adding the more > readable font display you mentioned. I'm on the list, actually. On the UI, maybe the other little things I mentioned (alternate-row shading for the basic window, perhaps a subtle display of the table grid, etc.) would be easy to add during one of the flights as well? ;-) Bruce |
From: Michael M. <mic...@ma...> - 2002-10-16 19:23:10
|
Hi, Just a quick note - I've been too swamped to reply, but I've been paying attention to your emails, and I'll send comments along soon. I've CC'd this message to bib...@li... mailinglist. You've made a lot of great suggestions, and I don't want to restrict who gets to comment on them. (That said, i don't know how many people have subscribed. probably just me.) Also, I have two 8 hour flights coming up this weekend, and I'm thinking I'll spend some of that time hacking on BD. I'll probably start with some of the small bugs, and move on to adding the more readable font display you mentioned. I'll also commit changes I made a few weeks ago that add support for an online help file, which seems necessary, even though I hate the Apple Help browser, because it's so slow. -mike On Sunday, October 13, 2002, at 10:53 AM, Bruce D'Arcus wrote: > Re: the search field issue Mike: > > This might be a little radical, but what about just removing the > drop-down option for where to search? The search functionality in OS > X is pretty powerful, and I don't really think we need to be able to > define what field is searched, and it may even be a hindrance. The > designers of the new AddressBook seemed to come to this conclusion as > well, and using the search field there, I think they were right. It > would also be easier to implement, and might translate into a more > elegant services (and contextual menu?) completion functionality > (just type a combination of words specific to a citation, like author > last name, and a few words from the title, etc.). > > The clear option would be nice though... > > Bruce > > -- Michael McCracken mm...@ac... http://www.cs.ucsd.edu/~mmccrack/ |
From: Michael M. <mic...@ma...> - 2002-10-16 19:18:23
|
You're welcome about the quick response. :) I'm fast at easy things. I'll be especially interested in any changes you had to make to get it to compile. I want to be sure it's as easy as possible to work on - I've almost exclusively worked on it on one machine, so there's plenty of chance for problems. I understand that the OmniFrameworks dependency makes it a pain at times, but it's totally worth it for the preferences framework alone. So, I CC'd this email to bib...@li... - I don't know if anyone else is using it, but it'd be good to use that list to discuss development stuff, so if other people start working on it too, we'll be able to manage it. When you do start working, if you could send a quick note (one sentence is fine, or even just 'working on feature request #nnn') so we don't duplicate effort? Thanks! -mike On Wednesday, October 16, 2002, at 11:31 AM, Josh Flachsbart wrote: > Hey thanks for the quick response. I got it all compiling and running > right away with the library. ProjectBuilder is fun, but makefiles are > just so straightforward. I ended up having to make a number of > changes to the project to get it to compile. Probably random stuff > from your paths left in on the last checkin. > > Thanks again, hopefully I will be done soon and able to do some "fun" > programming! > > Josh > > > On Thursday, October 10, 2002, at 02:20 AM, Michael McCracken wrote: > >> Hi, thanks for the enthusiasm! I've added libbtparse.a to the CVS. I >> don't know why it wasn't there. >> >> What were the oddities about your use of BibTeX? Hopefully it's not >> something that would require rewriting btparse. It's open source too, >> but it's not very simple. >> >> Thanks, >> -mike >> >> On Wednesday, October 9, 2002, at 10:08 PM, Josh Flachsbart wrote: >> >>> Michael, >>> >>> First off let me thank you for writing BibDesk. I am at the end of >>> writing my dissertation and have been using Mac OS X with TeXShop >>> for the past year preparing it. I am pulling together all my >>> sources from many different .bib files, and BibDesk has been >>> invaluable. In the process however I noticed that I have a few >>> oddities about the way I use BibTeX that make it difficult for me to >>> use BibDesk. When I noticed that you have it up on SF I decided >>> that I would download it, and see if I could (quickly!) make the >>> changes I wanted. So all the parts are here, but I seem to be >>> missing btparse.a which your "how to build" document claims is in >>> CVS. Am I missing something? >>> >>> Obviously the next month or so will be much too busy to make >>> anything clean enough to release, but if I am able to make this work >>> I could see implementing some of those feature requests. This is an >>> interesting program that could become tremendously useful for a >>> large number of people. >>> >>> Thanks for a great product! >>> >>> Josh Flachsbart >>> jd...@po...<PGP.sig> >> -- >> Michael McCracken >> mm...@ac... >> http://www.cs.ucsd.edu/~mmccrack/ >> > > -- Michael McCracken mm...@ac... http://www.cs.ucsd.edu/~mmccrack/ |
From: Bruce D'A. <bd...@ma...> - 2002-09-04 13:50:16
|
Great! On Wednesday, September 4, 2002, at 12:00 AM, Michael McCracken wrote: > If I recall what you wanted to do, it sounded like at least parts of > it would involve writing large parts from scratch (ie, the MSWord > integration) - meanwhile, the XML reading stuff would go in > BibDocument.m in a function like loadXMLDataRepresentation: - there > are already loadRSSDataRepresentation and loadBibTeXDataRepresentation > functions... called by loadDataRepresentation:ofType: ... I don't care that much about MS Word at this point. My bigger interest is in moving BibDesk to an xml data model, and with getting it to process rich text citations/references via services (in apps like Okito Composer). Bruce |