Re: [dev-biblio] Re: porting citeproc; wanna help?
On Jan 29, 2006, at 11:03 PM, Bruce D'Arcus wrote: More tomorrow; gotta go to bed. Heh, doesn't look like you need much help from me for programming :-) Still, I think it bears repeating that looking at your library from the outside first might help in this design process. //Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev-biblio] Re: porting citeproc; wanna help?
On Jan 29, 2006, at 9:52 PM, pt wrote: I agree that test-driven development will help a lot here. One starting point would be tests that show you can load data into some object from the RDF serialization suggested by Bruce then re- serialize it back out. Trivial to implement at first, but needs to be there as more code gets built. Bruce, you certainly have the skills to write unit tests that show how the objects should behave, and hope that others can help fill in the code. Ed - do you have test frameworks in mind for Python / Ruby? (I know there are a couple of options in Python - I've used py.test but not others) I've used a few different ones, but since I'm in ruby, python and java pretty frequently I've found myself using unittest, Test::Unit and junit since they all follow the same xunit pattern. py.test might be the simplest way to move forward though. I saw Ian Bicking talk [1] about py.test at a local python meeting and was pretty impressed with its simplicity. I'm psyched you agree pt :-) Defining a set of tests that illustrate how to use the API might be a good way for us to visualize how the library could be used, and for us to measure our success as the library gets fleshed out. //Ed [1] http://ianbicking.org/docs/pytest-presentation/pytest-slides.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev-biblio] Re: porting citeproc; wanna help?
On Jan 28, 2006, at 10:08 AM, Bruce D'Arcus wrote: On Jan 28, 2006, at 10:43 AM, Bruce D'Arcus wrote: I really don't care whether it's Python or Ruby, since both are object-oriented, and both are easy to read. At any rate, ultimately I'd like to see both citeproc-rb (think a module that could be included trivially in rails apps for example), AND citeproc-py (think integrating citation processing into, oh, textile processing). I don't care much how we get there though ;-) Also, obviously c++ or obj-c would be good, but it seems like the dynamic languages would be better for quick coding, and code that can be a good blue-print for other implementations. Bruce, I'm interested in helping out with this. I'm pretty familiar with both ruby and python but I don't have a good grasp on what exactly you want to do. Assuming the library existed could you flesh out how it would be used programatically? This is how test-driven- development often is of great help because it forces you to think about the API you are building before you actually build it :-) //Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev-biblio] clarification on coding needs
On Nov 19, 2005, at 1:09 PM, James Howison wrote: Probably I'm crazy. If you're crazy, then so am I. It seems odd to me as well. //Ed - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev-biblio] Update
On Nov 12, 2005, at 3:21 PM, David Wilson wrote: My impression is that they support, in principle, our approach and goals. We have to wait and see what resources can be scheduled for this work and when. Wow, this is great news. I'm a new subscriber to the dev list. I got interested by following Bruce's work for close to a year. Bruce actually asked me to send a quick introduction. I'm a software developer at Follett Corporation (a book distributor and library software company). I am currently working as a Java programmer but also have experience programming in Python, Ruby and Perl. A long time ago in a galaxy far far away I got an MLS and worked in academic libraries before deciding to pursue my life long interest in computers. At any rate, I'd like to contribute programming skills to this project. Hopefully I'll find the time to get involved as things progress. Ed Summers aim: inkdroid yahoo: inkdroid jabber: [EMAIL PROTECTED] http://www.inkdroid.org ; http://www.textualize.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
