New JavaScript / CSS file bundling implemented

The css/js bundling that I wrote about in my previous post, have now been fully implemented, and is verified to work.

There are big differences with how file bundling is done now, compared to the first alpha and previous Wigbi versions:

• Pros:
  JS/CSS file bundling is Wigbi-independent and thus a new, full feature
  Compared to Wigbi 1.0 a1, no session handling is required
  JavaScript init code is packed and thus compact and obfuscated
• Con:
  Since no additional PHP file is used, the JavaScript init code is written to page

A new alpha release will be up shortly, once a bunch of data plugins have been created.

JavaScript and CSS file bundling in Wigbi 1.0

I have just blogged about JavaScript/CSS file bundling here.

In Wigbi 1.0, this new approach will replace the bundling that is used in 0.99.2, where the bundle PHP file automatically appends all JavaScript files that exist in the wigbi/js folder.

The old approach works well, since you just add all files you want Wigbi to include into wigbi/css and wigbi/js. However, this new approach is much more flexible.

In Wigbi 1.0, Wigbi will handle files by itself, and instead create a valid path to the bundle URL, which it then adds to the page.

This means that bundle URL will be entirely independent of Wigbi. You can thus use it for js/css files that exist anywhere else within the application, and even without being bound to use Wigbi.

The bundle urls will be
~/wigbi/bundle/js:<comma-separated file/folder list>
~/wigbi/bundle/css:<comma-separated file/folder list>

For further information, check out the full post here.