Go to Page... |
Compatibility: | Shadowlands patch (9.0.2) Shadowlands pre-patch (9.0.1) |
Updated: | 12-20-20 05:30 PM |
Created: | 12-03-08 07:08 PM |
Downloads: | 92,323 |
Favorites: | 752 |
MD5: |
A display platform for LibDataBroker (LDB) based plug-ins. The display is provided through panels, each having sections (Left, Center, Right) corresponding with how a plugin is justified within it.
All plugins are disabled by default and you must turn on the ones you want to use. This is to avoid the complete mess that results from all plugins being on with the first use. The only plugin on at the start is the one provided by this addon to access its options easily. Just click it to start changing settings.
With plugins unlocked you can drag and drop them to other panels/sections and have them automatically adjust to their new location. There are no limitations on the drag and drop capabilities other than the new location for a plugin must be within a panel. You may also change the location of a plugin through the plugin options menu.
Almost all sub-sections of settings have a default option. The defaults follow a set pattern. First plugins check their settings, if default, they next go to their panel's settings. If the panel is also set to default then it defers to the addon's global settings. Finally, if the global settings are still set to default, then the hard coded defaults are used.
Note: It is recommended that you delete the folder(s) for an existing addon when updating to a different version. This is to keep files that are no longer used from taking up space.
Translators: To submit a translation please just edit existing files (example: DockingStation\Locales\deDE.lua and DockingStation_Config\Locales\deDE.lua) and send them to me.
Comment Options |
OarisJM |
View Public Profile |
Send a private message to OarisJM |
Find More Posts by OarisJM |
Add OarisJM to Your Buddy List |
Vrul |
View Public Profile |
Send a private message to Vrul |
Find More Posts by Vrul |
Add Vrul to Your Buddy List |
12-11-08, 01:08 PM | |
|
FuBar Replacement?
I saw people talking about DockingStation being a replacement for FuBar. Does DockingStation include the movement of default UI elements to place the bars at top/bottom as FuBar and Titan do? Or is DockingStation just an LDB container, with which I'd need to use something like DummyBar to have a complete solution?
Looks like I may finally be near an LDB-based FuBar replacement. Thanks much. |
|
dwex |
View Public Profile |
Send a private message to dwex |
Find More Posts by dwex |
Add dwex to Your Buddy List |
12-11-08, 03:49 PM | ||
|
Broker_SocialState ZOMGBuffs I made no changes to Broker_SocialState, but: Original ZOMGBuffs plugin creation code is not correct, so at first the plugin isn't showing at all... Here is what I did to make the Plugin valid: The Plugin itself has a label and an OnClick-Handler (provieded 2 lines below NewDataObject() ), so 1. I changed type to "launcher" and 2. moved the OnClick-Handler to the NewDataObject() function.
Last edited by motzky : 12-11-08 at 03:50 PM.
|
|
|
motzky |
View Public Profile |
Send a private message to motzky |
Find More Posts by motzky |
Add motzky to Your Buddy List |
12-11-08, 06:01 PM | |
A Kobold Labourer
Forum posts: 0
File comments: 7
Uploads: 0
|
Fubar2Broker
this patch:
PHP Code:
|
|
Diungo |
View Public Profile |
Send a private message to Diungo |
Find More Posts by Diungo |
Add Diungo to Your Buddy List |
12-11-08, 06:10 PM | |
|
DockingStation breaks DO text coloration. For an example, look at the screenshots for Broker_Factions. The text has three separate colors in it, but is white after the first color when displayed on DockingStation.
|
|
Torhal |
View Public Profile |
Send a private message to Torhal |
Find More Posts by Torhal |
Add Torhal to Your Buddy List |
12-12-08, 09:15 AM | ||
|
Maybe you're monitoring a faction you're neutral with ? |
|
|
motzky |
View Public Profile |
Send a private message to motzky |
Find More Posts by motzky |
Add motzky to Your Buddy List |
12-12-08, 11:38 AM | ||
|
Last edited by Vrul : 12-12-08 at 11:38 AM.
|
|
|
Vrul |
View Public Profile |
Send a private message to Vrul |
Find More Posts by Vrul |
Add Vrul to Your Buddy List |
12-12-08, 11:13 PM | ||
|
I decided to remove most of the restrictions I placed on plugins since the spec is not really standardized and I don't really agree with some of it anyway. Mostly I don't care what plugins do since I do make sure there is always a label to show so they will all default to that if there is nothing else or everything is turned off in the options (something must be showing). Also, I am now treating both the 'data source' and 'launcher' spec exactly the same. They really shouldn't have been two seperate specs to begin with (imo) and it allows for people with tastes that stray from the original creators to get their way too. Since LDB is a generic library that can be used for much more than plugins, not enforcing things may come back to bite me in the ass. If/when that happens I'll probably enforce the 'type' field and no longer allow for defaulting to a type if not defined. It will then be up to anyone using a plugin that still isn't declaring a type to bug the author to get their shit together. |
|
|
Vrul |
View Public Profile |
Send a private message to Vrul |
Find More Posts by Vrul |
Add Vrul to Your Buddy List |
12-14-08, 01:23 PM | ||
|
That said, I've tried several versions of DockingStation, and have yet to see a single plugin show up, either on the panel itself or in the configuration. The panel appears, and I can configure it just fine, but none of my 25 or so data feeds (most of which are launchers that I don't want to see anyway) seem to be recognized. Any thoughts on why this might be so? |
|
|
Phanx |
View Public Profile |
Send a private message to Phanx |
Find More Posts by Phanx |
Add Phanx to Your Buddy List |
12-14-08, 03:01 PM | |
|
What I meant by there didn't need to be two different specs was that a display could easily tell the difference between a 'launcher' and 'data source' by the fields they used so only one type was really needed. If it really was that important to seperate the two via data, then "they" should've just stuck with the launcher field to indicate such.
Really it comes down to how displays are handling the two types. Basically the type is checked at creation and that's it. From there on the fields are just processed as needed regardless of whether or not they belong to that type or not. Having DockingStation be the sole display mod that isn't doing this just led to lots of "Why does mod X work with plugin Y and your's doesn't?" I had to switch from verifying plugins actually complied with the type they said they were to an anything goes mentality to avoid the hastle. Either way it doesn't really matter that I treat both specs as identical internally. The information is still displayed the same before and after. I just got tired of trying to enforce something I didn't even agree with and after looking through the code of many, many plugins I realized it was pointless to continue trying. As to "tastes," there was mention by someone wanting their 'launchers' to not show an icon but use the label instead. This could be considered a display issue vice plugin issue until you consider the author of a plugin that wants it that way too. The icon field is flagged as required so they must provide one to comply with the spec and thus lose their ability to only use text as they wanted. The other option would be to call it a 'data source' but really be a 'launcher' which defeats the purpose to begin with. This just feeds back into what I said above, and as stated, its just a matter of opinion so I'm not going to force mine on someone by limiting their options. As for plugins not showing up I think by now you figured out why. Until the last version I was strictly enforcing fields flagged as required by the specs. So many plugins don't bother to actually assign data to themselves until after creation that I had to reverse that decision. Either way, there is an option to show why a potential plugin isn't created. This does require a reload to see the errors. |
|
Vrul |
View Public Profile |
Send a private message to Vrul |
Find More Posts by Vrul |
Add Vrul to Your Buddy List |
12-15-08, 02:00 AM | |
|
Overall really happy with the layout options and such, only one caveat. Broker_professions (profession launchers) doesn't seem to work properly. Gives an "Interface action failed because of an AddOn Error" doesn't happen with any other LDB displays I've used in the past.
|
|
Seiyu |
View Public Profile |
Send a private message to Seiyu |
Find More Posts by Seiyu |
Add Seiyu to Your Buddy List |
12-15-08, 11:43 PM | |||
|
Well, I see the "type" field as primarily being useful for specialized display addons that only want to show one or the other. For instance, a "minimap button bag" kind of display might want to only show launchers, without the user having to go through and turn off everything that isn't a launcher. Or a "info ticker" kind of display might want to only show data sources. For an all-in-one, general purpose display like DockingStation, the difference is immaterial, really. While I think LDB should enforce certain rules (i.e. plugins must specify a type, and must provide certain fields depending on their type), it doesn't, and because it doesn't, trying to enforce such rules in a display addon is more hassle than it's worth.
Specifying an icon in no way prevents a display addon from not showing the icon, but not specifying an icon is an extreme annoyance for users who want to only see an icon. By contrast, it doesn't matter if a plugin fails to specify a label and/or text, because LDB will fall back on the data object's internal title in such cases. If an icon isn't specified, there is nothing to fall back on that isn't totally arbitrary and totally useless for users.
Edit: Also, you should add the embedded libraries to the OptionalDeps field in the TOC, so I (and anyone else using standalone libraries) don't have to keep typing them in there by hand every time I download a new version. Edit #2: Loading 0.0.21 (Beta) still doesn't give me any plugins, but it does give me this error: DockingStation-0.0.21 (Beta)\Plugins.lua:143: attempt to call method 'pairs' (a nil value) The line in question reads LDB: pairs (without the space) where it should read just pairs. Fixing this results in most of my plugins being recognized, although only 3 or 4 have their icons recognized; the rest simply will not display an icon through any combination of settings. The plugins in question do specify an icon at the time of their creation, so that shouldn't be an issue.
Last edited by Phanx : 12-16-08 at 05:19 AM.
|
||
|
Phanx |
View Public Profile |
Send a private message to Phanx |
Find More Posts by Phanx |
Add Phanx to Your Buddy List |
12-16-08, 11:05 AM | ||||
|
|
|||
|
Vrul |
View Public Profile |
Send a private message to Vrul |
Find More Posts by Vrul |
Add Vrul to Your Buddy List |
12-16-08, 11:11 AM | ||
|
|
|
|
Vrul |
View Public Profile |
Send a private message to Vrul |
Find More Posts by Vrul |
Add Vrul to Your Buddy List |