Pierre Östlund

So I’ve managed to reach the devilish point of this project: Mork. Used yesterday to brush up on it and created the various types that I will need to create my implementation. I’m currently hacking on some basic parsing methods and everything seems to be going pretty well so far. Since this implementation is stream based (reading byte by byte, the way it should be), adding debugging capabilities will be a breeze. One of the things I just added is line and position count so that debug message can give the exact position where a parsing error occurred. One of the major pros of this is that no one will have to send me their Mork files to me when debugging, just a few bytes around the trouble area so that I can locate the error. Much better from a privacy standpoint IMHO. Time to continue hacking!

I’ve just committed new code from the past week and sent my weekly report to the dashboard mailing list. It’s been a great week (I actually managed to complete my goals) and I’m very pleased. The upcoming week will probably be the most interesting and hardest week for me this summer: I will have to implement the Mork parser. Mork is this projects beast and I really hope to be able to complete it this week as I don’t want it haunting me. It would be nice to finish like a day or two early as well, leaving a few days for reviewing and testing before we enter next month (when I will begin to write the actual backend, woho!). I’ll leave it at that for know.

Update: The API is updated. Forgot to mention that.

Just wanted to give a small status report since last time (which would be last Friday). I’ve been working on the RangeList a lot, has taken some work but is mostly done and working. Might save some memory one day. The PreferenceParser (as mentioned in the API) is also almost finished. The remaining part is to fix a small bug in the FileReader (which is not yet in the API btw). I hope to be able to take Friday as my “update documentation and write tests/regression tests”-day so that I can post them here, in case anybody wants to help out by testing my accomplishments.

I also want to point out that the API is quite out of date at the moment and will be updated sometime this Friday.

Finally - I’ve set up a new Subversion branch and uploaded some code. It’s all stubs and can’t be used for anything yet. So… filling all the blank spots and writing some code will be the next step. All planning and documenting is pretty boring when one do it to much, so I need to get some coding done to increase my motivation a bit.

I’ve added a lot of things to my new branch, so just check it out if you are interested. [1] There’s also an “API” page with some reference material as well. [2]

If you want to do an anonymous check out, you only have to type:

svn co http://svn.gnome.org/svn/beagle/branches/beagle-tbird-soc07

…to get a local copy. Just compile and install it as usual.

[1] Browse the code

[2] API reference