mat2 issueshttps://0xacab.org/jvoisin/mat2/-/issues2018-08-03T20:25:18Zhttps://0xacab.org/jvoisin/mat2/-/issues/2Create a Nautilus extension2018-08-03T20:25:18ZjvoisinCreate a Nautilus extensionSince I'm too lazy, know far too little about UX to implement #3, most of the userbase is using GNOME because of Tails/Debian, the plan is to write a small, nice, well-integrated and usable Nautilus extension instead.
# Design
- [x] Re...Since I'm too lazy, know far too little about UX to implement #3, most of the userbase is using GNOME because of Tails/Debian, the plan is to write a small, nice, well-integrated and usable Nautilus extension instead.
# Design
- [x] Read the [GNOME Human Interface Guidelines]( https://developer.gnome.org/hig/stable/ )
- [x] Especially the [Design patterns]( https://developer.gnome.org/hig/stable/patterns.html.en ) part
- [x] Decide how we want to display failures to the user
- ~~With an [app notification]( https://developer.gnome.org/hig/stable/in-app-notifications.html.en )?~~
- With an [infobar]( https://developer.gnome.org/hig/stable/info-bars.html.en )
- Show a button in the ~~app-notification/~~infobar to allow the user to spawn a popup with a [list view]( https://developer.gnome.org/hig/stable/lists.html.en ) in it, detailing why the files couldn't be successfully processed
- [x] Decide if we want to allow multiple-selection
- Yes we do, because it's convenient for pictures gallery
- [x] Decide if we want to allow users to select a folder
- Yes we do, but this implies that we do need a way to display a _massive amount_ of processing failure, since users will likely do *interesting things* like trying to clean `/` or `/dev`.
- [x] Find a way to display failed cleaning, even for a big number of files
- [x] Find a way to convey why the cleaning process failed.
# Implementation
- [x] Display a progress bar, since cleaning can take quite some time. Maybe something like [this]( https://i.stack.imgur.com/q6bE3.png )
- [x] Thread the cleaning process
- [x] Find a way to put the extension in the testsuite. This is important because I'm not using Nautilus at all, but most of the userbase is/will.
- This is going to be *fun*, because there is [no documentation]( https://github.com/GNOME/nautilus-python ) on how to do this.
# Packaging
- [ ] Find a way to package the extension in Debian
- Currently, the required version ([1.2.](https://github.com/GNOME/nautilus-python/releases/tag/NAUTILUS_PYTHON_1_2_0)) of `nautilus-python` isn't packaged in Debian.
- I don't want to put a hard-dependency on GNOME nor on Nautilus
# Misc
- [ ] Find some ~~guinea pigs~~ volunteers (\*wink* \*wink\* @sajolida \*wink\* \*wink\* @emmapeel) to test the usability of the chosen implementation. 0.3.0 - Pigjvoisinjvoisin