Plugin Support?

[ashaikh]

Are you planning to allow plugins to extend functionality?

[julyx10]

Not at the moment, but I’m interested in this direction.

For Lap, I’d probably start with something lightweight first, like external tool/script integration for selected files, instead of a full plugin system right away.

A full plugin system sounds powerful, but it also brings a lot of complexity around stability, permissions, security, and version compatibility — especially because Lap works directly with local files and metadata.

Long term, I can imagine exposing controlled extension points, for example custom export actions, metadata processing, AI model providers, or batch workflows. But I’d want to design it carefully rather than adding a plugin API too early.

[OPGERUIMD97]

Are you planning to allow plugins to extend functionality?

Still wondering which type of plugin you mean? LR plugins?

[softyoda]

One example of such a plugin could be a special "type" (regex for example for some image, or metadata) that allow image to have a recto-verso, could be handy for example for scanned material with the epson-fastfoto that name img-a and img-b for respectively recto and verso, such feature would allow to see quickly all images without having the verso in grid view, while preserving the possibility to see it in plain view, an icon could also be present to inform the user it's a double-image (or another add-on for photo stacking like mentionned in this workflow).

As the app is open-source, it would also allow other app to reuse the database to expand metadata, one could perhaps envision a VR viewer there one scatter the images in a virtual environment, or anything else unrelated to lap but that interoperatively would allow such affordances !