From: Bernie R. <br...@ec...> - 2004-06-23 16:24:33
|
Hmm... that's very nice of you to offer. I would suggest the money goes to Matthias, for these reasons... 1) The code is his, I'm just making small changes to it 2) When I do commercial projects, $300 isn't much money 3) When I do non-commercial projects, $300 is way too much! *smile* At 02:38 PM 6/22/2004, brett hartshorn wrote: >Hello Bernie and Matthias, > >Clean and quick with Pyrex sounds like a good plan, i wish you luck. I >won't be able to help with >any of the code for the next 2-3 months. But in two months i am quitting >my day job to make more >time for working on free software projects, and then i may have time to help. > >I want to see the ODE wrappers done and done well. So i am putting a $300 >bounty on them. This >bounty is not meant to make people fight, everyone should still work >together as much as possible. > I just know from my own experiences it can be hard to work on free > software and pay the bills, so >this bounty is just meant to help out the developer a little bit. > >Here's the conditions for the bounty: > 1. All the features of ODE are exposed in Python (within reason, not > every little thing, but all >of the important stuff) > 2. The code is clean and easy to build (clean: i should have no > problems in reading it) (easy to >build: can be built on all platforms) > 3. It is licensed under the GNU GPL or LGPL > > >Thoughts? >-brett > > >--- Bernie Roehl <br...@ec...> wrote: > > At 11:05 AM 6/21/2004 -0700, brett hartshorn wrote: > > >Wrapping a > > >wrapper is not ideal, but from the perspective where several python > > >wrappers must be created and > > >maintained, it makes sense that they all use the same wrapping language. > > > > Perhaps, though I think it depends on the circumstances. > > > > For example, in the project I'm working on, I'm wrapping a C++ graphics > > library using SWIG and > > wrapping ODE using Pyrex. My reasoning is that the C++ graphics API is > one > > project, the > > ODE wrapper is another, and my main project simply imports modules from > the > > other two. > > > > In fact, I initially just used Mattias' PyODE without even knowing that it > > was written > > using Pyrex -- it was just a .pyd that I imported. The fact that I am now > > modifying some of the > > code in that wrapper doesn't really change anything -- the main project > > doesn't care where the .pyd > > files came from or what tools were used to create them. > > > > That means we can use the right tool for the job in each case. Since ODE > > is written in C, it makes > > sense to use Pyrex. Since the graphics library is written in C++, it > makes > > sense to use SWIG. > > For other things, it makes sense to use Boost. I could easily see a > Python > > application that > > imports modules that were created using all three tools, and the > > application developer doesn't need > > to know. > > > > >So it is a blancing act, do we > > >shoehorn ODE to fit into the Boost model, or do it the clean and quick > way > > >with Pyrex? > > > > I vote for clean and quick. :-) > > > > >Btw, is anybody in the San Francisco area? > > > > I'm in Waterloo, Ontario Canada (about an hour west of Toronto). > > > > > > -- > > Bernie Roehl > > University of Waterloo Dept of Electrical and Computer Engineering > > Mail: br...@ec... Voice: (519) 888-4567 x 2607 [work] > > URL: http://ece.uwaterloo.ca/~broehl > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > Pyode-user mailing list > > Pyo...@li... > > https://lists.sourceforge.net/lists/listinfo/pyode-user > > > > > > >__________________________________ >Do you Yahoo!? >Yahoo! Mail is new and improved - Check it out! >http://promotions.yahoo.com/new_mail -- Bernie Roehl University of Waterloo Dept of Electrical and Computer Engineering Mail: br...@ec... Voice: (519) 888-4567 x 2607 [work] URL: http://ece.uwaterloo.ca/~broehl |