Download
(243 Kb)
Download
Updated: 07-17-14 09:44 PM
Pictures
File Info
Compatibility:
Siege of Orgrimmar (5.4)
Escalation (5.3)
Thunder Isle (5.2)
Landfall (5.1)
Mists of Pandaria (5.0.4)
Updated:07-17-14 09:44 PM
Created:12-03-08 06:08 PM
Downloads:61,833
Favorites:749
MD5:
5.4
DockingStation (Display)  Popular! (More than 5000 hits)
Version: 0.5.2 (Beta)
by: Vrul [More]
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.
Version 0.5.2 Beta (07/17/2014)
- Correct an issue with panels not staying where they should

Version 0.5.1 Beta (06/07/2014)
- Fix for an error that was occurring when upgrading a version older than 0.4 and with new installations

Version 0.5 Beta (05/24/2014)
- Library update

Version 0.4.15 Beta (09/27/2012)
- Library update to fix a potential error

Version 0.4.14 Beta (09/11/2012)
- Fix for some undesired interactive tooltip behavior

Version 0.4.13 Beta (09/02/2012)
- Updated for MoP

Version 0.4.12 Beta (07/06/2012)
- Updated for MoP Beta

Version 0.4.11 Beta (01/31/2012)
- Traditional Chinese localization 繁體中文化 by andy52005

Version 0.4.10 Beta (12/22/2011)
- Make sure all tooltips are clamped to screen

Version 0.4.9 Beta (12/21/2011)
- Fix for GameTooltip type tooltips

Version 0.4.8 Beta (12/19/2011)
- Attempt at allowing plugins that create tooltips via OnEnter/OnLeave to be scaled and reanchored

Version 0.4.7 Beta (11/27/2010)
- Fix for error when enabling/disabling an unloaded plugin

Version 0.4.6 Beta (10/13/2010)
- Libraries updated

Version 0.4.5 Beta (09/11/2010)
- Added the option to override a plugin provided label with it's name

Version 0.4.4 Beta (07/19/2010)
- Corrected a potential issue with generating panel keys
- Updated to use the new AceGUI-3.0-SharedMediaWidgets
- Minor code tweaks

Version 0.4.3 Beta (06/10/2010)
- Fix for panel positioning bug

Version 0.4.2 Beta (06/10/2010)
- Added localization support
- Corrected an issue with ConfigMode support
- Modified the behavior of the icon zoom option
- Convert.lua may now be deleted (only needs to run once each update)

Version 0.4.1 Beta (06/02/2010)
- Fixed issue with icon updates (iconCoords, iconR, iconG, iconB)

Version 0.4 Beta (05/31/2010)
- Major overhaul

Version 0.3.3 Beta (12/11/2009)
- Added MMOUI Minion support to TOC file (X-WoWI-ID)
- Library update (fixes buff frame not moving with other Blizzard frames)

Version 0.3.2 Beta (05/24/2009)
- Corrected an issue with plugins that define their type after their data object is first created
- Fixed a bug with the report option not properly hiding errors/warnings when disabled

Version 0.3.1 Beta (05/23/2009)
- The configuration window now remains centered when the panel/plugin lists are added on the side, this can be disabled with the option DockingStation-General-Center Configuration

Version 0.3 Beta (05/23/2009)
- LDB type is no longer defaulted to 'data source' if none given
- Most duplicate errors/warnings are now ignored
- Changed the way panel labels are templated
- Reworked how panels and plugins are selected in the options panel

Version 0.2.26 Beta (05/08/2009)
- Fixed a bug with panel visibility
- Updated libraries

Version 0.2.25 Beta (05/08/2009)
- Fixed a bug with panel visibility
- Changed the minimum values for panel height and width (from fixed to 1/64 of screen height and width)
- Changed the maximum value for panel height (from fixed to 1/16 of screen height)
- The options for panel height and width (Appearance) now update all min/max values instead of just max panel width on a resolution change

Version 0.2.24 Beta (04/28/2009)
- Corrected some issues with changing profiles
- Fixed an error with opening the configuration panel
- Changed the OnClick handler to better deal with other LDB displays
- Added an option to allow right clicking on a panel to open it's configuration
- Warnings are no longer generated for unsupported LDB types
- Warnings are now generated for any 'launcher' using 'data source' specific fields: text, value, suffix
- Panel tooltips are now only shown while one of DockingStation's configuration panels is open

Version 0.2.23 Beta (04/24/2009)
- More tooltip corrections

Version 0.2.22 Beta (04/23/2009)
- Taking a shot at the vanishing tooltip issue

Version 0.2.21 Beta (04/23/2009)
- Added more options for panel backgrounds

Version 0.2.20 Beta (04/21/2009)
- Fixed an issue with some string settings

Version 0.2.19 Beta (04/20/2009)
- Better support for shared media
- Trying out a new library for easier LoD options

Version 0.2.18 Beta (04/18/2009)
- Corrected an issue with panels anchored outside the screen's bounds

Version 0.2.17 Beta (04/16/2009)
- Fix for panels moving from their positions on a reload

Version 0.2.16 Beta (04/16/2009)
- Changed tooltip hiding options slightly
- Tooltip scaling is now off by default
- Enabling the report option now also provides error information for previously hidden execution problems

Version 0.2.15 Beta (04/13/2009)
- Added an option for disabling tooltip scaling
- OnMouseWheel support enabled

Version 0.2.14 Beta (04/12/2009)
- More tooltip fixes

Version 0.2.13 Beta (04/09/2009)
- Fix for plugins that call their own OnEnter function internally

Version 0.2.12 Beta (04/09/2009)
- Added panel fading
- More tooltip fixes

Version 0.2.11 Beta (03/26/2009)
- Corrected a bug with tooltip settings that are set to default
- Fixed some issues with tooltip scaling

Version 0.2.10 Beta (03/19/2009)
- Corrected a display issue with panel labels
- Fixed a bug with plugins appearing behind their panel
- Deleting a panel that contains plugins should no longer generate errors
- Fixed an issue with tooltip behavior (still not completely fixed though)

Version 0.2.9 Beta (03/18/2009)
- Changed panel labels to only show up if the Panels or Plugins configuration screen is open
- Configuration options are now visible in the Blizzard options panel for addons before being loaded
- Corrected some tooltip behavior (still not completely fixed yet)

Version 0.2.8 Beta (03/15/2009)
- Fixed a tooltip bug

Version 0.2.7 Beta (03/14/2009)
- Changed how and when setting inheritance takes place
- Added and changed tooltip options
- Revamped the way panels and plugins are locked

Version 0.2.6 Beta (03/13/2009)
- Fixed another bug with converting old settings to the new launcher name
- Changed the way panel labels are handled (old settings are no good)
- Corrected an issue when enabling plugins or changing their location via the configuration settings

Version 0.2.5 Beta (03/11/2009)
- Fixed a bug with converting old settings to the new launcher name
- Added the ability to change panel labels for easier identification
- Changed creating a panel to automatically select the settings for the new panel

Version 0.2.4 Beta (03/10/2009)
- Renamed the launcher to DockingStation_Config to avoid issues with LoD and other LDB displays that add plugin options directly to Blizzard's option panel
- Moved AceDBOptions-3.0.lua to DockingStation_Config to make it LoD
- Added the ability to edit/remove settings of plugins that are not loaded

Version 0.2.3 Beta (01/28/2009)
- Corrected an issue with plugins not inheriting their panel's settings properly upon creation

Version 0.2.2 Beta (01/22/2009)
- Fixed a bug with settings when creating a new panel

Version 0.2.1 Beta (01/21/2009)
- Changed the way plugins are updated in a panel
- Fixed a bug with the center section of panels not always staying centered
- Reverted some changes dealing with plugin strings while tracking down a bug

Version 0.2 Beta (01/20/2009)
- Reworked some high CPU usage code to require much less processing
- Added options to disable showing tooltips in combat and to allow for a small portion of panels to be moved off-screen

Version 0.1.2 Beta (01/19/2009)
- Changed the minimum value allowed for Panel Background Inset from 0 to -1 to help with the "gap" problem

Version 0.1.1 Beta (01/14/2009)
- Added a slash command (/dockingstation) that opens the configuration panel
- Corrected bugs with panel anchoring and ordering
- Load on demand for configuration is now functioning properly

Version 0.1 Beta (01/12/2009)
- Configuration is now load on demand and some options were added/changed
- DockingStation's launcher is now a true LDB plugin instead of only being available to itself
- Panels are now at different levels based on the most recently moved (persistant)

Version 0.0.25 Beta (12/23/2008)
- Fixed some bugs with options and their defaults

Version 0.0.24 Beta (12/19/2008)
- Added options for placing borders on panels
- Added support to get panel frame references
- Updated to the lastest plugin spec: iconCoords (4 or 8), iconB, iconG, iconR

Version 0.0.23 Beta (12/18/2008)
- Added an option to apply an outline or shadow to the various text elements

Version 0.0.22 Beta (12/17/2008)
- Added code to correct a LibDataBroker bug
- Fix for an issue with OnClick handlers

Version 0.0.21 Beta (12/12/2008)
- Fixed an issue with dragging and dropping plugins into the "Right" section of a panel
- Fixed an error with tooltips for some plugins
- Removed most restrictions placed on plugins

Version 0.0.20 Beta (12/11/2008)
- Fixed a bug with zeroes being removed from either ends of strings
- Fixed an error where a plugin in the process of being moved would jump back into place if it or another addon in the same panel/section was updated
- Added a new option to show warnings/errors generated during the creation of new plugins

Version 0.0.19 Beta (12/10/2008)
- Uncommented the code that broke the UI scale fix from 0.0.17 (Oops)

Version 0.0.18 Beta (12/10/2008)
- Fixed a bug with panels not always deleting properly
- The plugin type 'data source' now accepts either the field text or value, instead of just text, for initial type verification

Version 0.0.17 Beta (12/09/2008)
- Fixed a bug when utilizing the UI scale video setting
- Ability to set default settings for panel plugins and panels and plugins in general
- Can now turn off the icon for 'launchers' if the label is still showing

Version 0.0.16 Beta (12/08/2008)
- Fixed a bug with plugin label/suffix using the option "Same as Text"
- Changed the disply of panel options
- Added the option to change the panel background texture
- Plugins now listed by label (name also shown once selected if different from label)

Version 0.0.15 Beta (12/07/2008)
- Changed the way plugin options are displayed

Version 0.0.14 Beta (12/05/2008)
- More options for plugins added

Version 0.0.13 Beta (12/03/2008)
- Initial public beta release
Optional Files (0)


Archived Files (17)
File Name
Version
Size
Author
Date
0.5.1 (Beta)
240kB
Vrul
06-07-14 07:06 AM
0.5 (Beta)
240kB
Vrul
05-24-14 02:19 PM
0.4.15 (Beta)
240kB
Vrul
09-27-12 02:59 PM
0.4.14 (Beta)
238kB
Vrul
09-11-12 10:19 PM
0.4.13 (Beta)
238kB
Vrul
09-02-12 04:46 PM
0.4.12 (Beta)
173kB
Vrul
07-06-12 10:58 AM
0.4.11 (Beta)
171kB
Vrul
01-31-12 05:10 PM
0.4.10 (Beta)
166kB
Vrul
12-22-11 05:09 AM
0.4.9 (Beta)
166kB
Vrul
12-21-11 07:14 PM
0.4.8 (Beta)
166kB
Vrul
12-19-11 06:29 PM
0.4.7 (Beta)
165kB
Vrul
11-27-10 10:58 PM
0.4.6 (Beta)
164kB
Vrul
10-13-10 02:48 PM
0.4.5 (Beta)
162kB
Vrul
09-11-10 07:29 PM
0.4.4 (Beta)
161kB
Vrul
07-19-10 09:43 PM
0.4.3 (Beta)
157kB
Vrul
06-10-10 10:03 PM
0.3.3 (Beta)
147kB
Vrul
12-11-09 01:20 AM
0.2.26 (Beta)
133kB
Vrul
05-08-09 07:54 PM


Post A Reply Comment Options
Old 12-16-08, 10:11 AM  
Vrul
A Chromatic Dragonspawn
 
Vrul's Avatar
AddOn Author - Click to view AddOns

Forum posts: 194
File comments: 230
Uploads: 24
Originally posted by Seiyu
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.
I know what the problem with this is. The author is using CastSpellByName which only works if used within an OnClick handler (not sure if that's a bug or not). I'm only using generic frames at the moment which don't have OnClick handlers so I'm trying to find a work around that doesn't involve using Buttons over Frames. Switching to a Button type does fix the problem (I did make a temp change to verify) but I'm not happy with that solution and I'm testing a couple other things before going that route.
Vrul is offline Report comment to moderator  
Reply With Quote
Old 12-16-08, 10:05 AM  
Vrul
A Chromatic Dragonspawn
 
Vrul's Avatar
AddOn Author - Click to view AddOns

Forum posts: 194
File comments: 230
Uploads: 24
Originally posted by Phanx
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.
This will be in the next version.

Originally posted by Phanx
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)
Since you are using standalone libraries are you using the most recent version of LDB? Revision 4 added the method that is returning nil for you. I'm still not sure how it would work even changing the line to pairs though, as LDB nils out the fields in the original table (now just a proxy) and keeps it all internally so that it can use __newindex to detect changes and fire callbacks. I've only used revision 4 so I don't know if NewDataObject was coded different in earlier versions to where it didn't nil out the data.

Originally posted by Phanx
Well, I see the "type" field as primarily being useful for specialized display addons that only want to show one or the other.
I understand that. What I'm saying is that it could easily be done with just the one type. A display can see that a DO is just a 'launcher' by looking at the text/value fields. But seeing how that could lead to a bit of overhead on the display's part, a simple field 'launcher' set to any value but nil or false would suffice. That was how it was being handled, if only briefly and by only a few, but it worked. Just because the first person to set it down in writing choose to make two seperate types doesn't mean that was the only way it could be done, or even the best way to do it. And no, I'm not suggesting that it be changed now.
Vrul is offline Report comment to moderator  
Reply With Quote
Old 12-15-08, 10:43 PM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3986
File comments: 1913
Uploads: 38
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.

Originally posted by Vrul
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.
If a plugin author is intentionally misusing or omitting fields in an attempt to force his or her personal preference on users, the author is wrong, and you shouldn't waste your time and effort going out of your way to coddle and cater for authors who do this.

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.

Originally posted by Vrul
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.
Possible, but with 25-30 data objects, it's unlikely that none of them follow the spec. In fact, I know at least three of them follow the spec exactly, as I wrote them myself. I'll give the new version a try and look for the errors.

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 04:19 AM.
Phanx is offline Report comment to moderator  
Reply With Quote
Old 12-15-08, 01:00 AM  
Seiyu
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 34
Uploads: 2
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 is offline Report comment to moderator  
Reply With Quote
Old 12-14-08, 02:01 PM  
Vrul
A Chromatic Dragonspawn
 
Vrul's Avatar
AddOn Author - Click to view AddOns

Forum posts: 194
File comments: 230
Uploads: 24
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 is offline Report comment to moderator  
Reply With Quote
Old 12-14-08, 12:23 PM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3986
File comments: 1913
Uploads: 38
Originally posted by Vrul
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.
They are separate because many people (including myself) do not ever want to see useless "minimap buttons" (a.k.a. "launcher" objects) cluttering up our displays, but don't want to have to deal with manually turning them off every time we install a new addon that has one. This also allows "launcher displays" that work like MinimapButtonBag, and show only launcher icons. I'm not sure how anyone's "tastes" should cause any issues with this -- if your data feed exists primarily to be clicked on to open windows or perform actions, it's a "launcher"; otherwise, it's a "data source". If addon authors are labelling their data feeds improperly, that's their problem to fix, not yours.

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 is offline Report comment to moderator  
Reply With Quote
Old 12-12-08, 10:13 PM  
Vrul
A Chromatic Dragonspawn
 
Vrul's Avatar
AddOn Author - Click to view AddOns

Forum posts: 194
File comments: 230
Uploads: 24
Originally posted by motzky
Tooltips created via Tablet-2.0 don't always show on DockingStation.
I think this is fixed now.

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 is offline Report comment to moderator  
Reply With Quote
Old 12-12-08, 10:38 AM  
Vrul
A Chromatic Dragonspawn
 
Vrul's Avatar
AddOn Author - Click to view AddOns

Forum posts: 194
File comments: 230
Uploads: 24
Originally posted by Torhal
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.
Spent several hours trying to find any problem as I could make as many different colors as I wanted while testing. The display mod in that screen shot uses the yellow color as its default text color where as DockingStation uses white as its default text color. So when a plugin doesn't specify a color its up to the display as to what it will be and Broker_Factions doesn't specify a color for that last section of text.
Last edited by Vrul : 12-12-08 at 10:38 AM.
Vrul is offline Report comment to moderator  
Reply With Quote
Old 12-12-08, 08:15 AM  
motzky
A Kobold Labourer
 
motzky's Avatar

Forum posts: 0
File comments: 4
Uploads: 0
Originally posted by Torhal
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.
It works for me exactly as it should. Faction's name is colored by hostility, status by standing and numbers in text color I set in options...

Maybe you're monitoring a faction you're neutral with ?
motzky is offline Report comment to moderator  
Reply With Quote
Old 12-11-08, 05:10 PM  
Torhal
A Pyroguard Emberseer
 
Torhal's Avatar
AddOn Author - Click to view AddOns

Forum posts: 1026
File comments: 196
Uploads: 28
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 is online now Report comment to moderator  
Reply With Quote
Old 12-11-08, 05:01 PM  
Diungo
A Kobold Labourer

Forum posts: 0
File comments: 7
Uploads: 0
Fubar2Broker

this patch:
PHP Code:
--- FuBar2Broker.lua.old    2008-11-11 07:08:08.000000000 +0100
+++ FuBar2Broker.lua    2008-12-12 00:54:27.125000000 +0100
@@ -132,28 +132,46 @@
     
local name addon:ToString()
     
local brokerIcon addon.icon or addon.hasIcon
     local brokerPlugin
-    local launcher = (not (addon.OnTextUpdate or addon.UpdateText ~= FuBarPlugin.UpdateText) or quickLaunchers[name]) and "launcher"
     
if brokerIcon then
         
if type(brokerIcon) ~= "string" then
             brokerIcon 
"Interface\\AddOns\\"
         
end
     end
-    brokerPlugin broker:NewDataObject(name, {type launchericon brokerIconlabel nametocname folderNames[addon]})
+    
+    
local ldbPrototype = {
+        
icon brokerIcon,
+        
label name,
+        
tocname folderNames[addon],
+        
+        
OnClick = function(framebutton)
+            if 
button == "RightButton" and addon.OnMenuRequest then
+                FuBarPlugin:OpenMenu(frameaddon)
+            elseif 
button == "MiddleButton" and addon.OnDoubleClick then
+                addon.OnDoubleClick(addonbutton)
+            elseif 
addon.OnClick then
+                addon.OnClick(addonbutton)
+            
end
+        end,
+    }
+    
+    if 
quickLaunchers[name] or not (addon.OnTextUpdate or addon.UpdateText ~= FuBarPlugin.UpdateTextthen
+        ldbPrototype.type "launcher"
+    else
+        
ldbPrototype.type "data source"
+        ldbPrototype.text "FubarPlugin"
+    end
+    brokerPlugin broker:NewDataObject(nameldbPrototype)
+    
DEFAULT_CHAT_FRAME:AddMessagename .. " LOADED" )
+    
+    
     
brokerPlugins[addon] = brokerPlugin
         
     addon
:SetIcon(addon.icon or addon.hasIcon)
     
-    
brokerPlugin.OnClick = function(framebutton)
-        if 
button == "RightButton" and addon.OnMenuRequest then
-            FuBarPlugin:OpenMenu(frameaddon)
-        elseif 
button == "MiddleButton" and addon.OnDoubleClick then
-            addon.OnDoubleClick(addonbutton)
-        elseif 
addon.OnClick then
-            addon.OnClick(addonbutton)
-        
end
-    end
     
     brokerPlugin
.OnEnter = function(frame)
+        
DEFAULT_CHAT_FRAME:AddMessagename .. " OnEnter" )
+        
         
addon.frame frame
         
if not addon.blizzardTooltip and not tablets[framethen
             FuBarPlugin
:TabletRegister(frameaddon)
@@ -
164,11 +182,13 @@
     
end
     
     brokerPlugin
.OnLeave = function(frame)
+        
DEFAULT_CHAT_FRAME:AddMessagename .. " OnLeave" )
+        
         if 
addon.blizzardTooltip then
             GameTooltip
:Hide()
         
end    
     end
-    
+        
     
addon.UpdateTooltip = function()
         if 
currentTip[addon] and ((addon.blizzardTooltip and GameTooltip:GetOwner() == currentTip[addon] or not addon.blizzardTooltip)) then
             FuBarPlugin
:OpenTooltip(currentTip[addon], addon
lets fubar2broker somewhat work with dockingstation. neither tooltips nor rightclick-menus work, though they do work when testing with fortress. any ideas?
Diungo is offline Report comment to moderator  
Reply With Quote
Old 12-11-08, 02:49 PM  
motzky
A Kobold Labourer
 
motzky's Avatar

Forum posts: 0
File comments: 4
Uploads: 0
Originally posted by Vrul
If you could provide the name of an addon or two that you are using with messed up tooltips that would help. [/b]
Plugins not always showing Tooltip are:
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 02:50 PM.
motzky is offline Report comment to moderator  
Reply With Quote
Old 12-11-08, 12:08 PM  
dwex
A Fallenroot Satyr
AddOn Author - Click to view AddOns

Forum posts: 20
File comments: 91
Uploads: 3
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 is offline Report comment to moderator  
Reply With Quote
Old 12-11-08, 11:18 AM  
Vrul
A Chromatic Dragonspawn
 
Vrul's Avatar
AddOn Author - Click to view AddOns

Forum posts: 194
File comments: 230
Uploads: 24
Originally posted by motzky
As of 0.0.19 text strings starting or ending with "0" get that zero truncated.
This should be fixed in the new version.

Originally posted by motzky
it would be nice to have a list of the rejected plugins (and perhaps the reason)
This is added in the new version.

Originally posted by motzky
I started porting my favorite Fubar plugins to LDB and noticed that Tooltips created via Tablet-2.0 don't always show on DockingStation.
I'm still looking into this. If you could provide the name of an addon or two that you are using with messed up tooltips that would help.
Vrul is offline Report comment to moderator  
Reply With Quote
Old 12-11-08, 11:12 AM  
OarisJM
A Murloc Raider

Forum posts: 4
File comments: 28
Uploads: 0
Vrul, the scale in the current version (0.0.19) now works great and the bar extends fully across the screen, thank you!

More Broker plugins that don't seem to be recognized by DS: Bagsy, Broker_Extractor, Broker_Mail, Broker_TradeCooldowns, TheTravellersReference. These all worked fine in Fortress fref. Some of these can be replaced easily, but some can't, so that makes me qq. Some other random things:

- DS is overriding the 'hide monitored faction' setting of Broker_Factions (Fortress did not).
- DS seems unable to hide both Violation texts blocks.
- The Omen and Violation icons/texts reset size every time on reload (I thought it might be a problem with mods that weren't really built for Broker, but AtlasLoot's icon works ok, and I don't use any FuBar2Broker stuff). Pretty much changing and changing back any setting in DS will fix this problem.
- On most of the mods, toying with the suffix options doesn't do anything except move the text left slightly to over the icon.
- Changing the general plugin default to hide the label does not actually cause activated plugins to hide their labels before or after changing that setting, it still needs to be done manually.

I know you're still in beta, and you probably know about all of this, just passing it along just in case, hopefully I'm not too annoying. I love your mod, LDB has been needing a true bar mod so desperately, and it's really mostly usable already.
OarisJM is offline Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: