The Laravel News site has continued their series of posts covering the creation of a Laravel translation package with part two of the series. In this latest article they build on part one's introduction and start to build out some of the scaffolding for the package.

In Part 1, we introduced that this series would cover the process of building and maintaining an open-source package for Laravel. Check it out for an overview of what we’ll create in this series. Next, we are going to get to work on scaffolding a new Laravel package.

The post then walks you though the basics of scaffolding a package including:

• repository setup
• Composer configuration creation
• defining the package structure
• the creation of a service provider
• testing

Examples of the Composer configuration are included but the remainder of the points will be developed over the next several parts of the series.

On PHPBuilder.com today they have another tutorial that involves the Fuel PHP framework (previously mentioned here). This time, though, they dive in a bit deeper and look at how to create a database-driven application using the database/ORM tools the framework comes bundled with.

In a recent article I introduced the Fuel PHP framework, which shows great promise despite its status as a relative newcomer to the crowded PHP framework market. While hopefully this introductory tutorial helped to acquaint you with fundamental Fuel concepts, it barely scratched the surface in terms of its impressive capabilities, so I thought it would be worthwhile to pen a follow-up article which examines a feature fundamental to almost any web application no matter how small: database integration.

He shows you how to configure your database connection settings, create your first model and work with the "oil" command line application to scaffold out the CRUD of interacting with the model.

Nik Chankov feels pretty strongly about the CakePHP framework - strong enough that he's written up a post of ten reasons why he thinks you should choose Cake over other PHP frameworks.

Here I want to list all those things, but near to each of them I will give short explanation what is it and how CakePHP implement it. So, if somebody ask me what are those 10 things which drive me to choose this framework as my primary one I will answer with [this list].

Included in his list are things like it's MVC pattern, the object relational mapping, that it's easily extensible, has ajax support and makes the CRUD scaffolding easy.

Nik Chankov feels pretty strongly about the CakePHP framework - strong enough that he's written up a post of ten reasons why he thinks you should choose Cake over other PHP frameworks.

Here I want to list all those things, but near to each of them I will give short explanation what is it and how CakePHP implement it. So, if somebody ask me what are those 10 things which drive me to choose this framework as my primary one I will answer with [this list].

Included in his list are things like it's MVC pattern, the object relational mapping, that it's easily extensible, has ajax support and makes the CRUD scaffolding easy.

The results of the latest poll from the International PHP Magazine are in. The question this time asked which, of the options given, were your favorites in the Smyfony project's feature set. There was a clear winner above all of the others - the scaffolding that it makes so simple.

Some of the other options that were included but didn't get nearly as many votes were:

• Simple templating and helpers
• Multilingualism and I18N support
• Object model and MVC separation
• Ajax support

Following at a distant second was the "Object model and MVC separation" choice (and to others, "Enterprise ready" and "Ajax support" nipping close at its heels).

Be sure to cast your vote in this week's poll that asks your opinion on some of the rules that the PHP Throwdown has set in place. Vote for the one that you think fits best with the spirit of the competition.

The results of the latest poll from the International PHP Magazine are in. The question this time asked which, of the options given, were your favorites in the Smyfony project's feature set. There was a clear winner above all of the others - the scaffolding that it makes so simple.

Some of the other options that were included but didn't get nearly as many votes were:

• Simple templating and helpers
• Multilingualism and I18N support
• Object model and MVC separation
• Ajax support

Following at a distant second was the "Object model and MVC separation" choice (and to others, "Enterprise ready" and "Ajax support" nipping close at its heels).

Be sure to cast your vote in this week's poll that asks your opinion on some of the rules that the PHP Throwdown has set in place. Vote for the one that you think fits best with the spirit of the competition.

In his latest blog post, Chris Shiflett talks about CakePHP "visiting" New York at this month's NYPHP meeting as well of some of his impressions on the framework.

Last night at the monthly NYPHP meeting, Nate Abele presented an introduction to CakePHP, a web application framework. The New York subway wasn't cooperating with my schedule, and due to a problem affecting all uptown 4/5 trains, I was 30 minutes late to the talk.

Here are some of my notes from the talk as well as the conversation we had over dinner and drinks later.

He wonders about if the fact that Cake supports PHP4 hinders it, the scaffolding available, Ajax functionality, and, of course, some of the security features of the framework. He notes that "as long as you stick to the Cake way of generating output, it handles the escaping for you" - definitely a plus.

In his latest blog post, Chris Shiflett talks about CakePHP "visiting" New York at this month's NYPHP meeting as well of some of his impressions on the framework.

Last night at the monthly NYPHP meeting, Nate Abele presented an introduction to CakePHP, a web application framework. The New York subway wasn't cooperating with my schedule, and due to a problem affecting all uptown 4/5 trains, I was 30 minutes late to the talk.

Here are some of my notes from the talk as well as the conversation we had over dinner and drinks later.

He wonders about if the fact that Cake supports PHP4 hinders it, the scaffolding available, Ajax functionality, and, of course, some of the security features of the framework. He notes that "as long as you stick to the Cake way of generating output, it handles the escaping for you" - definitely a plus.