On 3/15/17, 12:24 AM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> Clearly, it must be possible to create good apps without numeric font >> weight since most everyone on this list has created a Flash-based Flex >>app >> and could not use numeric font weight. > >What's your point? It's possible to create applications without any >features you name, be that components like datagrid, or using no CSS at >all or not using borders or colour or images or what ever. Yes, that is Pay-as-you-go (PAYG). CSS Functionality should also be PAYG. > >If you add a designer to your team they are very likely to want to >support different fonts, alphas, font weight, background image, line >height, text transform and the like. > >Why would we actively want to stop people from setting font weights? Why >would we not want to follow the standards? Why would we want to disable >browser features just because they are not supported in AS? It seems to me you are still thinking in the "there's only one way" mentality of the regular Flex SDK. In FlexJS, we give folks choices. If I can reduce my JS and SWF output sizes and retain parity in the UI by using a reduced set of CSS styles, I should be able to do so. That has been the intent of SimpleCSSStylesImpl for several years now. > >I think a nice 1.0 set of CSS features to aim for would be to support >most of the well supported subset of CSS 2.1 features as mentioned on >caniuse.com and elsewhere. > >Users of the framework would probably expect this as a minimum if they >have a JS background. Absolutely. And that's why we need someone to create a more complex CSSStylesImpl with numeric font weight and all of these styles. I'll get to it eventually, but it would be great if someone else could get started. And your code will go there and probably be shipped in way more apps than those that use SimpleCSSStylesImpl, but SimpleCSSStylesImpl is at least there to give folks a choice. So far, most, if not all of our examples have been completed without the need for numeric font weight. To me, that means that numeric font weight is there "just-in-case". Another principle of FlexJS is to try to make just-in-case code PAYG. Please, we have an existing pattern of development. If you don't like the naming scheme, let's discuss a new one, but for now, please use what we have and start a CSSStylesImpl or CSS2StylesImpl or AdvancedCSSStylesImpl that supports more JS styles and put your code in there. FlexJS has been designed to handle multiple component sets so folks can use different philosophies in different sets. One reason for this is so we don't have to all agree. The MDL set doesn't care a bit about SWF fidelity. Basic components do care about SWF fidelity. You are welcome to create different components and component sets with your philosophy. Thanks,
