Articles in the ‘All’ Category

JavaScript Challenge #3: Review

Written By Christopher Pitt, on Wednesday, August 22nd 2012, 5:54am

The third JavaScript challenge showed us what it would be like to draw with canvas. The challenge was open ended, in so far as there were no restrictions as to what drawing technology could have been used, but everyone just went straight for canvas.


JavaScript Challenge #2: Review

Written By Christopher Pitt, on Wednesday, August 22nd 2012, 5:53am

The second JavaScript challenge was loads of fun! It seems the topic of game development creates interesting challenges and invited participation. Once again, there were many excellent entries but the following entries showcase something specific we want to point out…


JavaScript Challenge #5 (Cows never forget)

Written By Christopher Pitt, on Wednesday, August 22nd 2012, 5:52am

The other day I was playing Fez when I was reminded of an old memory game I used to play where a sequence of colours are shown and the player has to repeat the sequence correctly to proceed. Players are shown increasingly long sequences or colours, stretching their memory to its limits!


JavaScript Challenge #4 (Space, the final grassy gnoll)

Written By Christopher Pitt, on Wednesday, August 15th 2012, 6:01am

Back in the old days, there was an operating system named after transparent, glass-filled wall apertures numbering in mid-90’s. This operating system was designed to run on computers with CRT screens, which actually needed software to upset the patterns of light they generated, called screensavers.

This operating system had just such software, in a number of different variations. One of these created the “illusion” that the observer was travelling through space, passing stars. This is the subject of this week’s challenge.


Optimizing MooTools builds sans Internet Explorer

Written By Arian Stolwijk, on Monday, August 13th 2012, 1:32pm

Since the very beginning of MooTools you can only pick the right components that you need with the MooTools Download Builder, to ensure there are no useless bytes going through the wires. But this means you still download browser-specific code. What if you could optimize the code further by removing unnecessary browser-specific code?

The good news is, you can optimize MooTools builds to remove specific (IE) code! Packager has been used to concatenate builds since MooTools 1.3. Removing certain code blocks, like MooTools 1.2. compatibility or specific IE code is one of the features of Packager. Lets see how it works. We begin with downloading Packager.