[Suggestion]: delete file while viewing / playing

[knguyen0105]

At the moment, the software only support viewing images/videos. Sometimes I only need to keep a few images or videos in a whole downloaded albums / collections to save space on my server.

I'd love to be able to delete an image / video (or a folder) while browsing.

[bpatrik]

Hi,

Thank you for the suggestion. The aim of this app is to provide a directory-first photo gallery website (i.e., the phosoes should be rendered as they are, without modification). I would like to keep this approach.
Unfortunately deleting photos does not fit into this approach, so I do not plan to add such a feature. Sorry.

Best,
Patrik

[bpatrik]

I'm closing this due to inactivity

[flesser]

I really like the read-only and directory-first approach of PiGallery2, which is what makes it much better suited for light-weight installations than e.g. Lychee (which seems to use its own cryptic directory structure, making it hard to work with the images from outside the app).

My personal use case for PiGallery2 is an installation on a Raspi Zero W, which I use to backup my Camera's SD card while travelling (and syncing them back home to my Nextcloud server whenever there's free Wifi available).
With PiGallery2, I can comfortably watch the pictures from the Pi's SD card in my smartphone browser.

However, I also would like some option to delete photos before syncing.

One solution I could imagine -- while keeping PiGallery2's read-only approach -- would be to support flagging Images for deletion only in PiGallery2's database. Or more generally: allow some kind of tagging/flagging (#38).

Another script in the background (not part of PiGallery2) could then access the database and e.g. delete all images that are tagged/flagged in a certain way.

In that way, PiGallery2 core could keep its approach of not altering the images themselves while still allowing more advanced (admin) users to have some kind of image deletion/altering/whatevering options based on user input from the browser.

[bpatrik]

Hi
In the (distant) future I'll probably make some plug-in feature to the app that would allow adding small features without touching the core of the app. I can see such a deletion feature possible then.
Currently I would not like to add such a feature to the app, as it is not in alignment with the main 'vision' of the app.

Also, it is an open source project, feel free to alter for your taste :)

[flesser]

Here's my Work in Progress (and mostly quick&dirty) fork with support for trashing images/videos while playing, similar to what the OP @knguyen0105 asked for:
https://github.com/flesser/pigallery2/tree/trashsupport

Basically, once you enable the feature in config.json (Client.Trash.enabled), it shows an additional "Trash" button in the Lightbox (also listening to the Del key).

Trashing files is implemented server-side by moving them into a new subdirectory (Client.Trash.trashFolderName, defaults to _pigallery2_trash) inside each album, which can then be deleted manually on the server. (No Gui support for that yet).

Images can be restored by "trashing" them from the trash folder. In that case, they just get moved back one dir up into the original album.

It's all not really field-tested yet, use at your own risk!

[bpatrik]

Hi.

Thank you!
As I mentioned, I don't feel this to be in the path of the app, but I'll keep this in mind, when I prepare the plug-in method for the app.

Patrik

[palitu]

I think that this is something that i would like. I'll tell you how i use PIG.

I dump ALL myp hotos into {YEAR} / {xx MONTH} directories. It is from my camera, or our phones. It doesn't matter. They all go into those folders. From there, i use DigiKam to add tags/captions to the photos.

This allows me to generate "logical albums" using tags (which PIG does a good job of displaying) as well as view all the photos that have been taken by the month.

There is a lot of crap in my bulk uploads, and it would be good to be able to delete them where ever i am, whether i am using DigiKam, or on the net at work. Same goes for adding tags to photos.

I would love a limited set of functionality that would allow me to edit the files via PIG. Also a list of tags from the DB would be awesome too!

[jezikk82]

Any change that the delete function will be implemented ? (even @flesser approach is enough).
PiGallery is running on mobile Rpi. I have similar use case that all my pic from DSLR and phones are auto sync to "yy.mm.dd - event" structure and for first, quick preview I use pigallery. On bigger screen (often TV in hotel) I'd like to be able to remove bad shots.

[bpatrik]

No really. I was thinking about putting this to some kind of addon, but the more I think of that the less I see the solution for creating addons.

Generally I do not want so see any gallery modifying feature on my personal instance. Making #310 would it make possible to separate it.
Not sure if I will have time for this in the near future.

I updated the README.md to reflect this state of the app.

[bpatrik]

Closing this as it goes against he current philosophy of the app:
😥 Its simple. Shows what you have that's it. No gallery changes (photo delete, rotate, enhance, tag, organize, etc), your gallery folder is read-only.

[pepa65]

Here's my Work in Progress (and mostly quick&dirty) fork with support for trashing images/videos while playing, similar to what the OP @knguyen0105 asked for: https://github.com/flesser/pigallery2/tree/trashsupport

Basically, once you enable the feature in config.json (Client.Trash.enabled), it shows an additional "Trash" button in the Lightbox (also listening to the Del key).

Trashing files is implemented server-side by moving them into a new subdirectory (Client.Trash.trashFolderName, defaults to _pigallery2_trash) inside each album, which can then be deleted manually on the server. (No Gui support for that yet).

Images can be restored by "trashing" them from the trash folder. In that case, they just get moved back one dir up into the original album.

It's all not really field-tested yet, use at your own risk!

Does this still work 4.5 years later?!?

Edit: Just checked it out, the file structure seems to have changed too much...