dvip
I would like to see as you said something that "Makes CHDK a whole ot easier to use in real photographic usage situations".
Better DNGs, HDRs, fast scripts to talk to the ARM architecture... And a simple menu for real photographic situations.
A speedy and slick CHDK 😁
Okay - its easy to ask for "better". Its something else to define what better means. In this case, the actual coding once you know what you want to do is probably the easy part.
For example, what does "better" DNG mean ?
On the other hand, I understand your comment about HDR. HDR is currently done with a script or a whole convoluted setup involving menus & timers. On my
G10, the built-in HDR provided by Canon is just two button clicks and the camera just takes the 3 necessary exposure bracketing pix for HDR. It all just works. I wish the CHDK version was as easy.
But then what does "fast scripts to talk to the ARM architecture" mean though ?
For me, the user menu function is a big step towards a more "user friendly" CHDK. Was reading through another photography forum today and was surprised to see people talking about trying CHDK and giving up because the menu were too complicated.
If you are serious about this, then we probably need to move to a new thread. Something like "Thoughts for a speedy and slick CHDK" would be a good topic title if you want to start a new thread for this.
