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

Python Code Completion

<< < (12/12)

Alpha:

--- Quote from: dmoore on October 29, 2013, 06:14:30 pm ---Is there enough ready to be able to do anything with it yet? Testing out his work with Python would obviously be a good test.

--- End quote ---
I think so.  API for auto-complete popups, documentation popups, tooltips, and calltips are present and (mostly) functional.  These subsystems still contain some hardcoded defaults, but other than that, I believe it is ready for a test with Python.  (Be prepared for uncaught bugs and frequent API breaks though ::).)

dmoore:

--- Quote from: Alpha on October 30, 2013, 12:52:38 am ---I think so.  API for auto-complete popups, documentation popups, tooltips, and calltips are present and (mostly) functional.  These subsystems still contain some hardcoded defaults, but other than that, I believe it is ready for a test with Python.  (Be prepared for uncaught bugs and frequent API breaks though ::).)

--- End quote ---

I will take a look soon (if for no other reason than I want to use the docstring UI rather than roll my own). Some hints (e.g. doc strings) on how to use the plugin virtuals (i.e. what the plugin is supposed to do with each one) and what events are available and need to be used would be extremely helpful! Looks like a fairly extensive overhaul of the existing interface. (Well done!)

Navigation

[0] Message Index

[*] Previous page