6.5 news: CSS order
Locked
 
|
Dear Aiders,
Order of CSS resources is important because later can override previous (that's the meaning of 'Cascaded' in CSS). To achieve maximum flexibility we have now such order in Aida 6.5: 1. on-demand loaded CSS from method libraries (like with 2. jQueryLibrary ensureUI 3. per-site CSS in WebStyle subclass 4. in-line CSS in page header (self page addStyle:) 5. in-line CSS to some element (anElement style: ) Note specially that resources from WebStyle subclasses are always loaded after those from method libraries. That way you can customize default look of them, for example jQuery UI controls. And per-website, so that each website can have its own customized look&feel of components from libraries. And as you know with Aida you can run many websites from a single image. In-line CSS comes last but it is not recommended, because you loose quickly the control of where the CSS in your code lies. Separation of style (in WebStyle subclasses) from code is good thing and should be respected. Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
|
|
Am 26.07.2012 08:36, schrieb Janko Mivšek:
that's how I'd assume it would work. I did very few CSS changes and they all worked like I expected. Has it ever been different? Cheers Herbert > Dear Aiders, > > Order of CSS resources is important because later can override previous > (that's the meaning of 'Cascaded' in CSS). > > To achieve maximum flexibility we have now such order in Aida 6.5: > > 1. on-demand loaded CSS from method libraries (like with > 2. jQueryLibrary ensureUI > 3. per-site CSS in WebStyle subclass > 4. in-line CSS in page header (self page addStyle:) > 5. in-line CSS to some element (anElement style: ) > > Note specially that resources from WebStyle subclasses are always loaded > after those from method libraries. That way you can customize default > look of them, for example jQuery UI controls. And per-website, so that > each website can have its own customized look&feel of components from > libraries. And as you know with Aida you can run many websites from a > single image. > > In-line CSS comes last but it is not recommended, because you loose > quickly the control of where the CSS in your code lies. Separation of > style (in WebStyle subclasses) from code is good thing and should be > respected. > > Best regards > Janko > > _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
|
|
Dne 26. 07. 2012 19:05, piše Herbert König:
> Am 26.07.2012 08:36, schrieb Janko Mivšek: > > that's how I'd assume it would work. I did very few CSS changes and they > all worked like I expected. Has it ever been different? New is an explicit moving of screen, print and mobile CSS, auto generated from a style class, to the end of page header, ensuring that they are after all manually or otherwise added CSS in header. This is achieved by adding them just before streaming phase begin, while manual or from libraries additions happen in composing phase of page rendering. By the way, same goes with JavaScript in header as well. So you can override JS functions with your own per-site JS in WebStyle sublclasses. And yes, if you add CSS in-line in page header, tis one is really at the end, so you can override even style CSS with it (with self page addStyle: ) Best regards Janko > > Cheers > > Herbert >> Dear Aiders, >> >> Order of CSS resources is important because later can override previous >> (that's the meaning of 'Cascaded' in CSS). >> >> To achieve maximum flexibility we have now such order in Aida 6.5: >> >> 1. on-demand loaded CSS from method libraries (like with >> 2. jQueryLibrary ensureUI >> 3. per-site CSS in WebStyle subclass >> 4. in-line CSS in page header (self page addStyle:) >> 5. in-line CSS to some element (anElement style: ) >> >> Note specially that resources from WebStyle subclasses are always loaded >> after those from method libraries. That way you can customize default >> look of them, for example jQuery UI controls. And per-website, so that >> each website can have its own customized look&feel of components from >> libraries. And as you know with Aida you can run many websites from a >> single image. >> >> In-line CSS comes last but it is not recommended, because you loose >> quickly the control of where the CSS in your code lies. Separation of >> style (in WebStyle subclasses) from code is good thing and should be >> respected. >> >> Best regards >> Janko >> >> > > _______________________________________________ > Aida mailing list > [hidden email] > http://lists.aidaweb.si/mailman/listinfo/aida -- Janko Mivšek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565 _______________________________________________ Aida mailing list [hidden email] http://lists.aidaweb.si/mailman/listinfo/aida |
«
Return to AIDA/Web
|
1 view|%1 views
| Free forum by Nabble | Edit this page |