Mmm, didn't really mean for them to be named Broker_ tho, they'll get renamed as soon as I come up with something.
If you are out of ideas, start a thread and a vote.
I'm all for 'merlon' as prefix, goes along with 'fortress'. merlon - wikipedia merlon - google pictures - may or maynot be worksave
If you are out of ideas, start a thread and a vote.
I'm all for 'merlon' as prefix, goes along with 'fortress'. merlon - wikipedia merlon - google pictures - may or maynot be worksave
Hahaha I like this.
Never even knew that company existed. =p
In any case Broker_* isn't too bad, It let's people know it's an LDB capable addon. Unless you want to use LDB_* .... or siege_* waka waka.
Anyhoo, that's my two cents for this hour of mornin, yarr.
Here's a selection of my Fortress stuff. I said I'd post Friday - sorry 'bout that folks. I'm old and confused and entering a Magoo phase of life I think...
Here's a selection of my Fortress stuff. I said I'd post Friday - sorry 'bout that folks. I'm old and confused and entering a Magoo phase of life I think...
Looks like when Fortress creates the config for new data objects it's registered, it does so with the name of that plugin, which means it potentially overwrites the plugin's existing/separate config:
function Fortress:AddObjectOptions(name)
local t = self.optionsFrames[name] or {}
t.name = name
...
LibStub("AceConfigRegistry-3.0"):RegisterOptionsTable(name, t)
LibStub("AceConfigDialog-3.0"):AddToBlizOptions(name, name, "Fortress")
end
Probably this could be solved with something simply like using name.."_Fortress" instead of just name for registration.
[2008/07/13 20:51:33-2629-x1]: Violation-1.0.74674\Violation.lua:1316: attempt to index upvalue 'db' (a nil value)
AceAddon-2.0-57245 (Ace2):926: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:919>
<in C code>: ?
AceEvent-2.0-66043 (Ace2):260: in function `TriggerEvent'
AceEvent-2.0-66043 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>
Got this in 8 plugins (and every time SpamFu gets a message)
(Cross posted in FuBar2Broker)
**edit**
Not paying attention - the above is an error that's been around awhile w/o causing issues. This is the error:
"Assessment-r69925\\Extras\\FuBar.lua:271: attempt to call upvalue 'textMethod' (a nil value)\nAceAddon-2.0-57245 (Ace2):926: in function <Interface\\AddOns\\Ace2\\AceAddon-2.0\\AceAddon-2.0.lua:919>\n<in C code>: ?\nAceEvent-2.0-66043 (Ace2):260: in function `TriggerEvent'\nAceEvent-2.0-66043 (Ace2):910: in function <Interface\\AddOns\\Ace2\\AceEvent-2.0\\AceEvent-2.0.lua:903>\n\n ---",
["type"] = "error",
is the one.
Assessment had over 1000 of theses in 5 minutes.
I know it's not really the good thread, but considering that Fortress display LDB addons...
Is it possible to include some possibility for translation on the broker_* addons or every addons that use LDB, cause right now, I must do some "dirty" lua editing... ?
Mmm, didn't really mean for them to be named Broker_ tho, they'll get renamed as soon as I come up with something.
What is wrong with having all the LDB plugins named LDB_*? They are not specific to Fortress, SBC or any other LDB display addon and should not be named after one of those.
What is wrong with having all the LDB plugins named LDB_*? They are not specific to Fortress, SBC or any other LDB display addon and should not be named after one of those.
This sounds good.
edit: But naming them Broker_ has the same effect. But, yeah... You'll have some users who won't fully realize that you can use the StatBlocks_ plugins with any display - they'll think they go with StatBlocks.
Currently the main thing holding me back from using this over FuBar is that with FuBar, I can set my bars to hide until moused over. With Fortress, I can only set each plugin to hide until moused over, which has a very different functional effect. I don't like playing hide-and-seek to find the plugin I want to see; I want to just stick my mouse anywhere over the plugin blocks that are "stickied" together, and see all of them. Is anything like this planned?
Currently the main thing holding me back from using this over FuBar is that with FuBar, I can set my bars to hide until moused over. With Fortress, I can only set each plugin to hide until moused over, which has a very different functional effect. I don't like playing hide-and-seek to find the plugin I want to see; I want to just stick my mouse anywhere over the plugin blocks that are "stickied" together, and see all of them. Is anything like this planned?
This sounds like one logical extension of the "grouping" feature that Pusikas proposed on the previous page.
This sounds like one logical extension of the "grouping" feature that Pusikas proposed on the previous page.
Also see my request for "LDB Bars" in the Addon suggestions section. I don't understand why we have two completely competing products (Fortress and SBC) but no Fubar replacement based on LDB. It seems to me that it should be almost as light weight as Fortress (a bit more since you need to add frames independent of the plug ins).
Also see my request for "LDB Bars" in the Addon suggestions section. I don't understand why we have two completely competing products (Fortress and SBC) but no Fubar replacement based on LDB. It seems to me that it should be almost as light weight as Fortress (a bit more since you need to add frames independent of the plug ins).
Your suggestion means a FuBar 4.0 based on LDB. It's not impossible IMHO, but I think very unlikely now.
Your suggestion means a FuBar 4.0 based on LDB. It's not impossible IMHO, but I think very unlikely now.
It doesn't need to be "FuBar 4.0". I just like the "bar" model rather than the "bunch of blocks that can stick together" model, for the reasons I mentioned in my last post. I like to keep my screen clean, so I have FuBar set to hide until moused over. With the "blocks" model, if I use auto-hide, I have to play hide and seek to find any information when I want to see it. It'd also be nice to be able to control the spacing between text elements, which doesn't really work with the "blocks" model.
Quote from Yssaril »
all someone needs to write is a LDB to libFubarPlugin-3.0 addon no need to update fubar
There are several improvements I'd like to see over FuBar, such as the ability to configure each bar individually (auto-hide, object spacing, font size, background texture, etc). I'd also be very welcoming of anything FuBar-like that didn't cover 90% of my screen with a gargantuan RockConfig window if I missed right-clicking a plugin and right-clicked the bar instead. :P
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
If you are out of ideas, start a thread and a vote.
I'm all for 'merlon' as prefix, goes along with 'fortress'.
merlon - wikipedia
merlon - google pictures - may or maynot be worksave
Hahaha I like this.
Never even knew that company existed. =p
In any case Broker_* isn't too bad, It let's people know it's an LDB capable addon. Unless you want to use LDB_* .... or siege_* waka waka.
Anyhoo, that's my two cents for this hour of mornin, yarr.
Here's a selection of my Fortress stuff. I said I'd post Friday - sorry 'bout that folks. I'm old and confused and entering a Magoo phase of life I think...
How'd you configure it like that? O_o
Probably this could be solved with something simply like using name.."_Fortress" instead of just name for registration.
Got this in 8 plugins (and every time SpamFu gets a message)
(Cross posted in FuBar2Broker)
**edit**
Not paying attention - the above is an error that's been around awhile w/o causing issues. This is the error:
is the one.
Assessment had over 1000 of theses in 5 minutes.
Sorry for the confusion.
I know it's not really the good thread, but considering that Fortress display LDB addons...
Is it possible to include some possibility for translation on the broker_* addons or every addons that use LDB, cause right now, I must do some "dirty" lua editing... ?
What is wrong with having all the LDB plugins named LDB_*? They are not specific to Fortress, SBC or any other LDB display addon and should not be named after one of those.
This sounds good.
edit: But naming them Broker_ has the same effect. But, yeah... You'll have some users who won't fully realize that you can use the StatBlocks_ plugins with any display - they'll think they go with StatBlocks.
This sounds like one logical extension of the "grouping" feature that Pusikas proposed on the previous page.
Also see my request for "LDB Bars" in the Addon suggestions section. I don't understand why we have two completely competing products (Fortress and SBC) but no Fubar replacement based on LDB. It seems to me that it should be almost as light weight as Fortress (a bit more since you need to add frames independent of the plug ins).
Your suggestion means a FuBar 4.0 based on LDB. It's not impossible IMHO, but I think very unlikely now.
all someone needs to write is a LDB to libFubarPlugin-3.0 addon no need to update fubar
It doesn't need to be "FuBar 4.0". I just like the "bar" model rather than the "bunch of blocks that can stick together" model, for the reasons I mentioned in my last post. I like to keep my screen clean, so I have FuBar set to hide until moused over. With the "blocks" model, if I use auto-hide, I have to play hide and seek to find any information when I want to see it. It'd also be nice to be able to control the spacing between text elements, which doesn't really work with the "blocks" model.
There are several improvements I'd like to see over FuBar, such as the ability to configure each bar individually (auto-hide, object spacing, font size, background texture, etc). I'd also be very welcoming of anything FuBar-like that didn't cover 90% of my screen with a gargantuan RockConfig window if I missed right-clicking a plugin and right-clicked the bar instead. :P