On 12 feb., 21:31, Jeppe Nejsum Madsen <je...@ingolfs.dk> wrote: > On Fri, Feb 12, 2010 at 8:20 PM, Marius <marius.dan...@gmail.com> wrote: > > Jeppe probably we can combine the two proposals. > > Yes, that would be natural > > > Perhaps something like: > > > <lift:css name="mycss.css, some_other.css. /classpath/baz.css" /> > > > thus Lift could generate: > > > <link rel="stylesheet" type="text/css" href="compound_2434rfe34534.css? > > i784yrfiuhferfhweir57=_"/> > > > compound_2434rfe34534.css is a synthetic name that would contain the > > mycss.css, some_other.css. /classpath/baz.css concatenated. Same thing > > for JS. This content could potentially be compressed. > > One thing that I think will be important (at some point :-) is to do > combining of individual tags. If a page is constructed from several > snippets/widgets, each emitting different js files (think jQuery > plugins) and css files, these need to be combined somehow. This means > that each page will get it's own unique synthetic css/js file. This > probably needs to be configurable in some way :-)
Yeah that is a slightly different use-case that require more noodling. But would worth considering in the future. > > > I can open a ticket and start looking into this. > > Awesome! I'll watch from the sideline! > > /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
