The problem isn't with secure stuff. The problem is when you try to mix secure with non-secure stuff, for instance anchoring them together, then trying to modify settings of the non-secure plugins while in combat, or worse having the plugins modify attributes automatically, eg resize text width to fit better in a frame, based on events or timed updates. You can postpone/queue/deny that update to avoid action blocked but that is also wrong, because the display wouldn't really be doing what was intended. Bottom line, 9/10 times the non-secure stuff will frak things up.
Addons like SBC and perhaps ButtonBin are the least affected by this (they can still taint if you attach/stick secure to non-secure), but I'm willing to bet, a lot of people would whine.
I would love to sell the idea honestly, I'd like to believe I'm open minded and all that :p but all I've seen so far is some basic examples. Can we have the custom spec outlined for us please or at least a very rough idea so we can brainstorm and discuss it. For instance, what kind of attributes do we need in the LDB object (I've seen 2-3 so far explained), which ones are displays going to use, which ones will be used purely by the DO. What is the proposed way that a display goes about "detecting" the spec (let's say set type attribute to "secure object"), does the display need to fire/register callbacks and if yes when and how (I've seen so far that the display may/will need to detect and call a func defined by the DO). This is the kind of thing I'm talking about when I say "outline the spec". Without this plus some solid, useful examples (call me weird but using tradeskills or applying weapon buffs when I'm fighting a mob that is about to eat me for breakfast isn't exactly very common, on the other hand let's say storing target(s) on a button/block is something that may interest me), this is all vaporware.
There is no need to extend the basic LDB spec. You are basically asking display authors to support a/your custom LDB spec. To be perfectly honest, I'm not that crazy about secure buttons as LDB objects, it creates a huge headache of possible issues with the buttons been created with proper handlers so that that won't taint every second, plus it's an implementation mostly suited for action buttons/action bars/action whatever rather than data feeds, but I'm willing to see how you picture this working.
yea this is similar to MRGN, which i'm currently using. i would like to see these kind of addons also support the Blizz (i'm thinking of the LFG, arena, and BG buttons specifically) and other addon (like Fizzwidget's Hunter Helper) minimap buttons so that i could drop addons like minimapbuttonframe. any chance of this happening, atleast for the Blizz buttons?
I was under the impression that tek already wrote some plugins that effectively "replace" several "Blizzard buttons" (see picoButtons). There are already other replacements for World Map/Clock/Tracking etc (or will be very soon).