Future of KDE Connect

[Michael Tiernan]

Knowing that this isn't the best forum for it I'll apologize if it is 
too far out of the remit for this list. I offer these thoughts in the 
hopes of sharing and fostering new/ideas/features.
No expectations, just trying to be helpful.

 1. A "suggestion" (or random neurons having a drunken tango lesson)
    would be that there may be an opportunity to split the design so
    that the "front" is separated from the middle "do the 'action'"
    separate from the "back" or transport part of the process which may
    allow or encourage others to expand from direct connect to maybe
    include indirect connect across non local networks.
 2. A grumble I've always had but never formalized (until now) is that I
    think it would be helpful if the settings could be saved in a
    transportable format (XML/yaml/json/etc.) to then load on another
    machine. Separating the "kde connect" part from the "actions" would
    help.
 3. Someone out there must be clever enough to figure out how to create
    a reasonably consistent interface for it that permits something like
    a CLI action for some things.
 4. As part of all that, *maybe* it would be an option to permit queuing
    messages/commands/responses between connections.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20260106/bcc4ec18/attachment.htm>