Ow. Ow. Even though contractors are hip deep in our first floor bathroom renovation, we still have plenty of projects of our own, including (ow ow) framing in the niches where the radiators used to be, so that the plasterers can make them flush with the walls. This, as always, turned out to be more complex than we ever imagined.
Background: we didn’t want to find a plasterer ourselves and so had put off this project, but we’ll have one coming in to finish the walls and ceiling in our new shower. So we decided we would take advantage of his coming to have him do the work. And it turns out to be affordable, provided that we do the basic framing ourselves. So on Saturday we cleaned out all the broken plaster from the niche, which turned out to be pretty much all of it, measured, and cut the 2x4s to length. Then I started swinging a framing hammer, and learned about slow progress. Really slow project. Fortunately we finished the dining room one and I even hung a box for the outlet.
Then things started to slow down. We had to remove trim from each of the other openings—intact, if possible, since we would need to reuse it once the plastering is complete. And in some cases we needed to bring up floorboards, since we had some floor to replace where there was some water damage and need to reuse the good boards to patch the bad ones.
Then there were the two pipes, that, in spite of all our HVAC installers’ efforts, were still too high to lay floor over. Fortunately our contractor volunteered to knock one off during his lunch hour—seeing that otherwise his plasterer wouldn’t be able to finish his job. And tonight I got another one done, in spite of a nightmare of bad angles and sheer fright. (Handling a reciprocating saw to cut a few inches off a loose cast iron pipe just below our bedroom floor ranks as my least home improvement chore ever.)
But that’s done, and all the lumber is cut to length. Now I just need to rig a jig so that I can use my circular saw to trim about 5/8ths of an inch off each piece, so that the blueboard will lay flush with the wall surface or below it. A few shots of the progress here, including the shower stall pre-rough piping and tile.
If this works, I will have successfully blogged from Flock. To get posting to my Manila site working, I had to bypass Flock’s blog autosetup and hand-edit the configuration file, which on my Windows machine is saved in my Documents and Settings directory under Application DataMozillaFlockprofiles[default]blog_alpha.rdf.
The problem with Flock’s autodetection technology is that both the Blogger and Metaweblog API attempt to use the GetUsersBlogs API call, which is not implemented on Manila. All I had to do to get it working, though, was to save a profile that called Blogger using the Metaweblog API, then edit the RDF file to set all the correct user ids and URLs based on my RSD file.
A few things I like about the blog editor—the built-in Flickr topbar is cool, cool, cool. And the UI for the actual editor is pretty nice. I especially like the option to show me the HTML of my post. I have used enough “WYSIWIG” editors that end up generating nasty HTML that I don’t really trust them anymore. —Flock is no exception to this rule, btw; rather than wrapping paragraphs in <p></p>, it ends a paragraph with a <br /><p>. Bad bad bad, particularly if your blog is HTML 4.01 Transitional. But once you drag up the splitbar to get to the raw HTML you can edit to your heart’s content. Which is good, because Flock totally mangles HTML entities. I put a curly quote in the HTML view with & rsquo;, which turned into the proper ’ in the preview; I then went and copied and pasted that into another place in the preview, but it pasted as a high ascii character rather than an HTML entity. Bad, bad, bad. And when you hit Italics in the preview, it formats it as <span style=”font-style: italic;”></span> rather than the more semantic <em></em>. Bad, bad, bad, bad. Forget what I said about the blog editor; it needs work, and I will be posting some bug reports.
Also, the draft functionality is weird. When you save as draft, your post window closes, and you have to open a new blog window, switch to the Draft account, open the Blog topbar, and click on the saved post to get it to open. Then you have to mouse down in the text field to enable the Publish button. Not intuitive.