[klippy]

Description:
When you save a *.sma file in ST2, this plugin searches for a version in your plugin and auto-increments it.
PPalex's plugin helped me in writing this one(this thread), and I haven't asked him about using his plugin as a base for mine. PPalex, if you do not want me to release a plugin that uses your code, feel free to write me a PM and I will take it down.

How to use
The version written in a plugin can't be in any format, it has to follow certain rules.
The version format looks like: [v]{major}.{minor}.{build/revision}[b[eta]], and it can either be a define(macro), or a constant string, with a symbol name of PLUGIN_VERSION or VERSION (case-insensitive). The plugin will increment the {build/revision} number by 1.

Valid version string examples:

PHP Code:

#define PLUGIN_VERSION "1.0.124"
#define       VERSION       "v1.0.124" // Use as many spaces/tabs; also there is 'v' in front of the version number
#define Plugin_Version      "v1.0.124b" // Case-insensitive; 'b' following the version number

new const Version[] = "1.0.124beta" // Constant string; 'beta' following the version number
new   const   VeRsIoN [ ] = "v1.0.124b" // Again, use as many spaces 


Installation:
Put the archive contents to:

• WinXP: %appdata%/Sublime Text 2/Packages/User
• Others (or at least I think so): %appdata%/Roaming/Sublime Text 2/Packages/User

* If you have any suggestions, or complaints, feel free to write it down in this thread.

[Kia]

Looks nice, good job.

[GuskiS]

It would be nice to have a way to define your self the macro name. Also, does it check in that particular .sma file which you save? Cause I'm using version number in .inc file. Does this work for ST3?

[klippy]

Originally Posted by GuskiS It would be nice to have a way to define your self the macro name. Also, does it check in that particular .sma file which you save? Cause I'm using version number in .inc file. Does this work for ST3?

It is ST2, not ST3 (it has some extended API), but either way, I am not sure if I can do it.
I can allow user to change macro name with settings, that would be no problem. And, because you are using it in your .inc, is .inc in the same folder as .sma is? Or at least relative to it, i.e, .sma file location is

C:/plugins/plugin.sma

and you include your .inc file like so:

#include "include/version.inc"

so, include file location is

C:/plugins/include/version.inc

If so, that can be done I guess, because I can get .sma file's path.

@Kia, thanks.

[GuskiS]

I just include it this way:

#include <myinclude>

So that file is in my includes folder.

C:\plugins\plugin.sma C:\plugins\includes\myinclude.inc

Also, In windows it is \ not / (smartassoverhere)

[klippy]

Originally Posted by GuskiS I just include it this way: So that file is in my includes folder. Also, In windows it is \ not / (smartassoverhere)

In Windows, '\' is standard, but '/' is also valid. And I've only written '/' because I didn't know what OS you are using.

I guess I will check both in the same directory, and also "./include/" for included files, so I will try to fulfill your request.

[Netsys]

I think it's buggy, of "0.1.10000" goes "0.1.10010" instead of "0.1.10001"