Backfill

I have started to backfill this blog with what was almost lost from the previous blog, from oldest to newest.

VNC Server on Mac OS X 10.3

I didn't want to get more hardware right now, so I wanted to use the keyboard and mouse that was on my older PPC Mac, still running OS X 10.3. It doesn't do Remote Desktop's Screen Sharing as easily as newer OS X, so I wanted to use Vine VNC for a VNC server. I downloaded version 3.12, but the disk image wouldn't mount under 10.3. So, back to my newer Mac, mount, copy the application off, and (not wanting to hit further problems, although I did not test if this were still necessary) I also deleted Tiger.bundle before copying it to the older Mac. Voilà! it works!

Cocoa Powder

I've been making chocolate cupcakes for Karston's lunch. He knows he has to finish his lunch (two cheese sticks) first, but then he loves the treat and packs in more calories. So I was wondering about cocoa powder, specifically if I should use dutch-processed (alkalized) cocoa powder instead.

And, across the board, the two Dutched cocoas beat out the two natural cocoas in terms of both flavor and texture. So does the home cook need both Dutched and natural cocoas? Not based on our findings. But buyer beware, too much “dutching” is not a good thing. Our tasters found that while moderate Dutching helps alleviate harsh notes, the overzealously Dutched cocoa we tasted took on a taste and consistency reminiscent of talcum powder.

This suggests I should stick with Hershey's Special Dark cocoa powder since it is partially dutched. Plus, I've been looking, and alkalized cocoa powder is hard to find in my local stores. But Hershey's Special Dark? Easy to find, and Yum!

Cake Faults

This week's small batch of chocolate cupcakes turned out nicely. The previous two weeks, using a different recipe scaled down, did not. I read about cake faults to note that

Fault — cake sinking in the center

Causes

1. Too much aeration. This may be caused by:
(a) Too much sugar used in the recipe. This can be detected by excessive crust color and a sticky seam running in the shape of a U.
(b) Too much baking powder. Difficult to detect because it can be confused with (c).
(c) Overbeating of fat/sugar/egg batter prior to adding flour.

2. Undercooked. This can easily be detected by the presence of a wet seam just below the surface of the top crust.

3. Knocking in oven prior to cakes being set. If during cooking when all the ingredients are in a fluid state, a cake gets a knock or disturbance (such as a draught of cold air) some collapse may take place which will result in the center of the cake caving in.

4. Too much liquid. This is easy to detect because, firstly the sides will tend to cave in as well as the top, and if the cake is cut a seam will be discovered immediately above the bottom crust. Cakes containing too much liquid do not show this fault until they are removed from the oven. During baking, the excess moisture is in the form of steam and actually contributes to the aeration of the cake. On cooling, this steam condenses into water which sinks to the bottom of the cake, collapsing the texture by so doing.

I didn't see the behavior described for #4, so that's not it. I was careful not to knock them, so not #3 either. I really doubt #2 as well, just based on the clean toothpick. The cupcakes rose, and then fell, so I think it's #1. I don't think it's a because the cupcakes weren't as sweet as most. I didn't use any egg in the scaled down version, so either I did too much with the butter and sugar (by hand? really?), or too much baking soda (no baking powder in that recipe either). Or maybe it was leaving out the egg? Maybe more protein would hold the risen shape and not collapse?

Since the first recipe didn't scale down well, and I'm enjoying testing recipes designed for small batches, I don't think it matters. But it's nice to know what causes this sort of problem too.

Why Do I Have to Learn the Hard Way?

Why do I have to learn this the hard way? My previous blog host shut down, and I promise I didn't see any large notices, but most of the posts are backed up in MacJournal. It'll take me a while to push everything here (sans comments), and I'll have to re-create the pages that were outside of the post hierarchy, but here goes!

Windshield Cleaning

The inside of my car windshield gets filthy (and I don't smoke!), so I tried making my own windshield cleaner from equal parts of rubbing alcohol, ammonia, and water. It worked, I suppose, although there were some streaks.

So I decided to work on the streaking angle. This time, I used an old sock with a hole and water. After I rubbed the windshield, I went over it with a squeegee to remove all traces of water. Guess what? That worked really well!

So pick the window cleaner recipe you like best or use water; my best advice is to use a squeegee immediately afterwards!

Tinkering with XSLT again

The cool tricks for today (since I wanted to update my syllabus) include replacements and improvements to what I did before. Since TestXSLT is PowerPC-only, I had to find an alternative method. I'm using the command 'xsltproc --output Syllabus.html opmlsyllabus2html.xsl Syllabus.opml' where Syllabus.opml is a file I edit in OmniOutliner and save as OPML, and where opmlsyllabus2html.xsl is a modified version of beigeopml2web.xsl from Buzz, as noted before. Runs like a charm on Lion!

Since I was mucking about, I decided to try to insert the current date for "Last Modified" line, and this time I found a wonderful hint to insert the current date with XSLT (see the top reply). For a brief overview of the XSLT date options, see this reference. While playing around with formatting the date, I ended up without a space where I wanted one, so I had to look for a way to insert a single space too (see the first hint in the last reply). It works, better than ever! I just needed TestXSLT to stop working to motivate me to try again.