found_drama

If your hero wouldn't do it, now's your chance.



    Archive for October 2007

    #the great Google Calendar switch

    Google Calendar (beta) logoBack at the beginning of October, I decided to take the plunge and “switch” from using iCal more/less exclusively for my calendaring to using the web-based Google Calendar more/less exclusively. The reasons for the switch (even as just an experiment) were myriad and had built up slowly over a period of about two years. The catalyst however, the item that really caught fire with me, was when I decided that I needed to be able to add calendar events on the fly, from pretty much anywhere1 and then discovering that SMS’ing “GVENT” already does this with the Google calendar… Well, that pretty much sealed the deal.

    As a long-time iCal user advocate, I was reluctant to make this switch. I tend to perceive web-based applications as implicitly less-reliable and thus implicitly untrustworthy when compared to relatively stable desktop alternatives. If this seems a little unfair then I suppose I don’t give enough credit to the stability and/or ubiquity of internet connectivity2. I feel the need to have the information “right there” and available to me whether Google’s servers are up and running or not. Perhaps I have trust issues in that way; it’s one thing for Flickr or Twitter to flake out for an hour (those are just for playtime, right?) — it’s a whole other thing for my calendar app to be down.

    Now even with the add-via-SM feature, I had a couple of other questions I needed answered before moving forward:

    1. What about my existing calendars? Easy enough. Export those from iCal as .ics files and import them. A two-step operation, eh? Non-issue.
    2. But what about my recurrence rules? Should have known better than to worry about this… The .ics files store the recurrence rules (and the exceptions and violations); it’s built right into the standard. Non-issue.
    3. What about invites and notifications? I wasn’t worried about losing these. Actually, I was more concerned that they would get imported “too easily” and would wind up bacn bombing my contacts. Not sure how I was going to control for this. And though I took no special measures, this fortunately did not happen3
    4. And what about syncing? I knew that as fail-over, I could set up iCal to defer to the Google Calendar. I knew that if it all failed, I could dump the calendar events back out of Google (with .ics again) and put them back. Reverting wouldn’t be hard. But what about pushing that calendar to my phone? For reminders and such. I didn’t necessarily want to get hit with SMSs from Google every time an event was coming up due. Well, luckily iCal could pull the events from Google and dup them into the syncing engine where iSync could push them to my phone as I had been doing all along.

    Simple enough?

    So I made that switch. And of course, the same day that I commit everything to Google Calendar is the same evening that the whole thing is inaccessible for about two hours. Universally so? Perhaps not. I didn’t see or hear of any widespread clamor. But it certainly annoyed me. And struck as at least mildly ironic.

    But beyond that it’s gone well enough. No one’s been bacn bombed. My phone has all of my appointments. So that much appears to be working out just fine. And the GVENT add-via-SMS feature is teh hawt.

    The web interface itself is reasonably smooth — certainly on par with the iCal desktop interface. Sharing with others has proven easier than the iCal-plus-private server arrangement I had going before4. Overall the uptime and reliability has been fair; aside from the one major “outage”, there have only been a handful of cases where I could not connect immediately (and those passed with a brief refresh). Now, I’d been keeping the calendars in sync via a private PHP iCalendar + WebDAV solution but… Well, if you’ve messed around with this at all, you’re already aware of the limitations you quickly come across.

    With so much emphasis on syncing and sharing, some folks may be wondering: why not just jump on with Spanning Sync? Well, two simple reasons: (1) it would crash either iCal or the Finder on a daily basis when I was trying it out during the beta period5 and (2) I am looking for a no-cost solution if at all possible. For the possibility of getting iCal/gCal two-way syncing in play, Spanning Sync comes close to “worth it” so perhaps that is our next assignment.

    That said, the next question becomes: will iCal Server provide yet another alternative to consider? Only if it lets me add events via SMS, right?



    1. Translation: “from my phone”. []
    2. An old fashioned attitude? Maybe so. []
    3. Yet? []
    4. Which really only helped A. & I. Well, mostly just me. []
    5. Yeah, I know what beta means. The fact remains that regardless of the system I installed this on, my apps crashed and my calendar data was compromised. []

    #links for 2007-10-30


    #links for 2007-10-28

    • via Gus Mueller (maker of VoodooPad): “Mail.app now has a message: URL for each message, meaning you can now drag and drop messages to VoodooPad, and VP will link it up (in the upcoming release of VP 3.2.3 anyway).” This alone might be worth the price of
      (tags: Mac OSX essay todo)

    #links for 2007-10-26


    #links for 2007-10-25


    #links for 2007-10-24


    #autumn

    autumn

    When breakfast was over, John recited “To Autumn.”
    He recited it slowly, with much feeling, and he articulated the words
    lovingly, and his odd accent sounded sweet.
    He didn’t offer the story of writing “To Autumn,” I doubt if there
    is much of one.

    –Galway Kinnell, “Oatmeal”


    #Simile Timeline

    2007 Garden TimelineMentioned in passing the other day, Simile Timeline is a neat little API for building rich timeline visualizations with annotations.

    Though the documentation is a bit thin at the moment, the core code is not too difficult to figure out1 and if you start with a straightforward example (like this one) then you can get a quick-and-dirty one going in about as much time as it takes you to write out the XML.

    Considering that the community garden shut down for the season yesterday, I decided to experiment with the Simile Timeline API by building out one for our 2007 garden foray. Again, getting the initial events into the XML data file is super-easy (if a bit tedious); tweaking the JavaScript to get your timeline looking the way you want? That takes a bit longer… Most of the main variables (e.g., the height/width of the timeline) are well-enough exposed that a novice would be able to get it right with a few guesses. Customizing the theme and “zooming in” on sensitive “hot zones” however, that takes a bit more experimentation. That said, considering what I was able to accomplish in an afternoon (between loads of laundry), I must admit to being impressed with its relative simplicity — Simile Timeline is certainly an elegant solution for these kind of visualizations. Poking around on their site a bit, it seems I’ve just barely scratched the surface of its sophistication.



    1. Translation: “Don’t look for comments but be grateful that the variables have Plain English names.” []

    #links for 2007-10-21


    #2007 garden wrap-up

    Our first year of veggie gardening comes to a close. And what a year it was! Some thoughts and meditations on our crops, pests, techniques, etc….

    First, the crops:

    • garden #2515: basilBasil: nearly dead when we put it in the ground, we didn’t think that the basil was going to make it at all. And then this thing flourished like the weed it is. It got huge and bushy and we could scarcely keep up with it. Seemed to need no special care. Perhaps it is the leading candidate for a special section of herbs next year. Many a tasty dish prepared with these leaves.
    • garden #2751Beet: had more luck with these than expected … but also had lower germination rates than expected. The seed packet was promising germination rates in the 60-80% range. We got more like 20-40%. Which was a bummer because these were extremely tasty. So much so that we decided to do a second round. Too bad those didn’t really get much bigger than quarters (if they got that big at all).
    • garden #3699: AWESOME broccoliBroccoli: not sure if we’ll do these guys again next year. They were reasonably successful. I would say that (pound-for-pound) we got a great return on our investment in seedlings. And the florets were certainly good. But considering that we planted them in May and didn’t get anything edible from them until August… Well, it seemed that we could have used the space better. Jury is still out on broccoli in ‘08.
    • garden #3260: carrot topCarrot: a big winner for this year’s garden. If not the biggest winner. Rows and rows of crisp, tender, gold-orange carrots. Germination rates were high, yields were high (even with thorough bed thinning). And they needed next to no care. Just keep the bed clear of weeds, eh? Done and done. They’ll be back in ‘08.
    • garden #3641: one last cucumberCucumber: another big winner for 2007. We planted 8 seedlings in our cuke row expecting relatively low yields overall. I don’t know where we got that expectation. We were practically drowning in cucumbers for a couple months there. We juiced them, we put them in Hendricks & tonics, we put them in ice water, we made cucumber salad, we put them in “regular salad”, we used them for salsa, we made pickles1… Definitely doing these again next year. But I think next year we’ll look specifically for pickling cucumbers as we’re convinced our pickling experiment failed because of the fruits. And maybe the salt, too.
    • Garlic: a no-show, for all intents and purposes. Of course, didn’t see to many other folks having any success with garlic up here either. Skip this one all together next year.
    • garden #2971: onion manifoldOnion, red: well-enough-done, these guys. Something seemed not quite right about them, to me. Like they didn’t get big enough or like we pulled them too soon or something… I’m judging them harshly though, I think. The sizes were all across the spectrum and all of the ones we’ve eaten so far have been good-tasting. I’m just being unfair to the onions. We’ll do them again.
    • Parsley: another high-performing herb. Not at all fancy but effective. Another candidate for a patch of herb garden in ‘08.
    • garden #3455: peas!Peas, sugarsnap: dismal failure. Maybe we planted them too late. Maybe we were just at the mercy of that damn rabbit. In any case, we got limited germination and what germination we did get got chomped down my tiny buck teeth. The pepper spray helped for a day. And then it rained. And the pie plate trick helped for a week. But that was just long enough to get our hopes up. If we do peas next year, it will be out of some kind of hubris.
    • garden #3631: twinsPumpkin: alas! If the garlic tragedy had yielded even one cured and edible bulb then the pumpkins would have been “the big loser”. That said, the pumpkins were the garden’s big heartbreak story. Being a winter squash, we go into the deal knowing that it’s going to be a long time start-to-finish before we get anything useful from these vines. But to get the starts of so many tiny fruits (we knew they were supposed to be small “pie” pumpkins but still) and then to have the vines start to drop off like that… Going every day, plucking off those damn squash bugs, spraying down everything with the pepper spray, and then spraying for the mildew with the baking soda spray… All that work and then all we take home is a handful of pumpkins the size a racquet ball each? Crushing.
    • garden #3632Squash, Butternut: jury may be out on this one for a few weeks more still. Good yields overall. Good-sized fruits. They seem to have cured well. But we’re told that they take time to reach their peak flavor. Hopefully by Thanksgiving we can revisit that point there. But we didn’t lose any of these vines (unlike the pumpkins) and though they were sleepers all summer, they really came to life starting in late-August. Debating whether/not to do them next year, though. It’s a lot of space to commit for something that doesn’t give up fruit until right at the end. But like I said, the jury is still out on this one.
    • garden #3925: gibbous tomatoTomato, big kind: more intermittent heartbreak. Some jerks took it upon themselves to periodically loot our plot, making off with about a dozen of these Mountain Fresh and Celebrity tomatoes in all. The punks! What’s most irritating is that it did not seem as if any of the neighboring plots were similarly looted. Granted: (1) I would not wish that fate upon our neighbors, it just sucks to feel singled out like that and also (2) I cannot say for sure if anyone else got hit or not (I wasn’t keeping track of their tomatoes). That said, the output was okay but not great. These seemed to take too long to mature (even when they weren’t getting sniped). We got our money’s worth out of the seedlings (output-wise) but I think next year we’ll try a different variety (Romas, perhaps). We mostly use these for sauce-making and from what we saw in neighboring plots, the Romas seem the way to go for sauce tomatoes.
    • garden #3259: like traffic lightsTomato, cherry: holy crap! Six of these plants definitely put us over the top. Next year we’ll be looking at a maximum of three of these plants. No more. We were inundated with these cherry tomatoes. We couldn’t keep up; so many went to waste — just falling to the ground. And that’s even with us going every day, pulling all the ripe ones, making as much salsa as we could manage, and giving away the rest. Tremendous. Awesome. Prodigious. Frightening and overwhelming.
    • garden #2728: first harvestZucchini: we planted six of these seedlings. Everyone said that we would be sorry. But we got screwed by those damn bugs and the powdery mildew here, too. Of the six that we planted, one of them died pretty quickly, not sure why. Of the five that remained to bear fruit, the bugs and the mildew retarded their growth enough that the fruit yields were low. And I don’t care what anyone says — the smaller fruits may supposedly be tastier — but the finger-sized ones that we got were stunted midgets. Questionable if we’ll do these again next year.

    What else is there to say? It was great to get out in the open air, meet some folks from the city, other gardeners. Great to get tips on how to keep things growing, how to tease more fruits out of something, also fun to get competitive about who had fewer weeds or more carrots. Fun to trade cucumbers for lettuce or even just give away the handfuls of cherry tomatoes that otherwise overwhelmed us. It was amusing to improvise trellises from bamboo poles and twine — especially when those bamboo poles started to lean and tip under the weight of cucumber vines pregnant with future aborted pickles.

    Of course, there was the bit of heartbreak snuck in there, too. Dealing with the squash bugs and the powdery mildew the ravaged the pumpkins and zucchini (and yet left the butternut squash mostly alone). The realization that some jerk-off was thieving our tomatoes. The grim reality that a wild rabbit was helping itself to our baby sugarsnap peas.

    But that all comes with the territory, I suppose.

    And now we have all winter to figure out what we’ll do come spring. Step up to a full plot? Or is that, too ambitious? What crops to repeat? Which ones to abandon? Which new ones to try? And in the meantime, we have a whole season’s worth of pictures to help us remember. And more than a few jars of cherry tomato salsa.



    1. Well, we tried to make pickles. []