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
I would like to propose a standard for the TOCs for Libs, specifically the title.
## Title:|cff7fff7f-Ace2 Lib- |r Libname
This would group all of the Ace2 Libs together and clearly identify the Ace2 Libs while keeping with the Ace2 color scheme.
My reason is that I use the !!!StandaloneLibraries and when I to re-enable my addons I have to hunt all down all of the various libs and enable them. Usually it takes a couple of logins/logouts to get them all enabled. The ones that I commonly miss are the Ace2 Libs that don't have lib in their name (DAMN you Metrognome!!).
Of course there may be some objection to grouping them together therefore you could also do this:
## Title: Libname |cff7fff7f -Ace2 Lib-|r
This of course wouldn't group them together but still identify the libs.
Also, I was wondering why don't the Ace2 Libs have Ace2 as a dependency?
I usually disable all of my mods when starting a new character and then go back and re-enable only the ones I need for that class. I also will disable all of my mods if I am troubleshooting my UI and then go back and enable them one by one. Creation of a new character on a new server I believe all mods are enabled by default (WoW has crashed because I forgot to disable the mods I don't need, lol).
I also thought it was odd how most Ace2 mods carry the -Ace2- tag but the libs don't. Mostly I made my suggestion because of aesthetics and convenience.
I too enable & disable by class and have gotten to the point of running a batch grep tool to modify the tocs to enable the groupings above. It makes it so much easier to verify the correct addons are enabled per class.
Here's an idea, a simple mod that will iterate over all the mods installed and enable all the ones that are LoD and have X-Category: Library. Simplest solution I see....
I use Loadit http://ui.worldofwar.net/ui.php?id=2198 for addon management, I think it's much better than MCP. I do agree that there should be an ace2 addon manager but that's a discussion that belongs in another thread.
I still maintain that my argument to standardize the Ace2 Lib names is a valid one and an easy solution.
1) It's a visual indication that the addon is an Ace2 Lib that needs to be enabled
2) It groups all of the Ace2 Libs together for easy mass enabling.
No need for extra mods or greping and what not.
Hell, give me SVN access and I will make the modifications myself, lol.
From now on ALL libs will be prefixed with "Lib-Blah"!!!
I just want at the very least a visual indication that the mod is a lib. If it's -Ace2 Lib- or Lib-Blah, I really don't care.
Just curious Tekkub, what do you think about -WoW Lib-?
Also, what needs to be done to move this proposition forward? Is it as simple as you or another Ace Dev with SVN access changing the Title field in the TOC for libs? Or would it be up to each individual lib author to implement?
Never said that it was a new standard, you're going to need the main author's votes here.
I still fail to see why it matters at all. The metadata is in the TOC, write an addon to manage this shit. ModMenu has served me fine for a long time. The char-select addon menu is not designed for any of this shit you people want it to do.
It's not something I perceive as a problem, so I'm not changing my crap till you give me a compelling reason otherwise.
I know that a lot of developers don't want to fool with libraries that aren't embedded or with adjusting the configuration in the TOCs and I respect that. Personally, I wouldn't mind seeing this done, though. Even it's just for consistency's sake. My thoughts:
This would solve directory sorting when using Stand-Alone Libs and would solve the sorting in the default (and other) add on configuration screens. And it wouldn't be difficult to apply. Heck, I'd go through myself and do it if someone told me what to do. :P
Of course some add ons authors using ! already (BugGrabber/StopTheSpam) would have to add one to their current directories. But it wouldn't be that much of a pain. >.<
Edit: I don't know if that would make a difference as far as loading sequence, since the libraries are LOD but it was an idea, anyhow. >.<
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumFirst, 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
## Title:|cff7fff7f-Ace2 Lib- |r Libname
This would group all of the Ace2 Libs together and clearly identify the Ace2 Libs while keeping with the Ace2 color scheme.
My reason is that I use the !!!StandaloneLibraries and when I to re-enable my addons I have to hunt all down all of the various libs and enable them. Usually it takes a couple of logins/logouts to get them all enabled. The ones that I commonly miss are the Ace2 Libs that don't have lib in their name (DAMN you Metrognome!!).
Of course there may be some objection to grouping them together therefore you could also do this:
## Title: Libname |cff7fff7f -Ace2 Lib-|r
This of course wouldn't group them together but still identify the libs.
Also, I was wondering why don't the Ace2 Libs have Ace2 as a dependency?
I usually disable all of my mods when starting a new character and then go back and re-enable only the ones I need for that class. I also will disable all of my mods if I am troubleshooting my UI and then go back and enable them one by one. Creation of a new character on a new server I believe all mods are enabled by default (WoW has crashed because I forgot to disable the mods I don't need, lol).
I also thought it was odd how most Ace2 mods carry the -Ace2- tag but the libs don't. Mostly I made my suggestion because of aesthetics and convenience.
I do this for Ace and non-Ace addons as well.
NEED! :P
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttp://www.wowace.com/forums/index.php?topic=2691.0
maybe we should start another thread about managing libraries
I still maintain that my argument to standardize the Ace2 Lib names is a valid one and an easy solution.
1) It's a visual indication that the addon is an Ace2 Lib that needs to be enabled
2) It groups all of the Ace2 Libs together for easy mass enabling.
No need for extra mods or greping and what not.
Hell, give me SVN access and I will make the modifications myself, lol.
I'm okey with Lib-Blah however.
From now on ALL libs will be prefixed with "Lib-Blah"!!!
I just want at the very least a visual indication that the mod is a lib. If it's -Ace2 Lib- or Lib-Blah, I really don't care.
Just curious Tekkub, what do you think about -WoW Lib-?
Also, what needs to be done to move this proposition forward? Is it as simple as you or another Ace Dev with SVN access changing the Title field in the TOC for libs? Or would it be up to each individual lib author to implement?
I still fail to see why it matters at all. The metadata is in the TOC, write an addon to manage this shit. ModMenu has served me fine for a long time. The char-select addon menu is not designed for any of this shit you people want it to do.
It's not something I perceive as a problem, so I'm not changing my crap till you give me a compelling reason otherwise.
and about the classes thing... look at supply&demand.. I wrote a small perl script to add s&d headers to .toc files .0
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumTOC Entry:
Contents of Stand-Alone Libs:
This would solve directory sorting when using Stand-Alone Libs and would solve the sorting in the default (and other) add on configuration screens. And it wouldn't be difficult to apply. Heck, I'd go through myself and do it if someone told me what to do. :P
Of course some add ons authors using ! already (BugGrabber/StopTheSpam) would have to add one to their current directories. But it wouldn't be that much of a pain. >.<
Edit: I don't know if that would make a difference as far as loading sequence, since the libraries are LOD but it was an idea, anyhow. >.<
but then, this will be easier. I'd like to have all my libs sorted and in first in the addon section.
!Lib-Ace2
!Lib-Babble-2.2
!Lib-Glory
!Lib-Quixote
...
looks good and easy for new users, but boaring for dev the time to migrate.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium