The Bakery Everything CakePHP

Thank you for this contribution. The article is a bit long, please split in into several pages. It is important to clearly separate the shared code and the articles usage examples. I suggest putting background and install instructions on page one, usage examples on page two, the shared code (ie the datasource file) on page three and api on page four.

Hey again. Impressive documentation block there :) Maybe you could put some of those examples in the article instead of the code. The php short tags I wanted you to remove are in the view example, short tags is php tag with out php (add it after the question mark). It will colour code the code and also, short tags are bad.

For more content in the actual article I would be interested to hear why you choose to put so much code in php for a javascript function? Also are there not many js library out there that will already do this? Adding some information of why you choose the implementation you did ads a lot to the articles usefulness.

An important change you need to make is to remove the echos from your helper. Cakephp helpers returns strings to the view, and the view echo it. (For instance look at how you use FormHelper). When designing the API for your assets, it's a good idea to study existing core and community build classes and see what they do. For instance, your setup method would work in a more conventional way if it took in an $options array where all of the options where optional, storing defaults in the class. Also giving the option to add the js and css to layout would be useful. For instance:
<?php function setup($options = array(), $inline = false) {
  $this->options = array_merge($this->defaultOptions, $options);
  if ($inline) {
    return $this->Javascript->link('validation').
       $this->Html->css('validation');
  } // else
  $view = ClassRegistry::getObject('view');
  if (is_object($view)) {
    $view->addScript($this->Javascript->link('validation'));
    $view->addScript($this->Html->css('validation'));
    return true;
  } else {
    return false;
  }
}
?>

I unpublished your comment as I published the article. Greate work. Thank you.

Should it not also use $Controller->Auth-> isntead of $this->Auth?

Thank you for contribution, but without code or content, I cant really publish this. In any case, you should include in the article information about what it does and how it works. Usage example is good, but an API is even better.