This was one of the more broken update i have ever encountered. While updating apt was complaning that there was installed drivers manually by nvidia-installer.run. Then it tries to remove these using "nvidia-installer.run --uninstall". This would be fair enough if the program actually worked. Ended up with a half completed dist-upgrade. As some might know this is not the best place to be. After recovering the package dependency hell, for some reason the upgrade had removed "auto eth0" from /etc/network/interfaces. Why would they do that? Knew that there was going to be issues because django had been updated. So that is fair enough. Everything now seams to be running as it should. At least the server part of the machine. Should i really surrender and move my server to som generic hosting?
Have made some links in the bottom of the pages that takes you to the "secret" sub pages of ducky.dk. The recipe page has been there a while, but not been public. The recipes are in Danish. The newly created project page so far only has one project, but I will probably add more of the projects I already have in progress. The only project for now is my arcade machine. It is not that far in design face, but is getting along.
If you need to have audio on a web page, whether if it is for you game, or some web application that might require some button or notification sounds when events happen (that is not triggered by mouse events *notch* *notch*), you should get acquainted with Web Audio API. It has been available in Google Chrome for some time now. Has recently been introduced in IOS 6 and Safari, and it should soon get into FireFox aswell http://www.html5audio.org/2012/08/mozilla-announces-web-audio-api-intentions.html. The main advantages of the Web Audio API, as oppose to the <audio /> tag is that you can play multiple sounds at the same time, and you do not require a mouse event to trigger the playback. Which has been some of the limitations that has been put on the <audio /> tag by some systems. To get started on Web Audio API this small article is a great place to start http://creativejs.com/resources/web-audio-api-getting-started/. It covers the basics, and you get a nice introduction on how the "node system" and filters work.
The web page should be up and running shortly.
The reason for the long down time is a series of unfortunate events, starting with previous server CPU overcooking, caused by a faulty CPU fan. Then when ordering new parts the web shops had a bit of fun on my behalf. First board that i ordered was defect, it had a short circuit in the power connection. Second board i received, was the the board i had ordered at all. Although it said so on the outside of the box, the inside was quite different. But now finally i have a working new (extremely overpowered for this purpose) board that should give me lots and lots of joy.
Oh and just like every body else i am chickening out on XHTML and going for the buzzzz HTML5.
After talking a lot about coding convention with a college of mine the thought about complete tokenised programming came to me. Why is it that when our IDE's and text editors are so intelligent and so well knowing about the structure of the code and what it should look like, that the editors can not simply show the code in the preferred coding convention of the reader/writer, and when it is time to save the code, it is converted into the coding convention of the company or project that the code belongs to.
Pushing this idea one step further it would become that you would "configure" tokens in your editor and the code would "automagicly" appear as it normally would when programming. I am not sure this is a good idea, but think it is an area that is worth investigating. Chances are this could prevent some general programming errors since the configuration of each token is only possible when everything is defined.
If the first part, making code convention irrelevant for the individual programmer, could become a reality. Then religious views about where to put white spaces should be a thing of the past. But of course it does require two separate configuration, one for view and one for saving. What parameters should be possible to set could be a rather big task, but looking at how it is done in Eclipse it should be possible to make some "generic" configuration.