On May 9, 2007, at 10:27 AM, Peter N Lewis wrote:

Unfortunately, the benefit is how much it is customized to my needs which makes it pretty much useless as even an example for CamelBones.

I get the impression that your app isn't the only one. As you probably know, I've wondered aloud from time to time if anyone is using CamelBones; invariably, I've gotten an inbox full of responses like yours: Yes, I'm using it for custom bespoke apps, but I haven't released anything to the public.

Especially with the OpenGL stuff, I'm tempted to have a go at writing a game in CamelBones/OpenGL. I'm not sure if the license agreements let you write a commercial program using these things though. I think they do (CamelBones is LGPL and OpenGL looks to be fairly permissive, and most Perl stuff is Artistic License which is very permissive). If I ever did, I'd certainly be funneling some portion to support CamelBones.

It's certainly worth mentioning then, that the CamelBones license will be changing. Apple asked about the possibility of an BSD-style or Artistic license, and I'd been thinking of it for quite a long time anyway. Most of the modules in the *Kit PARS are licensed under the same terms as Perl itself, and having pieces of the distribution licensed differently is confusing.

So, the next version - 1.2 release, preceded by 1.1.x betas - will also be licensed under the same terms: GPL or Artistic, your choice. I wouldn't have had a problem with a commercial program using CB anyway, even before the license change - the LGPL only requires that the framework can be easily replaced with a custom version, and the structure of an .app bundle makes that a trivial task.

Also, I've been looking at PyGame, and watching how much enthusiasm it helps generate around Python. Games could definitely be a "killer app" area here.


Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net

Reply via email to