David HH has an interesting piece on “The false promise of template languages”. While neither Perl nor PHP may offer the same clean syntax in the code as Ruby can do, it does indeed raise a few interesting questions about how actually benefit from the templates and who does in the space between designers and developers. I do love some degree of separation between heavy duty code and the interface layer, and usually work with HTML::Template or Smarty – they work and the penalty for using a separation layer seems to be the smallest possible (at least in a balanced performance/ functionality view).
Providing feedback in user interfaces is quite important. If you have a task, which may take a while, one of the ways to signal to the users, that the system is working, is by displaying a progress bar. If you don’t know how to make one, we do have one available for you.
A new group has appeared on the net – the PHP Security Consortium (PHPSC). It is an international group of PHP experts dedicated to promoting secure programming practices within the PHP community. Nice. While many PHP developers make sites people are supposed to use and enjoy, few as actual education and experience in how to make secure applications and websites.
Through projects and articles, they’ll try to educate PHP developers.
Most developers and programmers know more than one programming language, but often do most of their development in just one language. Listening in on IRC channels on people using something other than their favourite language is often quite interesting. It’s often a common misconception, that their favoured programming language - be that perl, php or java - is the ultimate tool no matter what the challenge is. When they are forced to use something else, a large part of the development process seem dedicated to (a) bitching about how much easier this and that would be in their favoured language and (b) forcing the language they use into looking like their favoured language.
It’s been awhile since Stuart Langridge released some cool javascript which allows you t do client-side sorting of tables in an unobtrusive manner. Soon after Andy Edmonds released a merge with a function to made alternating row coloring he had made. Now Caspar has done a little magic and added (cookie) memory to the script – so it remember you most recent sort from visit to visit. The code is in my pre-alpha markup area.