Authors CurseForge

There's another kind of texture (or pair of textures, actually) I think would be useful in SharedMedia. That would be textures for minimap masks and minimap borders. This would allow these kinds of textures to be shared among various addons that manipulate the minimap. The minimap mask texture would also benefit from additional metadata describing the shape of the mask, for addons which use it. (If it's impractical to add these kinds of metadata, perhaps texture contributors could agree on a naming convention that implies the mask's shape.)

Edit: I'm rethinking the utility of this now, since there can only ever be one of each texture active at any time. However, it would still facilitate contributions of new textures for minimap addons which supported them.

So maybe I'm missing something (Probably not, but I'll say this for the fun of it)

But the point of embedding icons into text, or sending it between users is because you want to send something static like a spell icon, it's not like fonts or textures where it can actually be useful to let users expand their list beyond what you have.

Theres no reason to make SML support this, if your addon wants support for an icon then add a map with what the default things Blizzard requires, that way you can add something simple like say {foobar} without wasting half of the message on metadata that people without the addon are going to see.

For example, Afflicted will send {spellID} with messages, all Afflicted users have a :AddMessage hook that will call GetSpellInfo on any numbers within {} it finds, if results are returned it replaces it with the texture meta data. It's simple, Afflicted users get spell icons, non Afflicted users get a little bit of meta data that doesn't really hurt (And you can disable sending the icons anyway).

It's not like it's complicated to add your addon to the tag list, all you do is.

table.insert(ICON_LIST, "|TInterface\\TargetingFrame\\UI-RaidTargetingIcon_1:")
ICON_TAG_LIST["foobar"] = #(ICON_LIST)

And there you go, you now can use {foobar} to show the raid icon #1.

nev sums it up pretty well

I already see people whispering me with stupid tags that i cant read because i dont have that specific addon .. oh my, please not

If you're embedding icons it should be simple, and not getting in the way. You're forgetting that everyone sees the meta data, if you're embedding {SML-IconName} thats really not convent to the people who don't have those icon names or the latest SML, on top of the fact that you then hinder the ability to read text instead of improve it.

Your argument is pointless for emotes in Prat, if you want to turn :) into a graphical emote you either need to hook something like SendChatMessage and turn :) into {SML-Smilie} (Which would be so incredibly stupid), or you're hooking something on the end clients side so if it sees :) it just turns it into the graphical emote and bypasses any sort of {SML-*} system you'd come up with, or you're going to add an entry for :) into the default Blizzard stuff so {:)} is automatically parsed and turned into the emote.

If you're seriously going to add {SML-Smilies} for every emote someone uses, even as an option when only Prat users would see the end result, that'd be very stupid given everyone sees it not just Prat users.

Quote from sylvanaar »

Frankly - I dont care if you like or dislike what I do, but spare me the insults. "...even for you".

The smiley was just an example, and i dont feel like providing any more for you to find fault with and/or pick apart, since that is what you appear to be bent on doing.

The point is do we add new ICONS to SML so everyone can use them or not.

So you want to provide icons for SML, but you don't want to provide an actual example as to why they're useful? If you're adding something to a library, an actual reason beyond "Lets do it" is usually helpful.

Quote from OrionShock »

{{IMO }}

this is a good reason to redifine what we use SharedMeida for.

The name Implies that a given addon will make available it's own common graphics / sounds / textures ect to other addons that a user could use elsewhere to make a consistant UI.

So adding Icon support to LSM is a valid and quite relavent point, but it would require a slight restructure of it.

LSM shouldn't have with it any actual media of any sort as it is a libary, it should however provide access to already avaiable ingame material as it does now. It NEEDS have the ability to add ANY type of media to it's repository, be it a texture / status bar, sound, Icon, Picture, ect; The Point is valid.

@Shadowed, your quest to barate another should be overlooked as an angry person out on a witch hunt, the specific use of said media in LSM is not in question. Use of it in Prat is quite irrelavent as it was simply used as an example. One could quite easily, as i understand, use it in a Ace3-OptionsTable as well as any custom UI that is designed or made.

It's far more relevant and consistent to redefine SML and let people register custom types beyond background, border, font, statusbar and sound, saying you want support for something besides {SML-Name} or icons specifically is irrelevant and entirely different from what was asked in the original post, nothing wrong with making more types available for authors in the SharedMedia library

You're argument about berating doesn't even make sense, the specific request in the post is for something like {SML-Name}, not new types.