On 1/13/17, 3:35 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>mmm I was thinink on Injecting, but inject could be problematic since >mainly *all* components would get the automation bead and maybe that's not >what we want. Ejecting? mmm don't like the idea of "writing" it down to >the >component...don't know right now.... > >I like the spring framework philosophy for this cases where some >configuration makes what you want without *blurring* the code. > >In such philosophy you don't put nothing in the code, and instead you >configure in some external resources what you want to put or quit at your >discretion, so in this case, you could have a list of controls that will >have automation bead in a config file, and that list would be used to >inject automation bead in the listed controls (maybe even the relation of >control and its corresponding automation bead That sounds good to me as well. -Alex
