Authors CurseForge

Quote from durcyn »

It's not feasible. If you want fubarplugin to work as designed, don't use F2B. if you want minimap icons via F2B, use a display that puts things on the minimap. You can't have your cake and eat it too, though, sorry.

It's not feasible to tell FSB to just not collect the addon into an LDB display?
Shouldn't the addon default to the minimap if it's not being collected?

It's not feasible because F2B doesn't supplement the FuBarPlugin library (the thing that renders onto the minimap if FuBar proper isn't found)... it outright REPLACES it. To make minimap possible F2B would have to implement all those little display bits, something which is out of the feature scope of F2B. As has already been said, get someone to make a Broker display addon that renders the plugins as minimap buttons, and have it render the broker plugins you want.

That's really a much better approach anyway, because it's in line with the whole LDB design, it'd support not-fubar LDB feeds, and it's not outright undoing what F2B is trying to do (remove the need for FBP in the first place).

Quote from tekkub »

It's not feasible because F2B doesn't supplement the FuBarPlugin library (the thing that renders onto the minimap if FuBar proper isn't found)... it outright REPLACES it. To make minimap possible F2B would have to implement all those little display bits, something which is out of the feature scope of F2B. As has already been said, get someone to make a Broker display addon that renders the plugins as minimap buttons, and have it render the broker plugins you want.

That's really a much better approach anyway, because it's in line with the whole LDB design, it'd support not-fubar LDB feeds, and it's not outright undoing what F2B is trying to do (remove the need for FBP in the first place).

Oh ho. I didn't realize that the addons still drew on Fubar for MM support.
That's kind of...wonky. =p

Although QuestAnnouncer can support it's MM button with out Fubar, and even that doesn't revert to the MM when it's turned off in the LDB display by SBC.
Is there a way to perhaps send addons like that a message waving it's arms and screaming "DO NOT ENTER GO BACK TO WHENCE YOU'VE COME!" so it just adheres where it normally would?

I don't particularly care, I'm glad to have my BEQL displaying again, and my buttons being collected, or hidden again :3

FPB is the whole motivation for making LDB in the first place. It's a fairly large batch of embeds needed to simply get a minimap button if the user doesn't have FuBar proper to display on. The idea is to provide a much smaller embed for people to use, and at the same time decouple the addon providing data from any one specific display addon.

Yeah that's really weird that FuBar is required for minimap button support; I thought the whole point of various FuBar plugins being able to display instead as minimap buttons was so that people without FuBar could use them. If FuBar is actually required for that then, yeah, it's definitely reasonable for LDB/F2B to not support that functionality.

Now if someone wants to show some plugin addons on, say Fortress, and some on a yet-to-be-implemented minimap button display addon, is there a way to manage which display addon gets to show which plugin addons? It's probably sufficient to make plugins accessible to all display addons and let the user tell each display addon which plugin addons to show or hide.

You're still failing to see the difference between FuBar proper and FuBarPlugin. FBP is the meat of the whole thing, and is embedded in every single plugin that does not ReqDep FuBar proper (most of them). Throw in tablet and dewdrop and all the other libs FBP requires... and it's a hefty bit of code just to get a minimap button that can be moved onto FuBar if it's present.

In all reality, FuBar proper is a "simple" display addon since it's the library embedded in the plugins that does most of the work (granted, that library is embedded in FuBar as well).

=( Any idea how to get bEQLs #/# display back since last commit?

So, who wants to write a minimap button display frontend for LDB, would be the next logical question.

NOT IT!

I considered it with Quikie, but decided to go the SlideBar route instead.

What *I* would like to see in a minimap button addon:
* Single button, no herpes
* Clicking gives a quasi-menu. Don't use Blizzy's menu system, instead render a frame of buttons
* Buttons would, of course, be an icon and a name. Use the dataobject's name or .tocname field to pull in pretty names from the TOC Title field
* Tooltips maybe, toggleable or something I guess
* Name it Blister, in honor of the minimap herpes it's making go away for good

Basically it's just taking Quickie's frame, maing it vertical, adding names, and making it toggleable from a minimap bunnot instead of onhover.

Yea, except opt-in instead of the current standard, "I GIEV YOU A BUTTON AND YOU HAF TO DISABLE IT IF YOU DON'T LIKE HERPES"

Quote from tekkub »

"I GIEV YOU A BUTTON AND YOU HAF TO DISABLE IT IF YOU DON'T LIKE HERPES"

And who does? :p
MBB was horribly flawed anyway, I presume this undertaking would turn out much much better.
For anyone taking up the challenge, look at MBB code as to what NOT to do xD

MBB was a wonderful idea, but horrible execution (if I recall correctly, something about an OnUpdate handler and it eating 3 metric shittonnes of memory?). Plus it's a patchjob hack to fix something that should just be handled in a better way in the first place.

So yea, LDB's launcher spec is an attempt to get people using some sort of standard when it comes to making minimap/fubar/whatever launchers, and giving the user power of how, if at all, it's displayed. Hard part is convincing authors that it's better to NOT give the user a button by default. But I'm hopeful that it'll eventually get adopted, just like the old "Don't tell the user that your addon loaded, they don't care" standard that started way back in Ace1.

FuBar2Broker doesnt work properly with Manufac (the dewdrop menu on left clic doesnt open and there is a report in bug sack) :

[2008/07/12 15:02:43-153-x5]: Manufac-2.0.r55252\Manufac.lua:784: Dewdrop-2.0: Bad argument #2 to `Open' (table or string expected, got nil)
Ace2\AceLibrary\AceLibrary.lua:122: in function <Interface\AddOns\Ace2\AceLibrary\AceLibrary.lua:75>
(tail call): ?:
Dewdrop-2.0-56529 (DewdropLib):2950: in function `Open'
Manufac-2.0.r55252\Manufac.lua:784: in function `OnClick'
FuBar2Broker-1.0\FuBar2Broker.lua:146: in function <Interface\AddOns\FuBar2Broker\FuBar2Broker.lua:142>

Quote from Hjalte »

[2008/07/11 09:48:06-134-x1]: nQuestLog-1.0 r%d.75646\nQuestLogFuBar.lua:147: attempt to index field 'hide' (a nil value)
AceAddon-2.0-57245 (Ace2):484: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:461>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):298: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>

Getting the same error as well. Lands in Bugsack when I startup WoW. Otherwise, F2B is giving me no problems, and I can use nQL just fine, despite the error message.

Quote from tekkub »

NOT IT!

I considered it with Quikie, but decided to go the SlideBar route instead.

What *I* would like to see in a minimap button addon:
* Single button, no herpes
* Clicking gives a quasi-menu. Don't use Blizzy's menu system, instead render a frame of buttons
* Buttons would, of course, be an icon and a name. Use the dataobject's name or .tocname field to pull in pretty names from the TOC Title field
* Tooltips maybe, toggleable or something I guess
* Name it Blister, in honor of the minimap herpes it's making go away for good

Basically it's just taking Quickie's frame, maing it vertical, adding names, and making it toggleable from a minimap bunnot instead of onhover.

You know, if someone get this working. I may actually offer to have their babies <3