Remove the dev/deploy concept of static resource packing

[Paul Everitt]

...or composing, or whatever.

Let's rely on far-future expires to let us use jQuery, jQuery UI, and TinyMCE's "all in one" JS files without any system to try and compose all the JS into one URL.

Reduce as much complexity as possible. If we can get rid of different modes, and different code in the configuration files, then let's do so.

Later, if we find that we need to bring back some complexity, let's do so.

[Paul Everitt (paul-agendaless)]

Balazs, if this is something you think could be done by another person, or if you're busy this week, please let me know.

[Paul Everitt (paul-agendaless)]

Ok, guess I got my answer on https://bugs.launchpad.net/karl3/+bug/409055/comments/1

I'll see if Mike and Derek can pick up this and the other ticket.

[Paul Everitt (paul-agendaless)]

Move to next week.

[Paul Everitt (paul-agendaless)]

A brief "please please" on this.

We are still struggling with IE6 caching. It would be swell if the jQuery UI .css files (ui.base.css and friends) were combined into one. It would eliminate an extra 8 requests, I believe.

[Paul Everitt (paul-agendaless)]

After talking with Balazs and Mike, here's the plan:

- We'll keep a mode that allows you, personally, to go into jsdev mode

- All other modes (dev mode, deploy) will use the same approach

- "Library" code from external projects will be treated differently than KARL code

 - Library code changes very, very rarely

 - Library code has lots of files, many of large size

 - Thus, library code is a good target for one-time "optimization"

 - KARL code changes frequently

 - We need to avoid asking Balazs to re-run something each time we change KARL code

- Library code will be:

 - Joined together into a small number of files

 - No compression (we'll let Apache do gzip)

 - No packing or minifying (the gain isn't worth the lack of production debugging)

- KARL code will be:

 - Served up individually

[Paul Everitt (paul-agendaless)]

Let me add another point to this...

Balazs, feel free to do whatever you want with the "library" part. Minify, pack, whatever. Mike said that some browsers, even if you far-future, still ping the server.

So if you'd like, go right ahead and reduce the library.

[Paul Everitt (paul-agendaless)]

Balazs, I believe you are finished with this one. Let's mark it closed if there is no next action (beyond the other reported issue of the flashing JS error.)

[Paul Everitt (paul-agendaless)]

We still have more than I would like. For example, we seem to fetch 7 resources related to grid and autobox. However, marking this as complete.