• Hi, new automatic minify is absolutely huge killer feature! ??

    I think there are some reasons to do not minify all sources together. Like:

    • CDN network sources (google jquery etc.) with fallback to local
    • Critical/uncritical (functional/design – Some jquery functional plugins vs. cufon fonts). This could be loaded separately. Fonts take much capacity, one extra large minified file is worse than two medium sized. Even at the cost of two http requests
    • separate functional layers: standard generated page for visitor and special page for editor. eg. new Front-end-editor with Aloha inline editor. There are so many big javascript libraries. Minify groups/packages of javacrips for most of users(visitor). Minify another separate package for editor (script which are embeded when is user logged in – Admin bar etc.)
    • Not compatilable with minification or problematic: for example LESS.js with less css file, solution: exclude from minify. Minify broke less style. Or jquery.cycle.js sometimes broke minification and must be separate

    Similar examples should be for CSS minification.

    I know there is still manual mode. But automatic is absolutely best, because relieves quite complicated hand work.

    Some humble implemntation ideas:

    Every JS and CSS embeded by plugin uses handle string. Eg. expression: aloha-* groups all enqueued files with handle starting link aloha-

    But theme files are sometimes embeded in code. There must be similar behavior like in manual minify.

    Regards.

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Auto minify – excludes and groups’ is closed to new replies.