BTW.. all those externals make update really slow and I'm not sure if it's really good. I mean when an addon uses Ace 2.0 why shouldn't it make an svn copy ? It don't use more space on the server since it's a "cheap" copy and if the external lib moves to e.g. 2.1 it's not guaranteed that the addon will still work with the externals ?
Because svn copy would get a static version, not the most recent version.
If Ace2 needs a new major version, then the libs will be AceAddon-2.1, which is a different folder, thus externals are kept intact.
First, http://wiki.wowace.com/index.php/Library_Template
That should be at the top of every embedded library.
This makes it so much easier to tell what a library is, who to blame problems on, and what it does.
Secondly, library folder names will be the same as their major versions. e.g. AceAddon is now AceAddon-2.0
This solves many issues, especially with svn:externals. Now when you want a new major version, you do not need complicated external tagging/branching acrobatics, you just make a new folder that matches the new major version. This also streamlines and simplifies things.
Current addons which use the libraries can then upgrade to new versions at their own pace.
On the SVN, you would have /root/trunk/Dewdrop/Dewdrop-1.0/Dewdrop-1.0.lua
So having TekDurability or whatever is perfectly fine by me.
You don't have to, but I'm just saying it's fine by me.
I just don't like having a single plus, because it also makes it seem like it's "better", which it might not be in comparison. Thus, attaching your name or a few letters representing who you are is the best plan I can see.
0
0
0
0
Remove your old FuBar folder, download the new one from trunk.
Download FuBar-compat-1.2 and place it in your addons folder.
Tada, it all should work now.
Also, I am no longer supporting 1.0 plugins, so don't ask for it.
For an "ExampleFu", see ClockFu in branches.
0
Because svn copy would get a static version, not the most recent version.
If Ace2 needs a new major version, then the libs will be AceAddon-2.1, which is a different folder, thus externals are kept intact.
0
First, http://wiki.wowace.com/index.php/Library_Template
That should be at the top of every embedded library.
This makes it so much easier to tell what a library is, who to blame problems on, and what it does.
Secondly, library folder names will be the same as their major versions. e.g. AceAddon is now AceAddon-2.0
This solves many issues, especially with svn:externals. Now when you want a new major version, you do not need complicated external tagging/branching acrobatics, you just make a new folder that matches the new major version. This also streamlines and simplifies things.
Current addons which use the libraries can then upgrade to new versions at their own pace.
On the SVN, you would have /root/trunk/Dewdrop/Dewdrop-1.0/Dewdrop-1.0.lua
0
0
0
0
http://boss.wowinterface.com/portal.php?id=54&a=listfeatures
0
0
So having TekDurability or whatever is perfectly fine by me.
You don't have to, but I'm just saying it's fine by me.
I just don't like having a single plus, because it also makes it seem like it's "better", which it might not be in comparison. Thus, attaching your name or a few letters representing who you are is the best plan I can see.
0
I was also thinking of adding more stuff too, such as invite everyone in the BG, open bg minimap on entrance, etc.
0
Also, remember, everyone, if you write mods for Boss give them simplistic names, such as "Honor", there's no need to put the plus behind it, imho.
0
folder name: BossPanel_MyAddon
.toc name: BossPanel - |cffffffffMyAddon|r
I don't want to use the bracket syntax that is prevalent in Titan.