Re: [CODE4LIB] Native MarcEdit for MacOSX
This discussion is timely form my pov: in a new job where everyone uses a MAC. Agreed with Terry: as a command line tool, it works fine on a Mac but I'd rather not have to write one-off scripts just to avoid using the UI on a Mac (which crashes on me a lot). I had a Windows VM installed at work today just to help w/ MarcEdit stuff. re: types of machine: Personally, I'd rather he get enough $$$ to purchase a laptop if he chooses ... the software helps a lot of people earn part of their paycheck. Myself included. On Tue, Apr 7, 2015 at 1:36 PM, Cary Gordon listu...@chillco.com wrote: IMHO: 1) If you create something, and you are not under contract to another entity, you own it as intellectual property, and you can do whatever you want with it. 2) Open source and even free and open source does not imply any contribution model or the licensee's right to have input into development and maintenance. The open source licenses that I am familiar with do not confer any ownership on the licensees. 3) Under the major open source licenses, licensees are free to fork the project, with certain restrictions, such as identifying the source and inheriting the license. I support Terry's right to do whatever he wants with his work. That said, I encourage him to consider moving to open source, where he might learn to love the pull request. Probably not all of them, though. Cary On Apr 6, 2015, at 10:49 PM, Roy Tennant roytenn...@gmail.com wrote: I agree with Terry. His decisions on how to deal with his codebase has stood the test of time. Open source doesn't mean squat if no one steps up to maintain it (and I have some experience with that), so having someone dedicated to maintaining it is not a bad strategy. It may not beds the most politically correct solution, but so be it. Running (and maintained) code trumps everything. Roy On Mon, Apr 6, 2015 at 6:13 PM, Terry Reese ree...@gmail.com wrote: Hi Bill, Sure -- this has been asked before. In fact, I wrote an article about the responsibilities developers and organizations have, regardless of if they utilize a closed or open source model in the C4L Journal back in 2012: http://journal.code4lib.org/articles/6393. In my case, it's been two things. Until around 2006 or 2007, MarcEdit's code libraries were still largely written in assembly so there was very little interest. But since migrating the code to something more accessible (C#), I'd have to say that the main reason is that work on the project has, and continues to be, a hobby and avenue for me to pursue something that I happen to be quite passionate about. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of William Denton Sent: Monday, April 6, 2015 7:46 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Native MarcEdit for MacOSX On 6 April 2015, Terry Reese wrote: What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. I've always been curious, and now seems a good time to ask: I'm sure you've considered, and been asked about, releasing MarcEdit under a free software license, but decided against it. Why? Bill -- William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/ -- Nitin Arora nitaro74 (at) gmail (dot) com Hope always, expect never. humaneguitarist.org blog.humaneguitarist.org
Re: [CODE4LIB] Native MarcEdit for MacOSX
On 6 April 2015, Roy Tennant wrote: I agree with Terry. His decisions on how to deal with his codebase has stood the test of time. Open source doesn't mean squat if no one steps up to maintain it (and I have some experience with that), so having someone dedicated to maintaining it is not a bad strategy. It may not beds the most politically correct solution, but so be it. Running (and maintained) code trumps everything. It doesn't trump software freedom, in my opinion, and I don't understand the apparent feeling that free software can't have a dedicated long-term maintainer, but how other people handle their code is up to them, and I'm glad to now know the reasoning in this case. Bill -- William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
Re: [CODE4LIB] Native MarcEdit for MacOSX
Open source doesn't mean squat if no one steps up to maintain it Assuming we're talking about Free and Open Source (FOSS) (not just Open Source) then it actually it does mean something. If the maintainer looses interest in the project you can the code and make it your own. A company can go under. Then you're stuck without a solution. If you have the code you have the ability to maintain it yourself, or hire someone to do that. -Justin
Re: [CODE4LIB] Native MarcEdit for MacOSX
IMHO: 1) If you create something, and you are not under contract to another entity, you own it as intellectual property, and you can do whatever you want with it. 2) Open source and even free and open source does not imply any contribution model or the licensee's right to have input into development and maintenance. The open source licenses that I am familiar with do not confer any ownership on the licensees. 3) Under the major open source licenses, licensees are free to fork the project, with certain restrictions, such as identifying the source and inheriting the license. I support Terry's right to do whatever he wants with his work. That said, I encourage him to consider moving to open source, where he might learn to love the pull request. Probably not all of them, though. Cary On Apr 6, 2015, at 10:49 PM, Roy Tennant roytenn...@gmail.com wrote: I agree with Terry. His decisions on how to deal with his codebase has stood the test of time. Open source doesn't mean squat if no one steps up to maintain it (and I have some experience with that), so having someone dedicated to maintaining it is not a bad strategy. It may not beds the most politically correct solution, but so be it. Running (and maintained) code trumps everything. Roy On Mon, Apr 6, 2015 at 6:13 PM, Terry Reese ree...@gmail.com wrote: Hi Bill, Sure -- this has been asked before. In fact, I wrote an article about the responsibilities developers and organizations have, regardless of if they utilize a closed or open source model in the C4L Journal back in 2012: http://journal.code4lib.org/articles/6393. In my case, it's been two things. Until around 2006 or 2007, MarcEdit's code libraries were still largely written in assembly so there was very little interest. But since migrating the code to something more accessible (C#), I'd have to say that the main reason is that work on the project has, and continues to be, a hobby and avenue for me to pursue something that I happen to be quite passionate about. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of William Denton Sent: Monday, April 6, 2015 7:46 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Native MarcEdit for MacOSX On 6 April 2015, Terry Reese wrote: What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. I've always been curious, and now seems a good time to ask: I'm sure you've considered, and been asked about, releasing MarcEdit under a free software license, but decided against it. Why? Bill -- William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
Re: [CODE4LIB] Native MarcEdit for MacOSX
Clarification -- this will written using Xamarin's Mac toolset which utilizes Object-C for the UI and messaging, and an optimized version of the mono framework delivered for 32/64-bit mac systems). The present Mac version of MarcEdit is really two applications. There is the backend assembly files and a god-awful emulation of the WPF classes that work fairly poorly but allow for a single code-base. When run headless (via the command line) -- the non-UI version of MarcEdit runs quite nicely and at speeds that are close to the Linux and Windows version. Open it up to use it via a GUI, that it sucks (I'll admit it). What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. Since this was brought up -- I've sketched out a 3 month roadmap -- enough time I believe to migrate the core functionality to a native application build. From there, feature parity as appropriate. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Francis Kayiwa Sent: Monday, April 6, 2015 3:31 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Native MarcEdit for MacOSX Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you.
Re: [CODE4LIB] Native MarcEdit for MacOSX
On 4/6/15 3:57 PM, Salazar, Christina wrote: What happens to the Mac once you've completed the project? Or would it be used to continue parallel (Win/Linux/Mac) development? That would be the first time a software project was ever completed no? ./fxk Christina Salazar Systems Librarian John Spoor Broome Library California State University, Channel Islands 805/437-3198 -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Terry Reese Sent: Monday, April 06, 2015 12:46 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Native MarcEdit for MacOSX Clarification -- this will written using Xamarin's Mac toolset which utilizes Object-C for the UI and messaging, and an optimized version of the mono framework delivered for 32/64-bit mac systems). The present Mac version of MarcEdit is really two applications. There is the backend assembly files and a god-awful emulation of the WPF classes that work fairly poorly but allow for a single code-base. When run headless (via the command line) -- the non-UI version of MarcEdit runs quite nicely and at speeds that are close to the Linux and Windows version. Open it up to use it via a GUI, that it sucks (I'll admit it). What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. Since this was brought up -- I've sketched out a 3 month roadmap -- enough time I believe to migrate the core functionality to a native application build. From there, feature parity as appropriate. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Francis Kayiwa Sent: Monday, April 6, 2015 3:31 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Native MarcEdit for MacOSX Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you. -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you.
Re: [CODE4LIB] Native MarcEdit for MacOSX
That would be the plan. It wouldn't really be worth my time to do this once since it would fall out of date fairly quickly and will suck up nearly all my free dev. cycles for an initial 3 months or so. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Salazar, Christina Sent: Monday, April 6, 2015 3:58 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Native MarcEdit for MacOSX What happens to the Mac once you've completed the project? Or would it be used to continue parallel (Win/Linux/Mac) development? Christina Salazar Systems Librarian John Spoor Broome Library California State University, Channel Islands 805/437-3198 -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Terry Reese Sent: Monday, April 06, 2015 12:46 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Native MarcEdit for MacOSX Clarification -- this will written using Xamarin's Mac toolset which utilizes Object-C for the UI and messaging, and an optimized version of the mono framework delivered for 32/64-bit mac systems). The present Mac version of MarcEdit is really two applications. There is the backend assembly files and a god-awful emulation of the WPF classes that work fairly poorly but allow for a single code-base. When run headless (via the command line) -- the non-UI version of MarcEdit runs quite nicely and at speeds that are close to the Linux and Windows version. Open it up to use it via a GUI, that it sucks (I'll admit it). What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. Since this was brought up -- I've sketched out a 3 month roadmap -- enough time I believe to migrate the core functionality to a native application build. From there, feature parity as appropriate. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Francis Kayiwa Sent: Monday, April 6, 2015 3:31 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Native MarcEdit for MacOSX Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you.
Re: [CODE4LIB] Native MarcEdit for MacOSX
You might want to consider picking up a MacBook on Craigslist, or something like that. You can get a lot of only slightly vintage computer for $5-700. Cary Random ad: 13 MacBook ProTurbo 2.9GHz i5 Dual-core ϟ Thunderbolt! + 500GB Storage - $499 (Los Angeles) make / manufacturer: Apple MacBook Pro size / dimensions: 13 Up for sale my 13-inch Macbook Pro with free $40 case 2.3GHz Turbo 2.9Ghz 500GB Storage 4GB Ram DDR3 Thunderbolt USB FireWire On Apr 6, 2015, at 12:31 PM, Francis Kayiwa kay...@pobox.com wrote: Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you.
Re: [CODE4LIB] Native MarcEdit for MacOSX
What happens to the Mac once you've completed the project? Or would it be used to continue parallel (Win/Linux/Mac) development? Christina Salazar Systems Librarian John Spoor Broome Library California State University, Channel Islands 805/437-3198 -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Terry Reese Sent: Monday, April 06, 2015 12:46 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Native MarcEdit for MacOSX Clarification -- this will written using Xamarin's Mac toolset which utilizes Object-C for the UI and messaging, and an optimized version of the mono framework delivered for 32/64-bit mac systems). The present Mac version of MarcEdit is really two applications. There is the backend assembly files and a god-awful emulation of the WPF classes that work fairly poorly but allow for a single code-base. When run headless (via the command line) -- the non-UI version of MarcEdit runs quite nicely and at speeds that are close to the Linux and Windows version. Open it up to use it via a GUI, that it sucks (I'll admit it). What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. Since this was brought up -- I've sketched out a 3 month roadmap -- enough time I believe to migrate the core functionality to a native application build. From there, feature parity as appropriate. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Francis Kayiwa Sent: Monday, April 6, 2015 3:31 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: [CODE4LIB] Native MarcEdit for MacOSX Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you.
Re: [CODE4LIB] Native MarcEdit for MacOSX
Hello, I'll sell muy iMac for $400. I was owning in listing it on eBay this week. Thanks, Cornel Darden Jr. MSLIS Library Department Chair South Suburban College 7087052945 Our Mission is to Serve our Students and the Community through lifelong learning. Sent from my iPhone On Apr 6, 2015, at 3:18 PM, Cary Gordon listu...@chillco.com wrote: You might want to consider picking up a MacBook on Craigslist, or something like that. You can get a lot of only slightly vintage computer for $5-700. Cary Random ad: 13 MacBook ProTurbo 2.9GHz i5 Dual-core ϟ Thunderbolt! + 500GB Storage - $499 (Los Angeles) make / manufacturer: Apple MacBook Pro size / dimensions: 13 Up for sale my 13-inch Macbook Pro with free $40 case 2.3GHz Turbo 2.9Ghz 500GB Storage 4GB Ram DDR3 Thunderbolt USB FireWire On Apr 6, 2015, at 12:31 PM, Francis Kayiwa kay...@pobox.com wrote: Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you.
Re: [CODE4LIB] Native MarcEdit for MacOSX
I wish I could teleport my rarely used iMac, but in keeping with current technology capabilities, I'll just donate digital monetary value. This is definitely a worthy cause. kc On 4/6/15 12:31 PM, Francis Kayiwa wrote: Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: +1-510-435-8234 skype: kcoylenet/+1-510-984-3600
Re: [CODE4LIB] Native MarcEdit for MacOSX
Have you had one? I started out with one a while back because it was indeed the cheapest Mac. It seemed underpowered at the time. Plus you have to add a screen to it, and a keyboard, and a mouse so the price goes up. On the plus size, it doesn't take up much room... without the screen, the keyboard... kc On 4/6/15 2:36 PM, Roy Tennant wrote: Better yet, get a brand-new Mac mini for what you've already raised: http://store.apple.com/us/buy-mac/mac-mini Roy On Mon, Apr 6, 2015 at 1:18 PM, Cary Gordon listu...@chillco.com wrote: You might want to consider picking up a MacBook on Craigslist, or something like that. You can get a lot of only slightly vintage computer for $5-700. Cary Random ad: 13 MacBook ProTurbo 2.9GHz i5 Dual-core ϟ Thunderbolt! + 500GB Storage - $499 (Los Angeles) make / manufacturer: Apple MacBook Pro size / dimensions: 13 Up for sale my 13-inch Macbook Pro with free $40 case 2.3GHz Turbo 2.9Ghz 500GB Storage 4GB Ram DDR3 Thunderbolt USB FireWire On Apr 6, 2015, at 12:31 PM, Francis Kayiwa kay...@pobox.com wrote: Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you. -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: +1-510-435-8234 skype: kcoylenet/+1-510-984-3600
Re: [CODE4LIB] Native MarcEdit for MacOSX
Better yet, get a brand-new Mac mini for what you've already raised: http://store.apple.com/us/buy-mac/mac-mini Roy On Mon, Apr 6, 2015 at 1:18 PM, Cary Gordon listu...@chillco.com wrote: You might want to consider picking up a MacBook on Craigslist, or something like that. You can get a lot of only slightly vintage computer for $5-700. Cary Random ad: 13 MacBook ProTurbo 2.9GHz i5 Dual-core ϟ Thunderbolt! + 500GB Storage - $499 (Los Angeles) make / manufacturer: Apple MacBook Pro size / dimensions: 13 Up for sale my 13-inch Macbook Pro with free $40 case 2.3GHz Turbo 2.9Ghz 500GB Storage 4GB Ram DDR3 Thunderbolt USB FireWire On Apr 6, 2015, at 12:31 PM, Francis Kayiwa kay...@pobox.com wrote: Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you.
Re: [CODE4LIB] Native MarcEdit for MacOSX
On 6 April 2015, Terry Reese wrote: What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. I've always been curious, and now seems a good time to ask: I'm sure you've considered, and been asked about, releasing MarcEdit under a free software license, but decided against it. Why? Bill -- William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
Re: [CODE4LIB] Native MarcEdit for MacOSX
I have one and use it to power various house functions including storage and backups. I also use it for rendering video. I prefer a MacBook for coding, as I can take it with me around the (tiny) house, to the office, coffee shop, Mumbai, Paris, anywhere. I do most of my work on a 13 Air. Cary On Apr 6, 2015, at 3:36 PM, Karen Coyle li...@kcoyle.net wrote: Have you had one? I started out with one a while back because it was indeed the cheapest Mac. It seemed underpowered at the time. Plus you have to add a screen to it, and a keyboard, and a mouse so the price goes up. On the plus size, it doesn't take up much room... without the screen, the keyboard... kc On 4/6/15 2:36 PM, Roy Tennant wrote: Better yet, get a brand-new Mac mini for what you've already raised: http://store.apple.com/us/buy-mac/mac-mini Roy On Mon, Apr 6, 2015 at 1:18 PM, Cary Gordon listu...@chillco.com wrote: You might want to consider picking up a MacBook on Craigslist, or something like that. You can get a lot of only slightly vintage computer for $5-700. Cary Random ad: 13 MacBook ProTurbo 2.9GHz i5 Dual-core ϟ Thunderbolt! + 500GB Storage - $499 (Los Angeles) make / manufacturer: Apple MacBook Pro size / dimensions: 13 Up for sale my 13-inch Macbook Pro with free $40 case 2.3GHz Turbo 2.9Ghz 500GB Storage 4GB Ram DDR3 Thunderbolt USB FireWire On Apr 6, 2015, at 12:31 PM, Francis Kayiwa kay...@pobox.com wrote: Terry Reese (thanks Terry if you are reading this) has offered to write a Object-C version of MarcEdit. In order to this he needed access to a Apple Hardware. While my initial proposal on Go Fund me below was for a Macbook Pro, we've since realized it need not be a portable device. My current arithmetic puts the price of this at ~US$1300 as opposed to the listed ~US$2400 Thanks for boosting this signal if you cannot otherwise help fund porting MarcEdit for the Mac OSX platform. http://www.gofundme.com/qtbzq4 Cheers, ./fxk -- Your analyst has you mixed up with another patient. Don't believe a thing he tells you. -- Karen Coyle kco...@kcoyle.net http://kcoyle.net m: +1-510-435-8234 skype: kcoylenet/+1-510-984-3600
Re: [CODE4LIB] Native MarcEdit for MacOSX
Hi Bill, Sure -- this has been asked before. In fact, I wrote an article about the responsibilities developers and organizations have, regardless of if they utilize a closed or open source model in the C4L Journal back in 2012: http://journal.code4lib.org/articles/6393. In my case, it's been two things. Until around 2006 or 2007, MarcEdit's code libraries were still largely written in assembly so there was very little interest. But since migrating the code to something more accessible (C#), I'd have to say that the main reason is that work on the project has, and continues to be, a hobby and avenue for me to pursue something that I happen to be quite passionate about. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of William Denton Sent: Monday, April 6, 2015 7:46 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Native MarcEdit for MacOSX On 6 April 2015, Terry Reese wrote: What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. I've always been curious, and now seems a good time to ask: I'm sure you've considered, and been asked about, releasing MarcEdit under a free software license, but decided against it. Why? Bill -- William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
Re: [CODE4LIB] Native MarcEdit for MacOSX
I agree with Terry. His decisions on how to deal with his codebase has stood the test of time. Open source doesn't mean squat if no one steps up to maintain it (and I have some experience with that), so having someone dedicated to maintaining it is not a bad strategy. It may not beds the most politically correct solution, but so be it. Running (and maintained) code trumps everything. Roy On Mon, Apr 6, 2015 at 6:13 PM, Terry Reese ree...@gmail.com wrote: Hi Bill, Sure -- this has been asked before. In fact, I wrote an article about the responsibilities developers and organizations have, regardless of if they utilize a closed or open source model in the C4L Journal back in 2012: http://journal.code4lib.org/articles/6393. In my case, it's been two things. Until around 2006 or 2007, MarcEdit's code libraries were still largely written in assembly so there was very little interest. But since migrating the code to something more accessible (C#), I'd have to say that the main reason is that work on the project has, and continues to be, a hobby and avenue for me to pursue something that I happen to be quite passionate about. --tr -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of William Denton Sent: Monday, April 6, 2015 7:46 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Native MarcEdit for MacOSX On 6 April 2015, Terry Reese wrote: What I've offered is that I'd redo the application to provide a native Mac App that is Mac-Native while still making use of the present assembly code. This of course requires a Mac of some kind -- and since I'm not a Mac user, there it is. From the users perspective, it should all be Mac-tastic. I've always been curious, and now seems a good time to ask: I'm sure you've considered, and been asked about, releasing MarcEdit under a free software license, but decided against it. Why? Bill -- William Denton ↔ Toronto, Canada ↔ https://www.miskatonic.org/
