Skip to main content
areohbee
areohbee
Legend
April 11, 2011
Open for Voting

P: Integrate Library & Develop Modules

  • April 11, 2011
  • 18 replies
  • 683 views

The idea is to eliminate mode-dependent keystrokes and menus; make the library filter available whilst developing; be able to select the next photo for development from a folder or a thumbnail grid, instead of a one-line filmstrip or a collection; make the before-after comparison available while reviewing in the "library"; have the clipping indicators be available for quick-develop; be able to view photo-info/metadata in mid-develop; be able to do relative adjustments (quick develop) or absolute while developing; ...etc...; and last but certainly not least: eliminate mode-switching/re-rendering lag.

Many people have preconceived notions of what this integration would entail. Some assume the contents of the develop panels would just be dumped in with the library panels. But, there are many other possibilities.

Summary, by way of example:
-------------------------------------
If Adobe could find a way to change:

"Lets see, I'm in the Library Mode, so '\' will do the filters, not the before-after view...", and
"I want to make relative adjustments in bulk, so I need to switch to library module", ...
"and now that I want to develop again, I have to wait 'X' seconds for a re-rendering..."

To:
'\' is for lib filters, '/' is for before-after.
Click 'Relative' for relative adjustments, click again for absolute.
No waiting anymore for mode switching / re-rendering...

Many of us would be grateful...

PS - If the ACR caching were more effective, the smaller switching lag would be more bearable, but that's only part of the problem...

Rob

    18 replies

    Steve Gandy
    Steve Gandy
    Inspiring
    April 13, 2020
    Overstated for you. Not me.
    Steve GandyPhotographer - Instructorstevegandy.com
    Steve Gandy
    Steve Gandy
    Inspiring
    April 13, 2020
    Overstated for you. Not me.
    Steve GandyPhotographer - Instructorstevegandy.com
    J
    juw177
    Participating Frequently
    February 15, 2013
    There is no good reason why they have to be separate other than "just because that was how it was designed in the beginning".

    I must switch to library to
    - go through individual pictures (because it is faster than doing it in Develop)
    - browse pictures in a grid
    - comparing 2 pictures
    - bulk develop

    I must switch to devlop to
    - develop photo
    - check adjustment history

    Not to mention all the money Adobe is spending to maintain 2 different code bases with similar functions.

    F
    FeedbackCommunityMember
    Inspiring
    February 15, 2013
    I spend about 30% of my time in the Library Module and 60% in Develop (10% for everything else). However, I could do 90% of my real work in the Develop Module alone if the Library were somehow merged with this module. I spend plenty of time going back and forth between the two.

    With that in mind, here's the idea that I would like to open for discussion & debate:

    • Merge the Library's "grid view" (which is quite handy) into the Develop Module and do away with Library Module completely.

    • Add a tool menu to the Develop Module for the tasks that are currently taking place in the Library Module (e.g. keywording).

    • When you double-click an image in the grid view, that image enlarges to facilitate detailed developing work (same as the current Develop Module). The filmstrip at the bottom would become visible during this time.

    • However, if you select multiple images (Ctrl+Click) from the grid, you can perform modifications to all of those images simultaneously.

    This is easy for me to suggest since I know absolutely NOTHING about writing software. What do the rest of you think?

    areohbee
    areohbeeAuthor
    Legend
    June 2, 2011
    If you like this idea and you haven't already done so, please add your vote by clicking the '+1' button at top of page (lots of people don't know to do this).
    areohbee
    areohbeeAuthor
    Legend
    June 2, 2011
    If you haven't already done so, please add your vote by clicking the '+1' button at top of page (lots of people don't know to do this).
    areohbee
    areohbeeAuthor
    Legend
    June 2, 2011
    If you haven't already done so, please add your vote by clicking the '+1' button at top of page (lots of people don't know to do this).
    H
    hsbn
    Participating Frequently
    June 2, 2011
    I love this idea. I don't use Web, Print or Slideshow modules. It would be much faster for me to work in one module then switching from one to another.
    U
    uvagris
    Participating Frequently
    April 22, 2011
    Coming from Apple's aperture I can only support the idea of merging the modules. I like lightroom better than aperture for many reasons but miss the possibility to do it all in one place.
    F
    FeedbackCommunityMember
    Inspiring
    April 12, 2011
    Thank you for starting this idea. I generally agree with the reasons given by members above. I especially like Lee Jay's solution. It's elegant and fits into LR's existing reasoning. I am pretty confident that they ~have~ to do something like. Quick Develop already has so much of the Develop Module, just in a dumbed down way, and Develop Module already has Collections just not folders.

    My preference though would be a truly creative reinvention of the GUI. Don't let Apple be the one to do it again.
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices