As far as I (and many other folks) am concerned, "label" is just that - the label for the icon: I see a gold coin icon. What is it? Turn on labels, and I see "Broker_Currency". The "text" field is the actual data. How this can be confusing is beyond me.
If I remember correctly, X-Embeds was only used by the old WoWAce packager, whereas the current one uses the externals specified in the .pkgmeta. ACP more than likely checks RequiredDeps and OptionalDeps to get its information.
2. What is the embedding policy for addons nolib version?
What OrionShock said above, plus: Tekkub has stated that LibDataBroker should always be embedded. I don't know why, and I don't ask. However, he has also stated that if people start slapping it into their .pkgmeta as an external that he would remove it from github.
They're not enforcing a standard. :p They're a front end, doing what a front end is suppose to do, in a way that a lot of people were begging for. xD
The reason behind sylvanaar's post was that he was asked to change Prat's LDB feed from "launcher" to "data source" because DockingStation was complaining about it. So yes, in a way, it's enforcing a standard. Or, at least, nagging about it.
Because it's nice sometimes to be able to differentiate between something which only launches configurations/whatever and something that displays data. For example, MakeRocketGoNow. Using that on my LDB display, I can leave every launcher I have disabled because they're all contained there. Honestly, though, there is no real "standard" since the whole damn thing resides on a Wiki. Displays like DockingStation which try to enforce a "standard" are, quite possibly, limiting themselves by doing so - Cladhaire added the icon RGB stuff to TomTom and implemented it in NinjaPanel when there was no "standard" for it, and now other displays (including DockingStation) support it as well.
Nope. There are plenty that do that, and if they didn't it would effectively nullify much of the usefulness of most plugins. An addon doesn't have to solely provide data. That would be like saying that Postal should only send/receive mail.
A special purpose solution is to write a display that is meant exactly for this purpose, i.e. just show tightly packed icons and only grab brokers that you want, and move that whereever you want it, possibly even on top of a bar if you use that.
Found something interesting while perusing the changelog for Ghost: Recon...
0.9.4 beta: 2009-01-04
- Added support for an LDB launcher. I'm not embedding LibDataBroker in the Zip file - presumably your LDB display addon will include this for you. If this is somehow causing things to fail, let me know.
There is no actual relation between the "spec" and the library, other than convention, or common use.
That sound right?
Sounds about right to me, especially since Tekkub refuses to set things in stone for those reasons.
I'm beginning to think, however, that without some sort of Standard being set that things will fragment and in general be non-compatible rather than being a generic display/plugin paradigm. I'm not sure that's a bad thing, however, since inevitably the community will settle on one set of features should there actually be a "display war".