darktable-org / darktable-org/darktable
Separate the export and multi-preset export modules
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.1k
- Forks
- 1.4k
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 198
Description
Is your feature request related to a problem? Please describe.
The export module is overly complicated in my opinion and takes up too much of the screen. It is filled with options that are often set once and considered the defaults for my workflows.
Describe the solution you'd like
I'd like to set up export presets I the export module and then hide it away. But be able to have a seperate multi-preset export module that is identical to that component in the export module so that this is all that I see.
Alternatives
I can't see an alternate way to regain the screen space and access the small section of the module that I need.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the existing export module and its multi-preset export functionality in the darktable source, then determine how they can be separated while preserving the requested preset behavior. Done means users can configure presets in the export module and access an equivalent multi-preset export module independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100