Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
AutoVersioning Plugin
JGM:
Here the Auto Versioning plugin 1.0
[Changes 1.0]
- Now the plugin uses the project file to store settings instead of the ini file, thanks to killerbot.
- You can choose where to store the version.h header as change the filename.
- You can choose where to store the changeslog as change the filename.
- The settings tab option AutoIncrement has been changed to Do Autoincrement, because of some different behaviour.
- Also the Commit Changes menu was renamed to Increment Version.
- Now the version.h file is parsed to obtain the version values.
- You will have to increment version before closing the project if changes, since it doesn't store the modified flag as a configuration anymore.
- The build history is now part of the header file.
- Many other internal changes thanks to killerbot.
[Changes 0.9.1]
- Small change, now variables are declared const to suppress warnings
[Changes 0.9]
- Added a scheme validator to support the user while entering the values (error when dividing by zero on Revision random maximumn).
- Changed some strings from Auto Versioning to Autoversioning
- Now the project menus are disabled when no project is active.
- Edited some menu comments and make them shorter.
[Wiki] (actually I have to update the wiki since the plugin has changed a little)
Check the new wiki page for documentation of the plugin and updated screenshots:
http://wiki.codeblocks.org/index.php?title=AutoVersioning
[Downloads]
Win32 Binary compiled with rev. 4711:
http://prdownload.berlios.de/autoversioning/autoversioning-v1.0.win32.7z
Ubuntu 7.04 Binary compiled with rev. 4711:
http://prdownload.berlios.de/autoversioning/autoversioning-v1.0.ubuntu.7z
[Sources]
Svn: svn://svn.berlios.de/autoversioning (most recent sources)
MortenMacFly:
--- Quote from: jgm on June 27, 2007, 08:18:25 pm ---I see that the plugin classes only implement a few events. Like attach and release, but I don't see events like onmenuclick or something like that.
--- End quote ---
Have a look at cbEVT_COMPILER_STARTED -> that's what you need to listen to.
--- Quote from: jgm on June 27, 2007, 08:18:25 pm ---And what type of plugin this should be to work correctly? cbToolPlugin?
--- End quote ---
That's a good choice I'd say.
With regards, Morten.
JGM:
--- Quote from: MortenMacFly on June 27, 2007, 09:02:26 pm ---Have a look at cbEVT_COMPILER_STARTED -> that's what you need to listen to.
--- End quote ---
Thanks for your reply, I will try that.
JGM:
The compiler plugin is not generating EVT_COMPILER_STARTED or notifying the other plugins about this event. But is generating an EVT_COMPILER_FINISHED so i decided to increment the file after the compilation is finished. And thinking it now is the correct way of doing it. (Now increments before compilation using a wxTimer). Well, now it use the cbEVT_COMPILER_STARTED to make the changes necessary.
But how I know if the project was successfully compiled? Not so necessary now by the commit changes feature.
Edit:
cbEVT_COMPILER_STARTED still doesn't work. now work! fixed on revision 4324.
MortenMacFly:
--- Quote from: jgm on June 27, 2007, 10:30:25 pm ---The compiler plugin is not generating EVT_COMPILER_STARTED or notifying the other plugins about this event.
--- End quote ---
Ouch! :shock: That's obviously not as it should be... I need to have a look at this.
Navigation
[0] Message Index
[#] Next page
Go to full version