Change Details

Currently KIO is not functioning on Android. There is an Android build of Koko, but it isn't functional since it uses KIO. @camiloh is also interested in using KIO in his Android apps. Obviously the klauncher based codepath won't work on Android, but I think (a variant of) the slave forking codepath could be made working. This requires to bundle the kioslave executable in the APK and execute it. While possible in theory I wasn't able to have a working KIO on Android yet. If running an executable turns out infeasible we could also think about doing it in-process in a separate thread.

(not strictly related to Frameworks 6, but this seems like a good point in time to discuss it) Currently KIO is not functioning on Android. There is an Android build of Koko, but it isn't functional since it uses KIO. @camiloh is also interested in using KIO in his Android apps. Obviously the klauncher based codepath won't work on Android, but I think (a variant of) the slave forking codepath could be made working. This requires to bundle the kioslave executable in the APK and execute it. While possible in theory I wasn't able to have a working KIO on Android yet. If running an executable turns out infeasible we could also think about doing it in-process in a separate thread.

(not strictly related to Frameworks 6, but this seems like a good point in time to discuss it) Currently KIO is not functioning on Android. There is an Android build of Koko, but it isn't functional since it uses KIO. @camiloh is also interested in using KIO in his Android apps. Obviously the klauncher based codepath won't work on Android, but I think (a variant of) the slave forking codepath could be made working. This requires to bundle the kioslave executable in the APK and execute it. While possible in theory I wasn't able to have a working KIO on Android yet. If running an executable turns out infeasible we could also think about doing it in-process in a separate thread.