On Thu, Jun 9, 2016 at 8:44 PM, Martin Klapetek <[email protected]> wrote: > there is some development by me going > into a new KDE/Qt/QML client called SpaceBar, which does not > have any public releases yet and is moreless built on top of > ktp-common-internals fork... > > with ... all the goodness of ktp-text-ui filters. > k-c-i basement means that it squashes all message parts, right? It prevents client from proper multimedia message support, because such messages should have alternatives ("multimedia" message part for advanced clients and text fallback part for others) and we can't cut the fallback text from final message even if we somehow extract its multimedia content.
As a proof of geo messages concept, I changed KTp::Message to have Tp::MessagePartList parts instead of QStringList parts and implemented filters/geopoint for ktp-text-ui. The filter looks for "application/geo+json" mime type in message parts and adds iframe with google maps (I had no luck with OSM) as textual representation for the part. KTP::Message::finalizedMessage() goes through parts and concatenates best possible alternatives. Actually, I realised that I should just used "geo:" URI as text alternative, but, despite of this overkill :), we definitely need all message parts in KTp to support modern messages with complex content. _______________________________________________ telepathy mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/telepathy
