@okennedy @purism https://source.puri.sm/guido.gunther/phosh/-/commits/next-tickets - you just dump everything into a `~/phosh-ticket-box` folder atm. A real "ticket" app needs to come next as we want more metadata attached so the widget can become more clever.

@agx @purism Cool... I'll have to play around with this when I get a chance.

@linmob @agx @purism I haven't had any luck getting KDE Itinerary to import certain types of tickets (e.g., Amtrak). It tries and fails to identify metadata in the file and then refuses to import the ticket. Nautilus + Evince continues to be my method of choice.

@okennedy @linmob @agx @purism You should report the issue upstream and provide the author with an example ticket that fails. In my experience they are very willing to fix such issues when they appear.

@bart @okennedy @agx @purism Like Bart wrote (from recent blog post about Itinerary, https://www.volkerkrause.eu/2022/06/04/kde-itinerary-april-may-2022.html): "Feedback and travel document samples are very much welcome, and there are plenty of other things that can be done without traveling as well."

@bart @linmob @agx @purism What's missing is the ability to import just a simple PDF. No metadata, no need for developers to update things when schemas, APIs, or ticket formats change. I'm happy to provide examples of past tickets, but the point is that these tools default to being clever, which inevitably leads to excluded edge cases. I like @agx 's approach better: default to the minimum functionality required (display a PDF on the lockscreen) and layer the clever features on top of that.

@okennedy That too is worth an issue 😉