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: Adam R. M. <ama...@ma...> - 2020-11-16 05:59:47
|
> On Nov 14, 2020, at 06:22 , Christiaan Hofman <cmh...@gm...> wrote: > > It would be a lot of work to convert the project to git and move it to GitHub. I am not even sure how to do this. Also, moving from sourceforge would be a problem, because the app itself points to it, for instance for its update checking. We cannot retroactively change that. FWIW, moving from svn to github isn't too hard, as I managed it for all of my projects when googlecode shut down a few years ago. Not that I recall how to do it, and the update checking is indeed a problem. > As for the AppStore, I don’t have a license and am not willing to pay for it. Moreover, probably it would be rejected, because we use features they do not allow. And we are open source, so paying would be hard. A Mac developer on twitter once told me that if I really cared about my TeX Live Utility users, I'd pay Apple's certificate fee, since it's not that much money. Since I haven't even used TeX in a decade, I see no reason to fork out $100 per year for Apple security theater that makes development even less pleasant. One-time cost? Sure, I might, but not every year. Apple sees no value in supporting open source projects, and frankly I see little value in Apple these days. When my Mojave system dies, I'm probably jumping ship after 30 years of using a Mac. -- adam |
From: Christiaan H. <cmh...@gm...> - 2020-11-14 14:23:22
|
> On 14 Nov 2020, at 14:48, Hein Meling <hei...@gm...> wrote: > > Hi, > > I wasn’t planning to use BibDesk at the moment, so this isn’t urgent for my part. However, after upgrading to macOS Big Sur, I was once again notified that the app needs to be updated… (see attached screenshot). I can of course disable this check and run it anyway, but why not put this through the Apple process and get it checked and signed. > > At the same time, I’m curious why still stay on sourceforge? It feels so antiquated and full of commercials that I’d rather stay away from it… I personally use GitHub, but there are others like bitbucket and gitlab. While I’m not a macOS dev, I suspect that it would be easier to get help from others if hosted on github. > > Best, > :) Hein > > > <Screen Shot 2020-11-14 at 14.26.51.png> > It would be a lot of work to convert the project to git and move it to GitHub. I am not even sure how to do this. Also, moving from sourceforge would be a problem, because the app itself points to it, for instance for its update checking. We cannot retroactively change that. As for the AppStore, I don’t have a license and am not willing to pay for it. Moreover, probably it would be rejected, because we use features they do not allow. And we are open source, so paying would be hard. Christiaan |
From: Hein M. <hei...@gm...> - 2020-11-14 13:48:58
|
Hi, I wasn’t planning to use BibDesk at the moment, so this isn’t urgent for my part. However, after upgrading to macOS Big Sur, I was once again notified that the app needs to be updated… (see attached screenshot). I can of course disable this check and run it anyway, but why not put this through the Apple process and get it checked and signed. At the same time, I’m curious why still stay on sourceforge? It feels so antiquated and full of commercials that I’d rather stay away from it… I personally use GitHub, but there are others like bitbucket and gitlab. While I’m not a macOS dev, I suspect that it would be easier to get help from others if hosted on github. Best, :) Hein |
From: Adam R. M. <ama...@ma...> - 2019-10-21 14:03:23
|
> On Oct 21, 2019, at 01:47 , Christiaan Hofman <cmh...@gm...> wrote: > > I was afraid this would cause problems. Unfortunately it was necessary, because Apple has deprecated legacy localization names, and it starts to become real in Catalina. Apparently Launch Services does not support them anymore. Oh, that's neat, considering we used the full names because the short ones didn't work. Apple has lost its mind, and I'm likely staying with High Sierra until this computer dies. |
From: Christiaan H. <cmh...@gm...> - 2019-10-21 08:47:59
|
> On 21 Oct 2019, at 02:56, Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote: > > >> On Oct 17, 2019, at 21:44 , Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote: >> >>> On Oct 15, 2019, at 01:52 , Christiaan Hofman <cmh...@gm...> wrote: >>> >>> There weren't any nightlies for the last few days. Is the computer down, or something wrong with the code? >> >> Subversion merge conflict in the .pbxproj file. Hopefully it will work tonight. > > Apparently this still wasn't working because commits failed. It looks like renaming directories (English.lproj) broke the working copy of the svn repo, so I had to blow away the entire directory and do a fresh checkout. > > — adam > Probably SF.net’s shitty SVN services. I had a similar problem once. Apparently they choke when there are a lot of changes in a single update, which leaves the working copy in an inconsistent state. They say to just not do that, which is just ludicrous, because sometimes it just happens. I was afraid this would cause problems. Unfortunately it was necessary, because Apple has deprecated legacy localization names, and it starts to become real in Catalina. Apparently Launch Services does not support them anymore. Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-10-21 00:56:42
|
> On Oct 17, 2019, at 21:44 , Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote: > >> On Oct 15, 2019, at 01:52 , Christiaan Hofman <cmh...@gm...> wrote: >> >> There weren't any nightlies for the last few days. Is the computer down, or something wrong with the code? > > Subversion merge conflict in the .pbxproj file. Hopefully it will work tonight. Apparently this still wasn't working because commits failed. It looks like renaming directories (English.lproj) broke the working copy of the svn repo, so I had to blow away the entire directory and do a fresh checkout. -- adam |
From: Adam R. M. <ama...@ma...> - 2019-10-18 05:00:40
|
> On Oct 15, 2019, at 01:52 , Christiaan Hofman <cmh...@gm...> wrote: > > There weren't any nightlies for the last few days. Is the computer down, or something wrong with the code? Subversion merge conflict in the .pbxproj file. Hopefully it will work tonight. -- adam |
From: Christiaan H. <cmh...@gm...> - 2019-10-15 08:52:25
|
There weren't any nightlies for the last few days. Is the computer down, or something wrong with the code? Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-03-16 03:08:07
|
> On Mar 15, 2019, at 02:46 , Christiaan Hofman <cmh...@gm...> wrote: > > It seems to have failed again, niw even with the commit. svn+ssh error according to the log. That's usually sourceforge. |
From: Christiaan H. <cmh...@gm...> - 2019-03-15 09:47:05
|
It seems to have failed again, niw even with the commit. Christiaan |
From: Christiaan H. <cmh...@gm...> - 2019-03-13 09:49:48
|
Cganged them. It nie seems to have worked. Christiaan Op di 12 mrt. 2019 16:45 schreef Adam R. Maxwell via Bibdesk-develop < bib...@li...: > > > On Mar 12, 2019, at 08:41 , Christiaan Hofman <cmh...@gm...> wrote: > Somehow the nightly build still did not appear. > > > Looks like there are a bunch of these in Sparkle. > > if (@available(macOS 10.8, *)) { > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUURLRequest.m:76:31: > warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 > [-Wpartial-availability] > NSURL *url = [decoder decodeObjectOfClass:[NSURL class] > forKey:SPUURLRequestURLKey]; > > > $ find . -type f -name "*.m" |xargs grep @available > ./Sparkle/Sparkle/SPUURLRequest.m: if (@available(macOS 10.8, *)) { > ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) { > ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) > ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) > ./Sparkle/Sparkle/SUUpdater.m: if (@available(macOS 10.9, *)) { > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > |
From: Adam R. M. <ama...@ma...> - 2019-03-12 15:45:07
|
> On Mar 12, 2019, at 08:41 , Christiaan Hofman <cmh...@gm...> wrote: > Somehow the nightly build still did not appear. Looks like there are a bunch of these in Sparkle. if (@available(macOS 10.8, *)) { ^ /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUURLRequest.m:76:31: warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 [-Wpartial-availability] NSURL *url = [decoder decodeObjectOfClass:[NSURL class] forKey:SPUURLRequestURLKey]; $ find . -type f -name "*.m" |xargs grep @available ./Sparkle/Sparkle/SPUURLRequest.m: if (@available(macOS 10.8, *)) { ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) { ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) ./Sparkle/Sparkle/SUUpdateAlert.m: if (@available(macOS 10.14, *)) ./Sparkle/Sparkle/SUUpdater.m: if (@available(macOS 10.9, *)) { |
From: Christiaan H. <cmh...@gm...> - 2019-03-12 15:41:44
|
> On 11 Mar 2019, at 16:33, Christiaan Hofman <cmh...@gm...> wrote: > > > >> On 11 Mar 2019, at 09:55, Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >> >> That's a big problem. I updated Sparkle to the latest, and they say it is compatible with Xcode 8 and runs on 10.7. It looks like that's a lie. These available compiler directives and macros have to do with cross development, a bit like checking for NSAppKitVersionNumber, but on the compiler level. Unfortunately I don't really understand myself how they work. The particular ones have to do with using the newer URL loading API, but only when they're available. Annoyingly I cannot find bug reporting facilities for Sparkle. >> >> Op ma 11 mrt. 2019 02:27 schreef Adam R. Maxwell via Bibdesk-develop <bib...@li... <mailto:bib...@li...>: >> >> >>> On Mar 8, 2019, at 11:19 , Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >>> >>> I did not see the last nightly in Dropbox. Were there problems building? There were some changes yesterday for upgrading BibDesk that may give problems, although they should work for Xcode 8. >> >> Looks like it's complaining about @available, whatever that is? >> >> /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:55:9: error: unexpected '@' in program >> if (@available(macOS 10.8, *)) { >> ^ >> /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 [-Wpartial-availability] >> NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; >> ^ >> In module 'Foundation' imported from /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.h:10: >> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:89:1: note: 'decodeObjectOfClass:forKey:' has been explicitly marked partial here >> - (nullable id)decodeObjectOfClass:(Class)aClass forKey:(NSString *)key NS_AVAILABLE(10_8, 6_0); >> ^ >> /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: note: explicitly redeclare 'decodeObjectOfClass:forKey:' to silence this warning >> NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; >> > > I’ve changed this check to compare the system version rather than using this compiler directive. Hopefully it does now work. > > Christiaan > Somehow the nightly build still did not appear. Christiaan |
From: Christiaan H. <cmh...@gm...> - 2019-03-11 15:33:42
|
> On 11 Mar 2019, at 09:55, Christiaan Hofman <cmh...@gm...> wrote: > > That's a big problem. I updated Sparkle to the latest, and they say it is compatible with Xcode 8 and runs on 10.7. It looks like that's a lie. These available compiler directives and macros have to do with cross development, a bit like checking for NSAppKitVersionNumber, but on the compiler level. Unfortunately I don't really understand myself how they work. The particular ones have to do with using the newer URL loading API, but only when they're available. Annoyingly I cannot find bug reporting facilities for Sparkle. > > Op ma 11 mrt. 2019 02:27 schreef Adam R. Maxwell via Bibdesk-develop <bib...@li... <mailto:bib...@li...>: > > >> On Mar 8, 2019, at 11:19 , Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: >> >> I did not see the last nightly in Dropbox. Were there problems building? There were some changes yesterday for upgrading BibDesk that may give problems, although they should work for Xcode 8. > > Looks like it's complaining about @available, whatever that is? > > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:55:9: error: unexpected '@' in program > if (@available(macOS 10.8, *)) { > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 [-Wpartial-availability] > NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; > ^ > In module 'Foundation' imported from /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.h:10: > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:89:1: note: 'decodeObjectOfClass:forKey:' has been explicitly marked partial here > - (nullable id)decodeObjectOfClass:(Class)aClass forKey:(NSString *)key NS_AVAILABLE(10_8, 6_0); > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: note: explicitly redeclare 'decodeObjectOfClass:forKey:' to silence this warning > NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; > I’ve changed this check to compare the system version rather than using this compiler directive. Hopefully it does now work. Christiaan |
From: Christiaan H. <cmh...@gm...> - 2019-03-11 08:55:55
|
That's a big problem. I updated Sparkle to the latest, and they say it is compatible with Xcode 8 and runs on 10.7. It looks like that's a lie. These available compiler directives and macros have to do with cross development, a bit like checking for NSAppKitVersionNumber, but on the compiler level. Unfortunately I don't really understand myself how they work. The particular ones have to do with using the newer URL loading API, but only when they're available. Annoyingly I cannot find bug reporting facilities for Sparkle. Op ma 11 mrt. 2019 02:27 schreef Adam R. Maxwell via Bibdesk-develop < bib...@li...: > > > On Mar 8, 2019, at 11:19 , Christiaan Hofman <cmh...@gm...> wrote: > > I did not see the last nightly in Dropbox. Were there problems building? > There were some changes yesterday for upgrading BibDesk that may give > problems, although they should work for Xcode 8. > > > Looks like it's complaining about @available, whatever that is? > > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:55:9: > error: unexpected '@' in program > if (@available(macOS 10.8, *)) { > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: > warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 > [-Wpartial-availability] > NSData *data = [decoder decodeObjectOfClass:[NSData class] > forKey:SPUDownloadDataKey]; > ^ > In module 'Foundation' imported from > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.h:10: > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:89:1: > note: 'decodeObjectOfClass:forKey:' has been explicitly marked partial here > - (nullable id)decodeObjectOfClass:(Class)aClass forKey:(NSString *)key > NS_AVAILABLE(10_8, 6_0); > ^ > /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: > note: explicitly redeclare 'decodeObjectOfClass:forKey:' to silence this > warning > NSData *data = [decoder decodeObjectOfClass:[NSData class] > forKey:SPUDownloadDataKey]; > > > > > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > |
From: Adam R. M. <ama...@ma...> - 2019-03-11 01:27:32
|
> On Mar 8, 2019, at 11:19 , Christiaan Hofman <cmh...@gm...> wrote: > > I did not see the last nightly in Dropbox. Were there problems building? There were some changes yesterday for upgrading BibDesk that may give problems, although they should work for Xcode 8. Looks like it's complaining about @available, whatever that is? /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:55:9: error: unexpected '@' in program if (@available(macOS 10.8, *)) { ^ /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: warning: 'decodeObjectOfClass:forKey:' is partial: introduced in macOS 10.8 [-Wpartial-availability] NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; ^ In module 'Foundation' imported from /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.h:10: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSCoder.h:89:1: note: 'decodeObjectOfClass:forKey:' has been explicitly marked partial here - (nullable id)decodeObjectOfClass:(Class)aClass forKey:(NSString *)key NS_AVAILABLE(10_8, 6_0); ^ /Volumes/Local/Users/amaxwell/build/bibdesk-clean/vendorsrc/andymatuschak/Sparkle/Sparkle/SPUDownloadData.m:56:33: note: explicitly redeclare 'decodeObjectOfClass:forKey:' to silence this warning NSData *data = [decoder decodeObjectOfClass:[NSData class] forKey:SPUDownloadDataKey]; |
From: Christiaan H. <cmh...@gm...> - 2019-03-08 19:20:02
|
I did not see the last nightly in Dropbox. Were there problems building? There were some changes yesterday for upgrading BibDesk that may give problems, although they should work for Xcode 8. Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-02-08 22:34:41
|
> On Feb 8, 2019, at 14:32 , Christiaan Hofman <cmh...@gm...> wrote: > > > >> On 8 Feb 2019, at 23:31, Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote: >> >> >> >>> On Feb 7, 2019, at 02:34 , Christiaan Hofman <cmh...@gm...> wrote: >>> >>> Adam, what Xcode version is used for the nightly builds? It looks like the compiled nibs have dark mode problems. >> >> Looks like it's 8.2.1, running under El Capitan. I don't have anything running 10.14, and don't bother tracking Xcode updates anymore. If there's a later Xcode, I can probably download and try it. >> >> — adam >> > > I think 8.2.1 is the last one running on El Cap. It may well be. It's also the one I'm running on High Sierra, for whatever reason. My days of being an early adopter are long behind me, obviously :). -- adam |
From: Christiaan H. <cmh...@gm...> - 2019-02-08 22:32:50
|
> On 8 Feb 2019, at 23:31, Adam R. Maxwell via Bibdesk-develop <bib...@li...> wrote: > > > >> On Feb 7, 2019, at 02:34 , Christiaan Hofman <cmh...@gm...> wrote: >> >> Adam, what Xcode version is used for the nightly builds? It looks like the compiled nibs have dark mode problems. > > Looks like it's 8.2.1, running under El Capitan. I don't have anything running 10.14, and don't bother tracking Xcode updates anymore. If there's a later Xcode, I can probably download and try it. > > — adam > I think 8.2.1 is the last one running on El Cap. Christiaan |
From: Adam R. M. <ama...@ma...> - 2019-02-08 22:31:28
|
> On Feb 7, 2019, at 02:34 , Christiaan Hofman <cmh...@gm...> wrote: > > Adam, what Xcode version is used for the nightly builds? It looks like the compiled nibs have dark mode problems. Looks like it's 8.2.1, running under El Capitan. I don't have anything running 10.14, and don't bother tracking Xcode updates anymore. If there's a later Xcode, I can probably download and try it. -- adam |
From: Christiaan H. <cmh...@gm...> - 2019-02-07 10:34:11
|
Adam, what Xcode version is used for the nightly builds? It looks like the compiled nibs have dark mode problems. Christiaan |
From: Christiaan H. <cmh...@gm...> - 2018-11-14 14:40:09
|
I put a copy at https://bibdesk.sourceforge.io/FolderPenicon <https://bibdesk.sourceforge.io/FolderPenicon>.icns Christiaan > On 14 Nov 2018, at 14:21, Christiaan Hofman <cmh...@gm...> wrote: > > Yeah, they both have problems, and I also don't have problems with the current one myself. Also, I just made a somewhat enhanced scaled up version of the current one that looks pretty good. I think I will switch to that. Only have to update the document icons as well. > > Christiaan > > Op wo 14 nov. 2018 07:51 schreef Adam R. Maxwell via Bibdesk-develop <bib...@li... <mailto:bib...@li...>>: > > > > On Nov 9, 2018, at 15:02 , Christiaan Hofman <cmh...@gm... <mailto:cmh...@gm...>> wrote: > > > > I wonder if anyone here wants to chip in. I got two proposals for new icons for BibDesk with a higher resolution. Given that the icon is only 256 px now, that may be a good idea. I wonder what other people here think about these two proposals. These are not full size to avoid going over the size limit for this list. > > FWIW, the old icon doesn't bother me at all at normal dock sizes on a 15" retina MacBook Pro. It's held up pretty well, I think, and it's been there since the beginning. I now get Photos and iTunes mixed up all the time, because the shapes grab my eye similarly; BibDesk has a distinct enough shape and color to be useful. > > Specific criticisms of these icons: one has a misspelling ("Internation Journal…"), and the other looks way too much like Stickies. > > Anyway, random thoughts from someone who hates change. > > -- adam |
From: Christiaan H. <cmh...@gm...> - 2018-11-14 13:21:38
|
Yeah, they both have problems, and I also don't have problems with the current one myself. Also, I just made a somewhat enhanced scaled up version of the current one that looks pretty good. I think I will switch to that. Only have to update the document icons as well. Christiaan Op wo 14 nov. 2018 07:51 schreef Adam R. Maxwell via Bibdesk-develop < bib...@li...>: > > > > On Nov 9, 2018, at 15:02 , Christiaan Hofman <cmh...@gm...> wrote: > > > > I wonder if anyone here wants to chip in. I got two proposals for new > icons for BibDesk with a higher resolution. Given that the icon is only 256 > px now, that may be a good idea. I wonder what other people here think > about these two proposals. These are not full size to avoid going over the > size limit for this list. > > FWIW, the old icon doesn't bother me at all at normal dock sizes on a 15" > retina MacBook Pro. It's held up pretty well, I think, and it's been there > since the beginning. I now get Photos and iTunes mixed up all the time, > because the shapes grab my eye similarly; BibDesk has a distinct enough > shape and color to be useful. > > Specific criticisms of these icons: one has a misspelling ("Internation > Journal…"), and the other looks way too much like Stickies. > > Anyway, random thoughts from someone who hates change. > > -- adam > > > > _______________________________________________ > Bibdesk-develop mailing list > Bib...@li... > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop > |
From: Adam R. M. <ama...@ma...> - 2018-11-14 06:51:16
|
> On Nov 9, 2018, at 15:02 , Christiaan Hofman <cmh...@gm...> wrote: > > I wonder if anyone here wants to chip in. I got two proposals for new icons for BibDesk with a higher resolution. Given that the icon is only 256 px now, that may be a good idea. I wonder what other people here think about these two proposals. These are not full size to avoid going over the size limit for this list. FWIW, the old icon doesn't bother me at all at normal dock sizes on a 15" retina MacBook Pro. It's held up pretty well, I think, and it's been there since the beginning. I now get Photos and iTunes mixed up all the time, because the shapes grab my eye similarly; BibDesk has a distinct enough shape and color to be useful. Specific criticisms of these icons: one has a misspelling ("Internation Journal…"), and the other looks way too much like Stickies. Anyway, random thoughts from someone who hates change. -- adam |
From: Christiaan H. <cmh...@gm...> - 2018-11-09 23:02:51
|
I wonder if anyone here wants to chip in. I got two proposals for new icons for BibDesk with a higher resolution. Given that the icon is only 256 px now, that may be a good idea. I wonder what other people here think about these two proposals. These are not full size to avoid going over the size limit for this list. Christiaan |