Authors CurseForge

Quote from andreasg »

The solution might be .value = {"value1","value"} .suffix = {"suffix1","suffix2"}

Embedded tables won't fire callbacks unless the table itself changes, not the values inside it.

Quote from Funkydude »

Options Proposal

object.optionsType = "AceConfig3"
object.option1 = {}
object.option2 = {}
...etc

Why should the display handle config for the plugin at all? The plugin should just register a panel in Blizzy's UI.

I installed Fortress and some Broker plugins to test it out. Some things I noticed:

- Fortress and all of the Broker addons forcibly embed LDB-1.1 because LDB-1.1 is not on the trunk. LDB really ought to be on the trunk too since trunk addons are using it anyways, exposing the library to the trunk indirectly.

- Having *any* Broker addon enabled prevents a bunch of FuBar addons from loading at all or from operating properly (Bartender3, Skinner, BugSack, nQuestLog, a bunch of others), regardless of whether Fortress or FuBar2Broker are loaded. I suspect this to be an LDB or Broker addons issue.

- Disabling FuBar and enabling Fortress+FuBar2Broker seems to work a lot better.

Quote from Seerah »

This is on purpose, and it is said that it will never be in trunk.

Can you direct me to an explanation?

Quote from HunterZ »

Can you direct me to an explanation?

I use git.

Oh wow, so there will actually be a separate copy of LDB committed to the SVN for each addon that uses it? Ouch, okay.

Why ouch?

Why?

Wait did you just try to link the ideas "normal" and "sane" while talking about svn?

There is no need for the library to be in trunk, or in the svn at all. It opens up many possibilities I simply do not want. Hosting it on git lets me retain the degree of control I want. At the same time, it's trivially easy for someone to create a fork and submit their own commits, without ever having to contact me.

Ah, git. <toddlerlisa> Wave of the future! </toddlerlisa>

I'm not sure if this the appropriate thread to post this or not, but WTH. I created a data object that provides Friend and Guild support (doSocial). I appended a title tag, "DataObject:" much like the existing "Lib:" tag. I figured it might be helpful in keeping data objects organized in the same way. Personally, I don't really care what the tag is called (I just used Data Object since that was the most generic description from the DataBroker wiki). Thoughts?

We will be setting up a "Broker" category on WoWI soon. I personally am naming my plugins pico*

Broker category on WoWI is up. We've already nearly overtaken the "new Titan" section as well. Lawl, when will those Titaners (Titanics?) lern?

Also, made a nice pretty home page on the wiki full of random babbling and crap. Go read it damnit, I spent a good half hour or so writing that damn thing!

Quote from Sano »

I'm not sure if this the appropriate thread to post this or not, but WTH.
I created a data object that provides Friend and Guild support (doSocial).
I appended a title tag, "DataObject:" much like the existing "Lib:" tag.
I figured it might be helpful in keeping data objects organized in the same way.
Personally, I don't really care what the tag is called (I just used Data Object since that was the most generic description from the DataBroker wiki).
Thoughts?

i have some diffs for you, btw. where would you like them?