Re: [PEAR2] Proof of Concept Proposal - Dependency Injection

Hey there Shawn, I'm not sure why this got lost in the threads but let me attempt to kick-off a discussion :) > > I've got a package that I'm thinking might be a good fit for PEAR2, at least > as a proof of concept, it's technically still a proof of concept and it's a > fork from another BSD licensed project.  The container is called Wires, I > made it namespace / php5.3 compliant a while back and made some changes over > the weekend to refactor it to PEAR2 naming conventions (and use the PEAR2 > namespace.) That's really good to hear. > The project is currently up at Github - > http://www.github.com/mfacenet/Wires, the initial project (what > was > originally forked) https://github.com/spiralout/Wires, and the > CI server for > this package is http://phpdocumentor.org:8080/job/Wires/ > currently average > overall test coverage is 81%, all tests pass.  That being said, there are a > few other things that this project will need while I'm continuing to develop > it, I need to convert it to follow the PEAR2 code standards better, the api > documentation can definitely use some embellishment, I'd like to add other > configuration options (such as XML, INI, and possibly YAML,) and finally it > needs some real world usage to track down bugs. I think this would make an > excellent addition to PEAR2 as it's a simple library allowing developers to > use the Inversion of Control ideology. > This is looking version. I was thinking about codesniffer and was wondering if anyone had an idea where we could find a PEAR2 standards codesniffer as right now the current codesniffer with PEAR standards doesn't pass for PEAR2 formatted packages. Anyone has any feedback? -- David Coallier