CHDK 1.2 release planning - page 2 - General Discussion and Assistance - CHDK Forum

CHDK 1.2 release planning

  • 23 Replies
  • 7122 Views
*

Offline dvip

  • ****
  • 451
Re: CHDK 1.2 release planning
« Reply #10 on: 06 / July / 2013, 01:02:28 »
Advertisements
ok, got to use the "Set" key and go from there. Thanks!

*

Offline msl

  • *****
  • 1263
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK 1.2 release planning
« Reply #11 on: 07 / July / 2013, 11:08:23 »
offtopic:

Perhaps it is better we start a new topic about ISO issues. This thread should be more a overview for 1.2 release.

msl


CHDK-DE:  CHDK-DE links

*

Offline reyalp

  • ******
  • 12215
Re: CHDK 1.2 release planning
« Reply #12 on: 07 / July / 2013, 14:20:10 »
offtopic:

Perhaps it is better we start a new topic about ISO issues. This thread should be more a overview for 1.2 release.

msl

Done, new topic: http://chdk.setepontos.com/index.php?topic=10341.0

The decision of whether to do this for 1.2 will depend on what we find, but the detailed discussion is making the rest of this thread hard to follow.
Don't forget what the H stands for.

Re: CHDK 1.2 release planning
« Reply #13 on: 16 / July / 2013, 18:52:02 »
While I remember,  and as discussed a few times in the past,  when you create the new 1.3.0 trunk how about running the whole thing through a code beautifier? 

Pick a bracketing and white space vs tabs convention.

Also, some files (like autoiso.c) seem to have trailing carriage return ( ^M) so it wouldn't be bad to nuke those too.
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline reyalp

  • ******
  • 12215
Re: CHDK 1.2 release planning
« Reply #14 on: 16 / July / 2013, 21:28:43 »
While I remember,  and as discussed a few times in the past,  when you create the new 1.3.0 trunk how about running the whole thing through a code beautifier? 
The time to do it would be before creating the branch, otherwise porting fixes from one branch to the other will be painful. Since the change is theoretically whitespace only, this should be OK.

IIRC we discussed this last time, I  looked at a few beautifiers and didn't find one that would immediately do what I wanted without some additional work, so put it off due to lack of time. I am still open to doing this.
Quote
Also, some files (like autoiso.c) seem to have trailing carriage return ( ^M) so it wouldn't be bad to nuke those too.
All .c files should have eol-style set to "native" for automatic line ending conversion. This one slipped through, should be fixed now.

edit:
Previous code formatting discussion http://chdk.setepontos.com/index.php?topic=2145.msg36658#msg36658

From the 1.1. release thread http://chdk.setepontos.com/index.php?topic=8309.0 the reason I didn't do it then was mainly that there were a couple of developer branches open, so it would have messed up merging. I remember I looked at a couple of different tools, but I don't see any posts about them. I'll look around and see if I have any notes.

edit: Some tools I looked at were
Astyle http://astyle.sourceforge.net/
Uncrusitfy http://uncrustify.sourceforge.net/
Universal indent gui http://universalindent.sourceforge.net/
« Last Edit: 16 / July / 2013, 22:25:01 by reyalp »
Don't forget what the H stands for.

Re: CHDK 1.2 release planning
« Reply #15 on: 19 / July / 2013, 22:17:38 »
First draft done :  http://chdk.wikia.com/wiki/CHDK_1.2.0_User_Manual

Has holes big enough to drive a truck through but it's at least as good as the old one IMHO.

Biggest ommision is any mention of chdkptp - might just add a small section at the end pointing to the relevent wiki & forum pages for now.
« Last Edit: 19 / July / 2013, 22:25:37 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 12215
Re: CHDK 1.2 release planning
« Reply #16 on: 19 / July / 2013, 22:38:13 »
First draft done :  http://chdk.wikia.com/wiki/CHDK_1.2.0_User_Manual

Has holes big enough to drive a truck through but it's at least as good as the old one IMHO.
Thank you for all your hard work on this :)

As usual, I haven't had a whole lot of time for CHDK stuff during the week. I hope to get the remaining loose ends for 1.2 wrapped up this weekend.

Don't forget what the H stands for.

*

Offline reyalp

  • ******
  • 12215
Re: CHDK 1.2 release planning
« Reply #17 on: 27 / July / 2013, 20:39:46 »
Status update:

1.2 is now officially in "release candidate" status. Unless there are major problems, it will be released in the next few days.

Thinks that need to happen:
A snapshot of the last 1.1 autobuild should be saved somewhere.
The autobuild needs to be switched.

The items in the original post are disposed as follows:

* Clarify / resolve custom auto ISO issues http://chdk.setepontos.com/index.php?topic=8467.msg102489#msg102489 - Mostly done, users can enter approximately "real" ISO in the UI. Further improvements will wait until 1.3
* Raw stuff in  http://chdk.setepontos.com/index.php?topic=10242.0 (some of this is already taken care of by remotecap merge) - everything done except resolving the CHDK raw vs native raw stuff. This isn't urgent.
* fix a470 sensor size mismatch changeset 2929
* Fix the PTP alt mode confusion http://chdk.wikia.com/wiki/Lua/PTP_Scripting#General_information_about_executing_Lua_code_over_PTP changesets 2944-2945
* Allow PTP to cleanly kill running script (maybe), I think it can be done in straightforward way, will punt if it can't. deferred, not urgent.
* Make PTP not use 50% of available RAM for buffer if there's lots available. deferred http://chdk.setepontos.com/index.php?topic=4338.msg103076#msg103076
* Make PTP_CHDK_CallFunction use call_func_ptr changeset 2931
* Make convert_dng_to_chdk_raw smarter about it's buffer size deferred, not urgent.
* unify set_record and switch_mode_usb http://chdk.setepontos.com/index.php?topic=9582.msg98447#msg98447 (from msl below)   changeset 2971

Additionally, waterwingz suggested adding code to check if essential modules are present and showing some kind of notice if they aren't. I think this is a good idea, but I'm not going to hold up the release to do it. If it's easy / low risk, we can backport it later.

I decided to skip the whole code reformatting thing again.
Don't forget what the H stands for.


*

Offline fe50

  • ******
  • 3107
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: CHDK 1.2 release planning
« Reply #18 on: 28 / July / 2013, 04:22:20 »
Thinks that need to happen:
A snapshot of the last 1.1 autobuild should be saved somewhere.
done - 2976, http://chdk.wikia.com/wiki/Downloads#Conserved_Versions  :)

*

Offline msl

  • *****
  • 1263
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: CHDK 1.2 release planning
« Reply #19 on: 28 / July / 2013, 07:06:05 »
Thinks that need to happen:
A snapshot of the last 1.1 autobuild should be saved somewhere.

Also done for CHDK-DE: snapshots CHDK-DE
CHDK-DE:  CHDK-DE links

 

Related Topics