So some new updates:
The porting is done, and i don't find big bugs anymore.
Big changes since my last update:
The actual branches on my git repo:
https://github.com/bluehazzard/codeblocks_sf- sq_debugger: You need this branch if you want test the c::b squirrel debugger. I will merge this in "cb_push_candidate" as soon as possible
- cb_push_candidate: On this branch i try to integrate my code with the trunk of c::b so that i can make a big patch and post it.
- wx30_push_candidate: On this branch i try to integrate the whole wx30 stuff. This will also be merged (or rebased) on "cb_push_candidate"
I have currently stopped implementing new stuff ( i have tons of ideas, but they have to wait), and started to review code, add documentation and find bugs. As I mentioned earlier in this thread i don't like the current include structure. I try to minimize the dependencies to header files and implement a structure for PHC. On this i could need a lot help, because i have no big experience with managing include structures.
A other work in process is the testing suite. There are still missing a lot tests, and the xrc test stuff needs a lot cleanup.
So where does i need really help from outside:
My todo for the next few days (or weeks, my time is currently limited)
- Merge all branches to "cb_push_candidate" and try a rebase to trunk
- Fix the xrc test (currently they don't work and i have to look into it why. Meanwhile you can test the XRC stuff with this plugin: https://github.com/bluehazzard/cbSelectiveCompiling)
- Fix a bug where are showed multiple copies of one error message in the scripting error dialog (this is only a cosmetic bug)
- Complete the test suite (here i can also need some help from "script kiddies" )
After this changes i think the port is ready and all features for a good scripting base are implemented. If you want my changes we have then to clear how we bring them to trunk (patch or branch or whatever).
I still need testers and bug reports, because now i'm "blind" with my own work flow, i don't find glitches or non intuitive things, so someone from the outside needs to point them to me.
After the merging to trunk i have this todos:
- Implement the install.xml handling also for binary plugins*) (this is a secondary goal)
- Add scripting to the debugger (specially events for BREAK and function to add watches and watch values from the script, so that you can implement a recording of changes after a breakpoint, or automate debugging over a script)
- maybe add wxPanels to the script binding
- Add more wxControls to the binding (ex. wxGrid)
*) I have added the possibility to run script code before and after a installation / deinstallation of a scripting plugin. This code is specified in the install.xml file (like the mainfest.xml file) You can see a example in the cbSelectiveCompiling plugin installation process (a custom dialog will ask you if you really want to install this plugin).
If you test things, and find bugs, please report them on github or here.
For fast questions i try to stay in the c::b chat and answer them there.
greetings