User forums > General (but related to Code::Blocks)
C::B usage/download stats?
Wyrm:
--- Quote from: macr0t0r on May 24, 2013, 06:51:38 pm ---Seeing that the scripting engine has been revamped quite a bit, I'm working on improving a few of our plugins.
Off topic: the scripting documentation is....sparse (to be generous). I generally had to look at the source code to understand the nuances. However, like all open-source software, I know that the obvious answer is for me to update it if I don't like it. Ugh...I'll have to carve some free-time out to update your scripting wiki.
--- End quote ---
By scripting documentation, are you referring to the script language used in the "pre/post build steps" tab?
In the past I tried using post-build steps for my own regression system and I couldn't make it work exactly like I wanted to. I wanted to copy the newly built libraries and headers into a separate deployment directory and have test cases compile against that deployed installation. The deployment needs to be conditional on the target and successful build, so it shouldn't occur when my target is "clean". After a couple of hours I gave up on the post-build tab and wrote my own Perl script to do it from the command line instead.
If you can update the wiki or the documentation for this scripting it would be much appreciated.
macr0t0r:
Gah! Apparently I need to manually subscribe to threads that I participate in. Sorry for the late response.
Currently, I don't use scripting in the pre/post steps because I'm currently using legacy code with their own makefiles. I use the scripting to create my own plugins. Unfortunately, the documentation is a bit light there, so I had quite a bit of trial and error. Eventually I'll need to spend some quality time on the wiki and put in the missing info. The biggest omission is that there is almost no information on how to make your contextual menus play nice with the FileTree items. I managed to figure out how to make my context menus change when I right-click on a file, folder, project, workspace, etc.
Squirrel, though. I'm a little curious why you went with Squirrel instead of Lua. It's so much easier to find documentation and examples for Lua scripting. Ah, no biggie. They're similar enough.
- Jim
MortenMacFly:
--- Quote from: macr0t0r on June 13, 2013, 02:13:17 am ---Squirrel, though. I'm a little curious why you went with Squirrel instead of Lua. It's so much easier to find documentation and examples for Lua scripting. Ah, no biggie. They're similar enough.
--- End quote ---
Because at the time we decided to use scripting, Lua was way less sophisticated that Squirrel was (for c++, at least). This might have changed meanwhile... But it would be a major re-factoring to change the scripting layer. And as long as the current is doing the job just fine there is no need for such change.
macr0t0r:
No worries with Squirrel. As scripts go, I've already had to learn and use Csh, Bash, Awk, Python, Perl, Lua...what's one more? In any case, I like how Squirrel supports function pointers so easily, so I'm okay with it. The fact that Code::Blocks even has a scripting interface is enough to sell me!
- Jim
LETARTARE:
hello to all,
@macr0t0r
The "Scripting commands" section has been updated to 12.11.
What would you find in the wiki "Scripting Code::Blocks" ?
cordially.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version