Will's blog

purpose: Will Kahn-Greene's blog of Miro, PyBlosxom, Python, GNU/Linux, random content, PyBlosxom, Miro, and other projects mixed in there ad hoc, half-baked, and with a twist of lemon

[ home | blog home | recent activity ]

Thu, 03 Jul 2008

status of trunk

Over the last week I've been coming up to speed on the architectural changes that occurred when Ben landed the new widget code. I've also been hooking up menu items to their respective behavior and fixing bugs on the Linux and Windows platforms. In many cases, I've been re-implementing the behavior using the new messaging system which has required me to read through the "old" code and figure out what the behavior used to be. Progress was slow at the beginning, but is picking up now.

You can see checkins progress in the Trac timeline.

There's still a lot of work to do to get things working again, but things are progressing.

So, why all the trouble? Why not just leave it as is? Off the top of my head:

  1. Miro's UI is no longer rendered using HTML templates. w00t!
  2. It looks like overall memory usage is lower by around 20%.
  3. Memory usage of Miro when displaying feeds with lots of items scales much better.
  4. Miro's faster at displaying feeds with lots of items (where "lots" is defined as > 50).
  5. Miro on Windows is no longer a XULRunner application; instead we're embedding XULRunner for web-browsing. XULRunner is a great platform, but this change makes Miro a Python application on OSX, Linux and Windows and we can unify our toolset. That's a huge win for us and reduces the amount of work it takes to maintain all three platforms.
Regarding the performance gains, I'm seeing those on Windows and Linux, but I definitely haven't spent a lot of time doing rigorous measurements. Treat them as if they were wild unsubstantiated rumor. I haven't used Miro on Mac OSX enough to notice anything there, yet.

Getting there...!

[ tags: miro | category: /miro | Permalink | View/Add Comments: 3 ]

Comments:

Posted by stephen (marxistvegan) on Thu Jul 3 15:08:15 2008
So I guess the better question to ask, is when will the trunk be deemed fixed in relation to the previous post when the trunk was broken? I anxiously await to test, but have been waiting for updates.


Posted by wguaraldi on Thu Jul 3 15:35:51 2008
I'll try to do weekly updates until we get to something stable-ish. Beyond that expect me and other devs to be pretty quiet. We're busy trying to get things done quickly. In terms of estimates, it'll be done when it's done. Any answer more complex/accurate than that requires someone to spend time to do it. In regards to testing nightlies and such, you should talk to Janet as she heads up QA.


Posted by stephen (marxistvegan) on Thu Jul 3 17:48:32 2008
oh thank you very much...I'll try to get back into testing nightlies


Post a new comment:

Three things:

  1. New comments get placed in a "draft" status and will NOT show up on the site until I explicitly approve it. Sometimes that happens within 24 hours.
  2. I reserve the right to reject/remove inappropriate comments.
  3. Sometimes I'll reply to a comment directly in email--so make sure your email address is correct.

If you can't for some reason post a comment, send me an email: willg at bluesock dot org.

Your name:


Your e-mail address (this doesn't get displayed to anyone--sometimes I'll reply directly to you):


URL of your website (optional):


Comment:


Yes, I am a human!

pyblosxom::1.5-dev git-master

Copyright 1996 to 2012, Will Guaraldi Kahn-Greene, under the Creative Commons BY-SA 3.0 license

Creative Commons License
Will's Blog by William Kahn-Greene is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.