This Week:
This week I’ve been messing around with the client. First, I found a unicode error with the tpcl functions that mithro handled for me. After this was fixed, I was receiving KeyErrors when adding various components in the tpclient-pywx design window. Not knowing python, I couldn’t do much here. Over the weekend I studied some python code to figure out what was happening. With the help of ezod I was able to add some print statements (printing capabilities are amazing in python) and find out exactly where my problem was. Basically, I was missing a property that the client was trying to call. When you don’t match on a property it returns an index of 0, which is a huge problem when the client tries to use it.
I spent most of my week starting the work on my next milestone, which will commence on the 24th of this month. I created some of the missing components and properties for MTSec. In particular, I believe that I have an issue with how I implemented missile/torpedoe racks. While I am starting to get a grasp on how scheme works, I still have a long way to go here. I don’t think the racks are implemented properly.
Also, I have to look into why I am getting errors when adding tubes and the proper way to add them.
I will have another blog post tomorrow with more information on the work I’ve done and a use-case to show that it’s implemented properly.
Next Week:
The work will continue. I think for my next milestone to be successful, I need the design window to work properly. This will add a lot of fun to my ruleset, who wants to pick from pre-existing ships? Not me. I will need to get into missile/torpedoe design and have that working by July 10th. This is going to be a tough one, but it shouldn’t be too much of a problem. This iteration will also require me to work on the AVACombat class.
This is probably the most important part of the MTSec GSoC period for me, so I will be most likely be putting in the most time here.
Tags: GSoC, thousand parsec