mklabs / cakes Goto Github PK

• Tasks may be created using different modules (css, js, html, img, ...)
• A module defines a set of tasks
• A task is simply a function of the form
  • exports.task = function(options, em) {}
• tasks needs a name/description: name is the fn name, description could be attached to the fn (eg. exports.task.description).

modules would be autoloaded at runtime. The cake script could automatically load modules in a tasks/ folder or something.

probably, a simpler way of doing this would be to rely on vm.createInContext stuff to autoload modules in tasks/ and still use the same cake syntax.

doing this may also allow the use of regular .js files instead of .coffee. Both should work.

• stick with conf/default.coffee, but have to better declare namespace (quite ugly now)
• using json files
• using yaml files
• ini files

Inspiration from:

• Cake Php Assets Compress -> ini files
• Jammit -> yml files
• ...

should be easy to configure assets:

• each package, order of concat
• like Jammit, should be a list of glob patterns. This is also the way ant scripts are doing this usually, eg. ant fileset although a bit different)
• ...

Such as in .gitignore we have a line for h5bp/builds and cake createproject outputs to that dir.

We'll need to modify the Cakefile of course.

since its about build script, we can afford to go sync.

The emitter and (simple) task dependency stuff would remain, but the actual task code may try to use sync methods as much as possible, will drastically cut the overall size and the amount of nested callbacks.