mykzilla

Snowl: an experiment with messaging in the browser

2008-07-14T17:29:00.000-07:00

Last August, after Mitchell blogged about the future of email and penned an email call to action, I posted some thoughts about what a next-generation conversations app might look like. I've kept thinking about it since then, and several months ago I proposed a labs experiment to build a Firefox extension that tries out some of those ideas.

Lots of users use desktop applications like Thunderbird and Apple Mail to converse with each other online, while many others use web apps, including not only webmail but also social networks, web discussion forums, and other site/service-specific tools. Is there a role for Firefox in this mix?

That's the key question I'm trying to answer.

I've been hacking on a prototype on and off since then. It's not quite usable yet, but it's getting there. It currently has basic support for subscribing to, searching, and browsing messages from feeds via two views: a list view similar to a three-pane email application's interface and a variant of the "river of news" view described by Dave Winer.

I plan to have a 0.1 version of the prototype ready by the Mozilla Summit in two weeks, where I've proposed a session to present and discuss the experiment. In the meantime, adventurous readers are welcome to check out the source and send me feedback via comments on this blog post, email, IRC, Facebook, your own blog post that references this one, etcetera, etcetera, and so forth.

Why I Host Projects on Mozdev

2008-07-07T23:59:00.001-07:00

I've been using Mozdev for almost eight years, ever since it started hosting Forumzilla, my project to build a Mozilla-based web forum reader (which eventually became a Thunderbird extension and then Thunderbird's built-in feed reading feature).

Mozdev plays the critical role in the Mozilla community of hosting Mozilla-related projects that aren't considered core enough to the Mozilla mission to host on official community infrastructure. It's a great adjunct to AMO, which distributes many of the projects that Mozdev hosts.

Over the years, I've been happy to host a number of such projects there, including the aforementioned Forumzilla plus Bugxula (defunct), Tinderstatus, and revision control/bug tracking for the Labs project Personas.

Although there have always been alternatives, they have been unpalatable: SourceForge has a cumbersome and unfamiliar interface, and hosting on my own server would have meant doing all my own systems administration. I use Mozdev because I want to focus on my projects, not on the infrastructure for developing them.

Over the last couple of years, Google Code has become an option. Although it provides much less functionality than Mozdev (and limits how many projects you can create), it does have a simpler interface and a more modern revision control system.

The folks who run Mozdev (which includes me) want simplicity and modern services (without sacrificing power) for Mozdev too, and we've identified three priorities in that regard: adding Mercurial for revision control, implementing WYSIWYG content editing, and automating project creation and management.

So I'm thrilled to read Mozdev developer Doug Warner's announcement today, via a post to the project owners mailing list, that he has landed Mercurial support. Now you can get all the goodness of Hg hosted on your behalf for any of your Mozilla-related projects.

Eight years later, I think Mozdev remains the best place to host my projects, and it's just getting better. I can't wait to see what's next (and I have some ideas about what simple WYSIWYG editing could look like, about which more soon).

Merging with Mercurial and Meld

2008-06-03T18:19:00.000-07:00

When confronted with a merge conflict, Mercurial 0.9.5 (the version that comes with Ubuntu 8.04) uses its hgmerge script to call meld in a way that displays your version of the file on the left, the other version on the right, and hg's attempt to merge them in the middle, with conflict markers where it was unable to do so.

Here's meld handling the Merging conflicting changes example from the hg book:

You're supposed to fix the one in the middle, resolving the conflicts between the ones on either side, and then save the middle one (which will get saved to your working directory, from where you can commit your merge).

The following patch hacks hgmerge to display the base version (the one from which your version and the other version originated) on the left, the other version on the right, and your version in the middle.

--- hgmerge.orig        2008-06-01 13:51:10.000000000 -0700
+++ hgmerge     2008-06-01 14:35:46.000000000 -0700
@@ -158,13 +158,12 @@
         conflicts_or_success
     fi
 
     if [ -n "$MELD" ]; then
+        cp "$BACKUP" "$LOCAL"
         cp "$BACKUP" "$CHGTEST"
         # protect our feet - meld allows us to save to the left file
-        cp "$BACKUP" "$LOCAL.tmp.$RAND"
-        # Meld doesn't have automatic merging, so to reduce intervention
-        # use the file with conflicts
+        cp "$BASE" "$LOCAL.tmp.$RAND"
         $MELD "$LOCAL.tmp.$RAND" "$LOCAL" "$OTHER" || failure
         # Also it doesn't return good error code
         $TEST "$LOCAL" -nt "$CHGTEST" && conflicts_or_success || ask_if_merged
     fi

Here again you're supposed to fix and save the file in the middle, which gets saved to your working directory.

Here's what the example looks like using the hacked version of hgmerge:

After trying both versions of the script on several test and real merges (a few of which I screwed up), it's still not clear to me which approach is better (or if there's something better still). David Baron pointed out in a conversation that it can be useful to see the base version, but it's also useful to distinguish between your version and the version that ultimately results from the merge (which is presumably why kdiff3, which is shown in the book, displays all four: base, yours, other, and final).

Thoughts?

(Note: Devmo's Mercurial basics says to use Mercurial version 1.0 or later, although I hear that doesn't even include hgmerge, leaving configuration of a merge tool entirely up to each user, so the question is even more significant there.)

JS 1.8 syntax checking in Komodo

2008-06-03T16:42:00.000-07:00

I've been using JavaScript 1.8 expression closures lately, but ActiveState Komodo's JS syntax checker, which is just SpiderMonkey 1.7, doesn't recognize them, so it treats them as a syntax error and stops checking the file:

Fortunately, the fix turns out to be pretty simple. Komodo ships with SpiderMonkey 1.7 as an executable, so I first built SpiderMonkey 1.8 (on Linux) using the SpiderMonkey build instructions:

cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -l mozilla/js/src mozilla/js/src/config mozilla/js/src/editline mozilla/js/src/fdlibm
cd mozilla/js/src
BUILD_OPT=1 make -f Makefile.ref

Then I backed up Komodo's version and replaced it with the one I built:

cp Linux_All_OPT.OBJ/js ~/Applications/Komodo-IDE-4/lib/mozilla/js18
cd ~/Applications/Komodo-IDE-4/lib/mozilla
mv js js17
ln -s js18 js

Voila! Syntax checking works for expression closures:

In theory I might have just horked some part of Komodo that depends on JS 1.7, although the New in JavaScript 1.8 doc doesn't mention breaking changes between the two versions, and so far Komodo seems to be working fine.

If it does create problems, however, then a more contained fix, as ActiveState's Todd Whiteman points out on the Komodo Discuss mailing list, would be to update koXPCShellLinter.py's jsInterp variable to point to the 1.8 executable.

XPCOMless Preferences API

2008-05-11T23:41:00.000-07:00

I've been working on yet another JavaScript API for accessing preferences. My goals for it are simplicity, intuitiveness, power, and perhaps performance. I'm also interested in learning whether freeing it from the restrictions of XPCOM can make it better than existing APIs.

The Basics

It's a JavaScript module, so you start by importing it from somewhere:

Components.utils.import("resource://somewhere/Preferences.js");

Getting and setting prefs is easy:

let foo = Preferences.get("extensions.test.foo");
Preferences.set("extensions.test.foo", foo);

As with FUEL's preferences API, datatypes are auto-detected, and you can pass a default value that the API will return if the pref doesn't have a value:

let foo = Preferences.get("extensions.test.nonexistent", "default value");
// foo == "default value"

Unlike FUEL, which returns null in the same situation, the module doesn't return a value when you get a nonexistent pref without specifying a default value:

let foo = Preferences.get("extensions.test.nonexistent");
// typeof foo == "undefined"

(Although the preferences service doesn't currently store null values, other interfaces like nsIVariant and nsIContentPrefService and embedded storage engines like SQLite distinguish between the null value and "doesn't have a value," as does JavaScript, so it seems more consistent and robust to do so here as well.)

Look Ma, No XPCOM

Because we aren't using XPCOM, we can include some interesting API features. First, as you may have noticed already, the interface doesn't require you to create a branch just to get a pref, but you can create one if you want to via an intuitive syntax:

let testBranch = new Preferences("extensions.test.");
// Preferences.get("extensions.test.foo") == testBranch.get("foo")

The get method uses polymorphism to enable you to retrieve multiple values in a single call, and, with JS 1.7's destructuring assignment, you can assign those values to individual variables:

let [foo, bar, baz] = testBranch.get(["foo", "bar", "baz"]);

And set lets you update multiple prefs in one call (although they still get updated individually on the backend, so each change results in a separate notification):

testBranch.set({ foo: 1, bar: "awesome", baz: true });

Performance?

Getting prefs via the module is several times slower than getting them directly from the preferences service, but it's much faster than using FUEL, and we can make the module just as fast as the direct approach by making it cache values (at some unknown set and memory cost):

Nevertheless I wonder if it's worth the added complexity and other iatrogenic costs of caching, given that preferences generally don't get accessed very frequently, and all of these methods are fast enough for small numbers of accesses.

Everything Else

I haven't yet built the rest of the API (has, reset/clear, locking, adding and removing observers, etc.). Is it worth doing so? Is this API better enough than FUEL's or simply direct access to the XPCOM preferences service? And are there other improvements we can make given that we aren't limited to the language features XPCOM supports?

(To try it out, download the Preferences and/or CachingPreferences modules.)

a trademark to distinguish network neutral providers

2008-04-28T17:30:00.000-07:00

While on vacation last week, I saw a sign in front of a Burger King in New York advertising free wifi. The sign listed six things you can do with it (downloading songs, chatting, etc.), which left me wondering whether they provide the whole whopping internet or just the selected portions they highlight.

And that got me wondering whether it would make sense to trademark a logo and phrase for distinguishing internet providers that provide unobstructed access to make it easier for users to pick network neutral wifi hotspots at restaurants and hotels, DSL/cable providers, and mobile plans.

Providers licensing the logo could still rate limit, as long as they didn't do so on the basis of site or protocol. And the trademarked content would be designed to be simple and understandable by non-technical users, like Creative Commons' license logos, TRUSTe's privacy seals, and the feed icon.

I'm not sure what organization would be most suitable for running such a program, but it should be not-for-profit, as Creative Commons, TRUSTe, and Mozilla all are.

Properly implemented, it seems like a program like this would make it a whole lot easier for users to pick providers that don't have frustrating problems caused by access obstructions while putting pressure on providers to provide the whole internet so they can qualify for the program.

Thoughts?

me three

2008-04-14T15:03:00.000-07:00

myk@myk:~$ uname -a
Linux myk 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux
myk@myk:~$ history|awk '{a[$2]++ } END{for(i in a){print a[i] " " i}}'|sort -rn|head
115 cvs
61 cd
50 ls
33 safari
31 komodo
28 firefox
23 cp
16 ll
12 zip
12 scp
11 mv

proposed changes to Mozdev roadmap

2008-04-02T09:44:00.000-07:00

I'm on the board of the Mozdev organization, and we're in the process of reviewing our roadmap for development.

We're a small organization with limited resources, so we can't do everything that would be useful, and it makes sense to leverage the tooling taking place elsewhere in the Mozilla community.

At the same time, I want Mozdev to blaze a trail on the usability and functionality of key services like website development/deployment tools and discussion forums. And it should be super-easy to set up and manage a project on Mozdev.

So I am proposing that we revise the roadmap to make the following three items the top priorities for the organization:

Add one additional revision control system, and deprecate CVS.

The two systems in the running are Subversion and Mercurial, and they each have their advantages. Subversion's chief advantages are its similarity to CVS and familiarity to some existing project owners, while Mercurial's are its modern design (including support for distributed development) and its momentum in the Mozilla community.

Overall, I think we're better off adding Mercurial, which has the full weight of Mozilla tooling efforts behind it and which is on track to become the most popular system in the Mozilla community (until the next one comes along, anyway).

So I think we should add Mercurial to the site. But this would not preclude adding Subversion as well at some point if resources became available to deploy and maintain it.
Implement a new website hosting service with simple WYSIWYG wiki publishing and scp/sftp/ftps file upload.

Here we're tackling two constituencies at once: those who just want a simple hosting option where it is easy to create and edit pages, and those who want complete control over the files that make up their site.

The file upload option also addresses the needs of users who generally want the simple approach but occasionally need to upload a file or two (f.e. an image to display on a page in the wiki or a presentation in PDF format).
Automate project creation and management so that project creation requests can be addressed in minutes or hours and users can self-manage their projects.

This item combines the automate project creation process and centralized account management system items from the second and third priority groups, respectively, on the existing roadmap.

I think we should continue to require approval of new project requests from unknown people but no longer require approval of those from known, trusted people like existing project owners, so that trusted people can have a new project up and running in seconds.

There are certainly many other changes that would be beneficial, like integrating forums, feeds, mailing lists, and newsgroups, so users can pick their preferred delivery format and get the same communications as on every other channel.

But these three changes would make a big difference in the usability and functionality of the site, and I think we should make them our top priorities.

Thoughts?

Dynamic Personas - How They Work

2008-04-01T14:15:00.000-07:00

The recently released update to the Personas extension includes support for dynamic personas, which are personas that change over time. Here's a technical overview of the history and present condition of the feature (for a non-technical overview, see the labs blog).

Take One

Original discussions for making personas more dynamic started with the idea of building an API for them to specify a series of background images and when to switch between them. But the more ideas we had about what personas might want to do, the more complicated this API became.

I wanted something both simpler to scale to more complex functionality and more powerful right off the bat, so I suggested we simply stick iframes behind the browser chrome at the top and bottom of the browser window, let personas load any web content (HTML, SVG, etc.) into them, and let them update themselves as needed ajaxically.

That seemed promising, so I prototyped it by XBL binding the top and bottom chrome into XUL stacks, making their backgrounds transparent, and sticking iframes underneath them.

That worked great until I locked down the iframes with type="content" for security, at which point they were hoisted to the tops of the stacks and covered up the browser chrome.

I asked about this on IRC, and roc pointed me to bug 130078, which won't be fixed in Gecko 1.9. So I had to find a different solution.

Take Two

The one I hit upon, which is in the latest release, preserves as much of the web content magic of the original solution while still working (safely). And it still enables personas to change over time, albeit not as rapidly.

The extension creates two iframes in the hidden window, loads the persona content into them (which can still be any web content), takes a snapshot of them using the canvas 2D context's drawWindow method, converts the snapshots to data: URL-encapsulated PNG images using canvas's toDataURL method, and then makes those images the background images for the top and bottom chrome.

Rinse and Repeat

The extension then leaves the persona loaded in the iframes and periodically (once per minute by default) updates the browser chrome with new snapshots. And occasionally (once per hour by default) it reloads the persona from scratch, although personas are of course free to update themselves more frequently.

Once per minute is obviously not fast enough for animation (like an aquarium with fish swimming around in your toolbar), but it's fast enough for gradual changes, like a panoramic landscape that darkens as the sun sets or a pictorial depiction of the weather report. And there are plenty of interesting personas for which this update frequency is fast enough.

(Incidentally, one can jack up the frequency with a hidden preference, but doing so is not recommended, since it could impact performance).

Bits and Pieces

When dynamic personas change the background, the optimal foreground color might change too, so the extension sets the foreground (text) color to the one specified on the root element of an HTML dynamic persona.

For example, Heldenhaft's Paderborn, Germany panorama persona is dark at night and light in the daytime, so I adapted some code from an NOAA Sunrise/Sunset Calculator to enable it to determine the status of the sun at its location and set its foreground color appropriately.

And if you want to test out this "any web content" claim, just select Preferences... from the personas menu, press the Custom Persona Editor... button to open the custom persona editor, and enter any URL (f.e. http://www.mozilla.com/) into the Header or Footer fields. It might not be pretty, but it'll show you a chunk of the page behind the chrome.

Locking it Down

The code is a actually bit more complicated than described above, because the hidden window is an HTML document on Windows and Linux, and HTML iframes can't be locked down with type="content".

So instead of creating those iframes in the hidden window, it creates another iframe in the hidden window that loads a XUL document that contains the two iframes that load the persona content.

Tests like this one (and a version that tests the personas code directly) demonstrate that the content iframes are indeed locked down, so while personas can do anything web content can do in a browser tab, they can't break out of the content jail and access chrome UI or capabilities.

The only thing injected into chrome is static PNG snapshots of web content.

Of course, if you can think of a way around that or another security issue, I and other Personas hackers would be very interested in your thoughts. To confirm your suspicions, install and test the extension or peruse the code online.

a trio of extensions

2008-03-24T17:30:00.000-07:00

Last week while on vacation I spent a bit of time hacking, and I cooked up three extensions to improve the Firefox experience.

The first two are pretty trivial:

Bookmark Toolbar Icons unhides those icons on the Mac using Vlad's user chrome code (with the enhancement Abdulkadir Topal suggested in his comment on Vlad's post):

Extensions are easier to install and remove than chunks of user chrome code, so this makes that enhancement accessible to greater numbers of users.

And Command-PageUp/PageDown lets you use those shortcuts for switching between tabs on the Mac, which is handy for selectively closing tabs via the keyboard, since otherwise you have to switch accelerators between moving to a tab (Ctrl-PageUp/PageDown) and closing it (Cmd-W).

Besides making that use case easier, the Command accelerator feels a bit more Mactuitive in general, although there's no standard shortcut for tab-switching in particular. Apple apps like Safari and Terminal use the clunky Cmd-Shift-[/], while Colloquy uses Cmd-LeftArrow/RightArrow, and ActiveState Komodo uses Cmd-PageUp/PageDown (i.e. the same shortcut this extension enables in Firefox).

The third extension, Bookmarks UI Consolidator, is more involved. It consolidates the Bookmarks menu in the menubar and the Smart Bookmarks folder in the Bookmarks Toolbar into a single Bookmarks folder in the toolbar:

Besides simplifying the UI, the extension makes the toolbar keyboard-accessible. Just press Alt-B (Ctrl-B on Mac) to focus and open the folder, Esc to close it again (but leave it focused), and then the LeftArrow/RightArrow keys (or Tab/Shift-Tab) to move between items on the toolbar. Space/Return/Enter on an item in the toolbar loads a focused bookmark and opens a focused folder.

(That second step in the process, hitting Esc, shouldn't be necessary, but I haven't yet figured out how to make the toolbar behave like the menubar, where hitting RightArrow while a menu is open focuses the next menu to the right if the current menuitem doesn't have a submenu.)

Note: focusing outside the toolbar turns off the focusability of its items, so you don't have to tab through all items on the toolbar every time you want to go from the Search bar to the tab strip.

And while you can't drop off the toolbar with the arrow keys, you can drop off it with Tab/Shift-Tab (as with the tab strip, although there it drops you off immediately; maybe the Bookmarks Toolbar should behave the same).

Adding this keyboard access method allowed me to simplify further by removing the Bookmarks Toolbar menuitem, which was added primarily for accessibility over in bug 408938.

And replacing Smart Bookmarks with Bookmarks saves a "smart" amount of precious horizontal toolbar real estate for user bookmarks.

I wonder how far we could take this kind of change. Could we consolidate the History menu into the Back/Forward buttons dropdown menu? Could we get rid of the menubar entirely, integrating all menu-accessible functions into other UI (perhaps a command toolbar)?

Maybe the four menu commands (Bookmark This Page, Subscribe to This Page, Bookmark All Tabs, and Organize Bookmarks) could be buttons on the Bookmarks Toolbar for better discoverability and immediate accessibility (although it would take up more of that precious toolbar space).

thoughts on sheriffing

2008-02-27T11:51:00.000-08:00

I sheriffed yesterday, on the last day before the code freeze for Firefox 3, beta 4. Sheriffing is an unusual role within the Mozilla community in that it isn't distributed meritocratically. It's a shared responsibility of the development team, and you can be assigned to sheriff without a clue how to do it.

(That said, it's not clear how one gets on or off the roster. We'd benefit from a clear and simple policy here, like making it be the set of people who have checked in to Gecko and Firefox modules recently, or some other set that represents the most likely current stakeholders in the health of the tree.)

And it's a pressure cooker, with lots of hard decisions to make, plenty of chances to screw things up, and a bevy of developers clamoring for a more or less open tree depending on their individual circumstances and biases.

Nevertheless, it's great training in making hard decisions under pressure (with the safety net of revision control, unlike in the real world, where you can't uncut the red wire), and there are plenty of people helping out with advice and assistance with the chores of sheriffing.

Reed Loden and David Baron, in particular, were a huge help to me yesterday in tracking down regressions, backing out patches, filing bugs, and the like. And David ultimately took on the last leg of sheriffing when we extended the freeze a few hours to make up for a late tree closure (the third that day). Thanks guys!

(Thanks too to Matthew Zeier for jumping in at midnight to kick a box that was preventing the tree from reopening!)

Ultimately, despite the difficulties associated with an all "volunteer" force, I don't think I would professionalize the sheriff role. The tree is our shared treasure, and sheriffing is a great eye opener to the project-wide costs of individual mistakes and the value of good tree etiquette, helping us develop into better stewards of the source. I think it's worth the pain, but for a different perspective, see dougt's thoughts.

Update: dougt's blog post has since been removed, but he's expressed his current thoughts on the subject in a comment on this post.

better MDC searches from the search box

2008-02-06T15:07:00.000-08:00

I had an "MDC (English)" search plugin (not sure where I got it from), but it wasn't returning the Observer Notifications page when I searched for "xpcom-shutdown". Turns out it was using the old search engine instead of the new Nutch-based one, so I created a plugin that uses Nutch instead and uploaded it to Mycroft. Grab it from there if you want better MDC searches from the search box.

Update: the search plugin built into MDC now uses Nutch, so you can now simply install that one by going to MDC and then clicking the glowing icon in the search box.

keeping up with the Joneses

2007-12-17T12:11:00.001-08:00

I thought I'd mention a couple blogs I follow to keep abreast of what is happening with other browsers.

First, Bernie Zimmerman (author of the GrayModern theme) tracks news about multiple browsers at his Browsersphere blog. Second, WebKit and Safari news has long been available at Surfin' Safari, although I suspect the WebKit part of that will slowly move over to the new Planet WebKit.

What blogs do you read to track the coopetition?

Video of Joseph Smarr on High Performance JavaScript

2007-11-29T11:43:00.001-08:00

Last month Joseph Smarr, Chief Platform Architect at Plaxo, came to the MoCo office to talk about High Performance JavaScript: Why Everything You've Been Taught is Wrong.

Joseph has tons of experience optimizing JavaScript for a large-scale AJAX application and gave a great presentation chock full of useful info for web app and Firefox chrome developers on improving the performance of JavaScript-based applications.

A video of Joseph's presentation is now available, and the presentation slides are also online, so check it out. Unless you've already seen it or are Joseph, you're going to learn something.

Alt-Tab-like history navigation

2007-11-15T03:15:00.001-08:00

Here's an idea for an extension that I'll probably never get around to writing (but one of you might, perhaps for the extension contest!):

Overload Alt-(Left|Right)Arrow, the history back and forward keyboard shortcuts (Cmd-Arrows on Mac), to create an Alt-Tab-like experience with a row of thumbnail previews to which you can navigate by holding down the Alt key, pressing the arrow keys multiple times until you reach the target page, and then releasing the Alt key.

In other words, do the same thing for history navigation that Dão Gottwald is doing for tab navigation with his Ctrl-Tab extension.

(Bonus points for version 2: track non-linear meanderings and expose them as parallel tracks to which you can navigate with the up and down arrows.)

tabs for Thunderbird 2.0.0.9

2007-11-15T00:26:00.001-08:00

Anticipating requests, I've spun some tab-enabled builds of the latest version of Mozilla's mail/news desktop app for Linux, Mac, and Windows.

Note that the Mac version is no longer compatible with Mac OS X 10.2, as my Mac build machine (a.k.a. my laptop) has been upgraded to Leopard and XCode 3.0 and no longer has the 10.2.8 SDK on it. It should work on 10.3.9+, 10.4, and 10.5, however.

p.s. Congrats to the Thunderbird team on the release of 2.0.0.9! Getting a security and stability release out the door is no mean feat, requiring careful coordination between several groups of talented folk with a high standard for software quality that they consistently achieve. Bravo!

Mac OS 10.5 First Glance

2007-10-31T02:12:00.001-07:00

I spend most of my time in an Ubuntu VM, so I don't use many of the features of my MacBook Pro's host OS. But I upgraded to 10.5 yesterday for dtrace and checked out a few other features in the process.

Spaces

Spaces works about as well as VirtueDesktops. It's easier to configure, and it's less crashy, but it doesn't let me give my spaces names, which has been a palpable visual cue in VirtueDesktops that I've landed on the right one.

And although moving to the right of the rightmost space usefully wraps around to the leftmost one, the transition animation shows me moving left (but not across the intermediate spaces), which confuses me every time.

But most significantly, like VirtueDesktops it makes navigating to a window even more complex than it already was, with three somewhat-overlapping keyboard shortcuts: Control-ArrowKeys to change spaces, Command-Tab to change applications (across all spaces), and Command-BackQuote to change windows within an application.

I'm constantly hitting the wrong key. Maybe I'll get used to it, but I think I'll continue to prefer how I've configured multiple desktops in Ubuntu, where one shortcut (Control-Alt-ArrowKeys) switches between desktops and another (Control-Tab) switches between windows on that desktop. I wish there was a way to do that on Mac.

Time Machine

Time Machine looks like it could replace the manual backups I currently do with SuperDuper!. It seems to lack a "back up everything now" button, which I want to press before leaving for a trip, but perhaps its automatic hourly backups are good enough.

Nevertheless, it's unclear when and how it'll back up my 40GB Ubuntu virtual disk file, which is almost always open. Maybe I could exclude that file from Time Machine backups and then back up the files inside it from within the VM.

Unfortunately, there's no Time Machine (or even SuperDuper!) for Ubuntu, as far as I can tell, just a hundred blog posts describing how various smart folks have used some arcane combination of tar and rsync commands to back up their systems.

Networking

The Network preferences dialog is much better organized, which is nice, since I seem to visit it more often than I'd like. But perhaps I'll be visiting it less now that Mac OS X no longer turns up its nose at my home network's WPA personal security after every taste of the office network's WPA2 enterprise security.

The WPA2 enterprise username/password dialog also no longer goes away while I'm in the middle of filling it out if I take more than three seconds to do so, a welcome change.

VMWare Fusion

VMWare Fusion has a few minor issues in 10.5. It no longer resizes my Linux VM's resolution when I plug my laptop into my external monitor, nor does it recenter the desktop when I go from the external monitor back to my laptop's display until I switch from full screen mode to window mode and back.

And using Command-Tab to go to Fusion alternates between open Fusion VMs on two different spaces instead of taking me to the last one I used. Plus the tools need some munging to properly integrate with X.

But on the whole it still works fine, and I can continue to live in my full-screen Linux VM (from where I'm typing up this blog post now).

Appearance

I like the new darkness, with its multitude of gray tones. But I bemoan the addition of even more rounded edges, like those at the bottoms of menus. I prefer sharp edges in both virtual designs and physical ones (like cars and clothing), and its too bad everything has become a blobject since computers made it easy to draw a spline. Bubble buttons, bubble cars, bleh.

automated JS code rewriting

2007-10-15T15:53:00.001-07:00

Taras Glek has been doing awesome work on a framework for automated C++ code rewriting. I'd love to see something like that for JS code, since there are potential optimizations that are hard to do by hand (like changing the way we memoize nullary methods or removing the names of function expressions assigned to object properties).

Maybe Narcissus could be repurposed to provide round-trip JavaScript parsing, modification, and reserializing? This'd be a great project for someone who wants to help improve Firefox performance.

Bo Yang's Advanced Microsummary Builder

2007-10-04T00:41:00.000-07:00

This summer Bo Yang, a student at NanKai University in Tianjin, China, worked on a microsummary builder extension. His goal was to make it easy for regular users to create custom live titles for pages while experimenting with some additional features for power users.

He's recently uploaded the extension to addons.mozilla.org, and I've created a screencast showing it in action. Check out the screencast, then try out the extension (Firefox 3 pre-releases or nightly builds only).

Don't forget to file any bugs you find, and let Bo know (in comments on this blog post or by emailing him directly) what kinds of pages you're summarizing and how the extension works for you.

(For example, I used it to create a live title of timeandate.com's World Clock page showing the approximate time in Bo's time zone so I knew when I could expect to see him online.)

tabs for Thunderbird 2.0

2007-09-20T05:06:00.000-07:00

A user of one of the "Thunderbird 1.5 with tabs" builds I made a couple years ago recently asked me if it would be possible to update the patch for Thunderbird 2.0. After some wrangling, I got the patch to apply and behave itself in my testing, and I've spun some tab-enabled builds of 2.0.0.6 for Linux, Mac OS X, and Windows.

Note that the Thunderbird developers are implementing a different version of tabs for Thunderbird 3 over in bug 218999. So I won't be porting this patch to the trunk. But if you can't wait for that release to get your tabs, these builds may be useful to you.

To open a message in a tab, context-click it and select "Open message in new tab" from the context menu. To make this the default behavior when opening messages, set Preferences > Advanced > General > "Open new messages in" to "A new message tab".

p.s. congrats to Thunderbird on the new organization! I'm looking forward to great things from it.

Dave Winer's take on feed reading in Firefox

2007-08-17T14:31:00.001-07:00

Dave Winer came to MoCo yesterday for a chat about feed reading.

He gave us some food for thought, in particular the idea that limiting Firefox's feed reading functionality to a mere conduit for transferring feeds to the user's third-party reader of choice doesn't meet the needs of users who don't already understand the benefits of aggregated feed reading (which may well be a large majority of users).

Dave suggested we instead integrate feed reading directly into Firefox (while preserving choice for users who want to use another app). I'm inclined to agree, but I'll note that there's a third option: we could simply choose a default third-party feed reader, just as we've chosen a default search engine, and direct users there when they click on a feed.

it's not just about Thunderbird

2007-07-27T04:26:00.001-07:00

Folks seem to have missed half of Mitchell's recent email call to action. It wasn't only about finding a new home for Thunderbird.

Mitchell also says that "we would also like to find contributors committed to creating and implementing a new vision of mail" and that "Mozilla has a range of resources - funds, code, etc. - that can be applied to this problem. We're looking for people with expertise, vision and leadership capabilities."

MoCo's raison d'être isn't Firefox, it's improving the Internet through Firefox and other initiatives. That's why it's investing in the mobile space with projects like Joey, and it's why Mitchell and others (like me) are interested in mail.

But Thunderbird only has 5-10 million users (including me), while Firefox has 100 million, which means that at least 90% of Firefox users (and many more users of other browsers) are not being helped by Thunderbird.

That's not because MoCo hasn't invested enough into Thunderbird, it's because Thunderbird isn't the right solution for those users. And, based on its development trajectory to date, I don't expect that to change.

But neither do the other extant mail apps serve their users particularly well. As Mitchell says, we need a new vision for mail, and for me it's one that combines the portability of webmail with the usability of a desktop app and provides innovative new features for presenting and participating in conversations.

So let's not only focus on what to do with Thunderbird, let's also figure out what to do about mail and how to do it.

multi-OS builds from one source tree

2007-06-11T07:35:00.001-07:00

Someone asked me recently about the tabmail patch for Thunderbird, and, in some spare time between the super-intensive Hungarian language classes I was attending the last two weeks, I thought I'd see what it would take to get the patch working in Thunderbird 2.0.

I also figured I'd take the opportunity to switch my Windows build environment from the old Cygwin-based environment to the new MSYS-based MozillaBuild environment and--following roc's lead--try to set up a shared source directory on my Mac laptop that my Linux and Windows Parallels-based VMs could build from.

Setting up an SMB/CIFS share in Mac OS X via Apple > System Preferences > Sharing was trivial.

And mounting the share in Linux also proved fairly easy. I just had to install the smbfs package (available from Applications > Configuration > Synaptic Package Manager in Ubuntu 6.10) and then use Linux's standard mechanisms for mounting to an arbitrary filesystem location, f.e. via the smbmount command:


smbmount //10.211.55.2/myk ~/Machome -o username=myk

Note: you need to setuid on the smbmnt and smbumount binaries to be able to mount as a non-root user.

Getting things working on Windows proved harder, however. I tried to use mount to mount the share:


mount \\10.211.55.2\myk /home/myk/Machome

But mount complained "function not implemented", and googling for a solution proved unfruitful.

Then I tried adding a mount point to /etc/fstab per the instructions in /etc/fstab.sample, which got MSYS to mount the share (after also restarting Windows, since MSYS only parses /etc/fstab on DLL initialization), but then cl mistranslated a filename on the share and died with this error:


cl -Fohost_cppsetup.obj -c -TC -nologo -Fdhost_cppsetup.pdb -DXP_WIN32 -DXP_WIN
-DWIN32 -D_WIN32 -DNO_X11 -Ox -MD           -DINCLUDEDIR=\"/usr/include\"
-DOBJSUFFIX=\".obj\"   -I../../dist/include/mkdepend -I../../dist/include
-I../../dist/include/nspr    -I../../dist/sdk/include -I../../dist/include/nspr
/home/myk/Machome/Projects/bonecho/mozilla/config/mkdepend/cppsetup.c
cl : Command line warning D4002 : ignoring unknown option
'//10.211.55.2/myk/Projects/bonecho/mozilla/config/mkdepend/cppsetup.c'
cl : Command line error D2003 : missing source filename

I thought perhaps I could fool cl with a symbolic link:


ln -s /home/myk/Machome /home/myk/Machome2

But MSYS's version of ln apparently copies the directory (and all its contents) instead of linking to it (at least for network shares).

Finally I discovered that I could map a drive letter to the share in Windows Explorer > Tools > Map Network Drive, which MSYS (after restarting Windows again) maps to a path (/z in my case) that--although it's not where I want it--at least doesn't get screwed up by cl.

So now things are (almost) working. But not quite, as I'm seeing strange build errors like this one (when trying to build Firefox on the trunk):


/c/mozilla-build/moztools/bin/nsinstall -m 644 _xpidlgen/mozIPersonalDictionary.h _xpidlgen/mozISpellCheckingEngine.h _xpidlgen/mozISpellI18NUtil.h _xpidlgen/mozISpellI18NManager.h ../../../dist/include/spellchecker 
make[5]: Leaving directory `/home/myk/Projects/minefield/build/firefox-opt/extensions/spellcheck/idl'
make[5]: Entering directory `/home/myk/Projects/minefield/build/firefox-opt/extensions/spellcheck/locales'
make[5]: Leaving directory `/home/myk/Projects/minefield/build/firefox-opt/extensions/spellcheck/locales'
make[5]: Entering directory `/home/myk/Projects/minefield/build/firefox-opt/extensions/spellcheck/myspell'
make: Entering an unknown directory
make: *** src: No such file or directory.  Stop.
make: Leaving an unknown directory

And this one (when trying to build Thunderbird with the tabmail patch against the 2.0.0.4 release tag):


/c/mozilla-build/moztools/bin/nsinstall /z/Projects/bonecho/mozilla/xpfe/bootstrap/showOSAlert.cpp /z/Projects/bonecho/mozilla/toolkit/xre
nsinstall: cannot copy z:\Projects\bonecho\mozilla\xpfe\bootstrap\showOSAlert.cpp to z:\Projects\bonecho\mozilla\toolkit\xre\showOSAlert.cpp: Access is denied.

So I'm still working on building on Windows.

FWIW, build times feel OK on Linux and bad (but tolerable, for occasional use) on Windows, where initial build configuration and CVS operations seem particularly slow.

Speaking of CVS operations, I edited MozillaBuild's start-msvc71.bat file to start ssh-agent so I wouldn't have to enter my SSH key for every CVS transaction:


start "MSYS Shell - MSVC7.1 Environment" "%MOZILLABUILD%\msys\bin\ssh-agent"
"%MOZILLABUILD%\msys\bin\rxvt" -backspacekey  -sl 2500 -fg %FGCOLOR% -bg %BGCOLOR%
-sr -fn "Lucida Console" -tn msys -geometry 80x25 -e /bin/bash --login -i

Note: unlike in Cygwin, ssh-add in MSYS only registers ~/.ssh/identity by default. To get it to register your SSH v2 DSA private key, you have to specify the path to that key on the command line, i.e.:


ssh-add ~/.ssh/id_dsa

FWIW, MozillaBuild is a dream to install compared to the old Cygwin-based environment, but I miss the more Unixy Cygwin, not to mention the much more functional Puttycyg terminal.

The Importance of Good Translation

2007-05-02T00:51:00.001-07:00

A Hungarian and an American were walking down the street, both of them wishing they were holding hands. They'd been teaching English in the same Hungarian school for months, and they'd grown quite fond of each other.

The American was talking about a man she knew, and the Hungarian grew worried about this potential rival. "Did you two have a romantic relationship?" he eventually asked pensively.

"No," the American reassured him, "it was platonic."

The Hungarian was crushed. In the Hungarian language, a plátói relationship is an unrequited one, in which the pair still pines for each other. Quite different from common usage in English to mean a relationship devoid of romantic attraction.

So they didn't hold hands that day or any other for a year until they discovered the misunderstanding. All because of that single error in translation.

Fortunately, they did eventually discover the error, and last I heard, they were getting married.

toolsmith opportunity at Mozdev

2007-04-30T12:48:00.001-07:00

The Mozilla-related job market seems to be heating up these days, and I even received an inquiry from a recruiter lately asking if I know of (or am) someone to hire.

Job postings from that recruiter (and others) are available on mozilla.jobs, and the Mozilla Corporation is also hiring, but I'd like to highlight something else: a Web Apps Developer/Sysadmin contract position at Mozdev.

Mozdev provides project hosting and development tools to Mozilla-related projects, and we're looking for someone to enhance and integrate the services we provide.

This is a fantastic opportunity for an engineer's engineer who really appreciates the value of good tools in the software development process and wants to implement and integrate the state of the art collaborative development tools (VCS, wiki, forum, bug tracking, etc.) and push the toolsmithing envelope.

If you know of (or are) the right person for this job, then don't hesitate to apply!