<< Weekly Status Report, W16/2010 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>

Weekly Status Report, W17/2010

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 17/2010 (April 26 - May 2, 2010):

I've been trying Account Manager this week, and interestingly it installed right away for SeaMonkey and even works somewhat! Of course, it's in a completely experimental state and doesn't do much yet as well as doesn't work with many sites right now, but that should change over time. Even when it still was "Weave Identity", I already found its ideas quite compelling, and I hope we'll be able to continue to have it working as well as possible with SeaMonkey even when it grows up as a Firefox project.

In other news related to Weave and SeaMonkey, I'm mentoring a Google Summer of Code project on Weave Sync engines for tabs and mailnews status for SeaMonkey this year, and had the first planning talks with Harini Sirisena on how we'll proceed with this. You can also follow Harini's blog to see what's going on in her project. Having your tabs from Firefox (desktop or mobile) or another SeaMonkey installations available on your SeaMonkey is surely nice (and almost there already anyhow), having the read status of feed entries and newsgroup messages as well as possibly message tags being synched up between installations would be really cool though and is the actual goal here. :)

Entry written by KaiRo and posted on May 4th, 2010 19:09 | Tags: L10n, Mozilla, SeaMonkey, Status | 4 comments

TrackBack/Pingback

  • Twitter Trackbacks for Home of KaiRo: Weekly Status Report, W17/2010 [kairo.at] on Topsy.com (Pingback)
  • Comments

    AuthorEntry

    Tony Mechelynck

    from Brussels, Belgium

    quote
    Sm 2.1 alpha 1
    Alpha 1 code freeze: wow! Sounds like Sm 2.1 is starting to become serious stuff. :-)

    A couple of days ago I tried my first Mozilla compile ever, with SeaMonkey (off comm-central since 1.9.1 repositories are not publicly accessible), and it went remarkably well for a first try (thanks to Ben Smedberg, Gary Kwong, and the authors of the MDC Build Documentation, plus of course the whole SeaMonkey team). I've been playing a little with the browser component on a fresh profile, with no problems so far. However I don't know if I'll do another own-compile because the make took about 12 hours on my machine (a full configure and build from scratch, and not on a dedicated machine, so I preferred not to parallelize the make). Of course I'll want to know how well the mailer works before I make the big jump to using Sm2.1 (probably the Mozilla-buit executable) with my day-to-day profile (maybe define my POP servers with "leave mail on server", possibly also all or part of the feeds, maybe the NNTP news or maybe not, and temporarily neglect the 8-emails-a-week Movemail account). Any statistics on how many people are already using Sm2.1 for mail & news (and POP mail in particular, if it can be told apart from IMAP)?
    2010-05-04 20:54

    KaiRo

    Webmaster

    quote
    Tony, we don't know how many people are using mailnews anywhere, but we know we have about 300 active installations of 2.1 builds every day - and I can tell you I've recently been using 2.1 builds for all my mail, newsgroup and feed communications and so far haven't encountered problems with that.

    By the way, 1.9.1 source is available from hg.mozilla.org/releases/comm-1.9.1 :)
    2010-05-04 23:12

    Tony Mechelynck

    from Brussels, Belgium

    quote
    All right, so I did the jump, and the first news I have is for you as an addons author: your EarlyBlue theme works fine with 2.1a1pre, but only with a compatibility override since it only advertises support for 2.0pre to 2.0.* ;-).
    2010-05-06 01:05

    KaiRo

    Webmaster

    quote
    There are actually some details that don't work so fine - but anyhow, I have local versions of both EarlyBlue and LCARStrek that actually really should completely fine - but I'll only get them packaged and released for this one once we know what state we ship and once I can update even for the last changes. ;-)
    2010-05-08 01:30

    Add comment