[2008/07/06 16:49:38-2437-x1]: Broker_Clock-1.0\Broker_Clock.lua:1: Cannot find a library instance of "LibDataBroker-1.1".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
Broker_Clock-1.0\Broker_Clock.lua:1: in main chunk
happens for Clock, Durability and Mail. PvP and Sysstats are working for me.
[2008/07/06 16:49:38-2437-x1]: Broker_Clock-1.0\Broker_Clock.lua:1: Cannot find a library instance of "LibDataBroker-1.1".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
Broker_Clock-1.0\Broker_Clock.lua:1: in main chunk
happens for Clock, Durability and Mail. PvP and Sysstats are working for me.
Confirming this. FYI I am pulling from the trunk.
Is there a thread we should take this to, for errors / requests / suggestions?
Not really, Borlox (mia atm?) made most of Fortress, and various other people worked on LibDataBroker. Most of the current Broker plugins isn't very original, either.
Still getting errors about LibDataBroker-1.1 missing. BUT: seems to be a problem with load order. Only those Brokers beginning with a letter that comes after "F" (like Fortress) get loaded. PvP and Sysstats work, others do not. Renamed Clock to Zlock and it started working...
Edit: Renamed them Zroker_Clock, Zroker_Mail and Zroker_Durability and they all started working.
Hmm yeah, unless the same stuff is done in all other displays labels like "XP" or "DPS" won't show up when using Funkeh's plugins. On the other hand labels won't be colored in StatBlocks if using other broker plugins.
Of course this is something we need to talk about, why do you say we can't? :P
Maybe the plugin should provide the format as well as the text. I'm not sure the "label" is the solution that would work best everywhere. i bet Tekkub or Nevcariel got an idea of what's the best thing to do, they're usually pretty good at seeing the big picture. :P
[2008/07/07 03:37:42-1531-x25]: FuBar2Broker-1.0\FuBar2Broker.lua:51: attempt to index local 'frame' (a nil value)
StatBlockCore-2.0\StatBlockCore.lua:262: in function <Interface\AddOns\StatBlockCore\StatBlockCore.lua:259>
Of course this is something we need to talk about, why do you say we can't? :P
i agree, something that needs to be talked about. i don't say we can't, but people have a tendancy to like options and when you talk about a common format they only see options dissappearing.
IMO it should be 3 of them..
text == straight text string..
pattern == lua pattern used in formatting.
data == (...) or stored as a indexed table on the LDB object.
so the "text" callback from LDB
function OnTextChange(event, name, object, text, ...) <-- 'OnTextChanged', 'DPS', {dps_LDB_BLock}, "102.2dps"
if object.pattern then
...:SetFormattedText(object.pattern, ... or text)
else
...:SetText(text)
end
end
should LDB be in trunk, too? I just installed these without externals, and it did not pull the lib down.
LDB-1.1 is not hosted on an SVN and therefor "externals" are meaningless. I'm not sure why anyone would use 1.0, unless they're just afraid of git.
Quote from andreasg »
Maybe the plugin should provide the format as well as the text. I'm not sure the "label" is the solution that would work best everywhere. i bet Tekkub or Nevcariel got an idea of what's the best thing to do, they're usually pretty good at seeing the big picture. :P
Tekkub only uses "text". IF I implemented labels (I won't) I would just use the dataobj name, and take "label" as an override for that. I would make two fontstrings, one for label ond for text, and update them only when the corresponding value was changed. I wouldn't do this concatenation crap Funk's doing (sorry man). Either way, labels are up to the display, and my displays do not use them. The whole formatted text thing is neat, and you could certainly use it if the display addon supports it... but don't forget that the minimalist displays (like mine) won't support anything except that text field.
For those of you interested in all this jibba... I'm sure you're well away of Funky's work on StatBlocks to make a LDB data display addon. Well to complement that I've made Quickie for all those bastards that put "quicklaunch buttons" into fubar. The goal is of course to split the display from the source addon, give the user choice in display addons, and provide a super minimal embed and API for implementing buttons in an addon (don't want to embed FBP + tablet + dewdrop + all the libs those require, just to get a minimap button). I've started adding dataobjects into my addons to use this. I hope to see a few other displays as well.
In short, if you addon does not display any "real" data, and is instead simply an interface for getting into your config, please use the API I describe on Quickie's page. I'm fairly sure Funky plans to have StatBlocks ignore dataobjects with that spec and let other addons manage those.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
-
View User Profile
-
View Posts
-
Send Message
Forum Moderatortrunk/Fortress
trunk/Broker_*
happens for Clock, Durability and Mail. PvP and Sysstats are working for me.
Confirming this. FYI I am pulling from the trunk.
Is there a thread we should take this to, for errors / requests / suggestions?
I updated all the externals now, check and see if it works for you now, it works fine for me, with only the broker plugins and fortress loaded.
Edit: Renamed them Zroker_Clock, Zroker_Mail and Zroker_Durability and they all started working.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumStatBlocks is using a "Label" (a pattern) and formatting the "text" feild into it, where Fortress is using the "text" straight up...
can there be a formal method to this or is it going to be one of those indepandant issues that people can't talk about.
Of course this is something we need to talk about, why do you say we can't? :P
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Forum Moderator-
View User Profile
-
View Posts
-
Send Message
Curse Premiumi agree, something that needs to be talked about. i don't say we can't, but people have a tendancy to like options and when you talk about a common format they only see options dissappearing.
IMO it should be 3 of them..
text == straight text string..
pattern == lua pattern used in formatting.
data == (...) or stored as a indexed table on the LDB object.
so the "text" callback from LDB
function OnTextChange(event, name, object, text, ...) <-- 'OnTextChanged', 'DPS', {dps_LDB_BLock}, "102.2dps"
if object.pattern then
...:SetFormattedText(object.pattern, ... or text)
else
...:SetText(text)
end
end
you get the idea.
LDB-1.1 is not hosted on an SVN and therefor "externals" are meaningless. I'm not sure why anyone would use 1.0, unless they're just afraid of git.
Tekkub only uses "text". IF I implemented labels (I won't) I would just use the dataobj name, and take "label" as an override for that. I would make two fontstrings, one for label ond for text, and update them only when the corresponding value was changed. I wouldn't do this concatenation crap Funk's doing (sorry man). Either way, labels are up to the display, and my displays do not use them. The whole formatted text thing is neat, and you could certainly use it if the display addon supports it... but don't forget that the minimalist displays (like mine) won't support anything except that text field.
For those of you interested in all this jibba... I'm sure you're well away of Funky's work on StatBlocks to make a LDB data display addon. Well to complement that I've made Quickie for all those bastards that put "quicklaunch buttons" into fubar. The goal is of course to split the display from the source addon, give the user choice in display addons, and provide a super minimal embed and API for implementing buttons in an addon (don't want to embed FBP + tablet + dewdrop + all the libs those require, just to get a minimap button). I've started adding dataobjects into my addons to use this. I hope to see a few other displays as well.
In short, if you addon does not display any "real" data, and is instead simply an interface for getting into your config, please use the API I describe on Quickie's page. I'm fairly sure Funky plans to have StatBlocks ignore dataobjects with that spec and let other addons manage those.