CakePHP 3.0 Namespace

cake3ns.markdown

CakePHP Core

• Core namespace: Cake
• Namespace will follow the directories, ie. Cake\Cache\Engine\ApcEngine, Cake\Controller\Controller
• View files don't need namespaces
• Basic functions will not be namespaced as well
• Use the class loader defined by the PHP Standard Group, see https://gist.github.com/562509
• Suffixes will not be removed (ie. HtmlHelper will be Cake\View\Helper\HtmlHelper instead of Cake\View\Helper\Html)
• Remove App::uses()
• Remove filemap
• Support full class name in configurations, ie. DebugKit\Controller\Component\ToolbarComponent instead of DebugKit.Toolbar

Plugins

• Plugin must use namespaces
• The default top level namespace will be the same of plugin name, but can be configured a custom namespace using the Plugin::load()

Applications

• Application must use namespaces
• Include in core.php a configuration to indicate the application namespace (empty for global)

@ADmad I implemented and forgot to update this document. You will be able to put the files as you described, but you will have to setup the custom namespace in the Plugin::load(). Ie, Plugin::load('ADSearch', array('namespace' => 'ADmad\Search')) will load files on APP/Plugin/ADmad/Search/....

So you can use like $components = array('ADSearch.PrgComponent');.

I will update the document with that.

@jrbasso That takes care of two plugins with same name. Will that also allow me to simultaneously load PrgComponent from both the Search plugins? If that's the case then I am happy :)

Yes, you can use the className option available in the collections, so you can load simultaneously like that:

public $components = array(
  'ADPgr' => array(
    'className' => 'ADmad\Search\Controller\Component\PgrComponent'
  ),
  'CakePgr' => array(
    'className' => 'CakeDC\Search\Controller\Component\PgrComponent'
  )
);
// use $this->ADPgr and $this->CakePgr

Silly me, totally forget we already have classname aliasing.