Limit CSS selector count to 4095

I have create a patch that allows advagg to part out a single source CSS file over 4095 rules long into multiple parts first, then include them individually as style tags after aggregation.

This patch does assume that there are no media query blocks spanning the rules where it needs to split up the files at. (AKA: around every 4000th rule or about there).

OK I will see if I can implement advagg_parse_media_blocks() in the split line finding part

I worked on this patch for Drupal 6 where it will divide the css file groups in subgroups if it exceeds the selector limit.

The patch in #13 seems to work as expected from an initial test - will test some more before marking as RTBC though. Also there are a couple of typos and coding standards issues in the patch - will add a new patch later.

After applying the patch in #13 and enabling advagg_bundler, the advagg_bundler_selector_count table isn't actually created, because there isn't a hook_install calling drupal_install_schema()

Here's a new patch

@malcomio could you post an interdiff so we can see what you changed? @see https://drupal.org/documentation/git/interdiff

+++ b/advagg_bundler/advagg_bundler.admin.inc
@@ -23,10 +23,10 @@ function advagg_bundler_admin_settings_form() {
-    '#type' => 'checkbox',
-    '#title' => t('Bundler is Active'),
-    '#default_value' => variable_get('advagg_bundler_active', ADVAGG_BUNDLER_ACTIVE),
-    '#description' => t('If not checked, the bundler will passively monitor your site, but it will not split up aggregates.'),
+    '#type'           => 'checkbox',
+    '#title'          => t('Bundler is Active'),
+    '#default_value'  => variable_get('advagg_bundler_active', ADVAGG_BUNDLER_ACTIVE),
+ '#description'    => t('If not checked, the bundler will passively monitor your site, but it will not split up aggregates.'),

This type of indentation is not in our coding standards. https://drupal.org/coding-standards

Also changing the indentation makes it hard to see what part of the code is actually fixing the bug/feature in the issue so please avoid going all out and move the cleanup coding standards stuff to it's own issue(usually).

Good point - here's a new patch without the coding standards changes, and an interdiff.