I think there's a cost, don't know if the cost is higher or lower. To me is not only the cost, is about as well as methodology. For me is incorrect to have a CSS always be compiled, no matter what kind of application I'll be constructing, even if nothing of that CSS goes into the final Application. You're making a useless compilation, that can introduce bugs or not, or you must keep and eye always that is not doing wrong things. If you don't put that CSS in mandatory SWC, your problems are all gone. I think CSS should be *always* in optional SWCs. For me maybe this is the most important concept or rule we should follow.
2018-05-31 9:05 GMT+02:00 Harbs <harbs.li...@gmail.com>: > The point of analyzing css is one I hadn’t thought of. > > I’m a bit unclear on how the compiler deals with Framework CSS files. How > does the compiler know which CSS files it needs to examine? > > Most compiler methods use royalelib which points to a folder with all the > Royale swcs. Does it make a difference whether a specific swc is actually > used? > > Unless you are using Maven, the full set of framework libs will always be > downloaded. If Maven caches a particular sac, would that be in the royale > lib path as well? > > What is the performance hit on analyzing a swc css file? If we’re talking > a few ms or less, I don’t think it’s worth worrying about. > > Thanks, > Harbs > > > On May 31, 2018, at 9:02 AM, Carlos Rovira <carlosrov...@apache.org> > wrote: > > > >> I see a claim that there is a problem because of the compiler parsing a > >> CSS file from a SWC where that CSS will not be used. Is there proof > that > >> it is a significant performance problem? Such a claim should be backed > by > >> data from an experiment by making the Basic defaults.css one blank line > and > >> see if compile time of a Jewel-only example speeds up in a significant > >> way. Also, we already have an -exclude-defaults-css-files option. It > >> currently does not prevent parsing of the CSS file, but we could make it > >> so. > > > > > > I don't say it was a performance issue, I said that is no point in > process > > a CSS that will never be use. > > As well if exclude option continues parsing the CSS, seems a bit > incomplete > > right? > > -- Carlos Rovira http://about.me/carlosrovira
