A meta-project which contains all tasks and repositories related to packaging and releasing KDE software in desktop versions of Windows.
Sat, Dec 8
I think that dbus might have been fixed on windows. kdeconnect-cli seems to start dbus/kdeconnectd automatically for me, and even reverting/commenting out the patch referenced in the above description in kdeconnect-indicator seems to make kdeconnectd and dbus autolaunch.
Fri, Dec 7
Mon, Dec 3
Reassigning to Windows/Craft project
Tue, Nov 20
Done Android change here: https://commits.kde.org/kdeconnect-android/df0d02cd0d1f66e738d4072135a0baf657e86c19
Mon, Nov 19
Can you do the Android side? Since you have commit access you can just commit directly. I'm too lazy to clone the repo and create a diff for a one word change.
I have a couple minor comments, but looks good to me. It would be nice to implement a really simple MPRIS plugin for Windows now (even if only sending multimedia key inputs), so this can be used form the Android app :P
Is this what we want? https://docs.microsoft.com/en-us/uwp/api/windows.media.systemmediatransportcontrols
I tested this for a little bit and it seems to work pretty well.
Sun, Nov 18
- Improved Error Checking
Fixed some stuff
Fri, Nov 16
Nov 8 2018
@jambon I agree that the user can just invoke other shells but the user would probably find it easier to use if he knows what the default is, displaying it somewhere in the user interface would probably make it easier to use.
Merged, but arcanist (the command line tool for Phabricator) gave me some problems because it looks like you cloned the repo from Github. It will work better if you clone it from https://anongit.kde.org/kdeconnect-kde.git
Powershell is slow to start, especially on older computers. So if people just want to run a simple command, it'll create unessasary delay. If people really want to run powershell, they could just put powershell -c <command> in their command
Would powershell be a better default, though? I don't think you can do much with cmd, actually.
Sorry, I accidentally swapped -c and /c.
@shivanshukantprasad If the user wants to run commands on other shells. They could just invoke the shells themselves.
You should explicitly tell the user somewhere on the interface that cmd is being used to run the commands, since windows has many shells with entirely different syntax.
Maybe we can provide an option to select the shell. Basically an input box to fill the value of COMMAND and ARGS variable in the above code.
Thanks for the patch!
Nov 7 2018
Nov 6 2018
Unfortunately there is no standard way to control media players on Windows. There is a standard API for media players(ISystemMediaTransportControls) but there's no way to query it since it's per app. I think simulating VK_MEDIA key presses maybe our only option.
cmd /C command-goes-here can be used to run command line commands on windows.
An C++ api is mentioned in this stack overflow question.
Windows contains several shells like cmd, powershell and wsl, so we may need to handle that.