DodgerEditor 0.1a

So just to prove that I’m a masochist and that the Dodger Editor is not dead (even though I don’t think that anyone has been using it) I thought I’d post a quick update. No the editor is not dead and no neither am I.

I’m still writing for Python Magazine and working on the editor in some of the free time that I get. I just added a selection cursor mode to the editor which makes it easier for me to use. You can see it in the second row of the pallet in the following screen shot.

Now with a Select Mode!
Now with a Select Mode!

If you want access to the newest code you can grab it from the mercurial repository:

If anyone is at all interested in this project, whether it’s using or helping to develop, or just some suggestions please let me know. I’m always open to opinions. If I get the time I’d like to work on a short post showing you how you can use the Dodger Editor to create the level files for a game, when that will be I don’t know but hopefully soon.

5 thoughts on “DodgerEditor 0.1a”

  1. Hi.

    I was actually looking for an editor that will let me tag sprites and/or locations in the level with additional attributes (e.g. scripts) when I stumbled on to your project on Google Code – you can read all about my search at my blog website (see URL above).

    I just thought I’d drop a comment and let you know that I’m currently looking at your level editor – even at such an early stage.

    Good stuff!



  2. Hi Chris,

    Thanks for the comment. The editor as it stands is entirely usable. That means that you should have no problems using the levels that it produces. However the program is at such an early stage that it is in no way feature complete. But since it’s open source if you want to change or add anything you can go ahead and do it yourself.

    If you do decide to evaluate it, let me know how it goes or if there is anything that you are looking for. If you have a new feature request you can ask for it here or on the google code page:

Leave a Reply

Your email address will not be published. Required fields are marked *