Over all a productive day, with a few fixes to AbiWord of minor bugs. The latter part of the day I dabbled in E-related topics, trying futilly to hack Esound to not suck and then playing with EFM. I had fun making cool neon-cursive titles on my desktop, but it caused my computer to get extremely lagged and slow. I need a faster computer with more ram.
Also, showed CodeToad EFM. He seems to like it but his hardware is completely underpowered for something like EFM.
<aaronl> i just toured a 36,000 square foot house with a t1, 16 fireplaces, a home theater, centralized audio, two libraries, two swimming pools, a full sized guesthouse, a parking lot, a zen garden, a rose garden, a racketball court, ancient stained-glass windows from europe, ancient entryway from europe, fossils in the limestone that it is made out of, trails and forest, two historic french temples, a tenis court, a view of san fransiso, historic pieces of art, thousands of antique books, and bathrooms made out of onyx and other semiprecious materials <washort> aaronl: normal people wouldn't have noticed the t1 first. <aaronl> washort: he has 4 LCD monitors <aaronl> did i forget the star trek chairs that wrap around your body?
Same old top ruler stuff. More bugs, more fixes.
I got sentenced to life fixing AbiWord top ruler bugs today. Hrrm, I'm not sure that's a good start for a day. Fixed one bug and then waited for QA to point out more.
School starts at 10:30 tomorrow. YES!! That means more hacking. And after tomorrow, school is out.
Well, Paul Egli discovered EVEN MORE problems with the patch I checked in for bug #873. I fixed them.
I've been very busy studying for my finals. I took a good nap in the history final this morning, but during the physics final my physics teacher refused to allow me to borrow a calculator, and as a result, I probably did pretty poorly.
On the IRC side of things, Luke_ wrote some much-needed emacs code to move the point up one screen-line (when the lines are wrapped and you want to move up to the previous line - which emacs thinks is the same line you're on). I haven't got it to work yet.
I can't believe it's been 5 days since my last entry. I've been making an average of one commit per day to the Abi tree and thought I was documenting them here. Once I do something cool or important, I'll be sure to post an entry :). I haven't really been doing much, other than fixing issues that Paul Egli finds or participating in contraversial threads on abiword-dev, such as whether we should use STL, and whether the Insert key should be bound to turning on overwrite-mode. I say yes to the first and no to the second :). I was really supprized that samth suggested this change, since the Abi people are against templates and most other advanced features of C++. I posted that I expected "the Luddites to veto it", and the comments from AbiSource (sourcegear) actually turned out to be mostly very negative. Since Sam claimed he benckmarked the STL vector class to be 27x faster than AbiWord's internal vector implemention, I was all for the change. Since the reposonse was mostly negative, as I expected, I launched a thread about the importance of speed in desktop applications and how AbiWord feels a bit unresponsive sometimes. I was told that I was making a grave mistake by campaigning for changes that were not shown to have any visible impact, and the right thing to do is to profile the application. I will do this once I find a profiler for UNIX, as I am very inexperienced in that area.
I now have read/write access to the Abi CVS tree! Celebrated by writing and commiting a few patches to the tree. As you can see from the log messages, one was quite embarassing.
Studying like crazy for the Physics SAT II and for my finals.
Today the infamous bug got resolved. hj's XIM patch turned out to fix it. I was so excited when I discovered this that I screamed and demanded that it be checked in to AbiWord's CVS tree. It got commited and the bug got closed. That's gotta be the hardest bug I've ever worked on. A breif recap of the people who've worked on it:
Wow. I was so happy to have that over with that I dove in and tackled another bug. This one was a trivial fix, but it was still fun to mess around with the ruler code. The patch got commited to CVS soon after. I'm looking forward to getting CVS access tomorrow since I've been doing so much work on AbiWord and have been wishing I could directly commit small patches that would otherwise need to get someone's attention and get committed sometime in the future.
Had fun at VA discussing the possibility of me getting a job. Met raster, shaleh, and a few others.
I worked a lot on a bug that's been annoying me forever in AbiWord. I think I almost have it fixed. Stay tuned.
The first signifigant thing I did this morning was writing a patch to AbiWord to fix a bug that was annoying the heck out of me. After a few hours of frustration, I finally came up with something that improved the situation. It got commited to the CVS tree 10 minutes latter with a message of gratitude - thanks cuenca.
Didn't really do anything interesting in the afternoon. I went to see Mission: Impossible 2. The movie is the same thing as any James Bond movie. It's entertaining for the two hours while you see it but it's not something you'll ever want to watch again. The sound track is the best part, but disapointingly none of the songs from the sound track really make it into the movie.
The DSL has gone down for a few brief period already. According to Covad, it uses the first day to adapt to phone line conitions. We'll see.
Oh yeah, and I got DSL yesterday. Haven't plugged it into the Linux router yet, but so far it's been great. With the week will come all sorts of DNS madness that I don't really want to think about today.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!
