Ah, I see what you mean now. You don't need to add anything to use livecombine. Just add turn it on in the url.
On Thu, Mar 7, 2013 at 2:40 PM, Phillip Rasmussen <[email protected] > wrote: > Hi Blair, > Or added a word ;) > See below, there is a comment above the final render. Would be nice to get > rid of it in live production. > > <!-- > ID: yuiMenu > FILES: /yuiMenu/css-yui/yui_menu.css > --> > <link rel="stylesheet" id="stylesheet-yuiMenu" type="text/css" href=" > /cache/yuiMenu-AB47513741D37725266474ADBDAD100A.css<http://www.f-enomatic.co.nz/cache/yuiMenu-AB47513741D37725266474ADBDAD100A.css> > " media="all" > > > So, what was involved in adding 'livecombine' into those tags? > > Phil > > > > On Thursday, 7 March 2013 15:17:14 UTC+13, Blair McK wrote: > >> I think you left out an important word in that last question, so I'm not >> sure what you mean about comments :) >> >> Regarding refreshing caches - sometime in 6.0 (or 6.1?) I added support >> for livecombine=1. Not only will that enable automatic regeneration of >> caches during that session, it will even reload changed CSS into your pages >> without a refresh. I saw other people set their apps up so they can see the >> changes in the website while they edited the stylesheets, and thought it >> was awesome. >> >> Blair >> >> >> On Thu, Mar 7, 2013 at 1:06 PM, Phillip Rasmussen < >> [email protected]> wrote: >> >>> Hi All, >>> I noticed that perhaps after 6.1 the loadcss and loadjs tags don't >>> refresh if a referenced file gets changed. >>> This might have been a bug in previous versions and it's great in >>> production machines, but it would be handy if there was an attribute that >>> forced the refresh. Especially during developement. >>> Also does anyone else think an attribute for turning off commenting in >>> the listing of in the final render would be a good idea? So it doesn't >>> show the files being combined. >>> ergo: seeComments=false cache=false >>> >>> Cheers >>> Phil >>> >>> -- >>> You received this message cos you are subscribed to "farcry-dev" Google >>> group. >>> To post, email: [email protected] >>> To unsubscribe, email: farcry-dev+...@**googlegroups.com >>> >>> For more options: >>> http://groups.google.com/**group/farcry-dev<http://groups.google.com/group/farcry-dev> >>> ------------------------------**-- >>> Follow us on Twitter: http://twitter.com/farcry >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "farcry-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to farcry-dev+...@**googlegroups.com. >>> >>> For more options, visit >>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>> . >>> >>> >>> >> >> -- > You received this message cos you are subscribed to "farcry-dev" Google > group. > To post, email: [email protected] > To unsubscribe, email: [email protected] > For more options: http://groups.google.com/group/farcry-dev > -------------------------------- > Follow us on Twitter: http://twitter.com/farcry > --- > You received this message because you are subscribed to the Google Groups > "farcry-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry --- You received this message because you are subscribed to the Google Groups "farcry-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
