<< What a Game! What a Champion! Who Dat! | The roads I take... | No FOSDEM For Me This Year >>
Weekly Status Report, W03/2010
- Build Infrastructure:
A lot of more work on L10n nightly updates until I finally got then to work. Note that any SeaMonkey nightly updates are complete updates only, as the tooling to do partials for nightlies on our normal build machine pools is not done yet, currently waiting on Mozilla RelEng there. Getting our nightly updates to work correctly needed changes across 3-4 repositories (including mozilla-central and comm-central), but everyone was cooperative and it ended up great.
The next step I had on my mind was switching to packaged tests, both for being nearer to what Firefox run and making it possible to run test suite in parallel, esp. as mochitest-plain runs really long. To my surprise, this worked well, I needed only one small change to the generic test factory and it worked for SeaMonkey (I later coded up an improvement to report Mozilla revisions, but things worked fine without it) and tests did run fine except for a mailnews xpcshell problem, which I hope will be dealt with soon. With that, I could officially do the switch for the most part.
I also did experimentally create some hourly builders to run on a 1.9.2 tree, which we don't really want to target for SeaMonkey, but want to at least build fine. I spotted a packaging problem that was a regression form a recent build system port and Serge swiftly fixed that one - thanks for that!
And, as I now know how to deal with packaged tests and in the new architecture we should run them on normal debug and even optimized builds, I turned on the xpcshell test suite for SeaMonkey trunk Linux builds (the debug ones we do for leak testing), even if a number of failures show up there - it's the first step to fixing them. A one-cycle test run of the other suites pointed to some more issues to fix, but we don't have the machine power right now to run them all the time.
- Download Progress Windows:
After some proposals have come up for fixing progress window shortcomings, we were looking for icons that were usable under our licenses, and when those failed to materialize, I went and created my own SVG icons to match the small ones we have right now, so I could produce larger versions. Having done that, I worked on patching the dialog and posted screen shots of this work in progress in the bug.
Back when I did the version of those windows that is in 2.0 right now, I did the fastest solution I could while still applying a design facelift, now for 2.1 we should have the time to improve on that and correct problems we see with this 2.0 design.
I also updated my patch for moving core build master code to a shared place.
- History Expiration:
I'm risking the next flame war against me with this, but I did a patch to react to the places expiration rework done for the whole Mozilla platform, which also removes the ability to limit history to a fixed number of days or sites, but instead goes with a memory percentage. We will need to implement the cleaning up private data based on time frames to complement this to at least reduce the complaints, I think. While working on this, I saw that Thunderbird also has prefs for this around and filed a bug for them as well.
- SeaMonkey L10n:
As mentioned above, L10n nightly updates for SeaMonkey trunk work now, I posted to the L10n newsgroups about this as well.
- Various Discussions:
Add-on compatibility communication, new machines, comm-central policy for requiring tests, nightly.m.o, possible platform roadmap options, Firebug 1.5 release, Firefox 3.6 release, external linkage for mailnews, KompoZer and SeaMonkey, YouTube and "HTML5 video" vs. Ogg, community-based geolocation service, etc.
This has been a really productive week again and it feels good to get real things moving and also start to do work and planning for SeaMonkey 2.1 now, turning the head back and putting out fires on 2.0 was really getting tedious - even though we have a slightly conservative approach here in SeaMonkey land, we are as much about progress and innovation as the rest of the Mozilla project (even if it is in our way and sometimes means the some changes are not as much into-your-face and revolutionary as in other projects but have more of a continuity label on them).
I hope we all can get into this more again now and get some exciting patches landed for the next version of our great suite.
Entry written by KaiRo and posted on January 25th, 2010 17:36 | Tags: L10n, Mozilla, SeaMonkey, Status | 3 comments | TrackBack
>>>I'm risking the next flame war against me with this, but I did a patch to react to the places expiration rework done for the whole Mozilla platform, which also removes the ability to limit history to a fixed number of days or sites, but instead goes with a memory percentage
Yes, you know how bad it is.))
Some users don't want to see when they visited the site, but for others it is important. For example I remember that 3 days ago I opened 20 pages in one forum and I want to find 1 page. In SM 1.x it's easy - I go in History in 3 days ago folder and the site's folder an see list of 20 pages. In case there is no folder for 3 days ago - I will have what? A list of 200 pages found after search? And do I have to remember all domains of sites I've visited - for entering in search?
9 days limit in history is OK for me, limit in number of pages or memory is bad - I don't need older entries, but I will have them as I see.
It's better when history and bookmarks were in exact place - it's easy to find them, but now they will be like garbage - nowhere.
>>>I worked on patching the dialog and posted screen shots of this work in progress in the bug
And what about saving in browser pages with css and images? ))
I don't think the grouping of pages in the UI is affected in any way, so your fears are probably wrong. What is affected is that we don't delete pages from history when they are older than x days, but when they are the oldest pages and history uses more than x percent of the available memory.
This has nothing to do with how we present things in the UI, only with what we delete from our storage.
For details, read the blog post from the actual developer of the changes.
About the saving topic, I have no idea about that, please look for the relevant bug report.
I'm not much of a developer, I only take on small cosmetic things, my main job is to coordinate the project and not to dig into code I don't understand in the first place (and the whole saving stuff is something I don't understand one bit).
Last edited by KaiRo at 2010-01-26 13:56
I am not tech savvy enough (yet) to understand about the new history feature coming up in the next release but I just wanted to say I am glad you do things at a different pace than fx does... the result is a more stable, less RAM hungry reliable browser, one so nice that I dumped the once reliable and great fx and tb for it. Looking forward to the next release and please keep it as wonderful as it is now.
As for the history change, well you can please some of the people some of the time...
Thanks for reading Mr Kaiser