$enddelim = '<!--:-->';
 $englishdelim = '<!--:en-->';
 $hebrewdelim = '<!--:iw-->';

 $getpost = get_posts('post_type=page&include='.$post->ID);
 foreach($getpost as $p2) :
 setup_postdata($p2);
 $both_titles = 'blah'.$p2->post_title;
 $both_bodies = 'blah'.$p2->post_content;
 endforeach;

 if(strpos($both_titles, $englishdelim)) :
 $pt1 = explode($englishdelim, $both_titles);
 $pt2 = explode($enddelim, $pt1[1]);
 $p_title['english'] = $pt2[0];
 endif;

 if(strpos($both_titles, $hebrewdelim)) :
 $pt1 = explode($hebrewdelim, $both_titles);
 $pt2 = explode($enddelim, $pt1[1]);
 $p_title['hebrew'] = $pt2[0];
 endif;

 if(strpos($both_bodies, $englishdelim)) :
 $pt1 = explode($englishdelim, $both_bodies);
 $pt2 = explode($enddelim, $pt1[1]);
 $p_body['english'] = $pt2[0];
 endif;

 if(strpos($both_bodies, $hebrewdelim)) :
 $pt1 = explode($hebrewdelim, $both_bodies);
 $pt2 = explode($enddelim, $pt1[1]);
 $p_body['hebrew'] = $pt2[0];
 endif;

Schedule Sending

This script sends out an email to you with your full upcoming schedule.

[php]<?php
mysql_connect(‘{SQL SERVER}’,’[SQL USER}','{SQL PASSWORD}');
@mysql_select_db('rtm_memory') or die( "Unable to select database");
$sql = "select * from users where active = 1;";
$users = mysql_query($sql);
while($user = mysql_fetch_array($users)) {

//what's the current hour?
$curHour = date(G);
$userID = $user['id'];
$sql = "select * from hours where userID = ‘$userID’ and hour = ‘$curHour’;";
$hours = mysql_query($sql);
$hourc = mysql_num_rows($hours);
if ($hourc == 0){
exit;
}

//First, get the list of incomplete tasks, this list is sorted in reverse chronoligical order by due date. (The higher an item’s value in the array, the sooner it needs to be done)
//I opted to get the list in JSON format for easy manipulation. It’s what I’m comfortable with. It’s also available in REST.

//This API call is static, so we can just go ahead and calculate the sign
$apiCallVars = ‘{SHARED SECRET}api_key{API KEY}auth_token’.$user['token'].’filterstatus:incompleteformatjsonfrob’.$user['frob'].’methodrtm.tasks.getList’;

$sig = md5($apiCallVars);

//And build the URI
$url = ‘http://www.rememberthemilk.com/services/rest/?api_key={API KEY}&auth_token=’.$user['token'].’&filter=status:incomplete&format=json&frob=’.$user['frob'].’&method=rtm.tasks.getList&api_sig=’.$sig;
//echo $url;
//And retrieve and decode the response
$response = file_get_contents($url);
$tasks = json_decode($response);

//Make sure the string is good, if it’s not, keep trying until it is (up to 100 tries)!
$rt = 0;
while ($tasks->rsp->stat != ‘ok’ && $rt < 100) {
$response = file_get_contents($url);
$tasks = json_decode($response);
$rt++;
}
//var_dump($tasks);
if ($tasks->rsp->stat != ‘ok’) {
//Start building our email with a failure notice
$body = "Communications error with Remember The Milk. Sorry!
";
} else {
//Start building our email with a Past Due header for the first tasks. I almost always have something past due, so I keep this there always
$body = $body . "Past Due:
————————-
";
}

//I opted to break up my list into Past Due, Upcoming, and Future events, so I need to get the current time
$now = time();

//And set the future time 1 week from now (604,800 seconds)
$future = time() + 604800;

//Have we reached current events?
$nt = 0;

//Have we reached future events? (we set nt and ft so that it doesn’t show the headers more than once)
$ft = 0;

//How many tasks are there? Find out and subtract 1 because our counting starts at 0
//Note: I indicate the use of list 1 because that’s the list that all of my tasks are in (my inbox), YMMV. If you build this
//and get errors, try switching list[$listCount] to list['0'] thoughout the script

$tc = count($tasks->rsp->tasks->list->taskseries);

$tc–;

//Process each task
while ($tc > -1) {
//Pull out the name and due date… that’s all I use on RTM… if you use more, then you can include them. Not a big problem.

$name = $tasks->rsp->tasks->list->taskseries[$tc]->name;
$date = $tasks->rsp->tasks->list->taskseries[$tc]->task->due;

//Convert the due date/time to my timezone, MST (my server is in PST), and then put it into a friendly format
$ts = strtotime($date) + 3600;
$time = date(‘D, M j g:ia’, $ts);

//Check to see if this is the first "Upcoming" or "Future" task, if so, put on the appropriate header
if ($now < $ts && $nt == 0) {
$nt = 1;
$body = $body."
Upcoming:
————————-
";
}
if ($future < $ts && $ft == 0) {
$ft = 1;
$body = $body."
Future:
————————-
";
}

//Build the string we’re going to add to the body. This is just the time string – the task name and a line break, for example
//Thu, Mar 5 3:30pm – Meet the Qwest Installer
$bodyl = $time." – ".$name."
";

//Pin this onto the body
$body = $body.$bodyl;

//Reduce the count
$tc–;
}

//I now use the unix "cal" command to generate the next 4 months in plaintext calendar format to append to the end of the message
ob_start();
$cM = date(‘m’);
$com = "cal ".$cM." 2009";
passthru($com, $cal1);
$cM++;
$com = "cal ".$cM." 2009";
passthru($com, $cal2);
$cM++;
$com = "cal ".$cM." 2009";
passthru($com, $cal3);
$cM++;
$com = "cal ".$cM." 2009";
passthru($com, $cal4);
$calData = ob_get_contents();
ob_end_clean();

//Pin that calendar data on
$body = $body."

".$calData;

//Lets also put a note at the bottom about the number of communications tries it took:
$body = $body."

RTM reached after ".$rt." retries.

This schedule sent to you courtesy of Hotchkiss Consulting (http://hotchkissconsulting.net/)";
//Output the email body
echo $body;

//Build and send the email
$to = $user['email'];
$subject = ‘My Schedule’;
$message = $body;
$headers = ‘From: rtm@hotchkissconsulting.net’ . "rn" . ‘Reply-To: rtm@hotchkissconsulting.net’ . "rn" . ‘X-Mailer: PHP/’ . phpversion();
mail($to, $subject, $message, $headers);
} ?>[/php]

Notification Sending

This script sends out a notification email to you with appointments coming up within the next 30 minutes.

[php]<?php

//Lets get ourselves a timeline
$key = md5(‘{SHARED SECRET}api_key{API KEY}auth_token{AUTH TOKEN}formatjsonfrob{FROB}methodrtm.timelines.create’);
$url = ‘http://www.rememberthemilk.com/services/rest/?api_key={API KEY}&auth_token={AUTH TOKEN}&format=json&frob={FROB}&method=rtm.timelines.create&api_sig=’.$key;
$response1 = file_get_contents($url);
$tl = json_decode($response1);
$timeline = $tl->rsp->timeline;

//And download the tasks list
//This API call is static, so we can just go ahead and calculate the sign
$sig = md5(‘{SHARED SECRET}api_key{API KEY}auth_token{AUTH TOKEN}filterstatus:incompleteformatjsonfrob{FROB}methodrtm.tasks.getList’);

//And build the URI
$url = ‘http://www.rememberthemilk.com/services/rest/?api_key={API KEY}&auth_token={AUTH TOKEN}&filter=status:incomplete&format=json&frob={FROB}&method=rtm.tasks.getList&api_sig=’.$sig;

//And retrieve and decode the response
$response = file_get_contents($url);
$tasks = json_decode($response);

//Make sure the string is good, if it’s not, keep trying until it is (up to 30 tries)!
$rt = 0;
while ($tasks->rsp->stat != ‘ok’ && $rt < 30) {
$response = file_get_contents($url);
$tasks = json_decode($response);
$rt++;
}

//Get the current time so we know whether or not to send an alert
$now = time();

//How many tasks are there? Find out and subtract 1 because our counting starts at 0
//Note: I indicate the use of list 1 because that’s the list that all of my tasks are in (my inbox), YMMV. If you build this
//and get errors, try switching list to list['0'] thoughout the script
$tc = count($tasks->rsp->tasks->list->taskseries);
$tc–;

//Set the email headers now so it doesn’t do it repeatedly through the while statement
$headers = ‘From: {FROM ADDRESS}’ . "rn" .
‘Reply-To: {FROM ADDRESS}’ . "rn" .
‘X-Mailer: PHP/’ . phpversion();
$to = ‘sam@samandbecky.net’;

//Run this for every task
while ($tc > -1) {
//Get the list ID
$lid = $tasks->rsp->tasks->list->id;

//Get the task title
$name = $tasks->rsp->tasks->list->taskseries[$tc]->name;

//get the task notes
$notes = $tasks->rsp->tasks->list->taskseries[$tc]->notes;

//Get the due date
$date = $tasks->rsp->tasks->list->taskseries[$tc]->task->due;

//Get the estimated time field which I use to see if I’ve sent a notification for this task yet
$notified = $tasks->rsp->tasks->list->taskseries[$tc]->task->estimate;

//Get the task series ID
$tsid = $tasks->rsp->tasks->list->taskseries[$tc]->id;

//Get the task ID
$tid = $tasks->rsp->tasks->list->taskseries[$tc]->task->id;

//Convert both the task time and the current time into my time zone, MST from PST and make the due date pretty
$ts = strtotime($date) + 3600;
$now = time() + 3600;
$time = date(‘D, M j g:ia’, $ts);

//Calculate the difference, in seconds, between now and when the task is due
$tt = $ts – $now;

//Build a notify string that indicates the day so that we are reminded more than once
//for recurring tasks
$notificationVal = date(‘zy’) . ‘min’;

//Notify if the task is due in fewer than 30 minutes (1,800 seconds) and a notification hasn’t already been sent.
//We also check to make sure that the task wasn’t due more than 2 hours ago. This prevents an issue with repeating
//tasks where they will notify over and over.
if ($tt < 1800 && $tt > -7200 && $notified != $notificationVal) {

//The email subject will be the task name, then a dash, then the Task ID, Task Series ID, and List ID delimited by commas
$subject = $name." – ".$tid.’.’.$tsid.’.’.$lid;

//The email body contains the due time and the notes
$message = "Due: ".$time."
Notes: ".$notes['0'];

//send the email
mail($to, $subject, $message, $headers);

//Now we’re going to make it as notification sent by setting the estimated time to complete to our notification val

//first build the sig
$toHash = ‘{SHARED SECRET}api_key{API KEY}auth_token{AUTH TOKEN}estimate’.$notificationVal.’formatjsonfrob{FROB}list_id{LIST ID}methodrtm.tasks.setEstimatetask_id’.$tid.’taskseries_id’.$tsid.’timeline’.$timeline;
$sig = md5($toHash);

//then build our query URL
$url =’http://www.rememberthemilk.com/services/rest/?api_key={API KEY}&auth_token={AUTH TOKEN}&estimate=’.$notificationVal.’&format=json&frob={FROB}&list_id={LIST ID}&method=rtm.tasks.setEstimate&task_id=’.$tid.’&taskseries_id=’.$tsid.’&timeline=’.$timeline.’&api_sig=’.$sig;

//then submit the query. Voila!
//And retrieve and decode the response
$response3 = file_get_contents($url);
$result = json_decode($response3);

//Make sure the string is good, if it’s not, keep trying until it is (up to 30 tries)!
$rt = 0;
while ($result->rsp->stat != ‘ok’ && $rt < 100) {
$response3 = file_get_contents($url);
$result = json_decode($response3);
$rt++;
}
}

//Move on to the next task
$tc–;
}

?>

[/php]

Notification Reply Processing

This script processing replies that you send to the notification message, and submits any needed changes to RTM

[php]</em>

Post questions in the comments and I will be happy to help you out!

The WordPress theme is from http://graphpaperpress.com/.  We are big, big fans of WordPress for a lot of simple to moderately complex sites (like this one you’re on right now).  WordPress allows a lot of flexibility and customizability, and a well developed CMS backend.

What are the upsides of developing with WordPress?

1. Quick development.  With WordPress you’re building your site on top of a solid base that takes care of a lot of the basic stuff, which means less testing is necessary, and less new code is necessary.
2. Less expensive.  This ties into number 1– as it takes less time for us to develop your site on top of WordPress, you pay less.
3. Easily extensible.  Because WordPress has such a large user base, there are thousands of extensions available.

In the end, developing most “simpler” sites in WordPress changes from inventing the wheel to refining it.  Our workflow generally consists of putting together the elements needed to create your site, then going through and modifying things to fit your business and your needs.  Because we have a strong understanding of XHTML, CSS, and PHP, we’re able to tweak existing elements to fit the needs of your company.

So, What are the downsides of developing with WordPress?

1. Limited customization.  With WordPress, you can only go so far, and if your site is going to have advanced features, WordPress isn’t going to be the right solution.  What do I mean by advanced features?  Well… do you want customers to be able to log in?  Interact with the site?  Buy from you online?  Do you want to be able to aggregate information from other sources?  Do you want to interface with other services via API?  If you answered yes to any of these, then WordPress probably isn’t the right solution for you.
2. Security.  WordPress is not completely secure.  That said, it’s not like the computer geek at your local high school could easily break in, but if you had a dedicated hacker looking to get at your information, your site could be compromised.
3. Client Overconfidence. Now this one is a little bit of a tricky area… but I’ve seen a few occasions where the WordPress admin interface is so easy to use that the client will try adding features on their own, which has, more often than not, resulted in the whole site breaking.  Similarly, clients will automatically assume that they’re supposed to install every WordPress update, when, oftentimes, this ends up removing any or all of the customizations we’ve made to the site.

So, when is WordPress the right choice?  If you’re a small business looking for an attractive, simple website that you can update on your own, and you’ve got a moderate level of tech saavy, WordPress deserves a close look, and, at Hotchkiss Consulting, we’re happy to help you figure out the solution that’s best for your business.

I’m taking this weekend “off” which means I’m going to sit in my PJ’s and geek out all weekend.  Maybe this project will get some attention.

Are there any email-based apps you’d like to see?  Let me know!  And don’t forget to follow us on Twitter!

I’m always interested in what setups other people use, so I thought I’d give you guys a peek at how I work…

MacBook Air

As a developer, I’m pretty demanding when it comes to my computers.  I type hard and fast, I run a ton of programs simultaneously, and I work from just about everywhere.  Not just my desk or my couch or my bed, but from coffee shops, airports, the library, with clients, in cars, on trains…

For the last three years I’ve worked on a trusty 15″ MacBook Pro which had been a great machine, although with its quirks.  It made a number of trips to the repair shop, but never left me in a pinch.  Finally, this winder, I decided it was time to upgrade, and picked up a MacBook Air, with which I have been nothing but impressed.  I opted for the solid state drive, so there is no spinning drive, and this machine is sweet.  Fast, tiny, and light.  And I haven’t missed having an internal CD/DVD drive for a second!  The backlit keyboard is a major improvement over the MacBook Pro, and it’s great to type on, too.

The MacBook Air gets an A+ from me!

Peek

I’ve been a long-time Blackberry user/addict, but when the Peek came out I decided to take a look.  The peek does email and email only in a device smaller than any other smartphone at a very attractive price– just $20 a month.  At first, I wasn’t too impressed– the lag was huge (often times 30 minutes+), which is too long to wait to learn that a server is down or a client needs a change made immediately.   Frustrating!  But I’m now beta testing the new Peek software, Peek Pronto (due out in a couple weeks), and you can color me impressed.  Email now regularly shows up on my Peek BEFORE it shows up on my computer.  That’s good speed!  And it’s nice to be able to move around town without a cell phone, yet still be connected.

I look forward to seeing how the Peek continues to evolve over the coming months– it’s a young product with a very active and responsive team.

Software

Next comes software.  After a long struggle to figure out what my ideal setup was, I finally realized that the ultimate coding environment just doesn’t exist within a single App.  I use Coda, from Panic Software (a top-notch Mac development house), to do all of my project management.  Coda is awesome at letting me get at my files quickly, keeping track of which files need to be uploaded, handling those uploads, playing with CSS, and the built in SSH client is really handy.  The downside of Coda is the text editor, which, while good enough for quick edits, just doesn’t have the same polish of TextMate.

TextMate is an app I’d heard about for a long time, and just finally began to use, and my only regret is that I waited so long.  The code completion works perfectly, it’s quick, it’s beautiful, it’s… well, it’s just great.  I am a happier coder with TextMate, and that’s a beautiful thing.

My primary web browser is Firefox 3, because I love the plugins!  My favorite plugins are FoxMarks, Web Developer, and ColorZilla.  For testing, I also use Safari on the Mac and IE, Firefox, Safari, and Chrome in Windows XP Pro (through VMWare Fusion).

And while all of these things are great, my absolute favorite new app/service of the past year (and maybe ever), is Dropbox.  Dropbox is pretty much magic.  I keep all of my working files in my Dropbox, and it automagically sends them to a secure server off in the cloud, keeping them backed up and accessible from anywhere.  But that’s just the beginning.

Dropbox logs every revision of a file you save, so when I realize I screwed something up, I can go back to my 10-minutes-ago copy of a file in seconds, and, through Dropbox’s file sharing features, it’s easy for Becky and me to keep our current files accessible to both of us, and sharing files with clients is a snap.

So that’s my setup!  Of course, I also have MS Office, Adobe CS3, etc, etc, but those, to me, are secondary apps.  These are the programs that I spend 90% of my computing life in.

What software do you use?  Is there something you think I should try?  Let me know!  And stay tuned for an upcoming post where I let you know how we saved $50 a month on our cable bill!

So, in accordance with my plan to switch client communication from phone to email, I have decided that, instead of a Cell Phone, I will carry a Peek with me.  While it has been a rocky road so far, I trust that the people at Peek have some good updates coming down the pipeline, so I’m going to stick it out for a couple months and see how I like it.

The thing about the Peek is that it’s eMail only.  And I really do mean only.  No calculator, no games, no web browser, and no calendar.  For me, that just won’t do– I am an avid fan of Remember the Milk.  I keep it in my OS X dashboard and on my desktop email screen (I use GFYD, Google For Your Domain).  Having my RTM to go is a must.

Currently, RTM offers a couple email-based options.  You can email in new tasks, you can receive a list of your tasks for the day every morning via email, and you can receive an email reminder before a task is due.  This is a good start, but there are some problems:

1) With the daily schedule emails, you can only see what’s going on that day, you can’t see your entire schedule.  This information is crucial for setting appointments.

2) Reminder emails don’t have the task name in the subject line, meaning you have to open the email to see what you’re supposed to do.

3) You can’t do anything with the tasks– no marking them completed or postponing, you have to do this from the computer.

So, I wrote my own email interface, and will go over it and include my source files so you, too, can build your own (if you’ve got some PHP know-how).  If there’s enough interest, I will build a standalone, hosted solution for everyone of every skill level.

Now, you’ll note that I didn’t mention any problems with the task submission, that’s because it works pretty well already… the only issue I ran into there is that the Peek gives an alert every time you try to submit a new task because your RTM task submission email address contains a “+” sign.  So I simply added an email address to one of my domains that forwards to my RTM address.  Problem solved.

Issues with my RTM email interface:

1) I use the time estimate field to store my flag as to whether or not a notification has been sent.  This isn’t a field that I, personally, use.

2) I have built this to use only one list, my inbox.  If you want to use more lists, go for it, this script should give you a good starting point.

3) Even with my source code, this is a pretty technical process to get this up and running on your server.  I’m providing this to help those of you who have a basic understanding of PHP and REST/JSON data structure save a little bit of time.  If there is sufficient interest, I will consider building a service to do this for you– if you are interested, please post a comment letting me know.

4) These instructions assume that you already have an API Key and Shared Secret and a frob and token with read/write access to your user account.  If there are a lot of questions about this, I can post a separate how-to.

You are welcome to use this information for personal projects and distribute it with proper accreditation.

This interface uses 3 scripts, I will go through each in a separate blog post:

1) Schedule

This script sends me my full schedule at 7am, noon, and 5pm (It is triggered by crontab).   Here’s what one of those emails might look like:

Past Due:
-------------------------
Wed, Mar 4 2:00pm - call leanne smith re: PSD files
Thu, Mar 5 6:00pm - Send Back Candles

Upcoming:
-------------------------
Fri, Mar 6 10:00am - Change netflix plan
Fri, Mar 6 10:00am - Pay Care Credit Bill
Fri, Mar 6 10:00am - Pay Sallie Mae
Fri, Mar 6 12:00pm - call kennebec re contract
Sat, Mar 7 10:00am - Haircut!
Sat, Mar 7 11:00am - Go see an unlikely weapon at noon
Wed, Mar 11 8:30am - Dog Grooming @ Happy Paws
Wed, Mar 11 4:00pm - Meet with B. Peterson @ 430
Thu, Mar 12 5:15pm - Take out the Trash

Future:
-------------------------
Wed, Mar 18 3:45pm - Meeting w/ J. Doe at 4:30
Fri, Mar 20 8:15am - Dentist Appt
Sat, Jun 6 1:00am - Call Barbara to set up meeting on the 10th

     March 2009
Su Mo Tu We Th Fr Sa
 1  2  3  4  5  6  7
 8  9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31

     April 2009
Su Mo Tu We Th Fr Sa
          1  2  3  4
 5  6  7  8  9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30

      May 2009
Su Mo Tu We Th Fr Sa
                1  2
 3  4  5  6  7  8  9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31

     June 2009
Su Mo Tu We Th Fr Sa
    1  2  3  4  5  6
 7  8  9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30

You can see, also, that at the emails I’ve tacked on the next 4 months worth of calendars so I can see what’s coming up!

2) Reminders

To replace the reminder emails, I have a script that runs every 5 minutes to check to see if I have any tasks coming up within the next 30 minutes.  It then generates an email in which the subject is the name of my task followed by the Task ID, Task Series ID, and List ID (all of which are period delimitted).  This allows my next script to work its magic as well as putting my task info right there in the subject line so I can see what’s going on.

3) Modifications

This script checks a secret gmail account every 5 minutes, reads my messages and processes them based on the Process Code I send in.  The process code is the first letter in an email– if it’s “C” then this script tells RTM that the task is Completed.  If it’s “P”, the script tells RTM that the task is Postponed.  It figures out what the task is by parsing the numbers at the end of the subject line.

So… that’s what we’ve got!  Scripts are on their way and should be up today, please let me know what you think, and feel free to leave any questions in the comments field below.

So, I know it’s been around for a fairly long time, but I’m a busy guy, so I’m just getting around to it.  But, in under 20 minutes with pipes,  I was able to throw together a “pipe” that will sort through the USGS’s mountain of data and tell me what the current flow of the Animas river through Durango, Colorado is.

There’s just no way to sort through data by hand this quickly.  Pipes makes it easy to aggregate information.  Now that’s web 3.0 for you.

By the way, here’s the PHP code I used to fetch the flow.  Feel free to throw this code into your own site to show the current flow. Go go yahoo pipes!

$response = file_get_contents('http://pipes.yahoo.com/pipes/pipe.run?_id=augM3IDI3RGi4U7B1L3fcQ&_render=php');
$phpobj = unserialize($response);
$cfs = $phpobj['value']['items']['0']['description'];