You can make them bigger through some CSS tweaks: https://docs.darktable.org/usermanual/development/en/prefere...
I reported this issue on irc years ago and the dev response was so hostile I abandoned trying to use it and never looked back. I pay Adobe $500/year for software that had been tested by users with developers silently watching.
People have a finite slice of their life to give you for nothing. Putting specific suggestions on the issue tracker seems more respectful of their time.
Attention and stewardship are not universal.
1. "This one issue is what is stopping me from using this product. Is this current method preferred by your users or do you have any other reason to not want to change?"
2. "The proprietary solution costs $X per month. Is there any way to sponsor development? I am willing to give $X/n (where n is whatever number you are comfortable with) per month to get this issue merged and to have some sort of prioritization when triaging issues.
3. Failing those: write a blog post and propose a fork. This is usually the quickest way to get a reaction from narcissistic developers.
Depends on the PR. Bugfixes sure, but new features mean more work for the maintianer in the future.
Speaking as a project maintainer that is starting to see some traction: I'd love to see people coming with PRs for features. It would mean a big amount of validation.
I bought a Mac and use Lightroom and I’m happy to give them both my money.
I'm sorry you did not stumble into them, but instead in the few hostile ones. It's a pity that made you give up.
A general tip, I give to people wishing to contribute to OSS is to first watch from the sideline. Read issues, threads, subscribe to an ML etc. Then to ask. Don't just throw in PR or feature request, but ask: is this welcome? How do you work? Any particular details that you wish me to pay extra attention to (tabs, spaces, tests, documentation, design).
As a FLOSS maintainer myself, it can be very intimidating to have someone throw a PR at you that rewrites everything (it comes across as: you suck, your software sucks, but watch me fix all that), or that disregards things that I deem critical (tests, architecture) It is really hard to review it, without coming across as an arrogant bastard. And often software that I put on a back burner will require me significant effort to get back into. So merging a simple typo fix or dependency update might cost half a day, just to get the dev env back up.
Hey dudes, there's a pointer dereferencing crash here which occurs when I do X, Y then Z. Added one line change to fix it. SILENCE.
There are no test cases for most projects either.
My dad used to be a pro photographer, now retired, and gave me crash course in RAW processing. Besides some handling differences between lightroom and photoshop he nothing negative to say about darktable. And neither do I, it's not darktables fault that my photo library is a mess.
Making perfect AppImages is often possible, but the automated tooling isn't smart enough. A proper AppImage (this one is by me) look like this: https://github.com/Elv13/reclaimail/blob/master/docker-edito... . Obviously this doesn't scale very well to projects with 300 dependencies like Digikam. My NeoVIM appimage linked above "really, really" bundles all dependency and compile your NeoVIM config to luajit bytecode. It's 3.9mb compared to the upstream one which is 15mb without any config. Note than 0.7mb of that 3.9 is the spellcheck dictionary, 0.4 my enormous config, 0.5 the AppImage overhead and 0.7 all the legacy plugins still written in vimscript.
[0] https://packages.ubuntu.com/search?keywords=digikam
In clicking around, I've selected "add to library," and darktable is now beachballed. CaptureOne will continue to be my default.
(Before someone points this out, let me acknowledge that the apparent problems with darktable are undoubtedly my fault in some capacity and that I'm Using It Wrong, or that I can't properly read the manual, or that I should watch more videos on how to use darktable.)
>I'm also glad it exists but have never figured out how to use it on MacOS
* Open app, Select 'Add to Library' --> spinning beachball of doom
delete the ~/.config/darktable directory, to give me a clean start...
* Open app. App opens in a weird window the full width of my screen but only half the depth. I try to resize the window. It won't rezise, even though I get resize arrows when hovering over the corner. Finally manage to make it usable by hitting the fullscreen widget.
* Try 'Add to Library' again. This time it allows me to select my photos archive folder. I see there's a tickbox marked 'Recursive' so I click on that as I have subfolders in my photos archive. I can't select the box. Then the spinning beachball of doom starts again...
* Force quit
* Delete app.
Life's just too short to mess about with an app that hangs twice, requiring a force quit, before I've even managed to do a single thing with it.
This is the correct answer. I actually switched to Linux from macOS partly to be able to run darktable in a more native setting.
We're not talking non-MacOS [or non-Windows?] -like behaviour here. But the app not actually functioning. So why offer versions for other OSes, if it's Linux only software?
Here's a little list of the problems Pace can cause:
http://web.archive.org/web/20071009193327/http://www.paceap....
One contains your custom configurations like presets, the other contains info about file locations, ratings, film rolls, etc.
Deleting and reimport takes time when a lot of files are involved, but is my preferred way of handling the changes of large scale file operations.
But film rolls might not be the best way to manage files.
After six years, I found searching the database using tags and Exif data such as camera and date ranges with the collection tool works better for me.
What also helps me is never deleting or moving an image file.
That way the database stays current and I avoid the busy work of file and folder manager.
To put it another way, for me flat search is better than hierarchy navigation.
I've switched back and forth between RawTherapee and darktable for a few years now.
I prefer the UI and workflow or RT, but dt has better performance on my machine. And RT has this strange longstanding bug where the image is extremely blurry during editing, and only becomes clear after exporting. According to a github issue, a workaround is to disable lens correction (and anything else in the "transform" tab) but this didn't work for me, prompting my most recent switch to dt.
current biggest grip with dt... why are those damn arrows at the edges of the screen so tiny??? Expanding and retracting the side panels requires pixel-perfect accuracy on a ~20px target. I know I could use keyboard shortcuts, but my brain isn't wired for them yet.