Trippy doesn't take into account the time it takes to travel between the different items

Tell us what application you are using on what platform. (e.g., Wave Trippy
app, iGoogle Trippy app, Android Trippy app, Rucksack Wave app).

iGoogle Trippy app

What steps will reproduce the problem?

Because I was actually planning a trip I decided to see if it could be done 
better with trippy. I entered the information that I already had (which was 
very easy) but then discovered Trippy doesn't take into account, or lets you 
schedule, the time it takes to get from the various items in the itinerary. For 
me this makes the application useless, as the travel time is the key part of 
all trip planning.

What is the expected output? What do you see instead?

I'd expect items that cover a block of time needed to get from the particular 
location to the other location. I expect these blocks to change if I change the 
order of the items. I expect Trippy to know where I am at a certain point 
during the travel time (to be able to schedule a bar, restaurant or hotel at 
that particular point).

What browser and operating system are you using? If you can provide version
numbers, we would appreciate it -- they help a lot.

Using Chrome 5.0.375.86 beta on linux 2.6.24-gg804011-generic x86_64.

Please provide any additional information below.

To give an example why travel time is so important: I once went with my parents 
and sister to Rome. There we saw about ten things a day, guided by my father, 
who knew exactly how to schedule items. After my parents went back and I was 
still there with my sister, we tried to see lots of things as well, but 
discovered that it was hard to see more than two things a day because of the 
time it took to get around.

Original issue reported on code.google.com by mhof...@google.com on 1 Jul 2010 at 10:06

surendarhub / gulliver

Trippy doesn't take into account the time it takes to travel between the different items #270