Bug 82769 - Use eventlocation for travel-planning
Summary: Use eventlocation for travel-planning
Status: RESOLVED DUPLICATE of bug 91974
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-03 13:59 UTC by Andreas Bayer
Modified: 2020-06-06 03:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Bayer 2004-06-03 13:59:09 UTC
Version:            (using KDE KDE 3.2.2)
Installed from:    Debian testing/unstable Packages

What about using the eventslocation for routing-planing-tools like gpsdrive or for websites like www.bahn.de (a site where you can plan your travel by train). So if i could do so, it would be more easy to plan how much time i have do calculate for traveling to the event.
Comment 1 Brian Chabot 2006-01-31 07:50:02 UTC
I'd like to second this wish....

A bit more detail as to how I would envision it:

You make an appointment (or ToDo?) and attach a location to it, perhaps as an addressbook entry or such.  In the appointment edit dialog, would be a box/dropdown with your last appointment location, home, work, or addressbook entry or a manual entry to designate where you will be before this and where this will take place.  When you save/apply it would use one of the online tools as above or Google maps, Yahoo maps, or similar to find the approximate travel time (and attach a link to the directions).  

Ok, that's a lot of work.

A much more simple solution would be to allow a manual entry of travel/prep time which would show in a different color.  You don't always need directions and you can already attach a URL...
Comment 2 Reinhold Kainhofer 2006-11-02 18:53:57 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 3 gjditchfield 2020-06-06 03:30:35 UTC

*** This bug has been marked as a duplicate of bug 91974 ***