Hi, > Well, it is all supposed to be PAYG. If your app only needs padding and > fancy borders and backgrounds,
Just about all applications are going to need those features IMO. If every application developer has to implement themselves they may give up. In my experience most (but not all) application developers are not that interesting in extending the framework or getting their hands dirty in it innards. > then you could write a custom IValuesImpl > that only supports those things and it would be way smaller and faster > than AllTheThingsCSSStylesValueImpl. I think you may of missed my point, currently it looks like each application developer has to implement AllTheThingsCSSStylesValueImpl (well the subset they are interested in anyway and they gets large quickly for anything beyond a trivial application). Wouldn't it be better to be able to have those styles in into bite size chunks? That way there’s much higher potential for reuse and/or inclusion into the framework that way. And that PAYG ie you don't use you don't pay for it. Even in a single complex application some containers will need some features and other different features so it seems more PAYG to not have a AllTheThingsCSSStylesValueImpl. > Someone could also create an IValuesImpl that is a strand that can take > beads that support various subsets of CSS. That sounds more PAYG to me. Could you outline the steps needed to do this? Thanks, Justin
