CHDK UI version 2.0 ? - page 26 - General Discussion and Assistance - CHDK Forum

CHDK UI version 2.0 ?

  • 542 Replies
  • 98146 Views
Re: CHDK UI version 2.0 ?
« Reply #250 on: 28 / July / 2012, 20:09:28 »
Advertisements
Hmm. I will add additional checks before.
Because this is significant issue. If user would like to try CHDK on his camera and because of anything there are no help file on first start, he will got hanged camera. And will say "WTF. CHDK Doesn't work!"
« Last Edit: 28 / July / 2012, 20:28:00 by tsvstar »

*

Offline Pier

  • ***
  • 128
Re: CHDK UI version 2.0 ?
« Reply #251 on: 29 / July / 2012, 01:05:46 »
I've tested tsvstar uitest - rev.2007  on my SX130IS.
All is OK.No issue after exit from help.
After that I've deleted Help dir and when try to using Show HELP in Misscelanous, camera hang, and after switching OFF the Cam, You can't switch it On.You need to reset with open the battery door.
The button for Alt on SX130IS is Face detect.
Will continue to test it.I like this short help when Alt is ON.
« Last Edit: 29 / July / 2012, 04:14:11 by Pier »

*

Offline zeno

  • *****
  • 889
Re: CHDK UI version 2.0 ?
« Reply #252 on: 29 / July / 2012, 07:57:38 »
Just a quick reminder that my CFG Editor runs under Windows, OSX and Unix (it's written in Java) and lets you edit a CFG file - the OSD entries are shown visually. You can also save the values to a text file (but not load them back currently).

See http://www.zenoshrdlu.com/kapstuff/zcfgedit.html - it may be a bit out of date, I've not updated it since February.

I'm currently working on a simple OSD Editor for SDM which makes a better job of showing the OSD entries - I will probably rework it for CHDK.
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

*

Offline msl

  • *****
  • 1276
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK UI version 2.0 ?
« Reply #253 on: 29 / July / 2012, 10:16:34 »
The cfg editor is a good thing. But I think an extra needed program is not the right way.

An editable configuration file like an ini file which can be changed with a  simple text editor is the goal. So we can generate different configurations for special tasks.

msl
CHDK-DE:  CHDK-DE links


*

Offline reyalp

  • ******
  • 13457
Re: CHDK UI version 2.0 ?
« Reply #254 on: 29 / July / 2012, 15:11:42 »
An editable configuration file like an ini file which can be changed with a  simple text editor is the goal. So we can generate different configurations for special tasks.
I agree, text based CFG would be good. Issues that need to be considered
- error handling, if someone messes up, the chdk still needs to do something reasonable
- memory efficiency, loading speed
These things are solvable, but some effort to get right IMO.

A text based cfg is basically simple script, so it might be tempting to do it in the existing script system. The current magic number based set_config_value wouldn't really help, but if we re-write the cfg system to use named values, then we would want that directly accessible from script anyway. In that case, the cfg file could just be a special autoexec script. Of course, you'd either have to make this run in a stripped down environment, or deal with people putting in non-cfg code (you could just say it's their own darn fault though... in camera cfg saving would presumably only save known config values)

regarding camera specific default cfgs... I'm not really to fond having this in code. If you define the position of individual widgets for each camera in code, then if the size of the widget changes, you need to go through and adjust every camera. It's also likely these defines would end up being used for non-cfg stuff in code, which would cause headaches later. If we do define the defaults in code, I'd suggest we have something like cfg_defaults.h and not make it available to anything but the cfg code.
Don't forget what the H stands for.

Re: CHDK UI version 2.0 ?
« Reply #255 on: 29 / July / 2012, 15:32:11 »
The changelog.txt from the root directory still points me to https://chdk.kernreaktor.org/chdk-changelog.txt , but that link is dead! Can someone here please correct this? Thank you!
Ixus 115 HS / firmw.1.01b - using and testing the new beta - CHDK-beginner - Europe

*

Offline zeno

  • *****
  • 889
Re: CHDK UI version 2.0 ?
« Reply #256 on: 29 / July / 2012, 18:01:49 »
If you look at the display of a CFG file by my editor you'll see that there is a real problem trying to treat a CFG file as a 'simple script' that can be changed by a simple text editor. First, quite a few of the items are enums - internally the camera holds them as integers but displays them to the user as values (e.g. the "Histogram Layout' item has 8 numeric values (0-7) corresponding to "RGB", "Y", RGB Y", "R G B", "RGB All", "Y All", "Blend" and "Y". If the simple text file just uses numeric values the user will have little idea what the numbers mean. Other items represent a pair of colours (foreground and background) whose values are complicated by the fact that different cameras use different palettes.

So I think a specialised editor that translates the numeric values into meaningful ones (like my editor) and thus helps the user know what they are doing and avoid making mistakes is a better way to go if the editing is going to be done outside the camera.
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

Re: CHDK UI version 2.0 ?
« Reply #257 on: 29 / July / 2012, 18:24:41 »
I agree, make it simple for the majority, who are not interested in many (most?) features anyway.

The whole 'hack' is far too complicated for many potential users   ....  in my opinion.



Re: CHDK UI version 2.0 ?
« Reply #258 on: 29 / July / 2012, 18:33:51 »
The whole 'hack' is far too complicated for many potential users   ....  in my opinion.
david :  you posted earlier that you have some thoughts on how to make a "user friendly" version.  Did you get any farther in your thinking ?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline msl

  • *****
  • 1276
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK UI version 2.0 ?
« Reply #259 on: 29 / July / 2012, 19:05:58 »
So I think a specialised editor that translates the numeric values into meaningful ones (like my editor) and thus helps the user know what they are doing and avoid making mistakes is a better way to go if the editing is going to be done outside the camera.

perhaps, but every new or updated feature which has a dependency of the configuration, needs also a program update.

With the script commands set/get_config_value() I can create a simple text file, which is editable.

msl
CHDK-DE:  CHDK-DE links

 

Related Topics