How to get this to work?

One more question, how does this work with different themes? I use one theme for admin (no cache need then as only me logging in) and one theme for the site (cache needed).

Right so I looked throught the code and it seemed clever enough to work out if needed to include files so I'm trying it out. I added a bundle, had a look through the source of the site page, then added all those files to the new bundle. Same for js. Enabled the module and looking at the web page source it now has the bundle and the page is correct.

However, when I'm logged in as admin I use a different theme and I don't want my site bundle to load as it messes up the css. How do I define which bundle loads for which theme? As far as I can see there isn't a way to do that. Given that users changing theme can be an option then the bundles should be theme specific.

What I have done which seems to half work is to remove the main style sheet from my bundle. That removes most of the mess up of the admin theme but it's still not quite right. The site page now loads 2 css files, the bundle and the theme style sheet.

I've played around a bit more. I now have 3 bundles for css, basic, admin, site. Basic contains the common css files, site the site specific ones, and admin the admin specific ones. The module is clever enough to include basic+site for site pages and basic+admin for the admin pages. I guess it looks at what the page needs and if a bundle has it adds that bundle, but only once.

I haven't tried putting the contents of basic into admin and site as I doubt it is clever enough to work out which bundle is the best match. It will add a bundle if not all the files are required, which was what was messing up my admin theme.

It seems to speed up the pages and the version number is useful to force browsers to reload css files when you make a change to the css.

When you say:

You can exclude files from showing up in the list on admin/build/sf_cache/config/excludes. The ticks only indicate that the file may potentially be added to a page. If you uncheck a file, it means that it will never be added to a page under any circumstances (if it’s not included in a bundle). The same applies to bundles.

I'm not total clear what you mean. I assume the excludes list just means that the files are not list on sf_cache page and so not turned into sf_cache files, nor replaced. The "added" is confusing since the files are already added by the theme. SF_Cache is replacing. I should not say lose my theme style.css because I ticked exclude by mistake.

The excludes list would seem useful for reducing the amount of info presented but perhaps it would be better as an include or by default set to exclude all. I know on my site there are unused themes and unused modules (some core) so leaving them out would simplify SF_Cache display.

UPDATE:

I tried this. I added all my spare themes to the exclude list. Gave me a long list of files excluded but did not change the display of the css page. Still have all the css files in the css directory too so has saved any site MB. I'm not really sure what it is meant to do then. If it just excludes from a bundle then all I have to do is leave that file out of the bundle.

Tricky, I'm naturally not keen to give out admin access.

I put "sites/all/themes/zen" (without "") in the exclude list. It made that into "sites/all/themes/zen/*.*" (without "") and gave me a long list of files that excluded. For example, sites/all/themes/zen/style.css and sites/all/themes/zen/theme-settings.js . If then I go back to the main list..... Hmm. They are now gone. Odd I'm sure i looked at them. Perhaps something need to update or refresh. I put in Zen twice and deleted the copy. Now the css files list is as expected. Odd, but is working now so nothing to sort out.