repeat
make
-f client.mk build, installing the development library
found missing each cycle:
sudo apt-get install libgtk2.0-dev
sudo apt-get install libidl-dev
sudo apt-get install libxt-dev
killall firefox-bin
fb-opt-static/dist/bin/firefox
Subsequent builds can be done simply by running
make in the fb-opt-static directory.
In many ways, developing again in C++ was as comfortable as
putting on an old pair of shoes. The most painful thing was
having to once again get used to a traditional edit-compile-debug
cycle as opposed to the :w-refresh that I generally
use these days. This was made extra painful by the need to
bring down firefox between tests, as that tended to disrupt my
diversions.
That DOM element “linkElem” should have a “baseURI” property, as Mozilla already implements that part of DOM3. You can use the standard URI resolver to get an absolute URI. I wrote an equivalent JavaScript for Thunderbird ( there’s a patch coming for Atom 1.0).
Sam Ruby: Patching Firefox for Atom 1.0: “Phil Ringnalda decided to copy me on the Live Bookmarks should support Atom 1.0 bug report. This lead to my developing and testing a patch.” Very cool....
Somehow Tantek’s Atom 1.0 feed works with Firefox live bookmarks, and I’m using the official 1.0.6 release, not a nightly. Any idea how he’s doing this?
Brad, Atom 1.0 feeds like Tantek’s which explicitly state rel="alternate", don’t use relative URIs for links, and have titles as plain text will display fine in 1.0.6.
The alternate links in my feed simply have hrefs, as the Atom 1.0 spec indicates that the default for the rel attribute is “alternate”. None of these entries will show up in 1.0.6, but will show up in the nightly.
Cool. I’m adding syndication to a CMS I’m working on, and I really like Atom 1.0 after reading Tim Bray’s article comparing it to RSS 2.0 (link: [link] ), but it happens to be brand spanking new (which is a total coincidence for the timing of my project) so I’m trying to work out kinks such as these.
One thing Atom 1.0 could use is a nice, clearly laid out specification for laypersons, much like the RSS 2.0 spec on feedvalidator.org (link: [link] ).