Posted on 23 September 2004 by Demian Turner
According to a recent article at The Register, the IT salaries are on the rise again! At least in the UK – this has also been commented on by Harry. Needless to say corporate/media recognition of PHP is typically low and the language is not even mentioned in the results. However no need to worry, in fact moral of the story appears to be “drop everything and sell yourself as an HTML developer”:
The most popular skills demanded by the public sector were Oracle,
Office, SQL and Java. In terms of advertised salary Oracle developers
can expect £50,000, SQL developers £47,000 and Java developers £43,000,
figures for Office developers were not available. The rest of the Top
Ten was: Unix (£51K), HTML (£48K), Prince(£NA), Windows2000 (£NA), SQL
Server (£54K) and Visual Basic (£49K)
Posted on 21 September 2004 by Demian Turner
This is an article teaching PHP developers to set up and configure a LAMP system for web development.
LAMP [Linux, Apache, MySQL, PHP] refers to a set of software tools that allow for rapid development and deployment of sophisticated, robust web applications.
All components of LAMP can be downloaded and used for free. This helps a lot with cost savings, which is why so many webmasters and developers are moving to Linux and other open source solutions for a variety of projects.
Please click below to see the details of setting up a LAMP environment.
Posted on 21 September 2004 by Demian Turner
Codewalkers is proud to announce that the latest PHP Coding Contest has been released. In this latest contest, you are challenged to write a script that will connect all of the rooms on a map using the minimal amount of corridor blocks. A variety of prizes are being given and the top few places will be eligible to receive a prize. See http://codewalkers.com/php-contest.php for more information.
Posted on 15 September 2004 by Demian Turner
In searching around for solutions to the back button problem, I came across quite a useful article which discusses various approaches to this problem.
Too often web application designers attempt to disable the back
button, or simply refuse to support users who use or rely on the back
It doesn’t have to be that way. Disabling the back button is ultimately
impossible; it is far better to design for and live with the back
Well there are actually some nice hacks for totally disabling the backbutton, but the author is right, this is not an advisable solution.
There are three common problems
associated with the back button in a web application.
It’s helpful to identify which of these problems you are trying to solve:
It is important to clarify when it is appropriate to use GET and when POST, many developers pick and choose to suit their fancy but there are right and wrong reasons for each.
Where possible, GET requests should be used instead to perform read-only operations, like listing
information, displaying search results, showing menus, or executing reports.
These operations are normally
‘idempotent’ – if you carry out a read operation twice (for example by refreshing) no change
Read the article for the full story.
Posted on 14 September 2004 by Demian Turner
[Even though this posting is a thinly veiled promotion for commercial database software, I’m publishing it for those interested in migrating from MS products to MySQL — Demian]
In an era where data becomes volumetric in every business, much attention has been given to proper database management and the ease of data access. Businesses that use Access begin to look for an alternative which allows better database performance, higher reliability, higher flexibility, yet inexpensive.
With the numerous choices available in the market, considering you don’t want to put too much investment on it, only one, MySQL, stands out from the crowd. MySQL’s flexibility allows you to deploy it cross various platforms, it also allows multiple user access concurrently. If you wish, you can still continue to do your data administration through Access as a front end. However, despite the various MySQL’s features overtaking Access, whether or not to migrate your data from Access to MySQL still need an in-depth consideration.
In this paper, I will firstly discuss about whether or not to migrate your Access data to MySQL. Then, I will cover about the considerations, planning and preparations which you should made before migrating your data. After all the planning and preparation stages has been finished, I will illustrate to you how the migration can be done with the help of Navicat, a MySQL database administration GUI.
This article continues at: http://www.geocities.com/mchuthor/article_access2mysql.html
Posted on 13 September 2004 by Demian Turner
Seagull 0.3.10 is out at last, a lot of new features have gone into this release:
- a web-based installer has been added thanks to Gerry Lachac
- Seagull is now PHP5 compatible
- a PEAR installable version is available weighing in at half the size of the full package
- upgraded to the latest htmlArea 3, wysiwyg editing now works fine in Mozilla and on Linux
- vertical, left-hand navigation added with 2 new stylesheets
- new Spanish translation (Mario Izquierdo)
- improved admin integration: easier to reset password, and now the admin user sees the same pages as public/member users with the addition of ‘Config’ and ‘Modules’ tabs
- big round of CSS fixes (Riccardo Magliocchetti)
- improvement to translation mgr, you can now check all modules at once to see which require updates (Werner M. Krauss)
- character map functionality added via htmlArea plugin
- improved db singleton method so you can connect to x number of DBs and have the connection cached for each one
- pagination improved and Pager now fully replaces DB_Pager (Lorenzo Alberton)
- plus quite a few more, see the changelog for full detals
There is also a new tutorial in the wiki that’s aimed at first time users/beginners which shows you how to create your own site with Seagull in 5 minutes.
Additional work has gone into the usual mountain of bugfixes and usability improvements, and also a front-controller (search engine friendly URLs) has been implemented but disabled by default. This will become standard in the next release and will be indicated by a new minor version number increase signifying the BC break.
Additional changes slotted for the next release are:
- core framework to be separated from optional modules
- module manager enhancement with the ability load and upgrade modules via PEAR’s XML-RPC mechanism
Posted on 08 September 2004 by Demian Turner
The amount of hair you can pull out if you don’t know your CSS tricks properly is impressive, thanks to this article a few subtleties are not left to trial and error.
Some useful comments too.
Posted on 06 September 2004 by Demian Turner
Via Derick, a story about
Linux acceptance in a critical emergency role at the Department of Homeland Security (DHS). Specifically, that article discussed YHD Software Inc. and its efforts to provide Emergency Response Network systems (ERN) currently being used by “the Federal Bureau of Investigation, the Department of Public Safety and the Department of Homeland Security”.
Full story here.
Posted on 05 September 2004 by Demian Turner
Thanks to Ben Ramsey who’s figured this out, has been driving me crazy for a while.
A while back I mentioned a problem I had with seeing the changes made to PHP after running a make and make install. I couldn’t see the new build date or the changes in phpinfo(), nor could I see the new build date with php -v. I was perplexed and frustrated.
Amazingly, after I rebooted my computer, the changes took effect. This was stupendously odd. I shouldn’t have had to reboot.
Yesterday and today I struggled with the same issue on two different machines. A reboot didn’t help, and advice given me in the comments of my previous post didn’t work, either. Finally, on a whim, I tried a make clean before running make; it worked!
Posted on 04 September 2004 by Demian Turner
Thanks to good old Damien Seguy from my home town of Montreal who’s spotted this interesting article on how to go about stored procedures in the upcoming MySQL 5. Missed altogether from the PHP blogosphere as far as I can tell, I guess it says something about the boundaries between the english and non-english parts of the community.
Still very little talk about stored procs in PHP circles, I hope this will change soon. At a recent contract in Latvia I showed up and was introduced to the 850 procedures that ran the application – a bit taken aback at first but I came to appreciate how much easier it made the project to maintain.
Unsurprisingly, many feats of programming cleverness are equated with great manhood and oneupmanship – the chief there used to boast how in his consultant days he had to run around cleaning up after the Oracle folk, and in one case reduced a stored proc running time from 2.5 days to a mere 6 hours 🙂