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

Plugin for a Programming Language

(1/7) > >>

igorevc:
Good day.

I want to create a plugin for Code::Blocks for a programming language that has the following features:

- New project type and new file types
- Testing and debugging facilitations

I already made the Hello World tutorial but I need some more info to make my project possible.
Can you help me out?

Thank you for your attention.

dmoore:
what programming language? compiled or interpreted?

files types are handled automatically (more or less - at present, there's no programmatic way to add new file types for the project tree). you can create project wizards without creating a plugin.

a plugin would be suitable for adding testing or debugging facilities. I put together a "proof-of-concept" python debugger a couple of years back, which simply parses the output of the command line debugger (pdb) in order to offer familiar gui interaction. what do you have in mind for testing?

igorevc:
If you need to know, it's a interpreted.

But the plugin must add new project types and new file types.

For testing, it should create a console that interpretates commands and return the possible results.

I need what I asked to make a complete plugin.

By the way, is there a way to incorporate the console on "Log & others"?

Once more, I thank you for your attention.

dmoore:

--- Quote from: igorevc on January 27, 2009, 05:03:10 pm ---If you need to know, it's a interpreted.

--- End quote ---

I asked because it makes a difference. CB's project infrastructure was designed for compiled languages. Interpreted languages don't need all of that complexity. So what sort of project support do you need: just a container to say these files belong to this project?


--- Quote ---But the plugin must add new project types and new file types.

--- End quote ---

you could deploy a project wizard along with your plugin. It wouldn't be all that difficult to tweak the CB SDK to add the ability to add file types programmatically (file a patch if you want)


--- Quote ---For testing, it should create a console that interpretates commands and return the possible results.
...
By the way, is there a way to incorporate the console on "Log & others"?

--- End quote ---

You could use existing logs to send output (for example, commands that you set up on the tools menu can be redirected to the log)

Alternatively, you could create your own frame or window that handles process I/O. I've written a plugin called ShellExtensions that does just that for arbitrary commands. (you can find links to these plugins at the project page in my sig. I'm in the process of getting some of this code ready to move into C::B proper)

igorevc:
On the project part, I'll need a file container and to verify errors.

I really want my plugin to extend the project choices.

Thank you so much for your attention.

Navigation

[0] Message Index

[#] Next page