2013年3月25日星期一

Community News: Packagist Latest Releases for 03.25.2013

Recent releases from the Packagist:

NetTuts.com: The 11 Phases of a Web Developer's Career (As Illustrated by Memes)


NetTuts.com has started off the week on a humorous note with this latest post showing the "11 Phases of a Web Developer's Career" as illustrated with animated GIFs of various internet memes.



The career of a web developer is an interesting one with many slopes. Considering a learning curve this steep, you can fully expect to live through periods of frustration, enlightenment, self-righteousness, and every mindset in between. In this article, we'll have some fun, by reviewing each of these phases through the lens of a meme!

Some of the phases include:



  • Phase 1 - Noob
  • Phase 3 - Complete Frustration
  • Phase 5 - Fragile Code
  • Phase 7 - Cocky
  • Phase 9 - When Code Becomes Art
  • Phase 10 - Seasoned


Check out the post for the images of these and the others on their "top 11" list.

Lorna Mitchell: First Phing Plugin


In the latest post to her site, Lorna Mitchell walks you through the creation of a first Phing plugin, an extension to the popular PHP-based build tool.



I'm a huge fan of Phing and use it regularly for build and deployment tasks. Often, I'll ask about a plugin that I wish existed, and get a very courteous "patches welcome" from the nice people in the #phing channel on freenode. This has happened a few times, so I thought I should probably look at how to make a new phing plugin, this article shows you how to make the simplest thing I could think of: a simple "hello world" plugin.


She points you to the location to grab the latest version of the tool (the github repository) and how to define a configuration file for your test runs. Then she includes the sample code showing how to create the "HelloTask" plugin. It takes an input value of "name" and displays a greeting when executed. She shows the syntax for defining this in the XML build file and the sample result when executed.

Phil Sturgeon: Pick PHP Requirements for Packages Responsibly


In this recent post to his site Phil Sturgeon has a reminder that you should select the dependencies for your packages wisely, and not just because they're "cool."



When I say "make sure it is worth it" I mean, don't just switch your arrays from array() to [] just because it looks cool. That was the extent of my original tweet, because I've seen a few packages doing that and it annoyed me immensely. [...] Suffice it to say, if you require a user to upgrade their version of PHP simply so you can use some syntactical sugar inside a package that nobody else is even going to be looking at, then you're an idiot. Beyond that, you're actually hurting the community.


He notes that, by requiring users that are currently only at 3.1% of PHP installs to upgrade to 5.4 just to use your library is a quick way to not have your library used. He points out that PHP 5.4 is "more than just []" for arrays and includes a reminder that several projects are still in PHP 5.3-compatibility mode just because that's the widest audience. He also briefly touches on the "push it forward" comments that people have used to justify 5.4-only packages, but notes that it's still not as much up to the developer as it is the web host.

2013年3月24日星期日

Community News: Packagist Latest Releases for 03.24.2013

Recent releases from the Packagist:

2013年3月23日星期六

Community News: Packagist Latest Releases for 03.23.2013

Recent releases from the Packagist: