+- CodeIgniter Forums (https://forum.codeigniter.com)
+-- Forum: Archived Discussions (https://forum.codeigniter.com/forumdisplay.php?fid=20)
+--- Forum: Archived General Discussion (https://forum.codeigniter.com/forumdisplay.php?fid=21)
+--- Thread: CodeIgniter 3.0 Roadmap (/showthread.php?tid=55391)
CodeIgniter 3.0 Roadmap - El Forum - 10-24-2012
[eluser]hsn22[/eluser]
I've been trying to find the road map for 3.0 and have been unable to find anything concrete. Just a few phrases here and there about license change and Input class returning NULL. What I'm trying to understand is if and how CI will deal with these below points:
1. Using Composer and packages
2. Autoloading and dependency injection
3. PHPUnit integration baked-in
4. HMVC
CodeIgniter 3.0 Roadmap - El Forum - 10-24-2012
[eluser]PhilTem[/eluser]
1. Noting major to find about that
2. Nothing to find about this
3. PHPUnit testing
4. HMVC
CodeIgniter 3.0 Roadmap - El Forum - 10-24-2012
[eluser]Aken[/eluser]
CI will be using Sparks, not Composer. http://getsparks.org/
CodeIgniter 3.0 Roadmap - El Forum - 11-13-2012
[eluser]Jonathon Hill[/eluser]
I for one much prefer Composer over Sparks. I wish the community had standardized around Composer and Packagist instead of rolling yet another repository and installer. The PHP community needs more interoperability, not less, but I digress.
If you want to use Composer, check out this installer which provides better support for CodeIgniter packages (including sparks) than the official composer/installers package:
compwright/codeigniter-installers
I am currently working on a way to have Composer install packages from getsparks.org without having to define your own custom repository to bridge the two together.