On 10/27/16, 9:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>Hi Alex, > >I like the Yishayw concept os adding beads in CSS. Don't know about the >runtime cost of this, but it would allow users to configure if they want >this or those beads for their use. If you add in the component, all is >done >there and people can't change it. Maybe you're the person to decide if >this >could be done or there's a penalty to pay that make It not viable. You can already specify some beads like Layout and Views from CSS. I don't think the Basic set should do spend the cycles considering "additionalBeads" since I think once you get into production, you should have the option of optimizing if you know what beads you need where. But other component sets can. So no decision really has to be made. Folks who want it can implement it in a different component set. It might be time for someone to start on a "kitchen-sink" component set that bakes a lot of beads in and supports an "additionalBeads" property. -Alex
