• in OmniWeb I can take and add a URL for later reading, it’ll go into my inbox by default
• in OmniWeb I can take and add a URL to my ‘wish-list’ project (with a start date for at 2 weeks in the future)
• in OmniFocus I have scripts to easily change the context or the project of selected tasks
• in Mail I can press a key and have the selected e-mail(s) sent to OmniFocus with a ‘Respond to: ‘ before the subject line, sorting into either a default project or the one specified in MailTags, with the context set to ‘mail’ and the message URL in the note-field
• in OmniFocus I can select such a task, press a key to run a script that will open the message and immediately create a reply (I have a separate one for just opening, in case I have to read it thoroughly first)

All these scripts make the integration between all these programs very easy. That and FastScripts.
I found useful scripts over at Curtis Clifton’s site. His scripts use Growl notification so if you have Growl installed you get a small notification.

I had some trouble putting my own scripts together, so I decided to paste the info here, just in case I need it later on, or someone else runs into similar issues. I found it quite hard to figure out how to add a task to an existing project or to move it from inbox / other project. In the end, it only took a few lines.

First, when I started my script, I wanted a default project or context (I’ll use ‘project’ from now on, but it also applies to the context-script). To do this I created a ‘property’ at the beginning of the script:

I used the alterItemNum for my alerts through this very simple routine:

That went at the end of my script.

I started by addressing OmniFocus and ‘talking’ to the open document:

Then, I checked to see if that document had anything selected, and if not, give an error-dialogue:

If I have no items selected, the script will call the alert routine from above ( my notify(alertName, alertTitle, alertText) ). Because I created a separate routine, I can use this anywhere in the script.

Next, display a dialogue asking for the project:

The variable ‘theProject’ will now contain the name of the (new) project to move the tasks too.

Next, the loop to go through all the items and move them:

This loop will end as soon as the variable ‘selectNum’ (= numItems which I set to the count of the items in the variable SelectedItems) reaches 0. It calls the routine ‘ChangeProject’ which I’ll get to in a bit, but I first want to wrap up this part. Let me also explain the ‘if succeeded then set successTot to successTot + 1′ line. The line before sets ‘succeeded’ to the result of the ChangeProject routine. This result can mean anything, numbers, letters, whatever. In this case we use it to return a ‘true’ or ‘false’. That way, we only need to use ‘if succeeded’ (which will either be ‘true’ or ‘false’) as a condition. We don’t need to check the actual content of the variable. This can come in handy for various checks, and it took me a while to catch on to that, so I figured I’d mention it here.

To end this main routine, I used:

Basically, this tells the dialogue box to say the script ran successfully and displays the number of items successfully moved and only to use the ‘s’ after ‘item’ if the count of successful moves is higher than 1.

That wraps up the main part.

The routine to actually move the task to the other project only took 21 lines:

The first line sets the success to ‘false’, because we want to actively, after having our success, set it to ‘true’.
We then chat with OmniFocus again, and this time, we’ll just talk to the default document (the one you have open). If the variable ‘theProject’ is not empty, we’ll continue. If it is, the ‘if-end if’ ends, without having set the ‘success’ variable to true (and thus, the script failed). You could technically build in an extra loop to change it to a default project, however, I prefer it this way. If I accidentally emptied that dialogue-box, nothing will happen, just as I like it.

If theProject does contain something (anything), the script continues with its routine. It sets the MyProjectArry to null (makes it empty, just in case). It then used OmniFocus complete option to find the first matching project of OmniFocuses project-list. If you’ve ever only typed the first three letters in one of OmniFocus’s project-areas (to set the project) and it magically came up with the right project, this is the same thing. It means you only have to type the first three or four letters of your project, and the script will find it. If it can’t find the project, it will create it for you (at the end of your project-list).

After that, it will simply try to add the task to the desired project.

I’ve copied this part again, because this took me hours to figure out. I knew how to do it for a context-change:

so I tried to ‘set project of newtask to theNewProject’ but that didn’t work. It drove me crazy for a while, still haven’t fully recovered…

But it works! The complete script changes the project of selected tasks and gives a confirmation dialogue (so you know that it happened). Of course, before using it, make a back up of your OmniFocus database, and run the script from Script Editor first. Open the ‘Event Log’ (⌘-3) to follow what happens while you run the script.

zipped up version of ChangeProject and ChangeContext for easy downloading

Lots of times my beans got eaten by the larvae of the bean-fly (oh how I hate them!). I went looking for a better way and found something that works very well. This will probably work for other seeds too, and will give you a good idea about the germination rate of your seeds (if you have old seeds you sometimes want to check). I’ve had no problem transplanting the resulting sprouts, just keep in mind you will have to transplant them at some point. Not all sprouts like that.

Kids will usually love this too. Use beans though, they sprout fast :)

You will need:
- a ziploc bag (or another type of firm plastic bag)
- some toiletpaper or paper towels
- something to spray water with
- beans! Take the toiletpaper and put down several layers. Place a few beans on the paper. Spray thoroughly with water until the paper becomes moist with water, but does not drip.

Fold the paper, with the beans in the fold. It helps to not line up the edges so you can check later on. Keep the bag open (very important) and place it in a dark warm place. Most people prefer the top of their fridge, I used a kitchen-cabinet with pipes behind it.

After the first day you may or may not see little roots coming from the bean. Check daily if you prefer, or every other day, to make sure the paper stays moist and to check for beans that rot (it sometimes happens, especially with older beans, they smell bad so it’s best to remove the asap).

A few days later, however, the beans have sprouted!

Take it out of the bag, carefully. Make sure not to break any roots.

You’ll see here that not all beans sprouted. Two of them rotted (I felt very sad), but the others shot up! The ones on the right I deemed plant-worthy and planted them outside. I took the risk with the two on the left as well, but left the other two (barely rooting) in the bag for a while.
If the roots have gone through the paper, don’t worry! Just rip the paper and plant it with the bean-sprout. It’ll dissolve quickly enough.

Some beans take longer than others, perfectly normal. However, if after a week to ten days you see no action at all, and the beans have gone mushy, they failed. They’ll smell bad too.

Ingredients:

Directions:
Cook the lentils and mix together. Simmer with tomatoes and spices for about 45 minutes.
If needed drain excess liquid, and serve with grated cheese on top.

(Serves 4)

Note: I used a can of Bonduelle (brown) Lentils, dried red lentils and Heinz Tomatoes chopped, with herbs, in juice.