I decided to review my PHP and now I’m interested with the Lithium project. I wanted to get my hands on it just to see what it can do and what are the good stuff in it. Lithium by the way is a PHP web framework, it’s RAD. If you don’t know what a PHP web framework is, I don’t think I can help you. But a Google with the topic can result to many useful resources.
I almost forgot most of my PHP background because it’s been 2 years since I coded it. And it was with 4.3 and Oracle. I’m not too sure about what to do next. Instead of installing everything from scratch, I decided to install XAMPP. It’s easy and good stuff (I think). Unlike before, installing PHP and Apache, make Apache recorgnized PHP, add a module to it, install MySQL… You know what I mean. It’s a hassle. But with XAMPP, it’s just a single install and everything is in there. Of course, this doesn’t help if you’re a geek and pretend to know everything and installing everything by hand makes you happy. But for me, it’s fine. For now.
When I got Lithium source, I just pasted it in the htdocs directory and there it goes. It’s slick. It also has some good tutorial in their site. Everything is good. Until I decided to check on Contribution. Not that I can contribute but who knows. I bumped into an error with the coverage. I never knew PHP has coverage. That’s interesting. So I Google a bit and read a few statements in lithium’s wiki about xdebug. There it is. XDebug is actually and extension for PHP and has good stuff. It has code coverage and everything useful for developing PHP applications. God, I never knew this is coming. The more I surf the net, the more I know things I don't know.
So back with the error, it has something to do with xdebug_start_code_coverage method not found. I ran into xdebug installation and it’s just adding the extension to the Apache. That’s simple, I think I can do that. But when I look into the XAMPP’s PHP installation, I noticed php.ini has the extension but commented. Ha! That’s even simpler. I uncommented it and voila. When running lithium test cases it fetched off the call stack with information I found some useful. Although I’m not too sure I’m too familiar with it. :)
I almost forgot most of my PHP background because it’s been 2 years since I coded it. And it was with 4.3 and Oracle. I’m not too sure about what to do next. Instead of installing everything from scratch, I decided to install XAMPP. It’s easy and good stuff (I think). Unlike before, installing PHP and Apache, make Apache recorgnized PHP, add a module to it, install MySQL… You know what I mean. It’s a hassle. But with XAMPP, it’s just a single install and everything is in there. Of course, this doesn’t help if you’re a geek and pretend to know everything and installing everything by hand makes you happy. But for me, it’s fine. For now.
When I got Lithium source, I just pasted it in the htdocs directory and there it goes. It’s slick. It also has some good tutorial in their site. Everything is good. Until I decided to check on Contribution. Not that I can contribute but who knows. I bumped into an error with the coverage. I never knew PHP has coverage. That’s interesting. So I Google a bit and read a few statements in lithium’s wiki about xdebug. There it is. XDebug is actually and extension for PHP and has good stuff. It has code coverage and everything useful for developing PHP applications. God, I never knew this is coming. The more I surf the net, the more I know things I don't know.
So back with the error, it has something to do with xdebug_start_code_coverage method not found. I ran into xdebug installation and it’s just adding the extension to the Apache. That’s simple, I think I can do that. But when I look into the XAMPP’s PHP installation, I noticed php.ini has the extension but commented. Ha! That’s even simpler. I uncommented it and voila. When running lithium test cases it fetched off the call stack with information I found some useful. Although I’m not too sure I’m too familiar with it. :)
Comments
Post a Comment