By “where”, I literally mean “where”. PHP is typically used in server-side scripts, the output of which is served over the internet. As expected. But I’ve just finished writing an article on PHP-CLI, or using PHP on the command line, and we also have an article in the works on desktop applications in PHP.
Given the fantastic resources available for PHP development, and the possibilities for desktop applications, PHP-GTK- and WinBinder-based desktop applications written in PHP could be really powerful. Sure, they’re not terribly efficient, but I suspect in the next few years these applications - especially PHP-GTK, thanks to Glade - will really take off.
Keep your eyes peeled on the DT homepage for an interesting overview of desktop application development in PHP; if you really can’t wait, head to gtk.php.net and amuse yourself with the vast array of UI elements you can draw in just two lines of PHP. Where do you think PHP is headed? Will desktop apps really take off, or are they just a passing craze, like Wiimote-powered media players?
Akash Mehta in General, PHP | No Comments »
Over the years, I’ve seen quite a few different development environments, and I’ve come to the conclusion that there’s one perfectly simple way to keep software development running smoothly: keep your developers happy. Read on for the how and why of cheerful developers. (more…)
Akash Mehta in General | No Comments »
So, you’re an up-and-coming PHP developer, you’re spending a lot of time learning new tricks and you’re always on the bleeding edge when it comes to using technologies in your web applications. What’s next? Here are some of the options available for professional development. (more…)
Akash Mehta in PHP | 2 Comments »
It doesn’t advertise itself as such, but the jQuery JS framework is quite possibly one of the best JS frameworks for PHP developers. Most of the frameworks out there are designed for developers with JavaScript experience, and understandibly so. But when I first started using jQuery, my JavaScript experience was something along the lines of “take the dollar symbol out and your PHP is magically syntactically valid JS”. (Pitiful, I know.)
The main advantage of jQuery for us PHP developers is that it utilises our existing knowledge. When PHP code brings you closer to the HTML and other UI needs - CSS, for instance, - jQuery leverages that knowledge. It takes a little while to get used to functional programming, of course, but with CSS selectors, basic method chaining, and an approach to event handling that just works, jQuery is an ideal framework for PHP developers getting started with JavaScript interaction design.
So, next time you’re looking to get your hands dirty with DOM, DHTML and AJAX, head over to jQuery.com and give it a go.
Akash Mehta in JavaScript, PHP, Web | No Comments »
Web hosting: the bane of our existence. Time spent preparing servers, publishing code, dealing with deployment issues — as opposed to throwing money at unreliable oversold shared servers. Here’s why you should leave web hosting to the professionals (more…)
Akash Mehta in Web | No Comments »
GOTO, the infamous much-loathed feature of languages in decades gone by, is (sort of) coming to PHP. Read on to see why it’s actually a good thing. Luckily, it’s not that bad. In fact, it’s quite handy. (more…)
Akash Mehta in PHP | No Comments »
It’s a common point of heated debate between Ruby on Rails and PHP developers - can we really compare Rails with PHP? While most PHP developers would contest it, it’s a perfectly good comparison. Here’s why. (more…)
When it comes to choosing a framework, PHP developers are very much spoilt for choice. From Rails-alternatives, to .net-in-PHP attempts, beginner-oriented procedurals to full-on enterprise systems, and even those that let you code however you like, there’s bound to be a framework out there for you. Of course, if there isn’t, you can always take an existing one and modify it to suit your needs (although most are sufficiently extensible).
Wikipedia has probably the definitive list of major PHP frameworks, covering everything from CakePHP to Drupal to the Zend Framework, and includes a few notable yet less-known options. Of course, this doesn’t tell you much about them; the comparison table is a little more helpful, although it isn’t restricted to PHP-frameworks.
There are a few important features to look for in frameworks:
Beyond this, take a look at the options out there. If you’re familiar with Rails, take a look at CakePHP and CodeIgniter. If you’re more of a .net person, Prado might interest you. If you’re looking for a CMS that you can code on top of, take a look at Joomla. One website even has a feature-by-feature comparison, although beware of following it entirely, as it doesn’t really reflect the true power of each framework.
Of course, while you may be undecided on your choice of framework, one thing is certain: you should be using a framework, if only one you hacked together in a couple of hours. Most frameworks will help you code quicker and more consistently, code reuse is suddenly the drop-in-place approach it should be, and it’s always handy to be familiar with a dev shop’s adopted CMS when sending them your resume.
Most PHP developers have at least heard of GD2; thanks to its prolific use in CAPTCHA generation, the image functions in PHP are standard practice for many. But the extension’s uses don’t end there. After the fold, here are eight cool things you probably weren’t aware could be done with GD2, and might be useful for your web applications. (more…)
So, you’re about to build an entire web application in PHP. You’ve worked out how you’re going to do it, you’ve got a general idea what it’ll look like, maybe you’ve even chosen a framework (if you don’t have any to choose from, find some). Before you go any further, take a step back and run through this checklist.
