https://bugs.kde.org/show_bug.cgi?id=443199
--- Comment #6 from Volker Krause <vkra...@kde.org> --- (In reply to Nicolas Fella from comment #5) > https://invent.kde.org/utilities/ktrip/-/issues/27 goes into a similar > direction. > > Perhaps we can use the calendar as an intermediate for exchanging data? Trip > connections should model well as calendar events and we can include more > metadata in custom fields, much like the existing calendar integration in > Itinerary Assuming Itinerary would have the ability to create a new reservation element from a KPT Journey, KTrip -> Itinerary integration should be fairly straightforward, via KPT's JSON serialization. Whether we then send this through the calendar, the clipboard, an Intent or ApplicationLauncherJob is secondary I think, as Itinerary routes all that through the same unified importing code anyway. Itinerary -> KTrip should be even easier, as Itinerary already holds KPT Location and/or Journey objects for basically everything in the timeline, so this is mainly a matter of defining use-cases where we'd want that. With KPT gaining support for individual transport and inter-modal routing we also should discuss integration regarding that, e.g. for sharing user preferences (has a bike, can drive a car, etc) and for state (where did I park my bike/car on the way out so we route back there on the return journey). But that's getting off-topic here... Independent of that, I do agree that we should expand the calendar integration :) -- You are receiving this mail because: You are watching all bug changes.
