Thank you all. For now, I'm going to focus using the default way (put a reference directly on the template).
Alex Harui <aha...@adobe.com.invalid> escreveu no dia terça, 1/02/2022 à(s) 17:07: > When we started on FlexJS/Royale, the CSS compilation was intended for use > in Flash as well as JS. Thus, the compiler only handled CSS syntax we knew > we could easily implement in Flash. The goal back then was not to create a > full CSS implementation on Flash, or a full CSS parse in the compiler. > > Later, we tried to import some existing stylesheets from some Bootstrap > themes and I think Material themes so we gave up on full equality between > Flash and JS and taught the compiler to parse more CSS. > > Volunteers are welcome to enhance the compiler to handle even more CSS > syntax. > > HTH, > -Alex > > On 2/1/22, 8:32 AM, "Maria Jose Esteve" <mjest...@iest.com> wrote: > > Hi, some time ago I had the same problem and Harb helped me (you can > search for the thread in the list @users) I have made an excerpt for you: > > The compiler needs to understand the css in order to compile it. > Any features that the compiler does not understand must be added to the > compiler. Definitely add this as a Github issue. > > To use unsupported CSS features, you need a CSS file that doesn't > run through the compiler. What I do is add a "defaults.css" file where I > put that type of CSS and add the following line to my template html > file: > > <link rel="stylesheet" type="text/css" > href="./assets/css/defaults.css"> > > Must be a plain vanilla CSS file (HTML style) [1] > Namespaces are not recognized in normal css. > > [1] > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FStyle%2FCSS%2Fspecs.en.html&data=04%7C01%7Caharui%40adobe.com%7Caa7fd64ed8124ad2f60608d9e5a05e27%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637793299654184072%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=oJRui7w%2Ftt2y3gDkPze2Odvey6zl49bv4B9JL3bMuX4%3D&reserved=0 > > Hiedra > > -----Mensaje original----- > De: Hugo Ferreira <hferreira...@gmail.com> Enviado el: martes, 1 de > febrero de 2022 12:26 > Para: Apache Royale Development <dev@royale.apache.org> > Asunto: Re: Less and Royale > > Hi Yishay, > > It's a workaround that works, thank you (I tried yesterday before my > e-mail and I don't know why did not works, perhaps because was night) but > is working now. > > Ansering your question. > If I set the default theme with the generated css from less I got a > lot of errors. > For example: > > .bg-opacity-100 { > --bs-bg-opacity: 1; > } > > The compiler seems not not like -- > > Yishay Weiss <yishayj...@hotmail.com> escreveu no dia terça, > 1/02/2022 à(s) > 07:52: > > > It would be interesting to understand why Royale is complaining, but > > as a workaround you might want to have an index-template file that > > includes your css. > > > > From: Hugo Ferreira<mailto:hferreira...@gmail.com> > > Sent: Tuesday, February 1, 2022 1:16 AM > > To: Apache Royale Development<mailto:dev@royale.apache.org> > > Subject: Less and Royale > > > > Hi, > > > > I compile a less file that generated a big css file (a lot of > > references from bootstrap). > > I know that this css file is OK or should be OK, however royale > > compiler complains about it while compiling ending with error (using > VS Code). > > How can I compile and ignore all errors from the main css file ? > > > > > >
