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

a Qt plugin : QtPregenForCB => AddOnForQt

(1/15) > >>

LETARTARE:
From January 01, 2020, 'Qtpregen' will be replaced by 'Addonforqt'
http://forums.codeblocks.org/index.php/topic,20000.msg165730.html#msg165730

Hello everyone,
I suggest a plugin for compiling Qt project using Code::Blocks .
This extension of  Code::Blocks will be offered on:
https://github.com/LETARTARE/QtPregenForCB
and is called :
--- Quote ---QtPregenForCB-0.2.2
--- End quote ---

If this plugin interested persons, I would do an article in the Wiki.

See the discussion: http://forums.codeblocks.org/index.php/topic,19931.0.html
Sincerely

LETARTARE:
Hello,
I forgot to provide patches for 'Code::Blocks'  (svn 9501, 10035, 10091)  !!
It is repaired.
https://github.com/LETARTARE/QtPregenForCB
Sincerely

MortenMacFly:

--- Quote from: LETARTARE on February 11, 2015, 09:20:32 am ---I forgot to provide patches for 'Code::Blocks'  (svn 9501, 10035, 10091)  !!

--- End quote ---
...in SVN. I see no reason why we should not do this. However, keep the comments of obfuscated in mind... To be bullet-proof the event ID's should be standardised and exposed through the SDK. So this actually is only half of the way...

oBFusCATed:
I still don't think this is a good solution, in fact I think this is terrible solution and if it was up to me I'd revert it.

For example the current version of the plugin will break if the user uses the context menu in the project manager.
It will break, if the compilation is started by a script. Or even from the debugger.

If you need to know something like a reason why the event has been fired then we should use some kind enum for the task.

MortenMacFly:

--- Quote from: oBFusCATed on February 11, 2015, 09:03:49 pm ---If you need to know something like a reason why the event has been fired then we should use some kind enum for the task.

--- End quote ---
Thats what I meant with:

--- Quote from: MortenMacFly on February 11, 2015, 06:30:55 pm ---To be bullet-proof the event ID's should be standardised and exposed through the SDK.

--- End quote ---
However, in the compiler you'd then only replace the int ID with an enum ID. Therefore the code is "kind of" valid. I didn't state that its correct to use the ID's as done in the plugin.

Navigation

[0] Message Index

[#] Next page