It just hit me that this is a totally bad idea in the first place. Changing the .toc on EVERY addon or at lest the almost 400 you are using would be a complete waste of time. Most people are using auto updaters of one sort or another and most of those will overwrite the .toc's when people update thus undoing all the changes you have made. Samsan had the best idea IMO make your mod pull mod names rather then trying to modify every mod. Its certainly more feasible.
|
oh yea it also wouldn't require permissions :)
|
Though he'd still need permission to redistribute/repackage any mod with a restrictive license.
|
yea but thats most likely only a fraction of the 400, a more handle able number of PM's and emails.
|
Quote:
|
Yea but on the flip side of that coin.... 100's of authors owe their popularity to a compilation. For that mater many of them would never be known about if it wasn't for the more popular compilation they came with.
|
Quote:
The mods I'm asking about in bulk are the ones that I have not made any changes to at all. If I have 380 mods and I've changed 10 of them in the code because they didn't have a configure interface and their bars went horizontal and I wanted to add in verticle, those mods I will contact directly. My concern for Colorizing the groups would be on a "First Install" only . . . just so when you see an addon in the list who's name is HumHumDinger and you've never heard of it, have no clue what it does, but you see that it's title is green, you also see an addon by the name DingDongBell which you are familiar with and you know that it is an auto dinger! It's title is also green . . . so according to the compilation description . . . green can be assumed to be auto dingers and if you like DingDongBell then you would uncheck HumHumDinger . . . after the first instal, hopefully you'll be a little more familiar with what group each addon is in, and you'll have a working UI with all the settings for each mod intact, if you want to change settings you can for the mods that have a config. Make your updates and those that are not colored are now your updated addons. If it stays the same color for long periods of time, then you might check the addons page to see if it's a dead project or just not being updated due to good functionality. This idea would also introduce alot of new people to some new addons, if they see they work and how they look and how well they integrate, could create some new fans. Another idea for the colorizing the title is some addons are "Class Specific" and if a user plays a Hunter, I want them to see which addons are specific for a priest, no sense having an addon running you don't need for that character. So the colorization would be a "suggested" configuration and I would have to do it in the .toc because they load before anything else that I would be able to make to colorize them. If I've made any changes to your addon, I will contact you directly with specific explanations and descriptons and screenshot of exactlly what has been changed and ask permission to release the compilation with said changes, if permission is denied with changes, I will revert my changes if that will grant the permission, but I'm looking for ideal co-operative situation here. For instance. I added a button to one addon because it worked hand in hand with another, but there was no button to toggle the second addon, so I put a button in the first addon to "facilitate" ease of use for the common user. nothing big, just a button that onClick called an onshow function of another addon, but those addons I will contact directly. This post is about the coloring of the title line. Then again another addon I use has a LOT of chat spam upon load. That addon I took out all the onload chat spam, Or I might have just added a texture that wasn't in the code by default and no response to pm about adding it in but once again, I will contact those authors directly I can't believe that such a big issue is being made out of asking permission to take a large group of addons that would have a line in the .toc like this Code:
## Title: Mini-Targ Code:
## Title: Mini-Targ |cffcc00cc HUD|r Code:
## Title: cffcc00cc Mini-Targ | cffccff00 Priest and with WoWI policy on compilations each addon will be given credit on the compilation page, with links to each addon's page. If you don't want to post permission you could always pm me permission. Quote:
I also want to respond to a comment made about Authors and bug reports on UI compilations I'm not sure how other compilation designers do support on their compilations but I am the type, if it's a problem with my UI, I should support it, if it's a bad addon I will forward the comment and bug report. No need to bother the author of ThisAddon if it's something like the user toggled on ThatAddon at the same time. |
Quote:
Edit: Notice how our vinyl now has a C side! |
would be alot easier if I could just create a few of my own folders in the Addons folder, name them things like
Priest Hunter DK Maps Quests UnitFrames drop in a few of my own .toc files in those folders, have the addons in the right category folder then expanding that you get a list of the addons included in that suggested setup and the ability to check or uncheck the addons there in the list. I know that addons have subfolder (dependent plug-ins) which have similar functionality, my problem is they all show up in the addon list individually and I can't make a heiarchy menu before loggin in, so I figured color-coding them would be the simplist and most effective way of catagorizing the list of 300+ addons. But when I choose my character for login I could just click Priest if my character is a priest, expand maps, toggle on Cartographer, toggle off SimpleMiniMap, toggle on SexyMap I think you see where that was going, would be a good idea and the best way to do it, then I wouldn't need any permissions, but I see no way to do that . . . So I came up with a viable co-operative alternative to try to help satisfy everyone with staying with as many "as-is" addons as I can |
Just to be clear: You still might need permission. Distributing an addon that has a restrictive license, even if it is unmodified, requires permission. It's a side point, but one that people seem to be skipping here. You need permission from authors whose license of choice restricts distribution simply to include the addon with your UI package.
|
If you're only planning on changing the color to group them, why not just add a text string with the assigned color per group linking the name of the mod to that color coded group, that way you don't have to change the mods. :) just a thought.
I meant in a lua file or something, obviously my opinion and trying to offer a suggestion when un-noticed. categorize in lua with the mod title wrapped in color code tags would be easier than all this arguing and you wouldn't have to alter anything at all, thus no debate. eg: Quest Mods |cff4169e1QuestGuru|r" etc. It would save all this debating over policies etc. |
Quote:
|
Sam i noted your comment actually. I agree with you to that making an .lua with all the addon names and a color tag on each to correspond with its group is the best way.
|
Quote:
So if it's possible I guess I'll have to pass cause my lua scope is no where near that |
Quote:
I would not give permission unless I know exactly how, what and why something is changed. |
Quote:
Not all authors spend time on WoWInterface. They may release here as a courtesy however their main web home maybe elsewhere. Thus they are not going to see threads of this nature. PM them. If that is too daunting, then perhaps you need to rethink your idea. To be quite frank, uploading a compilation with 300+ AddOns in it is overkill. You are better off either going with a general compilation and users can add the class specific AddOns themselves or you can can create "bolt on" packs that add the class specific AddOns (including any settings you wish to include). Aka something like this:
|
One small issue is the addons in question are unknown. So even if there were authors that are willing to say yes they wouldnt know if it was their addons you want to modify. I know you covered this briefly in your original post. Asking for blanket approval (from what i got out of it) from essentially all authors is not likely going to go far. And if by chance the compilation is posted (ill admit i havent looked) your basically asking every author to look it up and see if they have addons in it and then decide if they want to allow you to do this.
Might be worth listing the addons in question if you still plan to continue to pursue this through a thread. I would imagine that authors are loathe to give a blanket approval especially if they arent even sure your request refers to them. Personally as much as it sucks i think pm's are your best route for what your after even though its certainly a daunting prospect to say the least. |
Quote:
|
Quote:
Even if you would argue it is still a copyrighted work, you can leave it intact, unpack addon into /foo/foo/ and make your own foo.toc file loading proper lua files from /foo/. |
Quote:
## Title: HUD ## Title: UnitFrame ## Title: HunterMod ## Title Healz+ | Priest/Druid But to be honest I like the idea of the "Bolt on Packs" or Plug-in Idea. Now doing it this way, it should still keep the saved variables and layout design I set it up with with my WTF included correct? Even doing it with the bolt on packs, I'd still like to colorize the Core addons by type, but this will cut the list down to where I maybe able to pm those authors. I'll look into that, any other ideas and suggestions are welcome. |
All times are GMT -6. The time now is 05:44 PM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI