and isn't CHDK derived from that firmware by reverse engineering it?
Quote from: fvdk on 12 / July / 2009, 11:47:52and isn't CHDK derived from that firmware by reverse engineering it? No, CHDK is not derived from Canon firmware. CHDK is software that parasitically runs in the same computer Canon firmware does. Time for a bad analogy:The camera a lot like some fancy new car you've just bought. The factory won't give you service manuals, schematics or mechanical drawings but still you manage to dig in deep enough to understand how it works using a set of screw drivers, a logic analyzer and other wickedly funky tools you may have in your garage/electronics lab. For example, you could figure out how to dismantle the dashboard, and after a few nights you'll figure out how the car's annoyingly stupid and featureless radio system works and how those steering wheel buttons communicate with it. This enables you install your own audio player yet maintaining control from the steering wheel volume buttons.And it's still very much your audio player, you just didn't get any help from the car's manufacturer to install it.Some of CHDK is like that audio player. Some of CHDK is like a little black box you made that you installed between the steering wheel and the original radio to make the volume button press 'vol+' twice instead of once because you think volume doesn't go up fast enough when you hit the button (and the original radio didn't let you configure this).This little black box would be very much yours too.
@fvdk:Youre still completely missing the point. Whether david or someone else makes money with SDM is not the issue. That he's even turning down donations with said reason may be honorable, but again, not the point.Its: "taking ideas but failing to contribute."
Open source software is all about taking and giving, making a fork is nice, but making it impossible to backport good features or even lack of reporting bugs wich apply both to the fork as well as the main project is just bad manners.
Forking a project is fine. Making money out of it too. Being a dick is not.
Let me take one example. For kite aerial photographers, the ability to switch between still and movie modes in a script is very useful. Following work by jeff666 I produced CHDK builds for a handful of cameras (see http://www.zenoshrdlu.com/kapstuff/zchdk.html). I posted my code in the CHDK bugtracker (see 0000118) hoping that someone would find a way to extend the set of cameras - something I could not do. Seven months later nothing has happened despite the occasional prod from other CHDK users. However David Sykes volunteered to add the facility to SDM - and did so for ALL the cameras that SDM supports. For another example - for Kite aerial photographers the ND filter on Ixus cameras is a real problem. David has done a great deal of work on SDM to try to make that filter properly controllable in scripts. Take a look at his frequent appends in the KAP forum (http://steel.ced.berkeley.edu/cris/kap/discuss/) to see how helpful he has been.
However, I don't believe that David makes it impossible to backport good features. Yes, it probably is problematic.
And if David would actually contribute back, or not deliberately make it hard to backport stuff, all that stuff could be in CHDK too. Calling him a "dick" may be rude and unproductive, but I'd say what he does is far ruder than a rude word.
You are under the impression that he is deliberately making it hard but I think that he has already explained that he (unlike most of you) is not an experienced programmer.
Started by Microfunguy
Started by Microfunguy
« 1 2 »
General Help and Assistance on using CHDK stable releases
Started by acseven
General Discussion and Assistance
Started by dmcdonnell
Started by kylefoley76
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)