Developer forums (C::B DEVELOPMENT STRICTLY!) > CodeCompletion redesign
CC plugin interface redesign
Alpha:
--- Quote from: Alpha on July 15, 2013, 10:41:52 pm ---
--- Quote from: oBFusCATed on July 15, 2013, 02:54:10 pm ---What is the difference between a calltip and a tooltip?
--- End quote ---
Not much, really. [...]
--- End quote ---
Correction: inside CC, calltips take multiple more steps to calculate, where as tooltips only display the full symbol below the mouse.
oBFusCATed:
So, if I see it right, the CC plugins should only implement the GetCalltipsAt() and GetFullSymbolAt() virtual functions and then the CCManager should decide what to show.
I don't think you need 3 functions, when you can get with 2. GetFullSymbolAt could return a struct probably containing a type and visibility flags.
dmoore:
Nice to see this is finally happening. Keep up the good work, guys! I am keeping an eye on this thread. When this is done, will I be able use my python CC plugin (after I port it to the new API) alongside the C/C++ CC plugin sharing the same UI?
oBFusCATed:
dmoore:
Hopefully you'll be able to do it.
I suppose it will be good if we can try to port your plugin after some works is done in order to provide some real feedback to the usefulness of the API.
MortenMacFly:
Interesting to see this discussion.
From my point of view: Make sure its also interface-compatible to Erans CC works. We shouldn't re-invent the wheel another time.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version