Authors CurseForge

Messing with a toc file might cause the Internet to crash - or the world to end, which pretty much amounts to the same thing. :cool:

Been trying to get Fubar_MicroMenu to work with Fubar2Broker and it seems the first "roadblock" is lack of "CreateBasicPluginFrame" on Fubar2Broker, any of you guys knows how easy/hard that one is to implement?

Quote from JaimSandar

I have slowly been finding LDB plugins to replace their FuBar equivalents, and using Broker2Fubar to display them. The plan was to switch to a LDB display eventually. Although I still have some FuBar plugins I haven't found good replacements for yet, I finally experimented with that using Fubar2Broker r83 and two different displays: ButtonBin and TitanPanel. That worked, for the most part, but I found was that several FuBar plugins indicate "Dependency missing" in the character login AddOns list and won't load. The other FuBar plugins work fine, but not these (that I have tested):

FuBar_DurabilityFu
FuBar_FuXPFu
FuBar_RestFu

Do you have any idea why, and can it be remedied?

Thank you.

See my response to Torhal below. Also, you can find good native LDB plugins that provide the same functionality as the FuBar plugins you listed. For example, I use zBrokerDurability instead of DurabilityFu and AllPlayed instead of RestFu.

Quote from Torhal

It's because of this line in the TOC of those AddOns:

## Dependencies: FuBar

You can either remove that line, or install FuBar Dummy.

Correct, and this is already explained in the project description for FuBar2Broker BTW.

Quote from daf2

Been trying to get Fubar_MicroMenu to work with Fubar2Broker and it seems the first "roadblock" is lack of "CreateBasicPluginFrame" on Fubar2Broker, any of you guys knows how easy/hard that one is to implement?

No, but there's a comparable native LDB alternative from Tekkub: http://www.wowinterface.com/downloads/info9774-picoButtons.html

My suggestion to people having issues with FuBar plugins is to look for LDB alternatives, as there are quite a few now.

I know of picoButtons, thing is it creates individual launchers. So instead of being a small button bar in the corner it takes up most of the bar due to spacing. Only way I see it work would be with a display that allows spacing to be set per plugin...

Ah. Well there are some alternatives discussed here: http://forums.wowace.com/showthread.php?t=14503

What display(s) are you using?

Also, I don't think it would be possible to have a single LDB plugin with multiple buttons that aren't separate launchers, whether done directly in LDB or via FuBar2Broker. The closest thing I could think of would be to make a tooltip/dropdown list of buttons when you mouse over the plugin.

I'm not 100% sure if this is what you mean, but I believe Tekkub's addon MakeRocketGoNow will do what you want.

Not a bad idea, except doesn't MRGN show all launchers and not just ones that you want?

And yeah that's pretty much like what I was thinking, except as a self-contained micro menu plugin and not a generic launcher container.

Also read that thread at (been around this one for a long time to the point of trying to fix it myself now), I basically just wanted to move from Fubar to something LDB since most of the plugins i use these days are LDB but the lack of Fubar_MicroMenu (Vrul's version) makes it a no go for me, I've used this setup for years so I'm pretty unwilling to change it.

The displays i'm trying are ChocolateBar and DisplayDock, as far as i noticed none of them allows individual launcher spacing just a global setting. MakeRocketGoNow would be interesting if itself was a LDB plugin so basically a display within a display (crazy but would work) which i think it's not.

Quote from daf2

MakeRocketGoNow would be interesting if itself was a LDB plugin so basically a display within a display (crazy but would work) which i think it's not.

MRGN's description isn't very clear, but that's exactly what it is. It acts as a display that is wrapped up in a plugin, so that you end up with an MRGN icon on your primary LDB display, which when clicked will show a list of icons for all of your LDB plugins that are designated as launchers.

I really thought rocket was just a mini launcher bar, still, the way it works is by showing a new panel when clicked instead of on the bar itself like Fubar_MicroMenu.

Ideally i'd re-write Fubar_MicroMenu as a LDB but tbh i don't know enough to do it yeat so the stop gap option seems to implement the missing function in Fubar2Broker to make it work, at first glance it seems doable but I kind wanted your opinion before wasting days banging my head against it :)

Quote from daf2

Ideally i'd re-write Fubar_MicroMenu as a LDB but tbh i don't know enough to do it yeat so the stop gap option seems to implement the missing function in Fubar2Broker to make it work, at first glance it seems doable but I kind wanted your opinion before wasting days banging my head against it :)

Even if that particular function was supported you will just run into more issues with it out of the equation. The next obstacle would be that no current LDB display supports multiple icons for one data feed so no matter what you are stuck creating a seperate launcher for each icon you want implemented.

Another hurdle is that the character, pvp, and game menu icons are two textures together which is also not currently supported. You could ignore one of the textures for the first two but can't for the game menu icon without losing the latency coloring. This may not be a concern for what you want but I'm mentioning it just in case.

...or you could create separate LDB objects with a custom, common .type, then make an LDB "wrapper" like MRGN that will grab that specific type and create an icon panel.

I think the best you could do with LDB is have a custom plugin similar to MRGN that just opens a dropdown/tooltip/panel with each of the micro menu buttons on it.

The problem, as others have said, is that LDB only allows one icon per plugin/launcher. The only way to truly implement a single multi-button-on-panel plugin in LDB would be to make a new .type that defines multiple buttons and then get every display author to implement support for displaying that .type.

I see, so Fubar actually allowed this (since Fubar_MicroMenu works) but LDB doesnt... I've been thinking of some "solutions" but mostly would end up being hacks. So a new .type (whatever that entails) or simply a display bar that sets spacing per plugin instead of a global setting, DisplayDock does it by section so by plugin might not be such a stretch, will need to ask nicely :)

That just makes the buttons bigger, it really doesn't resolve the spacing between them, pictures bellow :)

Fubar:


Chocolate:

Quote from HunterZ

...you can find good native LDB plugins that provide the same functionality as the FuBar plugins you listed. For example, I use zBrokerDurability instead of DurabilityFu and AllPlayed instead of RestFu.

One thing that DurabilityFu does that I haven't seen in the description for zBrokerDurability or other similar mods is to optionally either 1) pop up a prompt to repair when visiting a vendor that can repair or 2) automatically repair when at the vendor. If the zBroker version did that, I would switch. If zBrokerDurability DOES do that, I wish I had known about it.

Also, I haven't found a broker plugin that compares to GarbageFu. Once again, if there is one or are some broker versions of trash dumper/sellers that have the options I like in GarbageFu (sell button on vendor frame, exception list, dump item from bar icon, etc.) I sure don't know about it.

Those are the last two FuBar plugins I really care about. If I could find satisfactory replacements for those, I would be getting rid of FuBar for good.
Thank you.