To All "DataBroker Displays" Authors
If you're not an author of a DataBroker display, don't bother reading.
I'm just here to alert authors that one of my addons should break most of DataBroker launcher displays. Why? Until now, DataBroker has only been used for two dataobject types: "launcher" and "data... data... whatever. :o The thing is: my addon is using databroker to share other kinds of information. So, if your display is not checking for the dataobject type (.type), or assumes that, if an object is not a "launcher" then it's a "data whatever", it's going to start displaying launchers that do not exist, or simply start trowing out bugs. As requested, here is what the addon does and what object types it creates/uses: The addon is Cornucopia. The closest existing addons to it are probably the old & dead Bongos3 or Dominos. So, it lets you configure your interface trough bars (until now, nothing new). Now here is the big difference: it does not have his own "bars". It comes with a small set of bars that I already have done (all alpha stage), but the bars are provided by registering a dataobject with the "Movable Bar" type. And it also uses DataBroker for other functionalities. Mostly has an example, the Minimap bar uses "themes" registered trough the library. And I might use it in more situations: fonts, backdrops,... anything that can be shared between addons is a possibility to me. |
Quote:
|
hmmm, cant think of a type thats not a launcher or a data source ;)
|
Quote:
|
Quote:
|
if your addon breaks databroker... shouldnt you find another way, not expect the community to find work a rounds for your addon?
|
Quote:
It's a slight change: one or two lines of code and it's fixed. And no one is forced to do it, but will break with my addon running too. Also, this message is for DataBroker display authors. Some already answered and didn't seem worried about it, because they know it's a simple change. You also don't need to be. |
As long as your data objects have a .type attribute that is not "data object", "launcher" or nil (for backwards compatibility), I think most displays won't try to do anything with them.
It's a very good idea to remind the display authors, though! Edit: I know at least one other addon that uses non-launcher/d.o. objects: Cork. If your display does not break when using this, it should work with any data object creating addon. But it's important that the .type attribute is set. |
I got your PM but it contains almost no information. Vague information is vague. I'm not doing anything for now.
|
Quote:
|
Wouldnt it be better to give info what your type is and what you expect
a display-addon to do when it comes across it instead of saying start ignoring anything but launcher and data source ? I think most displays added a "lazymode" for the many cases where authors forgot to set the type or misspelled its type. |
Quote:
|
Quote:
|
Quote:
Oh dont get me wrong, I am not angry, I dont even use data broker addons (except maybe auditor, but i dont use a bar mod to hold it). I was just confused cause you made it sound like your addon could break other peoples. I was confused on why you chose to code that way instead of finding a way around. I was unaware that your addon might break other addons because their code isnt right. It was more of an inquisitive statement, not a , "change your ways" statement |
Quote:
|
Quote:
So you see that I just try to point out that you will be faced with displays that will handle your addon wrong just because they will "guess" your type when it does not fit what they expect. AddOn-Scripters come and go but their addons live on in our community ;) So a "warning" that you might break with whats there already might not arrive... |
Quote:
|
Basically, LibDataBroker wasn't only created with plugin-display AddOns in mind - it was created as an information (data) broker between multiple sources/destinations. Tekkub uses LDB internally in Cork, defining DataObj types which only Cork should care about.
|
Indeed, Torhal. This isn't a 'change' at all. It's how its always been, so I'm really really confused.
|
Quote:
Like I said, let's not make a big fuss about it. |
All times are GMT -6. The time now is 10:31 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI