Looking for a CHDK developer for a custom application using CHDK as a foundation - General Discussion and Assistance - CHDK Forum

Looking for a CHDK developer for a custom application using CHDK as a foundation

  • 106 Replies
  • 17986 Views
Advertisements
Hi,

I'm looking for a CHDK developer to build a custom application using CHDK as a basic foundation.
I would like to remove all unnecessary features (not needed in my app) to simplify the operation.
I'd prefer to work with a developer in the local Southern California region, but I'm not adverse to working with whomever is interested in this project.
This project uses a Canon G11 camera, so the build already exist. I just want to customize the build to meet my particular requirements.

Anyone that is interested, please contact me Gregg Bergman by email at: gsbergman@verizon.net.
Terms and pricing are negotiable. I look forward to doing business with a CHDK developer in the near future.

Thank you,
Gregg

Unusual request.

You want to eliminate certain features but the camera then becomes the basic foundation of a custom application.

Can you explain that more ?

As a matter of interest, which features do you want to remove and which do you want to keep ?


David

Quote

Unusual request.
You want to eliminate certain features but the camera then becomes the basic foundation of a custom application.
Can you explain that more ?
As a matter of interest, which features do you want to remove and which do you want to keep ?


I don't see why it's so unually?
It's a custom application and I don't need all the CHDK funtionality.
All I really need is the ability to run a script. That's it.
I'm just trying to keep it simple. I want CHDK to boot right into a menu asking if you want to run the script or not.
Too much functionality = too much complexity for what I'm trying to perform.

Gregg

ps. Are you interested David?

I promised myself that I would spend time actually taking photos this year rather than doing this sort of work.

Ask again if you ever get really stuck.


David


David,

Can't really imagine this project being all that complicated, stripping down CHDK.

I do appriciate the offer though. I'll let you know if I get stuck.

Thank you,
Gregg

*

Offline fe50

  • ******
  • 3105
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
All I really need is the ability to run a script. That's it.
I'm just trying to keep it simple. I want CHDK to boot right into a menu asking if you want to run the script or not.
Can't really imagine this project being all that complicated
Why not simply use what you/we already have (http://chdk.wikia.com/wiki/CHDK_User_Manual) ?

1) disable not needed CHDK OSD things
    - http://chdk.wikia.com/wiki/CHDK_User_Manual#OSD_Parameters
2) use a script with a little intro like "press X to run the script", autostarted
    this script either run your "custom application" code, or just exit / leaves <Alt> mode
    - http://chdk.wikia.com/wiki/CHDK_User_Manual#Scripting_Parameters
3) use the CHDK user menu to build your custom, simple menu, called directly with the <Alt> key
    - http://chdk.wikia.com/wiki/User_menu
    - http://chdk.wikia.com/wiki/CHDK_User_Manual#User_Menu
3.1) ...maybe using a special (e.g. bigger or smaller) font, or custom colors ? - http://chdk.wikia.com/wiki/CHDK_firmware_usage#Visual_settings_menu
4) coding with the Lua, you can do whatever you want in your script, only the sky is the limit ;)

*

Offline reyalp

  • ******
  • 12106
Why not describe your project here ? I'd say your chances of attracting interested help are much higher. You might even find people with similar interests who would work on it for free. In my experience, most people who say they would pay for customization change their mind very quickly when they find out the cost of a realistic number programmer hours at normal rates.

If you plan something that you would distribute in the end, keep in mind that CHDK is GPL, so you would have to release the source anyway.

I agree with fe50, the only reason you'd need to 'gut' CHDK is if you need more RAM for something. Even if the scripting/setting option fe50 descibes isn't what you want, it's would be trivial to comment out the OSD.keyboard stuff and just have it automatically run your specific thing.
Don't forget what the H stands for.

*

Offline fudgey

  • *****
  • 1705
  • a570is
You might even find I agree with fe50, the only reason you'd need to 'gut' CHDK is if you need more RAM for something. Even if the scripting/setting option fe50 descibes isn't what you want, it's would be trivial to comment out the OSD.keyboard stuff and just have it automatically run your specific thing.

A stripped down CHDK has been requested a number of times in the past. The way I understand it one of the major things is to make it virtually impossible to accidentally enter ALT mode while still retaining functionality because ALT mode behavior confuses beginners but they do want CHDK OSD and to occasionally run a script or give the camera to someone else for a while.

Two solutions that I think would be helpful to some (these have been proposed before, haven't they?):

1) Add a configuration option (and make it available in CHDK menu with easy access) to change the 'enter alt mode' shortcut (but not exit alt mode shortcut, for sanity) to a more complex combination or series of button presses, something that doesn't happen accidentally.

2) Add a config option which when enabled would cause the ALT key to be disabled unless the user presses a certain key while CHDK splash screen is being shown (add instruction for this key press to the splash screen). In this mode maybe CHDK should automatically add exit_alt to the end of the active script in case the script writer didn't and script autorun is enabled.

As for what can be done by mere config+script customization of current CHDK builds... on top of what's been already said, would an autorun script loop that calls exit_alt in an eternal loop be sufficiently equal to a disabled ALT key as long as the script isn't interrupted with a full shutter press during its other intended behavior (such as the initial "do you want to run the script" prompt, which I believe should cunningly take half press as an answer among other keypresses in order to avoid a full press exit as well as possible)?


I appriciate everyones responses on this post.

It really is much simpler than it appears.
Let me explain.

I am trying to develop a medical use for camera running a motion detection script. I do not want nor require any other CHDK functionallity. I do not want the camera users to have to dig through menu's to configure the application. What I'm looking for is a camera that boots to a simple menu asking if the user would like to run the motion detection script. If the user answers no, the user is brought to just the normal camera functionality. If the user answers yes to the question of running the motion detection script, the script is started immediately upon the user depressing the shutter button.

I dont want the end user to have to fiddle with the ALT mode, menu's or anything that might result in missing the running of the motion detection script.

The only configurable options I like is the option to adjust the motion detection sensitivity.

I think it's pretty cut and dry.

I'm not trying to hide anything, I know the code is GPL.

I'm just looking for a very simplified version of CHDK without all the bells and whistles, that does one thing and one thing only, run one script. If I could get the script hard coded that would even be better yet.

No mystery, no deception, just absolute simplicity, I want someone (the end user) that is not CHDK savvy to run motion detection scripts without any fuss.

If anyone has any other suggestions, please feel free to comment.

Thank you,
Gregg

You can of course autorun the motion-detection script and automatically exit ALT mode when it is finished.

With the current CHDK you would only need the option to enter the script parameters.

With SDM the script parameters can simply be in a text file so you would not need to enter ALT mode.
You would just edit the value in the text file.

As far as I know, this will also work with CHDK.
The SDM property-files allow you to include four lines of description.

As a matter of interest, do you want to detect motion or no-motion  ?


David

 

Related Topics