This addon is extremely outdated, is NOT supported in any way, and should not be used.
If you are looking for a factions plugin for Titan Panel, I suggest you check out Tristanian's Broker Factions, which works with Titan Panel and provides nearly all of the features this addon provided.
Please note that "outdated" and "unsupported" do not grant anyone the right to modify and redistribute my code without my permission. If you have a serious interest in developing, maintaining, and supporting Titan Factions on a permanent basis, it is not difficult to contact me. However, as a fully functional and actively supported replacement already exists, there is really no reason to update this addon.
Addon code is protected under US and international copyright law. It is not open-source unless its author explicitly licenses it to be open-source. It is not public domain unless its author explicitly places it in the public domain. If an addon does not specify any license terms, it defaults to being copyrighted to its author with all rights reserved, granting you no rights beyond downloading, installing, and running the addon as-is. Please take the time to educate yourself before you disrespect authors' hard work by distributing modified versions of their code. Thanks.
I can't even believe no one deemed necessary to alert me of this "issue", despite people talking about me and assume things, while most of what is written here is entirely inaccurate.
So, let's get a few things straight.
1) I had a working, self-modified and Wotlk compatible version of Titan Factions running on my own PC, way before I decided to write Broker_Factions. After playing around with it for enough time, I actually consciously decided NOT to ask Phanx for permission to continue or rewrite it, because of the reasons already mentioned. The plugin had some rather obscure and outdated code in certain places, that while not especially inefficient (CPU wise), it would have to be reworked to make the plugin usable again. With the introduction of LDB it really made no sense "patching up" something that supports ONE specific bar addon, while you can (re)write the exact same thing, with the exact same features that can be used in Titan, in Fortress, Docking Station, ChocolateBar, in FuBar or the Seven Gates of Hell bar, assuming that they support the library. I really hope that this is crystal clear now.
2) "people are comfortable with it" I have nothing more to add to what Phanx already mentioned. I share the exact same sentiments.
3) "native Titan plugins are easier to use and configure than Broker plugins" Please excuse the language, but this is simply bull**it. If people cannot handle going through one more listframe in order to show/hide an icon and a label description, that is not Titan's problem. Some people believe that native Titan plugins are "easier" to configure because of the existence of the otherwise horrible Blizzard dropdown menu system. Well, newsflash, you can accomplish the exact same thing by using widgets in the Addon interface options menu (Ace3 ones or others, it doesn't really matter) that was specifically implemented for addon usage, without running the risk of tainting the entire universe. The reason I've kept the dropdown system, as the lead Titan "maintainer" (I don't like the word developer), is backwards compatibility with several old, yet functional plugins because yes at the end of the day I do "care". If that system though becomes more of a trouble than it already is, I may remove it altogether in the future (time permitting of course and only on an absolutely required basis).
4) "native Titan plugins have a more consistent look-and-feel than Broker plugins" This is yet another argument pulled out of thin air, with nothing to back it up whatsoever. Moreover, I feel disappointed (to say the least) that I'm reading this from a "member" of the Titan Dev team, a member that has not brought these concerns to my own attention, instead going forward and emailing, pming other authors or whatever. A lot of effort and countless of hours have been put into integrating LDB support and making the plugins "feel" as close to native ones as humanly possible, if not better. Unfortunately due to the way the library works, display addon authors have limited control over several aspects of a Broker plugin if its own author decides that _HE_ wants to control something. Example: If a broker plugins provides its own tooltip, _I_, as a display addon author have very limited control (if any at all) on said tooltip and any attempts done by me to forcefully "assume" control, would require code hacks. This has never been my intention. Fundamentally, the strongest point of LDB plugins, besides being display agnostic, was the simple fact that the author could allow a certain level of control (or not), in order to make his plugin look and feel exactly as he wanted to.
5) "if every Titan plugin author pulled their plugin because there's a Broker alternative, Titan Panel would die" Let me put it another way. If I didn't integrate LDB support into Titan, early on, as I did, then I can assure you that Titan Panel would have been in a much worse condition. This is not an exaggeration, it is simply the truth. Things move forward, not backwards.
6) "I like the functionality of Titan Factions better than Broker Factions." Why ? I've made every effort to replicate all the features and even include features that I rarely use, just to make the addon better for people that actually use it for those features. In addition, I'm trying to keep it as simple as possible, yet not terribly inconvienient or cumbersome, configuration wise. If people are so lazy as to click a few options and buttons, instead of let's say "checking" entries in a dropdown, then I apologize but there is little I can do, to dumb it down even more.
I hope that this response will help to clear the confusion and shed more light behind my choices, in this particular matter.
Originally posted by Nyte Maybe he didn't want to jump through all your hoops just to get your permission! He did get permission from the author of the Fubar version without much difficulty.
Or maybe he just felt that LibDataBroker was the superior development platform. Please don't make assumptions about other people just to have something to try to insult me with. I've already told you no, multiple times. Get over it and stop trolling my comment page.
Originally posted by Phanx
[And, yes, it is indeed interesting that the author of Broker Factions is the lead Titan developer. If the Titan API is so much better than DataBroker, why is the lead Titan developer using DataBroker instead of the Titan API? [/b]
Maybe he didn't want to jump through all your hoops just to get your permission! He did get permission from the author of the Fubar version without much difficulty.
BTW, I did take no for an answer; I stopped asking for your permission when you didn't reply to my last email to you. I just posted here to correct your misrepresentation, to wit, "I still haven't ever gotten a specific reason from anyone why they don't want to use Broker_Factions instead."
Originally posted by Nyte Interestingly enough, the developer who is actively supporting Broker_Factions is the lead developer for the Titan API. And, contrary to what you posted, I gave you several specific reasons to keep this alive-- you just didn't want to hear it. Why not just ask Cairenn to remove this from the site?
Actually, you didn't give me any specific reasons, just a bunch of vague remarks. Why do you have such difficulty accepting "no" for an answer? If you really want to drag this up again...
"people are comfortable with it" -- So what? People have been comfortable with a great many horrific things throughout history. Change is neither good nor evil in and of itself.
"native Titan plugins are easier to use and configure than Broker plugins" -- This is not a reason to keep a duplicate addon alive. Instead, if it is an actual issue, it is a flaw in Titan's handling of Broker plugins. There is no reason Titan cannot present Broker plugins exactly the same as it presents "native Titan" plugins.
"native Titan plugins have a more consistent look-and-feel than Broker plugins" -- Again, if Titan makes Broker plugins "look and feel" differently than Titan plugins (though you gave no specific details on what this difference is), then your complaint should be with Titan imposing this difference, not with me.
"if every Titan plugin author pulled their plugin because there's a Broker alternative, Titan Panel would die" -- Not even remotely true. Titan already supports Broker plugins. How exactly would more Broker plugins make Titan die?
"99% of all Titan plugins have Fubar equivalents; that doesn't mean I want to use them" -- Again, irrelevant. FuBar plugins do not work with Titan. Broker plugins do.
"I like the functionality of Titan Factions better than Broker Factions." -- Yet you are unable to describe a single specific detail about this vast difference in functionality you keep referring to.
If Titan Factions really is so much better than Broker Factions, why can't you or any of the other people who have QQed give even one specific example of how it's better?
And, yes, it is indeed interesting that the author of Broker Factions is the lead Titan developer. If the Titan API is so much better than DataBroker, why is the lead Titan developer using DataBroker instead of the Titan API?
Originally posted by Phanx ... I'll just have to waste more hours figuring out what changes to make six weeks from now when the Titan API changes yet again.... And I still haven't ever gotten a specific reason from anyone why they don't want to use Broker_Factions instead. It's much better written, more widely compatible, and is actively supported by a developer who actually uses it.
Interestingly enough, the developer who is actively supporting Broker_Factions is the lead developer for the Titan API. And, contrary to what you posted, I gave you several specific reasons to keep this alive-- you just didn't want to hear it. Why not just ask Cairenn to remove this from the site?
Did you not read ANYTHING? This addon is unsupported. Use the replacement linked in the addon description.
Also, this addon has nothing to do with classes, and does not include any class names at all. Apparently you didn't even read which addon you were posting your comment to.
Yeah, and if I make the changes now, I'll just have to waste more hours figuring out what changes to make six weeks from now when the Titan API changes yet again. Also, the code is such a horrific mess of inefficiency that if I touch it, I will end up wasting yet more hours rewriting it from scratch. And I still haven't ever gotten a specific reason from anyone why they don't want to use Broker_Factions instead. It's much better written, more widely compatible, and is actively supported by a developer who actually uses it.
Quote:
Originally posted by madindehead Question for you...why not just quickly update this addon yourself?
I managed to get mine into a semi working state, and I know NOTHING about lua. All thats required is a few lines of code. Also...you wouldn't have people updating your addon without permission. Just an idea.
Originally posted by Phanx I have not granted anyone permission to modify or redistribute my code, nor has anyone even contacted me to ask permission. I have reported your unauthorized modification to the site administration, and expect that it will be removed soon. Under US and international copyright law, I also have the right to demand that you remove your unauthorized modification from any other sites where you may have uploaded it.
My last comment on this page, and the description page itself, include a very prominent link to an addon by another author which is actively supported, and provides nearly all of the features Titan Factions provided. I suggest you use that instead of violating my rights as an addon author by distributing modified versions of my addon without my permission.
Question for you...why not just quickly update this addon yourself?
I managed to get mine into a semi working state, and I know NOTHING about lua. All thats required is a few lines of code. Also...you wouldn't have people updating your addon without permission. Just an idea.
Phanx,
May I have your permission to modify your code and distribute the modified version of your addon?
Nyte
Quote:
Originally posted by Phanx I have not granted anyone permission to modify or redistribute my code, nor has anyone even contacted me to ask permission. I have reported your unauthorized modification to the site administration, and expect that it will be removed soon. Under US and international copyright law, I also have the right to demand that you remove your unauthorized modification from any other sites where you may have uploaded it.
My last comment on this page, and the description page itself, include a very prominent link to an addon by another author which is actively supported, and provides nearly all of the features Titan Factions provided. I suggest you use that instead of violating my rights as an addon author by distributing modified versions of my addon without my permission.
I have not granted anyone permission to modify or redistribute my code, nor has anyone even contacted me to ask permission. I have reported your unauthorized modification to the site administration, and expect that it will be removed soon. Under US and international copyright law, I also have the right to demand that you remove your unauthorized modification from any other sites where you may have uploaded it.
My last comment on this page, and the description page itself, include a very prominent link to an addon by another author which is actively supported, and provides nearly all of the features Titan Factions provided. I suggest you use that instead of violating my rights as an addon author by distributing modified versions of my addon without my permission.
[/b]
