EclipseCon 2007 is right around the corner. As aforementioned (or maybe not, I don’t quite remember now), I will be leaving on Saturday and returning on Wednesday morning (hopefully in time for my ACTSCI 221 midterm at 0830, oh ho).

I will be blogging regularly during that time frame, so if you give a damn, I’d recommend that you click ‘refresh’ on your RSS readers often to get my latest updates. I certainly do intend to blog at least once a day, so while I’m sure most of you don’t check this everyday (since I don’t blog everyday and since I rarely say anything that is so interesting that it warrants your immediate attention), it would be in your best interests to do so during that period of time (again, that is, if you give a damn).

I have not got Gallery setup just yet, but will definitely get to it since I’ll obviously be taking some photographs while I’m there.

Yesterday night, I committed the code for my MSN protocol implementation named “Gokigenyou” (WWWJDIC definition: ご機嫌よう; 御機嫌よう 【ごきげんよう】 (int) How do you do?; Nice to meet you; adieu; farewell) and its ECF implementation code into CVS. The two projects in question are org.hantsuki.gokigenyou and org.eclipse.ecf.provider.msn.

The basic functionality of sending and receiving messages is there but that’s really about it. The packet parsing code is horrid and really should be rewritten in all honesty. However, if you’re feeling adventurous and all, feel free to do a CVS checkout and poke around with it. And of course, by all means, please file bugs and enhancement requests.

Since I actually have a paper to write, I have not indulged myself in reading the entire thing but have instead merely read the first couple of paragraphs and glanced at all of the screenshots. No matter, really, because eye candy is what matters, right? With a user interface as sexy as this, it’s really hard to say no to UI Forms, don’t you think?

I don’t remember when I first heard about the “Drop To Frame” feature of Eclipse’s Java debugger, but I certainly don’t recall using it much, if at all, until today. It essentially pops back stuff off of the stack so that you can start debugging right at the entry point of the method. If you click on the preceding method call and click on the “Drop To Frame” button again, you can even go back to that preceding method call! As you can see, this function is useful for those times when you’ve mistakenly set a breakpoint too far down in a method or want to go back and step through a method one more time because you’ve missed something. There are of course scenarios where this isn’t going to work because of the way your object might have been modified over the course of those method calls, but it’s still a handy feature to have at your disposal.

You can find the “Drop To Frame” button to the right of “Step Return” in the “Debug” view.