Digg intergration

I've now added Digg submission capability to this blog. To add a post you like to Digg, just click the Digg This Story button. ;)

Click icon for Feedburner feed

I have created a FeedBurner feed for this blog. However there seems to be an issue somewhere that if I choose to add an external feed provider as Blogger allows users to, it creates some sort of error in the blog mark-up, which in turns means I get errors when I try to publish to this blog via ScribeFire via the Blogger API.

Anyhow to fix the issue, to subscribe to the feed provided by FeedBurner, just click the icon under the About Netting.NET section. Thanks.

Digg API on AIR

Larger screenshot on Flickr.

Hey, everyone. I do have a programming related post today.

I have been coding in JavaScript, XML/HTML and CSS to create the above simple Digg API AIR application, which retrieves the top (e.g. newest) story for each category on Digg.

I have as good as finished it and will be releasing the AIR installation package (*.air) and source code (*.zip) for anyone who is interested in the AIR platform to look at.

Although I could have done an XmlHttp request without any additional framework, I did use the Prototype JavaScript framework for this project.

Here is a quick rundown of the files used in my application and their purpose:


DiggAPI.xml - This is the file which specifies the name, copyright information and file to use for content, etc. An XML file such as this is a standard requirement in any AIR application.


DiggAPI.html - The application content. This contains all of the HTML code for my application and calls to the neccessary JavaScript functions in my external *.js files.


sampleCert.pfx - The certificate used to sign the AIR application. All AIR applications must be signed to be built, even if not by a recognised body such as VeriSign.


script/AIRAliases.js - JavaScript file containing code used by the AIR runtime. Referencing this file provides convenient aliases for use in your code. Included with AIR SDK.


script/prototype.js - JavaScript file containing code for the Prototype framework. I used the cross-browser new Ajax.request provided by Prototype in my application.


script/DiggAPI.js - JavaScript file containing my code used by the application.


style/DiggAPI.css - Style sheet used to format my links and text colours, etc in my application.


style/digg.png - Digg guy logo image used in my application.


Check back soon for included AIR package and source code. Happy coding. :)

Syntax highlighter script

I have been trying to write a simple script in JavaScript to highlight source code in a element such as the code.

Here is the code:

/*
 Syntax highlighter for source code
 Copyright (c) 2007 Samuel Saint-Pettersen
 This script is licensed under the GPL
 http://www.gnu.org/copyleft/gpl.html
*/

function syntaxHighlight()
{      
    var element = "code";    // element for source code
    var attrib = "class";    // attibute for language

    // count all code elements
    var codes = document.getElementsByTagName(element);

    // get contents and class value for each code element
    for(var a = 0; a < codes.length; a++)
    {
        var code = codes[a];
        var contents = code.innerHTML;
        var language = code.className;

        if(language == "boo")
        {
            // define first keywords
            var keyw1 = new Array();
            keyw1[0] = "def";
            keyw1[1] = "print";
            keyw1[2] = "if";

            // colour first keywords
            for(var b = 0; b < keyw1.length; b++)
            {
                var regex = new RegExp(keyw1[i], "ig");
                var matched = contents.match(regex);
                var keyword = matched.toString();
                var repl = keyword.fontcolor("blue");
                codes[i].innerHTML = contents.replace(regex, repl);
            }
        }
    }
}

Problem I have with this code is that after the first keyword is coloured, the loop does not seem to continue. Hmmm... If anyone knows what I'm doing wrong, please leave a comment. Thanks.

Yoda Origami: Destroy the scissors, we must.

This is one of the most interesting things I've found on Digg. Check it out. Yes, I know it isn't programming related. But I am working on a coding project and I will be sure to post about it here shortly.

Fnordography, a 3D Realmer web comic

Okay. Not a programming related post tonight.
But if you are a 3D Realms forum user (as I am - Samji);
you might want to check out this web comic being produced by my pal Justin Self or as he is better known on the Realms, Phait.

The comics are a lighthearted jab at some of the users we
have over there. Phait describes it as such himself...

Rather than having to think up my own characters and backgrounds, I thought the online personas of several members
themselves each exuded a type of character that was ripe for parody or playful exploitation - not excluding myself
(Phait). As this strip is mostly intended for the community, some of it's attempted humor might only be effective
for the members themselves. Though, I have tried to keep it fair to members and non-members alike.

So don't cry at his quips :).
Unless he starts putting you in situations involving 'net shock memes you would rather not be part of. Goatse or Tubgirl, anyone?

Anyway, be sure to check out Fnordography!

Adobe AIR

Today I decided to check out Adobe AIR.
AIR (Adobe Integrated Runtime) is a runtime platform / environment which allows the creation of desktop applications which use existing web technologies such as HTML and AJAX.
Since it is Adobe, unsurprisingly, it also has support for Flash.

To develop an AIR application, all you need is the AIR SDK (which is freely available from Adobe Labs) and your exisiting development tools. E.g. your text editor for your code.

Following the tutorial for developing for AIR with HTML and AJAX, I coded the customary Hello World application.

The tutorial, you follow for its output is complicated. But I think this is due to the demonstration of how a more complex AIR application should be coded. E.g. You use an XmlHttpRequest to display the message to the user.

Development of the AIR application was quite straightforward, so maybe I'll develop something which uses the Digg or YouTube APIs in it.

Digg API and Greasemonkey

I wrote this straightforward Greasemonkey user script in JavaScript using Greasemonkey's implementation of an XmlHttpRequest:

// Digg API script
// version 1.0
// Copyright (c) 2007 Samuel Saint-Pettersen
// Released under the GPL licence
// http://www.gnu.org/copyleft/gpl.html
// ---------------------------------------------------------------------
// This is a Greasemonkey user script.
// To install it, you need Greasemonkey:
// http://greasemonkey.mozdev.org
// ---------------------------------------------------------------------
// ==UserScript==
// @name Digg API script
// @version 1.0
// @author Samuel Saint-Pettersen
// @description Utilise the Digg API
// @include *
// ==/UserScript==
(function() {
    GM_xmlhttpRequest({
    method: 'GET',
    url: "http://services.digg.com/stories/topic/gadgets?count=1&
    appkey=http://apidoc.digg.com&type=xml",

    onload: function(responseDetails) {
    var response = responseDetails.status;
    var returned = responseDetails.responseText;
    if(response != "200")
    {
        // if the request fails, display error message
        alert("Error retrieving Digg Data");
    }
    else
    {
        // display Digg data in message box
        alert(returned);
    }
  }});
})();

The Greasemonkey script request returned fine.
I wonder what it is with my .NET application which meant it didn't work?

Digg API and .NET

I have being trying to develop a simple console application, which utilises Digg API in the Boo programming language.

This is the source code I have for my application:

/*
     Simple application to access the Digg API
     Version: 1.0
     Language: Boo
     Environment: SharpDevelop
     Author: Samuel Saint-Pettersen
     ---------------------------------------------------------------------
     Prerequisites:
      * Boo libraries (included with)
      * Microsoft .NET 2.0 Framework
     ---------------------------------------------------------------------
*/
namespace DiggAPI

import System
import System.Collections
import System.IO
import System.Net
import System.Text
import System.Xml
import System.Web

print "Digg API application\n"

// base request url 
burl = "http://services.digg.com/stories/topic/gadgets?count=3&appkey="

// encode appkey 
appkey = HttpUtility.UrlEncode("http://apidoc.digg.com")

// full request url
address = burl + appkey + "&type=xml"

// create request
request = cast(HttpWebRequest, WebRequest.Create(address))

// method
request.Method = "GET"

// get reponse
response = cast(HttpWebResponse, request.GetResponse())

// get response stream into reader
reader = StreamReader(response.GetResponseStream(), Encoding.UTF8)

// print response 
print reader.ReadToEnd()
print "\n"

// clean up
reader.Close()

// wait for key press
print "Press any key to continue...\n"
Console.ReadKey(true)

For some reason, when I run this application I always get a Forbidden (403) error returned.

Weird? I'm sure I've got the the request URL correct. I get this error whether or not I encoded the appkey.

I'm sure this is some sort of odd behaviour on .NET's part, so I decided to try using the Digg API with something else.

If you know what the the problem is with the .NET application, please leave me a comment or e-mail s dot stpettersen at yahoo dot com


EDIT 10/03/2007:

Timothy Parez helped me out. The solution was to specify the
UserAgent. So I used:


request.UserAgent = appkey;


I used my encoded appkey for the the user agent string. However, in
the Digg API's current state it does not seem to matter whether or not
the appkey is encoded. But I might as well encode it in case they
change this.

Thanks, Timothy.