Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Am finishing an STM32 wizard and need some tips...
Aerodesic:
Patch problem resoved. Using tips from http://stackoverflow.com/questions/159853/subversion-diff-including-new-files:
svn diff --force --diff-cmd /usr/bin/diff -x -au
Will be uploading patches this afternoon after my lunch break.
-Gary
Aerodesic:
README file for what has changed (a brief outline) is at
https://filebox.aerodesic.net/owncloud/public.php?service=files&t=6fe7a980354d5d66e7501d1da3b916e4
The patches (made against current SVN earlier this morning:)
https://filebox.aerodesic.net/owncloud/public.php?service=files&t=96bc9bb3e7efc52617644bd4f598c7d6
If you have problems accessing these, let me know and I'll just post the raw stuff here.
-Gary
oBFusCATed:
Why don't you attach the patch here or in the tickets section in our project page on sf.net?
What is the file format of the patch?
I can't read the .diff file it some binary, but it is not a zip, nor tar, so what is it?
oBFusCATed:
--- Quote from: Aerodeisc on April 18, 2016, 08:13:09 pm ---As soon as that part is resolved, I'll post the diffs. They are rather largish (13k + lines) with mostly in the wizard and support 'include' scripts - I broke the script into four pieces because maintiaining one LARGE script seems tedious - four smaller 'modules' made more sense and I might break it down further. As I stated, this is a complex script and includes (among other things) serialization of configuration to the user's .config/codeblocks/ area to save state so I don't have to grok through the STM32_CUBE modules over an over. (The serialization is a simple 'write config' / 'read config' that allows storing arbitrary data into an isolated 'jail' in the codeblocks configuration folder - not the project folder. I wrote a Squirrel data-structure dumper so I can serial Squirrel objects and then reload them later. Makes the loading configuration about 1000x faster than re-reading the files in the STM32 CUBE folders.
--- End quote ---
BTW I'm interested in patches to the scripting bindings of C::B only.
If the script is as complex as you describe it, I'll prefer if it stays as a separate project and not part of C::B.
The reason is that there will be very few people using it and none of the core developers will maintain it properly.
As a separate project it can have faster iterations and better support.
I'm eager to help with improvements to C::B to facilitate easier integration, installation and setup.
Hopefully this sounds reasonable to you.
p.s. I'm maintaining the arduino wizards in a similar fashion (no matter that a different version has been added to the main install). https://github.com/obfuscated/cb_arduino_template
p.p.s. You can use my git repo to post patches against. It is relatively up-to-date.
Aerodesic:
--- Quote from: oBFusCATed on April 19, 2016, 12:10:31 am ---erested in patches to the scripting bindings of C::B only.
If the script is as complex as you describe it, I'll prefer if it stays as a separate project and not part of C::B.
The reason is that there will be very few people using it and none of the core developers will maintain it properly.
As a separate project it can have faster iterations and better support.
I'm eager to help with improvements to C::B to facilitate easier integration, installation and setup.
Hopefully this sounds reasonable to you.
p.s. I'm maintaining the arduino wizards in a similar fashion (no matter that a different version has been added to the main install). https://github.com/obfuscated/cb_arduino_template
p.p.s. You can use my git repo to post patches against. It is relatively up-to-date.
--- End quote ---
Sounds completely reasonable. The diff is producted with the command I sent in an earlier post - it DOES contain some binary since it used the 'real' diff to allow 'patching' in the two .png files. Without those files, the base diffs should be simpler and no binary. I will post those to the sf as soon as I make sure I'm going it right... Been a while since I've submitted anything there. I can post back here once that's complete.
Roger the patching against the git repo. I've been messing with this script for a few months, and not ONCE have I had a patch collision... Not much going on in the areas I was touching.
Gary
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version