Subscribe
This year's PHP Advent calendar has finished up and if you haven't gotten a chance to check out some of the great content in this year's edition, be sure to take a look at the full list. It incudes topics like:
The articles are by several well-knowns both in the PHP community and outside. While you're there, be sure to check out some of the previous years too!
Padraic Brady has posted the third chapter of his "Zend Framework: Surviving The Deep End" book. It focuses on the Models in the Model-View-Controller (MVC) applications.
Today Chapter 3, The Model, has entered the online book. Apart from some early jitters when PHPIDS (an intrusion detection system I use) lost the plot and commenced a vendetta against Opera, the new chapter is fully operational.
If you get these first chapters, you'll notice that there's some color coding going on with status labels. Padraic is using this to give you some feedback as to the level of completion a certain chapter is in. He notes:
I've decided to start noting in these announcements that these early Chapters are akin to drafts. While they are written as complete units, it's intended to revisit them every few weeks for improvement until a final version emerges to be forever immortalised as a first edition of the book.
Paul Reinheimer has posted about a contest in the making - a turn-based robot battle sort of game where PHP scripts compete against each other.
Just a quick announcement, in an effort to come up with a self scoring contest, I came up with the ridiculously simple concept of robots firing lasers at each other in a fictional arena. Each robot controlled by a different PHP script, and a central arena managing it all. It's basically a turn based game where your robots take turns for you.
You can check out more about the game and its rules over on the Web Bot Battle site. It defines how your bots should act and even has some examples for you to work from.
In a new post Jonathan Street mentions a new PEAR package that's an API for the Compete API:
After writing about the compete API Hiroki Akimoto contacted me mentioning a proposal he had made to PEAR. Our scripts each had strengths and we decided to combine our attempts and hopefully make something better. After a week or so we updated the proposal with the new code and after a little time for comments and a week for voting the proposal was accepted and on 30th July a new package, Services_Compete, was available on PEAR
This package (currently in an alpha release, version 0.1.0) acts as a wrapper class to connect to and use the Compete SnapShot API.
In a new post Jonathan Street mentions a new PEAR package that's an API for the Compete API:
After writing about the compete API Hiroki Akimoto contacted me mentioning a proposal he had made to PEAR. Our scripts each had strengths and we decided to combine our attempts and hopefully make something better. After a week or so we updated the proposal with the new code and after a little time for comments and a week for voting the proposal was accepted and on 30th July a new package, Services_Compete, was available on PEAR
This package (currently in an alpha release, version 0.1.0) acts as a wrapper class to connect to and use the Compete SnapShot API.
Well, the PHP Throwdown event has come and gone with all of the teams giving their best creating an application hoping to reach the top.
Wow, what can I say but w00t! The throwdown was a tremendous success and went off without any major problems. We’re still compiling all the final projects and I’ll be reporting some statistics about those (as in who was using what and how many competitors we had per category). I am excited to see what all has come of it.
There were also bloggers from about the web that covered the event either for themselves or for the team they were a part of.
Congrats to all of those who participated and we'll all be anxiously awaiting the results! OH, and if you didn't get a chance to participate this year, you can still grab a tshirt to remember the event by.
Well, the PHP Throwdown event has come and gone with all of the teams giving their best creating an application hoping to reach the top.
Wow, what can I say but w00t! The throwdown was a tremendous success and went off without any major problems. We’re still compiling all the final projects and I’ll be reporting some statistics about those (as in who was using what and how many competitors we had per category). I am excited to see what all has come of it.
There were also bloggers from about the web that covered the event either for themselves or for the team they were a part of.
Congrats to all of those who participated and we'll all be anxiously awaiting the results! OH, and if you didn't get a chance to participate this year, you can still grab a tshirt to remember the event by.
For those PHPers out there that use the vi editor for their coding travels, Bjarte Karlsen has posted something that might help you out - two configuration files that he uses to work with PHP files in vim.
In a recent chat on #phpc we started discussing vim and talking about vim setups. Surripui posted a blog entry about this asking for setups. I promised that i would post my setup so here it is.
The two files are his:
Between the two of these, the editor is able to correctly handle PHP files, syntax check files and tab complete function names. There's also a mention of using gsnippets for working with code templates.For those PHPers out there that use the vi editor for their coding travels, Bjarte Karlsen has posted something that might help you out - two configuration files that he uses to work with PHP files in vim.
In a recent chat on #phpc we started discussing vim and talking about vim setups. Surripui posted a blog entry about this asking for setups. I promised that i would post my setup so here it is.
The two files are his:
Between the two of these, the editor is able to correctly handle PHP files, syntax check files and tab complete function names. There's also a mention of using gsnippets for working with code templates.It's always good to finish a rather large project, and Robert Peake shares his joy in this new post on his blog nothing that not only is the project off and running, but it was all created based on a best practices/standards-based approach with respect to PHP development.
I spent over 18 months architecting the system, from dedicated hardware to software including eCommerce, CRM, subscription management, recurring billing, and content management systems. I had great help from a small, dedicated, and very talented in-house team of artists and programmers. Absolutely everything is implemented on a LAMP stack.
He notes several of the things they used along the way, including:
I consider it a kind of real-world treatise on how to effectively implement enterprise best practices with LAMP technologies. No books, no debating, no theory -- we did it.
@phpdeveloper.org