Lightroom: make app preferences available to plugins

  • 3
  • Idea
  • Updated 6 years ago
  • (Edited)
Consider making preferences available to plugins. I don't mean plugin preferences, I mean user preferences, like setting for auto-write xmp...


L i g h t r o o m S D K : a c c e s s t o p r e f e r e n c e s

(without the spaces) is considered profane as topic title. Riddle me why?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes

Posted 6 years ago

  • 3
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
Oh my. I do not like this idea, one bit. It is bad enough that plugins can update the schema (at least just part of it.) But I do not want a plugin anywhere near my preferences.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes
Plugins can not alter your schema, one bit, except for custom metadata, the schema of which the plugin defined in the first place, and which the plugin must be responsible for maintaining as time goes on - assuming of course that the user will be upgrading the plugin, since if they don't - none of this will ever come into play anyway.
Photo of Dorin Nicolaescu-Musteață

Dorin Nicolaescu-Musteață, Champion

  • 703 Posts
  • 38 Reply Likes
Yes... I mean, no, they can't alter the schema. Just add records to a dictionary of custom metadata.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 386 Reply Likes
Read, *not* write. (or, if write too, maybe a mandatory Lr-enforced dialog box warning or something).

PS - Plugins can already read most of your preferences, or should I say:

what they were when you started Lightroom, excluding catalog settings.

What they can't do is:

* be sure the values they read haven't been changed since startup.
* read catalog settings - which have some of the more important ones.

Even if Adobe chose to support a subset of those I've previously mentioned here and there, it'd be a step in the right direction, although I'd prefer all of them.

Photo of John R. Ellis

John R. Ellis, Champion

  • 4058 Posts
  • 1069 Reply Likes
Being able to read current preferences and catalog settings makes perfect sense.

I don't have a strong use case for plugins modifying preferences, but it wouldn't add appreciably to the destructive capabilities of ill-mannered plugins. They can already wreak quite a bit of havoc: create keywords and add them to photos; change much metadata; create, change, and delete collections; move, delete, and overwrite the actual photo files; run arbitrary programs, silently; communicate silently with the outside world.