Uhm, it's entirely up to the display addon how it does it's config... there's no need for a "specification". If you don't like the display's config, take it up with the author or find/create a display that works the way you want.
Oh, I know it's on a per-display-addon basis. I was just hoping for a "best practices" notice or somesuch...to be adhered to or not. Right now, it's just a potluck...though, the community is still relatively young and may adopt an unspoken standard based on user preferences in the long run.
I was wondering if there was going to be "official" guidelines/suggestions for handling plugin registration. Most LDB displays seem to make the plugins child frames under the Blizzard options panel, which makes their sorting rely solely on load order. With a few handfuls of LDB feeds, this can be a nightmare to manage.
For example: Under StatBlockCore, if I wanted to change the font size or face of a particular feed, I would have to read the list line-by-line and hope I don't miss the addon I'm looking for.
ButtonBin handles its feeds a bit differently - they're located on the right side of the options panel after clicking on the Data Blocks child frame, and they are alphanumerically sorted (yay!). ButtonBin does not currently allow a per-feed configuration, so that panel simply has checkboxes enabling/disabling them. If it _did_ have per-feed configuration - given the limited space provided by Blizzard's UI - where would you select the feed and where would its configuration options be?
I use both addons I mentioned above: One to replace FuBar and the other to slap blocks of information in free-floating places. One is a nightmare to configure on the feed side. The other is a nightmare because I cannot configure the feeds.
Yes, these are design points for two different addons and are beyond the scope of what LDB does in of itself. I'm just concerned with the lack of a unified feed-handling methodology and/or mechanism in the LDB specification/community.