@KristijanZic I think you are thinking of the lua scripts installer, which is there but it has a bug and will not run.
darktable can be compiled to use the included internal version of lua, so it doesn’t require an external interpreter. However, in order to actually install the scripts, git is required so the flatpak packager would need to package it too.
I suppose you’re right. I was referring to the GUI of the script manager (idk much beyond that).
So you are saying that the manager uses git to fetch scripts but the lua is already present in the Flatpak? (I’m assuming he compiled it that way because it seems logical (to me at least)).
I would like to push this forward but my knowledge about Flatpak and Lua is little to none so if you would be so kind as to maybe structure a bit better bug report to the Darktable Flatpak GitHub repo.
I think that might be very helpful to the developer as I just opened one saying that the script manager/installer is missing (in the gui) which is not very helpful
Let’s enable multilingual support to the script manager, first.
It should be easy to change the English only variable to another language. Adding Localization is not the biggest issue for myself at least.
Anyway, bank to the problem, I can’t see any new entry in preferences to activate the script manager, with or without luarc in:
home/.config/darktable/
And having English or German set as interface language
The script manager didn’t load after installing 3.2.1, I got just the dialog to refresh my database.
Fundamental question, why is the script manager not added by default to the list of modules?
Is there some line to edit in darktablerc to get the script manager working?
I set my DT interface from German to English, re-installed your Lua scripts from git, deleted all the content of luarc and added only require "tools/script_manager"
and got it working.
Still, now I’m looking for the right variable to change “English” to “German” but can’t find it in script manager nor the libs it calls.
@Karsten, please try the following for me and let me know what happens. Change current_view().name to current_view().id and the string back to lighttable and let me know if that works. I’m hoping name is translated and id is not.
Awesome, it works greatly, “id” was the key
Pretty hard to guess such a detail, as Id and name are very generic and rather hard to associate to a full localization switch.
Then again, I think this will an unsolvable issue. I enabled the HDRMerge script and configured it to use the HDRMerge appimage but since appimages require FUSE to run, I get the “HDRMerge failed” every time because the Flatpak can’t run the appimage. On the other hand .deb darktable has no problem with it.
I was very happy and enthusiastic when Flatpak, Snap and Appimage came on the scene but I’m getting more and more frustrated with all of those formats. Not to mention that neither Flatpak, Snap nor Appimage can get to OpenCL. (Snap can but only in classic confinement which means no confinement at all).
Flatpak is sandboxed, so you need to grant it permission to run the appimage. Check out the Flatseal app on flathub, its a GUI permissions app for flatpak.