Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Support for Interpreted Languages?

<< < (10/12) > >>

MortenMacFly:

--- Quote from: dmoore on June 11, 2007, 04:45:35 am ---I've just commited Revision 15 of the Interpreted Langs plugins:

--- End quote ---
Hmmmm... whereas all previous versions work properly I have an issue with this one: First I had to point to the Python include/lib folder the first time for compilation which wasn't considered in the project files. It compiled/linked fine but now whenever I start C::B I receive an error, that the python plugin could not be loaded. What am I missing? Do I need to put e.g. the Python DLL somewhere?! What's behind the dependency on Python?!
With regards, Morten.

dmoore:
sorry about the current state of that plugin -- you should just remove py_embedder.cpp, py_embedder.h, libpython and any python related vars from the project as that is purely experimental stuff. I'm eventually going to implement symbol browsing and code completion for python using an embedded python interpreter. I'll remove the files from the default build target in a future commit (soon)

anyway, as soon as I'm done updating the InterpretedLangs plugin (currently working on a file explorer tab in the management pane -- Check out the latest SVN, then I'll do some more work on the menus and intepreter actions) I'm going to tie the Python plugin more closely to the InterpretedLangs plugin. so consider the current python plugin as being in a deprecated state until that time...

MortenMacFly:

--- Quote from: dmoore on June 13, 2007, 10:02:15 pm ---sorry about the current state of that plugin -- you should just remove py_embedder.cpp, py_embedder.h, libpython and any python related vars from the project [...]

--- End quote ---
Alright... will do that... thanks! :P Sounds interesting what you still have in mind! 8)
BTW: You can use a branch for this experimental stuff thus trunk would always be a "usable" version. SVN can do so much more that "just trunk". ;-)
With regards, Morten.

dmoore:

--- Quote from: MortenMacFly on June 13, 2007, 10:24:08 pm ---BTW: You can use a branch for this experimental stuff thus trunk would always be a "usable" version. SVN can do so much more that "just trunk". ;-)
With regards, Morten.

--- End quote ---

you've correctly surmised that I'm something of a vcs neophyte. :)
for now, I think having a second "experimental" build target will work just as well, because then I won't have to keep updating the branch for changes that i make to the trunk. There are lots of changes that I plan to make to the core python plugin that will remain compatible with the experimental bits.

dmoore:
latest build (rev 31), which includes a file explorer here:

http://developer.berlios.de/project/showfiles.php?group_id=7745&release_id=12952

Notes:
This self-extracting executable contains Code::Blocks, the CBIL plugins compiled for win32 using wxWidgets
 2.8.4 (dll included). Extract the file to your preferred directory and run codeblocks.exe

Disable plugins by starting codeblocks.exe and selecting Plugins->Management

IntepretedLangs and Python Plugin settings are available from Settings->Environment

Main features:
InterpetedLangs:
* Customizable Interpeter Actions that can be issued from the interpreters menu or with context clicks in Project Tree/File Explorer/Editor Pane. Customized actions support global/custom variable substitions, working directory specification, command line args, dockable vs console running mode
* File Explorer - provides a view of the file system (it's a tab in the management window).
* Launch multiple process with output piped to a tabbed "shells window". Run an interpreter action using option "W" in the action string (to run an interpreter in the cbconsole runnner use "C" in the action string). for example a python run action string to run a script in a dockable winodw tab might look like this: "Run;$interpeter -u $file;W;;" (the last to spaces are for setting the working directory and (not implemented) environment variable set)


Python Plugin (currently in a functional, though soon to be improved state)
* run python files with context clicks or from the Python menu
* debug python files (includes a watch, breakpoints, toolbar and code navigation in the cb editor)

Changes(from rev 15)

http://svn.berlios.de/wsvn/cbilplugin/?op=log&rev=0&sc=0&isdir=1

Navigation

[0] Message Index

[#] Next page

[*] Previous page