Witold put some great effort to make SPE catch up with the latest Blender 2.45 It is now available for testing in the subversion repository:
Now debugging (with breakpoints, changing variables on the run, …) should be more easy as well. Don’t thank me (I just tested and accepted his patches), but give a big thanks to Witold!! All credits go to him! I hope Witold agrees to answer here to further questions. He also will prepare a tutorial on how to develop scripts with SPE and how to debug scripts in Blender. If you want to help him, please let yourself be heard. This might give the ultimate tool to develop more serious python scripts for blender.
SPE 0.8.4.b runs on Windows, Linux & Mac. I use ubuntu gutsy as the main development platform for SPE.
Stani
From his email conversation:
I have started to use your editor, because it is the only one will be useful to write the scripts in Blender. I have found, that the original version 0.8.3.c has a lot of flaws, when it comes to cooperation with Blender 2.43.
Fortunately, it was not too difficult to fix these things, and I just have appended the description of these adjustments to this e-mail. Maybe you will find them useful for another version?
In general, I have found that most of the SPE 0…8.3.c commands, concerned with Blender, although obsolete, can be transformed into alternatives that are available in Blender 2.4: automatic adding scripts to Blender’s menus, loading into text editor, etc.
I have also used the Winpdb to debug scripts inside Blender, but, in fact, in this case this product is not used from within SPE, but as another product.
Usual pattern of work on Blender scripts was:
- load SPE from Blender (new shortcut appends it automatically to Blender Scripts–>System menu).
- create a new script in SPE;
- optionally: add it to the Blender menu, using SPE command “Reference in Blender”
- edit the file in SPE,
- to test: load updated file version into Blender’s Text Editor, using SPE command “Load in blender”
- close SPE
- set tracking by WinPdb
- run the script from Blender’s Text Editor - this enter the debuging in Win Pdb
- when the bug was found - detach Winpdb and call again SPE, if the changes are more serious (small adjustments can be added directly in the Blender’s text editor)
best regards
and thank you for the SPE
Witold Jaworski