I was wondering if someone here who better knows the inner workings of ButtonFacade might be able to take a look at FacadeBuffs? It's been half broken for a while now (last update on Curse looks to have been 6 months ago, and for all intents and purposes appears to be abandoned). I've tried looking at it and comparing with another mod that makes use of BF, but don't really seem to know enough to make any progress with it yet.
It loads without errors, however buff & debuff icons are not skinned, while temporary enchants still work properly. Drilling down to the individual group settings in the BF options seems to indicate it's still set to the Caith skin I usually use, so would appear that it's not properly applying the settings on load. Changing anything in the FacadeBuffs section in the BF options or the individual groups below does not seem to affect it, however changing the global BF options does... and it continues working fine until next login.
True. But we don't want to included textures with BF, do we? Honestly, I've been think there's a few we COULD add, like a couple of generic Backdrop textures (The one I've been using on nearly every single square skin).
I'd say no, aside from maybe just a FEW basic default sets. As much as I like SharedMedia, it has way too many textures included by default... something I, personally, wouldn't want to see repeated.
Finally, with looking at moving things to color spaces instead of raw textures, maybe everything can be integrated into a main skin entry, showing each derivative as a derivative instead of a separate skin?
If custom coloring support is being added in the manner StormFX mentioned above, is there really still a need for derivatives (I'm assuming you're talking about alternate sets of predefined colors for the skin to choose from)? If you create one as a grayscale base, the user would be selecting whatever colors they wanted per layer, which would seem to me to kind of eliminate the need for predefined variants.
Also, hit a possible minor bug when trying this out with Trinity2 tonight... I only tried the Caith skin so far with it (looks pretty good :)), but it seems that even though the Backdrop checkbox was selected in the BF options by default, it didn't actually apply the backdrop until I toggled the option off then back on again.
Heck, even the Vol II: Metal series has just a gray scale image as the normal texture and the additional skins just have different color settings. >.<
At least in this respect, user defined colors would save skin author work (requests for certain color variants to be made), and having to have say 6 different versions of a skin, just to please everyone who wants a red, green, yellow, blue, purple, or gray version.
Maul's suggestion (as "evil" as it may be :P), was pretty much what I had in mind. Alternatively, depending on how difficult it would be to implement, non-grayscale skins could possibly desaturate the image first (thus, essentially making it greyscale) then apply the chosen color, or even potentially go the route of hue shifting. I've seen both options offered in other skinning apps., but I've no idea how feasible this would be for an addon or how much actual work would be involved. Seems like SetVertexColor would be the simplest solution (regardless of the possible resulting hideousness of the user's selection :P).
Perhaps. I'm willing to negotiate. However, as was mentioned above, people WILL complain about certain skins looking bad with certain coloring. And I'm the type of person that will simply tell them where to stick it.
By all means, do so. :P In my opinion, it's kind of a weak argument for not supporting it.
Quote from StormFX »
Besides, I'm putting my hard work into creating skins for others to use free. If you don't like it, you don't have to use it.
The work is appreciated, and I never said I had to. ;)
Quote from StormFX »
On another note, the amount of work it would/will take on JJ's end is pretty steep.
This argument against it holds a lot more wieght to me, so I can agree with it. ;)
Quote from StormFX »
Not to mention that that means I have to go back and rework every single skin with the assumption that someone's going to be changing the colors.
I wouldn't think so... but then I'm not really familiar with the underpinnings of what makes it work. I'd say that if the color masking or whatever doesn't really show up that well on a particular skin, then so be it. Outright disabling the option altogether, is where I'd see issue. Using the "complaining users" argument, you'll probably be fielding repeated questions from people anyway about why they can change colors on skin ABC but not on skin XYZ.
Bottom line, people like customization... hence why pretty much every operating system these days now includes (or has available through some 3rd party application) some way to change colors, skins, fonts, etc.
However, some skins may include pre-colored textures (Onyx) that won't/don't look good recolored and the skin author should have the option of disabling it.
Wrong. If the end user likes the way it looks, why should the author's initial design trump the end user's preference? What may look bad to one person, may look great to another. If the user alters the colors and it looks like crap, it's the user's problem, not the skin author's.