<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 18:29:09 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Stefan Koopmanschap's Blog: Using custom namespaces with (C/S)ilex and Composer]]></title>
      <guid>http://www.phpdeveloper.org/news/17810</guid>
      <link>http://www.phpdeveloper.org/news/17810</link>
      <description><![CDATA[<p>
<i>Stefan Koopmanschap</i> has a quick new post to his blog with <a href="http://www.leftontheweb.com/message/Using_custom_namespaces_with_CSilex_and_Composer">a handy tip for Composer and Cilex/Silex users</a> when dealing with custom namespaces.
</p>
<blockquote>
For a new proof of concept application I'm building, I need both a simple web interface as well as some commandline tools. I decided to use Silex for the web interface and Cilex for the CLI tools, and opted for using Composer for installing these dependencies into my project. I ran into some issues with the custom project libraries I was building for this application however. Registering my custom namespace into Silex and Cilex didn't result in the classes being loaded for some reason. Composer helped me out though.
</blockquote>
<p>
His solution involves letting Composer be the default autoloader for the application via an "autoloader" configuration option in the "composer.json"  (that can also take a classmap option if you're not PSR-0 compliant, <a href="http://getcomposer.org/doc/04-schema.md#autoload">see here</a>).
</p>]]></description>
      <pubDate>Thu, 12 Apr 2012 12:22:47 -0500</pubDate>
    </item>
  </channel>
</rss>
