PHPDeveloper.org

Inhoud syndiceren
Up-to-the Minute PHP News, views and community
Bijgewerkt: 1 dag 20 minuten geleden

Reddit.com:

wo, 22/05/2013 - 18:52

Over on Reddit.com recently a discussion was kicked off asking people what framework they used for REST - their tool of choice for making API creation simple.

I was wondering what people here preferred for setting up REST APIs. Specifically if they had a preferred PHP framework for setting them up. in the past I had used CodeIngiter but am looking at Laravel some recently. I don't anticipate extremely heavy usage but I'd like to easily update the framework when it has new releases without a real pain working around my models and controllers.

Several different options were mentioned in the comments including:

Do you have a favorite you use for your REST APIs? share it here!

Link: http://www.reddit.com/r/PHP/comments/1em2ne/preferred_framework_for_rest_usage

Reddit.com:

wo, 22/05/2013 - 18:52

Over on Reddit.com recently a discussion was kicked off asking people what framework they used for REST - their tool of choice for making API creation simple.

I was wondering what people here preferred for setting up REST APIs. Specifically if they had a preferred PHP framework for setting them up. in the past I had used CodeIngiter but am looking at Laravel some recently. I don't anticipate extremely heavy usage but I'd like to easily update the framework when it has new releases without a real pain working around my models and controllers.

Several different options were mentioned in the comments including:

Do you have a favorite you use for your REST APIs? share it here!

Link: http://www.reddit.com/r/PHP/comments/1em2ne/preferred_framework_for_rest_usage

Reddit.com:

wo, 22/05/2013 - 18:52

Over on Reddit.com recently a discussion was kicked off asking people what framework they used for REST - their tool of choice for making API creation simple.

I was wondering what people here preferred for setting up REST APIs. Specifically if they had a preferred PHP framework for setting them up. in the past I had used CodeIngiter but am looking at Laravel some recently. I don't anticipate extremely heavy usage but I'd like to easily update the framework when it has new releases without a real pain working around my models and controllers.

Several different options were mentioned in the comments including:

Do you have a favorite you use for your REST APIs? share it here!

Link: http://www.reddit.com/r/PHP/comments/1em2ne/preferred_framework_for_rest_usage

PHPMaster.com: Openbiz Cubi: A Robust PHP Application Framework, Part 2

wo, 22/05/2013 - 17:27

PHPMaster.com has posted the second part of their look at the Openbiz Cubi framework (part one here), this time focusing on the code - mostly XML - that you'll need to create your own custom module.

In the first part of this series we talked about the development challenges we face and how Openbiz Cubi can help by providing a solid, ready-to-use web application framework. In this part we'll see how to build our own module and dive a bit deeper into the core architecture of the framework.

They include the SQL you'll need to run to create a new table for the "Customer" module they're going to help you build. With that in place, they walk you through the command to execute to make the module skeleton, the locations of the XML files to work with and the contents of each. Included in the module are things like a data object, a module description file and the form object. He finishes up the post with a look at the overall flow of the Cubi execution so you know where each piece falls.

Link: http://phpmaster.com/openbiz-cubi-a-robust-php-application-framework-2

PHPMaster.com: Openbiz Cubi: A Robust PHP Application Framework, Part 2

wo, 22/05/2013 - 17:27

PHPMaster.com has posted the second part of their look at the Openbiz Cubi framework (part one here), this time focusing on the code - mostly XML - that you'll need to create your own custom module.

In the first part of this series we talked about the development challenges we face and how Openbiz Cubi can help by providing a solid, ready-to-use web application framework. In this part we'll see how to build our own module and dive a bit deeper into the core architecture of the framework.

They include the SQL you'll need to run to create a new table for the "Customer" module they're going to help you build. With that in place, they walk you through the command to execute to make the module skeleton, the locations of the XML files to work with and the contents of each. Included in the module are things like a data object, a module description file and the form object. He finishes up the post with a look at the overall flow of the Cubi execution so you know where each piece falls.

Link: http://phpmaster.com/openbiz-cubi-a-robust-php-application-framework-2

PHPMaster.com: Openbiz Cubi: A Robust PHP Application Framework, Part 2

wo, 22/05/2013 - 17:27

PHPMaster.com has posted the second part of their look at the Openbiz Cubi framework (part one here), this time focusing on the code - mostly XML - that you'll need to create your own custom module.

In the first part of this series we talked about the development challenges we face and how Openbiz Cubi can help by providing a solid, ready-to-use web application framework. In this part we'll see how to build our own module and dive a bit deeper into the core architecture of the framework.

They include the SQL you'll need to run to create a new table for the "Customer" module they're going to help you build. With that in place, they walk you through the command to execute to make the module skeleton, the locations of the XML files to work with and the contents of each. Included in the module are things like a data object, a module description file and the form object. He finishes up the post with a look at the overall flow of the Cubi execution so you know where each piece falls.

Link: http://phpmaster.com/openbiz-cubi-a-robust-php-application-framework-2

PHPClasses.org: 5 Reasons Why the Web Platform War is Over: PHP Won with 75% says Google

wo, 22/05/2013 - 16:06

In this new post to the PHPClasses.org blog Manuel Lemos talks some about the recent introduction of PHP into Google's App Engine offerings.

During Google I/O 2013 event a Google manager said PHP runs on 75% of the Web sites. So they decided to finally support PHP as in their AppEngine hosting service. Read this article to understand why this puts an end to years of false claims that PHP was losing market, as well what it means to Web developers using PHP or other languages.

He looks at the App Engine PHP offering and looks at whether or not its a good platform to use for hosting your application. He points out some advantages and disadvantages (including no local file system access and no remote resource access). He also includes five reasons why the "web platform war is over" and why PHP has come out victorious:

  • Google Knows Because They Crawl the Whole Web
  • Google Does Not Influence Web Developers so much
  • Wordpress is the Dominant Blog Platform (not Blogger)
  • Programming Does Not Have to Be Beautiful
  • PHP Detractors Have the Wrong Focus

He admits, though, that PHP may not be dominant forever - it's not perfect, but there will always be a need for something that does what it can do (and does it well).

Link: http://www.phpclasses.org/blog/post/208-5-Reasons-Why-the-Web-Platform-War-is-Over-PHP-Won-with-75-says-Google.html

PHPClasses.org: 5 Reasons Why the Web Platform War is Over: PHP Won with 75% says Google

wo, 22/05/2013 - 16:06

In this new post to the PHPClasses.org blog Manuel Lemos talks some about the recent introduction of PHP into Google's App Engine offerings.

During Google I/O 2013 event a Google manager said PHP runs on 75% of the Web sites. So they decided to finally support PHP as in their AppEngine hosting service. Read this article to understand why this puts an end to years of false claims that PHP was losing market, as well what it means to Web developers using PHP or other languages.

He looks at the App Engine PHP offering and looks at whether or not its a good platform to use for hosting your application. He points out some advantages and disadvantages (including no local file system access and no remote resource access). He also includes five reasons why the "web platform war is over" and why PHP has come out victorious:

  • Google Knows Because They Crawl the Whole Web
  • Google Does Not Influence Web Developers so much
  • Wordpress is the Dominant Blog Platform (not Blogger)
  • Programming Does Not Have to Be Beautiful
  • PHP Detractors Have the Wrong Focus

He admits, though, that PHP may not be dominant forever - it's not perfect, but there will always be a need for something that does what it can do (and does it well).

Link: http://www.phpclasses.org/blog/post/208-5-Reasons-Why-the-Web-Platform-War-is-Over-PHP-Won-with-75-says-Google.html

PHPClasses.org: 5 Reasons Why the Web Platform War is Over: PHP Won with 75% says Google

wo, 22/05/2013 - 16:06

In this new post to the PHPClasses.org blog Manuel Lemos talks some about the recent introduction of PHP into Google's App Engine offerings.

During Google I/O 2013 event a Google manager said PHP runs on 75% of the Web sites. So they decided to finally support PHP as in their AppEngine hosting service. Read this article to understand why this puts an end to years of false claims that PHP was losing market, as well what it means to Web developers using PHP or other languages.

He looks at the App Engine PHP offering and looks at whether or not its a good platform to use for hosting your application. He points out some advantages and disadvantages (including no local file system access and no remote resource access). He also includes five reasons why the "web platform war is over" and why PHP has come out victorious:

  • Google Knows Because They Crawl the Whole Web
  • Google Does Not Influence Web Developers so much
  • Wordpress is the Dominant Blog Platform (not Blogger)
  • Programming Does Not Have to Be Beautiful
  • PHP Detractors Have the Wrong Focus

He admits, though, that PHP may not be dominant forever - it's not perfect, but there will always be a need for something that does what it can do (and does it well).

Link: http://www.phpclasses.org/blog/post/208-5-Reasons-Why-the-Web-Platform-War-is-Over-PHP-Won-with-75-says-Google.html

Community News: Packagist Latest Releases for 05.22.2013

wo, 22/05/2013 - 15:09
Recent releases from the Packagist:

Community News: Packagist Latest Releases for 05.22.2013

wo, 22/05/2013 - 15:09
Recent releases from the Packagist:

Community News: Packagist Latest Releases for 05.22.2013

wo, 22/05/2013 - 15:09
Recent releases from the Packagist:

Community News: Latest Releases from PHPClasses.org

wo, 22/05/2013 - 14:03

Community News: Latest Releases from PHPClasses.org

wo, 22/05/2013 - 14:03

Community News: Latest Releases from PHPClasses.org

wo, 22/05/2013 - 14:03

PHPMaster.com: Understanding HTTP Digest Access Authentication

di, 21/05/2013 - 19:09

On PHPMaster.com they've posted a new tutorial by Sean Hudgston that helps you understand HTTP digest authentication, a simple way to authenticate a user or script against your application.

Digest Access Authentication is one method that a client and server can use to exchange credentials over HTTP. This method uses a combination of the password and other bits of information to create an MD5 hash which is then sent to the server to authenticate. Sending a hash avoids the problems with sending a password in clear text, a shortfall of Basic Access Authentication.

He starts out by looking at the "basic authentication" mechanism that's built into most web servers and points out that it has a major flaw - sending the username/password in (pretty much) plain text. Digest, on the other hand, uses a MD5 hash created from a few pieces of information including username, realm and request method. The result is sent as a header back to the server that can then be parsed by PHP. He also talks about improving on the basic version of the digest method using the qop, nc, and cnonce optional parameters.

Link: http://phpmaster.com/understanding-http-digest-access-authentication

NetTuts.com: How to Create a PyroCMS Theme

di, 21/05/2013 - 18:19

On NetTuts.com today there's a new tutorial posted showing you how to create a theme for PyroCMS, an open source, PHP-based content management system with a large user base and community.

Like most content management systems, PyroCMS uses front-end themes. Though PyroCMS themes are built a bit differently than what you might be used to from other systems, they're still quite easy to create. They're so easy, in fact, that very little PHP experience is required to assemble them!

He walks through things like the folder structure of the templates directory and how to get started on a custom "Foo" theme of your own. He covers how to lay out the HTML markup for the theme and how you can use partials for the sections of the site. He briefly touches on using multiple layout files and how to use different layouts shown only to mobile devices.

Link: http://net.tutsplus.com/tutorials/php/how-to-create-a-pyrocms-theme

Gonzalo Ayuso: Google App Engine, PHP and Silex. Setting up a Login Provider

di, 21/05/2013 - 17:41

Gonzalo Ayuso has a new post to his site today showing how to use the recently released PHP support for the Google App Engine along with Silex to create a login provider.

Last week Google announced the PHP support for Google App Engine (GAE). PHPStorm, the great IDE for PHP development, also announced support for Google App Engine PHP. Because of that now is time to hack a little bit with this new toy. [...] To build a simple Silex application over Google App Engine is pretty straightforward (more info here). Because of that we're going to go a little further. We are going to use the log-in framework provided by GAE to log-in with our Goggle account within our Silex application. In fact we can use the standard OAuth authentication process but Google provides a simple way to use our gmail account.

He includes the code showing what the end result will look like as well as what's needed for the "LoginProvider" class. He also creates an "Auth" class where most of the work is done - creating the login URL, redirecting the user and checking to see if the user is logged in. He's made a screencast of the full process so you can see the authentication flow as its happening.

Link: http://gonzalo123.com/2013/05/20/google-app-engine-php-and-silex-setting-up-a-login-provider

Michelangelo van Dam: Survived php tek 2013

di, 21/05/2013 - 16:31

If you weren't able to make it to this year's php|tek conference in Chicago, Michaelangelo van Dam has posted a great wrapup of the event and some of the things that happened during the week.

If you were last week in Chicago, you've might felt the city was buzzing PHP all over the place. php[tek] 2013 was taking place at the Sheraton Gateway Suites Chicago O'Hare in Rosemont, just outside of Chicago city. This year it was also the first time Musketeers.me, a php consulting team from the East Coast, was running the show, putting their own signature onto the event. And with great success I might add. A well deserved applause to Eli White, Kevin Bruce, Sandy Smith, Oscar Merida and of course the Beth Tucker Long for their unlocked achievement running a great conference.

He talks about running the unconference for this year's event and one talk that resonated with a lot of people at the conference, Ed Finkler's "Open Sourcing Mental Illness". He also goes through some of the other regular sessions talks he found interesting covering things like security, refactoring, and dealing with distractions during work. He also mentions the hackathon and some of the good work that was done there.

In my experience the best php[tek] ever, and I'm really looking forward to the 2014 edition. If you don't believe me, have a look at the pictures taken at php[tek] 2013. They will tell the story. Link: http://www.dragonbe.com/2013/05/survived-php-tek-2013.html

Community News: Packagist Latest Releases for 05.21.2013

di, 21/05/2013 - 15:09
Recent releases from the Packagist: