GSoC/2019/StatusReports/Feverfew: Difference between revisions
(Created page with "== Project Overview: Polishing KIOFuse == KIOSlaves are a powerful feature within the KIO framework, allowing KIO-aware applications such as Dolphin to interact with services...") |
Fabian Vogt (talk | contribs) (Make link to GitLab more direct) |
||
| Line 24: | Line 24: | ||
translation of KIO URLs to their local path equivalents. | translation of KIO URLs to their local path equivalents. | ||
== Commits == | == Commits == | ||
Our development workflow is that I have a fork of the KIOFuse repo, and changes are done on branches. When the branch is ready to be reviewed a merge request is opened upstream.. All my merge requests can be found [https://gitlab.com/Vogtinator/kio-fuse/merge_requests here]. | Our development workflow is that I have a fork of the KIOFuse repo, and changes are done on branches. When the branch is ready to be reviewed a merge request is opened upstream.. All my merge requests can be found [https://gitlab.com/Vogtinator/kio-fuse/merge_requests?state=all&author_username=feverfew here]. | ||
== Blog == | == Blog == | ||
Revision as of 07:09, 27 June 2019
Project Overview: Polishing KIOFuse
KIOSlaves are a powerful feature within the KIO framework, allowing KIO-aware applications such as Dolphin to interact with services out of the local filesystem over URLs such as fish:// and gdrive:/. However, KIO-unaware applications are unable to interact seamlessly with KIO Slaves. For example, editing a file in gdrive:/ in LibreOffice will not save changes to your Google Drive. One potential solution is to make use of FUSE, which is an interface provided by the Linux kernel, which allows userspace processes to provide a filesystem which can be mounted and accessed by regular applications. KIOFuse is a project by Fabian Vogt that allows the possibility to mount KIO filesystems in the local system; therefore exposing them to POSIX-compliant applications such as Firefox and LibreOffice. KIOFuse is a feature that has been requested many times before, case in point this very active 15 year-old bugzilla bug report and several reddit threads (1, 2, 3, 4).
Project Goals
This project intends to polish KIOFuse such that it is ready to be a KDE project. In particular, I’ll be focusing on the following four broad goals:
• Improving compatibility with KDE and non-KDE applications by extending and improving supported filesystem operations.
• Improving KIO Slave support.
• Performance and usability improvements.
• Adding a KDE Daemon module to allow the management of KIOFuse mounts and the translation of KIO URLs to their local path equivalents.
Commits
Our development workflow is that I have a fork of the KIOFuse repo, and changes are done on branches. When the branch is ready to be reviewed a merge request is opened upstream.. All my merge requests can be found here.
Blog
I also have a blog which gives more details about the technical challenges that I have faced (and hopefully solved) in the project. The blog can be found here.
Done
• Map KIO job errors to fuse_reply_err Merged
• Install own signal handlers In Review
• Change of password support In Review
• 32 bit support In Review
• Disable writeback caching In Review
• Fix broken links kdeconnect - fixed upstream.
• Deal with slaves that don't support stat - it was decided that would be too much hassle for little gain. Slaves that don't support stat cannot be mounted.
To Do
• Deal with invalid size reporting slaves (http/gdrive).
• Kill KIO::put job if the cache got written to.
• Refresh attributes of files/dirs and children of dirs after a while
• Verify that write access works before writing into the cache
• Look into using KIO::read/KIO::write if possible
• Implement KDED module to manage KIO-Fuse mounts. Provide a service to convert KIO URLs to local path for KIO-unaware applications.
About Me
Name: Alexander Saoutkin
Mentors: Fabian Vogt, Chinmoy
Github: github.com/feverfew
IRC: feverfew (#kde-fm freenode)