1.4 development planning thread

reyalp

13948

1.4 development planning thread

« on: 19 / December / 2014, 01:27:00 »

Advertisements

General stuff
* I'd like to try for a faster release than 1.3. So once we've got some complete working features in place, we should start thinking about a release.
* Partially due to the long release cycle, the 1.3 branch became a sort of de-facto stable branch. For 1.4, I'd like to stick to the idea that we can make incompatible changes from version to version in the trunk. We should still try to keep it mostly usable, but users should expect that scripts could break from version to version or configs might need to be reset. That means if we suggest someone use the trunk because it contains a new whiz-bang feature, it should come with a caveat.

A few things off the top of my head for 1.4. Feel free to post your own below
* srsa's Long filename support http://chdk.setepontos.com/index.php?topic=10833.0
* Philmoz palette and touch UI reworks
* srsa' digic 6 support and ports
* Philmoz script loading and script header improvements http://chdk.setepontos.com/index.php?topic=12121.0
* waterwingz gps cleanup http://chdk.setepontos.com/index.php?topic=7791.20

Logged

Don't forget what the H stands for.

philmoz

3445

Re: 1.4 development planning thread

« Reply #1 on: 19 / December / 2014, 04:53:25 »

Palette, touch UI, shot histogram module, script parameter system, and file browser rewrite are in 1.4 - lets see how much I've broken

I've posted an updated patch for srsa' LFN code - I think this is ready for SVN.

The palette changes may require some updates of waterwingz GPS cleanup (sorry waterwingz) - haven't had time to check this yet.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

msl

1280
A720 IS, SX220 HS 1.01a

Re: 1.4 development planning thread

« Reply #2 on: 19 / December / 2014, 06:30:47 »

Quote from: philmoz on 19 / December / 2014, 04:53:25

... shot histogram module ...

Is there any description for the new script command 'shot_histo_write_to_file()'?

msl

Logged

CHDK-DE: CHDK-DE links

philmoz

3445

Re: 1.4 development planning thread

« Reply #3 on: 19 / December / 2014, 06:43:02 »

Quote from: msl on 19 / December / 2014, 06:30:47

Quote from: philmoz on 19 / December / 2014, 04:53:25
... shot histogram module ...
Is there any description for the new script command 'shot_histo_write_to_file()'?

msl

It just writes the last shot histogram buffer to a file (HST_nnnn.DAT) - nnnn comes from the last image file.

It's the raw histogram count buffer - so not really much use other than debugging the code.

If I do manage to revive any of lapsers enhanced shot histogram code then this will all probably change quite a lot.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

waterwingz

12134

Re: 1.4 development planning thread

« Reply #4 on: 19 / December / 2014, 15:00:36 »

Quote from: philmoz on 19 / December / 2014, 04:53:25

The palette changes may require some updates of waterwingz GPS cleanup (sorry waterwingz) - haven't had time to check this yet.

Yes - it's now going to need "some updates". And I haven't figured out how to get the new svn website to show me what was in commit 3812 so that doesn't help.

I've been working on the simulator part of the gps code so I'll just update from there and try to get something that will patch cleanly again.

Logged

Ported : A1200 SD940 G10 Powershot N G16

philmoz

3445

Re: 1.4 development planning thread

« Reply #5 on: 19 / December / 2014, 15:13:05 »

Quote from: waterwingz on 19 / December / 2014, 15:00:36

Quote from: philmoz on 19 / December / 2014, 04:53:25
The palette changes may require some updates of waterwingz GPS cleanup (sorry waterwingz) - haven't had time to check this yet.
Yes - it's now going to need "some updates". And I haven't figured out how to get the new svn website to show me what was in commit 3812 so that doesn't help.

I've been working on the simulator part of the gps code so I'll just update from there and try to get something that will patch cleanly again.

Yeah, the assembla tools are a bit of a pain (clicking the revision link says 'too many files or patch to large').

You might be able to use this page https://www.assembla.com/code/chdk/subversion/compare/3812...3811#files
Click the 'files affected' tab, then you can click 'view diff' against each file to see the changes.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

waterwingz

12134

Re: 1.4 development planning thread

« Reply #6 on: 19 / December / 2014, 15:22:15 »

Quote from: philmoz on 19 / December / 2014, 15:13:05

You might be able to use this page https://www.assembla.com/code/chdk/subversion/compare/3812...3811#files
Click the 'files affected' tab, then you can click 'view diff' against each file to see the changes.

Found an easier way : svn diff -c 3812 core/gps.c

One look at that and I decided to go to lunch.

I'll probably revert the change locally, add my patch, and then manually edit in the equivalent changes.

Logged

Ported : A1200 SD940 G10 Powershot N G16

philmoz

3445

Re: 1.4 development planning thread

« Reply #7 on: 19 / December / 2014, 15:39:25 »

Quote from: waterwingz on 19 / December / 2014, 15:22:15

Quote from: philmoz on 19 / December / 2014, 15:13:05
You might be able to use this page https://www.assembla.com/code/chdk/subversion/compare/3812...3811#files
Click the 'files affected' tab, then you can click 'view diff' against each file to see the changes.
Found an easier way : svn diff -c 3812 core/gps.c

One look at that and I decided to go to lunch.

I'll probably revert the change locally, add my patch, and then manually edit in the equivalent changes.

It probably looks worse than it is. The changes should only be to color related code; which was messy in the original GPS code as it checked the rec/play state all the time.

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)

waterwingz

12134

Re: 1.4 development planning thread

« Reply #8 on: 19 / December / 2014, 15:46:25 »

Quote from: philmoz on 19 / December / 2014, 15:39:25

It probably looks worse than it is. The changes should only be to color related code; which was messy in the original GPS code as it checked the rec/play state all the time.

Totally breaks my patch file if I try and apply it after your changes. Not fixable.

So I just reverted gps.c, applied my patch, and am almost done hand editing your changes back in.

No worries.

Logged

Ported : A1200 SD940 G10 Powershot N G16

philmoz

3445

Re: 1.4 development planning thread

« Reply #9 on: 19 / December / 2014, 19:30:59 »

In 1.4, do we need to keep the code that loads the old 1.2 CHDK config file if there is no 1.3 (or later) config file on the SD card?

Phil.

Logged

CHDK ports:
sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
g12 (1.00c, 1.00e, 1.00f & 1.00g)
sx130is (1.01d & 1.01f)
ixus310hs (1.00a & 1.01a)
sx40hs (1.00d, 1.00g & 1.00i)
g1x (1.00e, 1.00f & 1.00g)
g5x (1.00c, 1.01a, 1.01b)
g7x2 (1.01a, 1.01b, 1.10b)