Some PHP Research 
Sunday, October 21, 2007, 12:27 AM - Website, Tutorial
Posted by Administrator
Error Handling in PHP:
* Using 'die($errorMessage)' statements
* 'trigger_error($errorMessage,ERROR_LEVEL)' used in conjuction with 'set_error_handler()'
* Using the PEAR_ERROR object
* Using boolean flags

http://www.devshed.com/c/a/PHP/Error-Ha ... fensively/

Form Validation:

A more structured reusable style of form validation, instead of going ad-hoc:
http://www.phppatterns.com/docs/develop ... ing_in_php

For Later Reading

Unit Testing in PHP: http://www.phppatterns.com/docs/develop ... ing_in_php

Design Patterns in PHP: http://www.codeproject.com/gen/design/a ... tterns.asp

[ add comment ]   |  [ 0 trackbacks ]   |  permalink  |   ( 2.5 / 24 )
DirectX Slick Tutorial Links 
Saturday, September 8, 2007, 06:44 AM - Tutorial
Posted by Administrator
I have been learning to use the DirectX API/Game Programing. Here are some neat articles/tutorials:

http://www.pluralsight.com/wiki/default ... orial.html - excellent explanation about views and projections in the DirectX sense

http://blogs.msdn.com/coding4fun/archiv ... 40729.aspx - this whole series is good, its about game programming in C#

http://www.interact-sw.co.uk/iangblog/2 ... rojections - explanation with images showing difference in projections

[ add comment ]   |  [ 0 trackbacks ]   |  permalink  |   ( 3 / 56 )
Sick UI tutorials/articles 
Wednesday, August 29, 2007, 02:21 AM - Tutorial
Posted by Administrator
Here are some nice links I found, to make forms that are not the standard type:

1) http://www.devx.com/dotnet/Article/21448 - nice and simple
2) http://samples.gotdotnet.com/quickstart ... 20Controls - I have not read this yet, but its about creating custom controls
3) http://www.akadia.com/services/dotnet_u ... 20controls - again about custom controls

I realize moving away from the "standard" may not be good for usability, but that really depends on how you move away from the standard. Moving away from "standard" is what leads to innovation.

I also suspect, users would be too bored of seeing the same dull styles all the time. It is a balance of offering something refreshing to the eyes while maintaining the expected reactions that has to achieved - the user should be able to predict what happens when they perform an action, conversely the user should know what to do when they want something to happen - e.g. I want to close this window, I go to the top and click the 'X' button or press Alt + F4 or go to File->Exit, rather than press the 'X' button to play a video, press Alt + F4 to maximize the window or File->Exit to launch a sub-program!

I know the examples may be unrealistic, but unrealistic exaggerations are what help clarify differences and help understanding, at least to begin with :)

[ add comment ]   |  [ 0 trackbacks ]   |  permalink  |   ( 2.8 / 54 )

| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |