Dougal Matthews

From the makers of the Aptana IDE and Jaxer. We have another interesting product, Aptana Cloud. There is plenty of coverage out there already so I wont attempt to compete. Here are some of the best;

• Aptana Cloud home
• Ajaxian : Aptana cloud develop on your desktop sync out to the cloud
• eWeek - Aptana to Launch Cloud Platform

This looks very interesting to me and I’m a big supporter of all things JavaScript (note you don’t have to use JavaScript for Aptana Cloud).

__autoload is one of the magic methods added to PHP in version 5. It creates a very easy way for you to manage all your different class files. Actually, with __autoload you don’t need to manage them.

Often you will see in PHP projects files that include the other files needed for that page. You can then end up with a while bunch of require_once calls and so on. This can be quite tedious to maintain and you may not always need all the files.

When you create a new instance of a class PHP checks for it and if it can’t be found the __autoload method is called. It’s passed in one parameter, the name of the class.

Above is a simple example of autoload in action. When a new Foo is created the autoload function requires /path/to/class/files/Foo.php. So with a simple naming convention each class in its own file where the file name is the name of the class (similar to Java) you can easily include files.

This example can be taken slightly further to manage hierarchies of classes…

The above code simply replaces all underscores ( _ ) with forward slashes ( / ) before requiring the class. The naming convention changes slightly for this, the class name Foo_Bar would be found in following path: /path/to/class/files/Foo/Bar.php.

The final example shows the same code again with some optional error checking. It allows you to log errors and so on. However, exceptions cannot be thrown by __autoload unless its being called by class_exists. Since this function calls autoload to look for classes. When trying to throw exceptions, PHP runs into a fatal error before its thrown due to the order or __autload. This means a fatal error will be triggered as the class can’t be found and the exception will vanish.

Following up to this post I plan to do one of spl_autoload soon. With this you can have PHP automatically run its own autoload procedure on include paths. For further reading on this follow the link below. The documentation is a little sparse however.

Enjoy, lazy loading!

Useful links;

• Official PHP documentation on __autoload
• Official PHP documentation on spl_autoload

The singleton design pattern is a way of enforcing only one instance of an object. This is achieved by making 3 fairly simple steps to a class. Firstly making the constructor private, creating a static member variable that will contain the instance and then creating a static method for accessing the instance.

So, In PHP it would be;

Why are singletons good? It’s almost like a global object right? What is good about a singleton as opposed to a concrete class? A concrete class has more flexibility as you can create multiple instances and then each instance can of course be different. However, what if you only ever want one instance of an object and ensure you don’t accidentally make another instance (or another developer doesn’t). You could use globals but they need to be managed somehow and people can still make mistakes and forget things.

The most common example is a database class, you might want to make sure that you only open one connection to the database. Creating multiple instances of database class could (depending how you programmed it) open multiple database connections and be inefficient.

The singleton can also be useful if an object that is used infrequently across a website. It can provide you easy access to it without having to worry about passing the object around. In the above code, you can access that object instance with this snippet of code “Foo::getInstance();”.

So, this is my first post. Just a quick introduction to this blog and what you can expect to find here.

Interestingly I’ve always has mixed feelings about blogs. I’ve always been fairly anti personal blogs. They seem to be generally a waste of time, besides, who wants to know what I ate for breakfast? (I skipped breakfast today by the way). So instead of that, I’m going to attempt to make a blog based on my experiences as a developer.

Basically, this blog is going to be strongly focused around programming. I’ll be covering a number of languages and platforms. Most likely this will depend on what I’m using in my studies or in the workplace at that time.

I have a wide range of interests when it comes to programming, including JavaScript, PHP, .NET and everything in between. So you can expect coverage of all these topics in a fairly random order. Depending what takes my interest first!

I’m going to aim to try and do a post weekly, all going well and I’m not on holiday or something.

Some of the following are topic idea’s that I currently have;

• Design Patterns
• Cover some of the less well documented PHP features. Such as the magic methods or Soap (SoapClient, SoapServer etc.).
• Talking about new technologies such as Silverlight or Jaxer.
• Having fun with JavaScript – like animations and pyhsics.

I’m also open open to suggestions of topics. Feel free to send them in.

Edit;

On a side note, the design and layout of this page is going to be a work in progress. It’s not really the main focus of this website