Blog posts about tools

  • Great tool for documenting .NET projects

    August 15, 2015 | Tags: Tools

    As a developer I'm thankful for any tool that can help me through the process. Tools like ReSharper have really helped me improve as a programmer. But one area where tools also can be a big help is documentation (not my favorite part of the process, but one that is essential).

    Being a fan of Clean Code I don't want to clutter my source code with comments made only for documentation. In the meantime I do want to provide other developers with some nice IntelliSense if they use my projects as well as a collected API documentation. This has previously been mutually exclusive as tools like Sandcastle Help File Builder and others uses source code comments to build the help files and the comments also provides the XML-file that is used for IntelliSense.

    Wouldn't it be great to have a tool where you could import your project files, write the documentation and have it export both API documentation as well as the XML file used for IntelliSense? I was really happy when I found Document! X from Innovasys that not only totally solves this but is also very easy to work with.

    I'm currently using Document! X to document my open source projects and would really recommend it to anyone who want to keep their documentation separate from their code without losing features as IntelliSense.

    Download a trial and test it out!

  • BZR Player - a great music player

    August 14, 2015 | Tags: Tools

    Ever needed a free, non-bloated and very capable music player that both remember where you stop listened last time (great for long podcasts and audio books) and supports most retro system music formats (640+ supported formats!)? Then BZR Player is the player of choice. Download the latest version here and give it a try!

    If you remember the C64 or Amiga music with fondness, don't miss visiting the High Voltage SID Collection and Modland. (Using a moderate amout of the reverb feature in BZR Player really adds to the SID music experience)

  • Great screencast software

    August 11, 2015 | Tags: Open source, Tools

    I have previously been a user of CamStudio when it comes to screencasting. It's worked well in the past, but downloading it nowadays makes your anti-virus suite go haywire over the included malware. So it felt like a good time to shop around for an alternative.

    Read the complete post

  • Batch download from HTTP directory listing

    August 08, 2013 | Tags: Tools, Open source, HTML

    Want to download a number of files that are exposed through directory listings via HTTP? It can be really time consuming to do manually, especially if it also includes sub folders. Thankfully there's the tool Wget to the rescue! And these are the steps to follow:

    Download and extract GNU Wget:

    Launch a command line prompt (ie run "cmd") and enter the following command (replacing "http://domain/folder/" with the url you want to download from:
    wget --wait=1 --recursive --no-parent --reject "index.html*" "http://domain/folder/"
    ..or the same but with parameters in short-hand:
    wget -w1 -r -np -R "index.html*" "http://domain/folder/"

    Explanation of parameters

    -w1, --wait=1 adds a 1 second wait between requests out of courtesy
    -r, --recursive do a recursive request (follow links)
    -np, --no-parent don't follow links backwards
    -R "index.html*", --reject "index.html*" don't save any folder listings, just the files.

  • How to use Spine with Starling/AS3

    May 10, 2013 | Tags: Game development, Tools, Starling, AS3, Flash

    Hats off to the guys over at Esoteric Software. Not only did they live up to the Kickstarter promise to deliver generic AS3 runtime for their excellent 2d animation tool Spine, they also added a Starling version as a bonus! This post shows how to get going using Spine animation in your AS3/Starling project.

    Updated 2015-03-22 Since this post was originally written the Spine runtime has undergone a bit of refactoring. To reflect the changes the post was updated using the latest runtime for Spine as well as the latest Starling library (1.6 at time of writing).
    Spine is currently the most promising solution for 2d skeleton animation, featuring a lot of powerful features such as individual keyframing, skinning and more. The major advantages over traditional sprite sheets are that using skeletal animation uses far less memory and provides smoother animations and the ability to seamlessly shift from one animation to the next - something that makes your animations more vivid. Spine is currently offered for $60 and is definitely worth every cent of it. If you want to give it a try there's a export-disabled trial version for download. There are a couple of alternatives to Spine, but nothing comes close to its functionality. It's currently the most powerful 2d skeletal animation tool.

    Currently Spine does not have a texture packer built-in, so we will be using TexturePacker developed by Andreas Löw. It's a great tool that recently got even better with a content protection feature. If you haven't already you should definitely check it out!

    Setup the project

    Setup a new AS3 project inside FlashDevelop (or the IDE of your choice) and check under project properties so that it compiles for the latest Flash player version. (Or you can download the project here.)

    Download the latest version of Starling and place starling.swc in the lib-folder of your project. Right click on the file and select Add To Library.
    Download the latest Spine runtimes and copy the content of both spine-as3/src and spine-starling/src into your src folder:
    We've now created our project. Lets get some data into it and then return to do some coding.

    Export data from Spine

    Lets start by preparing the data. Once you've created your animations you need to get them out of Spine and into your project. This is done using the Export function.

    Be sure to use JSON as the data format and set the output path to src in your AS3 project:


    Create the sprite sheet using  TexturePacker

    Okay, so now we got the animation data, but we'll also need the body part graphics as a texture atlas. This is where TexturePacker comes in to do the job.

    Start TexturePacker, select all the images from your Spine project (we're using the Spineboy sample project for this demo)..

    .. drag and drop them into the Sprites panel of TexturePacker (you could also use the "Add Sprites" option inside of TexturePacker):

    In the TextureSettings panel, select "Sparrow / Starling" as Data Format and place both the Data file and Texture file in the src-path of your AS3 project:

    Lets write some code!

    Lets start by adding Starling into our Main class:
    package {
    import flash.display.Sprite;
    import starling.core.Starling;

    public class Main extends Sprite {
    private var _starling:Starling;

    public function Main():void {
    if (stage)
    addEventListener(Event.ADDED_TO_STAGE, init);

    private function init(e:Event = null):void {
    removeEventListener(Event.ADDED_TO_STAGE, init);

    _starling = new Starling(MyStarlingApp, stage);
    Next step is to add the MyStarlingApp class that we used as a constructor argument for Starling. Create a new class named MyStarlingApp and make it inherit from starling.display.Sprite.

    Embed the data files using [Embed(source="..",mimeType="application/octet-stream")] inside the class.

    Here's the complete code, I'll return to some of the more specific parts:
    package {
    import flash.utils.setTimeout;
        import spine.animation.AnimationStateData;
        import spine.starling.SkeletonAnimation;
        import spine.starling.StarlingAtlasAttachmentLoader;
        import spine.SkeletonData;
        import spine.SkeletonJson;
        import starling.core.Starling;
        import starling.display.Sprite;
        import starling.textures.Texture;
        import starling.textures.TextureAtlas;

    public class MyStarlingApp extends Sprite {
    static public const SpineBoyAtlasXml:Class;

    static public const SpineBoyAtlasTexture:Class;

    static public const SpineBoyJson:Class;

            private var _skeleton:SkeletonAnimation;

    public function MyStarlingApp() {
    var texture:Texture = Texture.fromBitmap(new SpineBoyAtlasTexture());

    var xml:XML = XML(new SpineBoyAtlasXml());

    var atlas:TextureAtlas = new TextureAtlas(texture, xml);
                var attachmentLoader:StarlingAtlasAttachmentLoader = new StarlingAtlasAttachmentLoader(atlas);
                var json:SkeletonJson  = new SkeletonJson(attachmentLoader);

    var skeletonData:SkeletonData = json.readSkeletonData(new SpineBoyJson());

    var stateData:AnimationStateData = new AnimationStateData(skeletonData);

    // Setup how to morph between different animation sets
    stateData.setMixByName("walk", "jump", 0.3);
    stateData.setMixByName("jump", "walk", 0.4);
    stateData.setMixByName("jump", "jump", 0.2);

    _skeleton = new SkeletonAnimation(skeletonData, false, stateData);
    _skeleton.x = 400;
    _skeleton.y = 460;
    _skeleton.state.setAnimationByName(0, "walk", true);

    setTimeout(makeJump, 3000);


    private function makeJump():void {
    _skeleton.state.setAnimationByName(0, "jump", false);
    _skeleton.state.addAnimationByName(0, "walk", true, 2); // delay next animation by 2 seconds
    All animations are referred to by the name given in Spine. For the Spineboy demo project there's two animations: "walk" and "jump".

    One of the powerful features of Spine is the smooth transitions between animations. This is made by defining "mixes" on the AnimationStateData object using the setMixByName function. The first parameter is the name of the animation that the transition will be made from, the second the animation that will be switched to and the third parameter is the transition time. In the code above the transition between "walk" and "jump" is set to 0.3 seconds. If no mixes have been defined the change in animation will occur instantly. To make the animations smoother you should set up mixes for all animation changes that can occur.

    To start an animation call the setAnimationByName function of the SkeletonAnimation object's state property. The first parameter is track, the second is the name of the animation and the third is if the animation should be looped.

    If you wish to play one animation and immediately after another, use addAnimationByName after setAnimationByName in order to stack animations that will be played after each other.

    Download source codeThe FlashDevelop project except the Spineboy data, which you can get from the Spine runtime download.


    Runtime sourceThe runtimes are undergoing continues updates, so the one used in the archive above may differ from the one available at