Transparently creates LDB ("LibDataBroker") feeds from all of your FuBar plugins so that they can be shown on LDB displays of your choice instead of on FuBar.
See this forum thread for general info on LDB.
Usage
FuBar2Broker is meant to be completely transparent. If FuBar2Broker is running, you should see LDB feeds for all of your loaded FuBar plugins listed in your LDB display(s).
NOTE: Many FuBar plugins require an actual addon named "FuBar" to load as a dependency, and will refuse to load if it is not present. Use this miniature FuBar stub to make them work with FuBar2Broker! If you use an automatic addon updater, make sure to also set it to ignore the miniature FuBar stub (or else it might "update" it to the real FuBar and mess things up for you as a result!).
Known Issues
Some FuBar plugins (such as NRT) expect you to double-click them to perform certain actions, but double-clicking does not seem to be handled in a compatible way by LDB. As a workaround, FuBar2Broker currently allows you to simulate double-clicks by clicking the middle mouse button instead.
Also, FuBarPlugin-3.0 based plugins such as FuBar_PerformanceFu and FuBar_DurabilityFu will not be converted to LDB plugins by FuBar2Broker because F2B works by acting as a FuBarPlugin-2.0 dummy library. Most FuBarPlugin-3.0 plugins that I know of have decent LDB-based alternatives though.
Bug Reports
If you have any issues, please report them in the FuBar2Broker forum thread and/or create a ticket in FuBar2Broker's WowAce ticket tracker.
------------------------------------------------------------------------
r82 | hunterz | 2009-05-03 20:36:09 +0000 (Sun, 03 May 2009) | 2 lines
Changed paths:
M /trunk/FuBar2Broker.lua
- create OnDoubleClick() handler method in the broker plugin, even though no displays that I know of implement double-click functionality
- also log a warning to the default chat frame if a FuBar plugin has an OnDoubleClick() handler to inform the user of the already existing middle-click -> double-click hack
------------------------------------------------------------------------
r81 | zuz666 | 2009-05-03 10:05:04 +0000 (Sun, 03 May 2009) | 1 line
Changed paths:
M /trunk/.pkgmeta
- enable nolib creation
------------------------------------------------------------------------
r80 | zuz666 | 2009-05-03 09:44:37 +0000 (Sun, 03 May 2009) | 1 line
Changed paths:
M /trunk/FuBar2Broker.toc
- more accurate nolib support
------------------------------------------------------------------------
r79 | hunterz | 2009-05-03 07:21:03 +0000 (Sun, 03 May 2009) | 1 line
Changed paths:
M /trunk/FuBar2Broker.lua
- Only call FuBarPlugin:UpdateText() from FuBarPlugin:Update() if plugin is a data source rather than a launcher (fixes DockingStation warnings). This shouldn't hurt anything since F2B was only setting the text to the plugin name for launchers anyways.
------------------------------------------------------------------------
r77 | hunterz | 2009-04-26 05:04:48 +0000 (Sun, 26 Apr 2009) | 1 line
Changed paths:
M /trunk/FuBar2Broker.toc
- Bump toc for 3.1
------------------------------------------------------------------------
r76 | hunterz | 2009-01-31 05:58:25 +0000 (Sat, 31 Jan 2009) | 3 lines
Changed paths:
M /trunk/FuBar2Broker.lua
- Warn user and abort if a Broker plugin cannot be created, especially if it's due to one already existing with the desired name (seems to be happening a lot lately with addons that try to natively provide both FuBar and Broker plugins).
- Note that the reverse case may still occur, in which an addon creates a FuBar plugin first that gets handled by FuBar2Broker, *then* an attempt is made to create a native Broker plugin. In this case, LDB will allow the FuBar2Broker-provided plugin and block creation of the native one, which is bad but can't be addressed at the FuBar2Broker level.
------------------------------------------------------------------------
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP has a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...
