On 1/14/17, 7:54 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:
>Hi Om, Alex, > >thanks for the suggestions but that not work. After sleep and thin about >it >a little more my understanding is that this is really not a problem of >malfunctioning, is simply that we have properties that operates visual >changes based on CSS, so the right way is yo apply the instruction *per >property*, since is in that case where we need the property to be part of >the frozen styles (if toggles to stay or is removed). In the rest of cases >this not apply and other kind of use by the customer should allow him to >override all if he want...if not he should make the same as we do to let >class selector remain. > >It's a bit of work, since I must to go through all the components making >this change in all the properties that behaves similar, but...don't see >other quick way where we could change in one point and affect all in the >right way. Not sure I understand. If there was an "internal" list (like typeNames) that the component developer controlled, and another "list" like className that the customer controlled, why couldn't you just merge the two to make the final set of classNames? Separately, also consider whether the kinds of things folks want to change (toggle or not) changes at runtime or at design time. If design time, maybe there should just be more classes like one with toggle and one without. -Alex
