chezyann custom title for pictures : "Largo Winch at the beach"
Files app already supports IPTC titles (titles stored inside images, created from apps like Lightroom or Photos).
The problem with custom titles stored separately in a data.json
file, is that it becomes very fragile. If someone renames an image or moves it into another dir, the title will be lost. This is why other gallery apps (CMS) take full control of the file system, and will control all file names and paths internally and control it virtually from a database ... Files app is passive, and simply uses users existing file structure.
This may very well be a future feature, but we are then entering CMS (content management territory). I actually have plans to create a "photo gallery" app (similar to Files app), but which will be more like a customizable website with CMS options which would have to be stored somewhere.
I could consider an option to edit titles directly into the image IPTC, but this is a bit clumsy technically.
chezyann multi user login : at least one simple user who can view and one power user who can upload/delete/rename. Ideally multiple simple users (for the next wished feature).
This is planned in a future release.
This can currently be resolved by setting up an additional Files app folder for "private" usage. Simply point the config root
to the same dir as the public version, and enable file manager options for the private installation.
chezyann user commenting : ability for users to comment/reply to pictures (informations could be stored in a subfolder of _files in txt or json files, or in a sqlite DB or inside pictures in EXIF data -- but it would be crap IMHO))
This feature basically has a similar answer as my first answer. It will never be elegant as long as the data stored for each image is dependent on file structure and file names never changing. Also for comments, unless you only allow for logged in users, you open up for all kinds of hackers, spammers and bots ... That's why I personally prefer to outsource comments to managed services like disqus.com, as on our www.files.gallery website.
chezyann ability to download : I would disallow personal pictures to be downloaded or directly accessed
You can already disable contextmenu
and enable prevent_right_click
, which essentially disables download options. Keep in mind, you can never block smart users from downloading images that load into your website, because anyone can just open browser > network inspector and see/download all images that load. That goes for any website.
chezyann ability to contribute with plugins : I've seen 2 files in _files/plugins, would it be possible for us to contribute ?
I'm not against it, but there are some challenges. As for the default plugins, they are PHP only, and it's not really a big problem adding custom PHP plugins. But 90% of the code in Files app is Javascript/CSS and you can't just build a PHP plugin that affects the interface. There are already advanced javascript config options.