Krusader will be a useful program on Windows. We should package it and upload it to the KDE Community's account on the Microsoft Store.
Checklist:
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T9575 Publish more of KDE's applications in the Microsoft Store | ||
| Open | None | T9581 Publish Krusader in the Microsoft Store |
Thank you very much for all, Lydia, although as far as Krusader developers know, there is no Windows version of Krusader (contributions are very welcome :-)).
Hi Lydia and everyone else,
I have to admit I'm not up-to-date about the status of KDE software (Plasma OR applications based on the KDE framework) running on Windows. Is it somehow stable?
And when looking at https://phabricator.kde.org/tag/windows/ there is the plan to create Windows packages for all applications? Can I read up the background somewhere?
I know from the code fragments dating back to 2008 that there was some effort to support running Krusader on Windows. But I never heard that this was tested recently. Because Krusader is a file manager it is somewhat OS depending. Most is done using KIO, so it's a question of KIO supporting all file operations. But there is also direct Qt code we have for performance reasons. In short: I doubt everything will work "out of the box".
My concern now is this: If you put effort in creating a Windows package for Krusader and there will be bugs (I bet there will), there should be someone working on it. Unfortunately we already don't have enough developer time to solve the >100 open bugs currently open for Krusader. And support for Windows will come on top of that. I would like to avoid a half working Windows version which will never be "stable" and that the effort will be for nothing.
Other opinions?
Cheers, Alex
Regarding background: You might want to read the blog posts here: http://kfunk.org/tag/kde-windows/ -- specifically: http://kfunk.org/2016/06/18/kde-on-windows-update/
KIO has seen some testing on Windows and should work in theory, but still Krusader should be tested by someone before we are putting it out in the wild.
That's a fair concern. We don't want to release something and then not be able at all to support it. However have you thought about using this as an opportunity to recruit someone new? Maybe a blog post or mailing list post asking if there is someone with the will and knowledge to drive this forward?