Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
AutoVersioning Plugin
Jeisson:
Hi JGM!.
I am trying to use the Change log feature. Is it possible to write changes in the log without incrementing the version?. For example. While I am working in the project, I fix a bug, so I want to track the change before I do some other tasks (and before I forget the change's details :D), but I am not ready for incrementing the version yet. So change events could be grouped by date then project version. That is only an idea, it seems laborious to implement...
I feel so thankful for the new changes.
Greetings!
JGM:
--- Quote from: Jeisson on December 09, 2007, 04:56:44 pm ---I am trying to use the Change log feature. Is it possible to write changes in the log without incrementing the version?. For example. While I am working in the project, I fix a bug, so I want to track the change before I do some other tasks (and before I forget the change's details :D), but I am not ready for incrementing the version yet. So change events could be grouped by date then project version. That is only an idea, it seems laborious to implement...
--- End quote ---
That was something that I thought when implementing that feature of the plugin, but I did'nt do it because I was on a hurry :(. I was thinking on doing a data grid consisting of two cells, the first cell to select the type of changes as:
1. Fixed
2. New Feature
3. etc...
and the second cell to write the description. And store those changes, until the user feel is time to make a release.
For example:
[Type] [Description]
"Fixed" "Crash on destructor, deleting pointer already deleted"
"New" "Now the user can modified some internal settings"
So the user should be able to write row by row the changes on the data grid and then choose when to write them to the change log, using the actual date that the user wrote the changes to the file, instead of storing the date when the user wrote the row in the data grid.
In that way the user will have the ability to keep adding to the list of changes every time he mades a change, and when hi finish the software, write the changes to the change log and the date he wrote the changes to the change log, so there should be an option where the user should be able to select if he wants the data grid to appear before compilation after a change has been made, and a button on the autoversioning dialog to show that data grid to edit or add rows of changes, even a menu item under the project menu named ChangeLog, to call the data grid.
I will implement that! :)
Jeisson:
Fantastic idea!
I plenty understand your hurry situation, I am in the same conditions :(. Of course, no stress, take all the time you need for the amusement adventure :D. I think is a very great job!, and again, thanks for sharing it with us.
Greetings :wink:
JGM:
FInally made the corresponding changes to the changes log editor, now it uses a data grid and has the ability to save the changes temporarily to write them later. Attached is a screenshot
Here is a sample output:
--- Code: ---13 December 2007
released version 1.1.0 of AutoVersioning-Linux
Change log:
-Added: Now the changes log has a data grid
-Applied: Nice drop down menu for the "Type" column
--- End code ---
[attachment deleted by admin]
JGM:
Updated the wiki page to reflect the new changes of the plugin as the new changes log generator (v1.1)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version