Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Support for Interpreted Languages?
Game_Ender:
I think it would make more sense if he got his own project on Berlios or Sourceforge.
dmoore:
--- Quote from: keenblade on November 19, 2006, 10:34:47 pm ---As stated before
"Once you choose "Run..." from the interpreters menu an OpenFile dialog appears."
I think if a file is already open within ide, then this file must be processed without asking. Or this type of behaviour can be specified from the settings page.
--- End quote ---
Personally, I like that it works this way as I don't necessarily want to have to open a file before I run it or run the currently active file. What I wanted to do was respond to right clicks in the editors tabs and/or editor pane with menu options for the appropriate actions. At the time, I couldn't tell whether the sdk allowed this behavior, because i was very unfamiliar with the C::B code. I'll have another look and make this change if possible. Will this be acceptable? My other plan is to put the last 10 executed commands directly in the interpreters menu as another shortcut way to execute commonly run scripts. These will be stored persistently.
In the mean time, if your source file is added to a project, you can right click the file in the project tree pane and you will be offered the appropriate actions.
So my current todo list for the interpreted languages plugin:
1. context action clicks in the editor pane/tabs of relevant sources (PARTLY COMPLETE)
2. recent command list on the interpreters menu
3. rerouting console input and output to a dockable window in codeblocks (there will be a few problems implementing this but its not a big deal to get very basic functionality)
4. add additional variables for the action commands (such as $activefile, $allopenfiles etc). also support iterative commands and macromanager variables
Let me know of any other bugs, undesired behaviors or things to add to the list.
dmoore:
--- Quote from: Game_Ender on November 20, 2006, 02:52:43 am ---I think it would make more sense if he got his own project on Berlios or Sourceforge.
--- End quote ---
I need to clean up the code before it goes into any repository, but especially the C::B one (quite a bit of experimental stuff in there)
BTW: How long will it take to get my debug patch (#1625) approved?
Game_Ender:
Why don't you take python's moto: "Release early release often", nothing wrong with placing alpha quality code in a repository. When the code is in heavy state of flux you will be able to track changes better when using source control.
dmoore:
--- Quote from: Game_Ender on November 20, 2006, 05:47:26 am ---Why don't you take python's moto: "Release early release often", nothing wrong with placing alpha quality code in a repository. When the code is in heavy state of flux you will be able to track changes better when using source control.
--- End quote ---
:)
until 2 days ago I had source control on my home server. hard drive broke and I'm waiting on a new one. Perhaps that is an object lesson in the value of a professionally managed external repository. I'll look into setting up a berlios project.
-----------------------------------
anyway, here is the fix to number one on my list. I would probably have completed number 2 as well but Morten's fix to the project file didn't work with my setup because i don't have the project in the contrib folder. I spent too much time messing around with the settings to try to make the project neutral with respect to folder location, but the debugger refused to cooperate, so i had to revert to my original project file. I'll fix this eventually, but I've removed the project file altogether from this version (use your own or Morten's/mine from the previous posts)
to explain the addition: you can now right click in the editor pane of the source file giving you the option to run actions on the script (file is not saved automatically, but i can change this). unfortunately you can't right click on the editor tabs (doesn't generate messages context menu) or the opened files list (does generate messages, but I wasn't sure how to determine the file that was clicked)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version