One-click "enable config mode for all addons"

[Mikk]

Yaknow... after playing WAR, there's one thing I'm missing in WoW: the ability to show everything and make it movable with one single button press.

I'm thinking that we would need to standardize on something very simple where addons can get notifications of "config mode on/off" events. No, this won't be AceEvent, I don't want any bars for non-ace addons.

Maybe something like this:

CONFIGMODE_CALLBACKS = {
["MyAddon"] = MyAddon_OnConfigMode
["OtherAddon"] = OtherAddon_CnfModeHandler
}

i.e. one global table that addons can create if necessary, and then stick an entry in.

Then their registered function pointers would get called with ("ON") or ("OFF") as parameters - nice and extensible if more things are needed.

Example code needed in an addon would be something like:

  CONFIGMODE_CALLBACKS = CONFIGMODE_CALLBACKS or {}
  CONFIGMODE_CALLBACKS["MyAddon"] = function(mode)
    if mode=="ON" then 
      MyAddon.EnableConfigShizzle(true)
    elseif mode=="OFF" then 
      MyAddon.EnableConfigShizzle(false)
    end
  end

Nice and clean.


As for what would actually CALL these? Well, that'd then be entirely open. Someone could write a standalone addon to do it, or integrate it into some other system, or whatever.


Input?


Edit: What I mean by "config mode" is not popping up config dialogs. I mean displaying drag handles.. making things movable.. popping out test bars / dummy message .... making things sizable.. stuff like that. So that you SEE if you're moving something on top of something else without having to hop into the config of every single on-screen addon you have first.

[OrionShock]

I like this idea, but with out a proof of concept enabler addon it wouldn't go very far :\

[Mikk]

It also won't go very far without addons responding to the event, which is why I thought it'd be a good idea to check if my idea is sound, FIRST

[Torhal]

Originally Posted by Mikk

It also won't go very far without addons responding to the event, which is why I thought it'd be a good idea to check if my idea is sound, FIRST

If you code it, they will come. Unless it's a library that shouldn't be a library because it'll only veer be used by a single addon.

Anywho: Nice concept.

[Mikk]

Seerah pointed me at http://www.wowace.com/projects/nshakedown/

It kinda does this already, but only for addons it knows about (it hardcodes calls into them). nShakedown would be one very obvious place to do these callouts from.

[Nemes]

Originally Posted by Mikk

Seerah pointed me at http://www.wowace.com/projects/nshakedown/

It kinda does this already, but only for addons it knows about (it hardcodes calls into them). nShakedown would be one very obvious place to do these callouts from.

I've abandoned wow for war... I haven't even installed wow 3.0...

If you want to take over NShakedown / hack it up / use the OO parts as a skeleton for this, you're most welcome to it.

NShakedown turned into a maintenance nightmare - only about 30% of the addons were done by the respective authors, the rest were done by me, and often broke during updates.

If this enablement code is built into the addons, NShakedown would be much simpler and easier - just build a list of addons that support these methods and call them.

[tenchu]

Would be great if this can get implemented. NShakeDown was awsome I can configure everything with one click.

[egingell]

"standardize" is a scary word amongst programmers. I had a hard enough time making one of my addons work with Khaos.

[Elsia]

I like the idea in principle, but I think in reality most people want: Make some (not all mods) go into config mode. And what people expect in that some-set varies.

A very different but related idea has to do with rapid config of many addons by allowing profile copy/setting for all addons that support acedb profiling. That is something that can be done, will work gracefully for most needs. But I understand that it's a different purpose. The idea here is for intial setup of the UI, this is for rapid propagation of setups (between alts, accounts etc).

[Adirelle]

Rough proof of concept:

Throw in LibDataBroker and LibDBIcon and do :

CONFIGMODE_CALLBACKS = CONFIGMODE_CALLBACKS or {}
local OneButtonConfig = LibStub('LibDataBroker'):New('OneButtonConfig', {
  type = 'launcher',
  state = false,
  OnClick = function(self)
    self.state = not self.state
    for name,callback in pairs(CONFIGMODE_CALLBACKS ) do
      local ok, msg = pcall(callback, state)
      if not ok then geterrorhandler()(msg) end
    end
  end
})
LibStub("LibDBIcon-1.0"):Register("OneButtonConfig", OneButtonConfig, OneButtonConfigDB)
SLASH_ONEBUTTONCONFIG1 = "/onebuttonconfig"
SLASH_ONEBUTTONCONFIG2 = "/obc"
SlashCmdList["ONEBUTTONCONFIG"] = function() OneButtonConfig:OnClick() end