LIGHTROOM develop module - Pointless modularity???

  • 1
  • Question
  • Updated 3 years ago
  • (Edited)
Lightroom's Develop module. I fail to see the point of it. What does the separation of process achieve? If I want to "develop" an image, there's a single keystroke (D) shortcut sitting between me and the Develop module. This seems so ridiculously arbitrary. Why not just be able to develop any image in the gallery where it is without moving to a module? How does moving the file to another module help my workflow?

Please help me understand.
Photo of Chris Oaten

Chris Oaten

  • 18 Posts
  • 7 Reply Likes

Posted 3 years ago

  • 1
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2586 Posts
  • 323 Reply Likes
From what I understand the Library mode is optimized for limited operations on multiple images, and the Develop module is optimized for many operations on a single image. This division is both for computer resources and UI elements.

How would a proposed combined Library/Develop module work? Do you see the lefthand panel a combination of Folders and History among other things and the righthand panel having a combination of Metadata and Settings adjustments--basically each is taller than it was before, so scrolling up and down replaces module switching, or are you imagining some changing view of panel contents based on whether you're in Grid view or Loupe view? Or what specifically does "develop any image in the gallery" mean in practical terms of the visibility of user-interface elements?

And another line of questioning would be what irks you about the current multi-image vs single-image division of UI, is it the lack of metadata/settings combined into one panel so all you have to do with scroll up or down, or is it the time and visual disruption when you go back and forth?

And how fast does LR run on your computer? Would you consider it fast or slow or somewhere in between?
Photo of Chris Oaten

Chris Oaten

  • 18 Posts
  • 7 Reply Likes
Having a left/right placement of clustered toolsets would work just fine. I like that idea. Spot on.

I suppose my issue is with usability, as in having to think of being "in" and "out" of the Develop module. Frustrates me no end.

As for visibility of panels, there doesn't need to be any association with them being "taller" but "tailored". Conditional in some way according to your activity, similar to the way you can easily swap layout views in Photoshop according to your activity. I'd prefer to invoke a certain set of tools in a particular layout suited to a particular task and be able to arrange panels/palettes and save and load them at will rather than being boxed into a working method that sits within the constraints of how programmers have decided I should use the software.

But having to isolate toolsets by swapping modules? It feels inefficient.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2586 Posts
  • 323 Reply Likes
So instead of 2 toolsets, one Library one Develop, you want an arbitrary number of toolsets, and have to be "in" the right one to have the set of functions you want?