Bertrand Delacretaz wrote: > Le 24 nov. 04, � 15:46, BURGHARD �ric a �crit : > >> ...an xmlcss file is writen like that: >> <css> >> <rule select=".myclass"> >> <padding value="0"/> >> <margin top="10px/> >> </rule> >> </css>.... > > ouch. Angle brackets strike again ;-) >
:-) >> ...any thought ? > > Without having looked at the details, I like the idea! > > The problem might be getting people to write CSS in XML. The native CSS > syntax is so much more comfortable to write. > yeah but it was easier for me to write it in xml (for parsing and transforming reasons) instead of writing an expression syntax above css. With xml i can use the power (and stability) of xslt, and my standard xml editor (outline view is more readeable than a rought css) for completion and syntax checking. xmlcss is just an xmlification of css. without defines an macros, convertion is immediate in both ways (simple scripts can do that for you). > generated CSS can be cached by Cocoon (or by whatever front-end cache > you're using).Maybe it would be easier for this to have different CSS > URLs (generated by Cocoon based on browser detection) for the different > browsers, instead of generating variable CSS content for the same CSS > URL based on the browser type. > In fact, there are two steps and two pipelines. The first one generate an xslt stylesheet (yes a stylesheet that generate another stylesheet) responsible for transforming a given xmlcss (only macros and definitions are used in this step) for a given browser. You can use cocoon caching. the second pipeline (which match for example css/*.css) just do the transformation on the xmlcss with the stylesheet generated at the first step (using of cocoon:/ in src url). this step can be cached too. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
