On Sun, Aug 19, 2018 at 8:22 AM thokster <[email protected]> wrote: > Am 19.08.2018 um 13:30 schrieb J Albrecht: > > Bill, this is BRILLIANT! I’ve been waiting for it ever since you had > mentioned it over a year (or 2?) ago. Thank you :-) > > As a MacOS user (running dt 2.4.4 on OS El Capitan 10.11.6), I have the > following observations: > > *The enable settings don’t “stick”* > > - Anything enabled and running successfully is automagically disabled > upon the next startup of dt ! > > Same on Ubuntu (Gnome). > Is it intentionally? > > It was a "feature" :-). I tested all the parts that didn't work or work well pretty extensively, but I forgot to double check the stuff that still worked. I moved some code around and cleaned stuff up and somehow lost the preference saving line. It's back now.
> > > *The optional “downloads” directory is limiting* > > - Because I regularly tend to clean-up my downloads directory, any > extra lua scripts sitting in there are at risk of being deleted and thus > unavailable to dt > - Wouldn’t it be a better idea if one could choose which directory > holds extra scripts? > - Yes, I understand that one could create additional directories > within the lua directory into which special scripts can be placed but… > > > *Special lua directories at risk of disappearing after an update (?)* > > - Wouldn’t a git pull result in the deletion of any special > directories created within the lua directory? > > > +1 > git pull doesn't overwrite any changes. If you add a directory, then git pull will see that a pull won't overwrite anything so it works. If, for instance, you edited contrib/gimp.lua and made a change, then git pull would refuse to update because it would overwrite the changes. You can make as many extra directories as you like and git just ignores them. You can also use links, which is what I do. The only time that the extra directories would disappear is on a reinstall of the lua scripts. In that case the existing lua directory is renamed to lua.orig, so they aren't lost, just moved. > > > > On 19 Aug 2018, at 05:27, William Ferguson <[email protected]> wrote: > > I’ve created script_manager.lua to install, update, enable and disable the > darktable lua scripts. It’s available at > https://github.com/wpferguson/script_manager. > > Download it and copy it to ~/.config/darktable/luarc (linux and MacOS) or > C:\Users<username>\AppData\Local\darktable\luarc (windows). Start darktable > and script manager will be in the lower left pane in the lighttable. > > script_manager uses git to install and update the lua scripts directory. > On windows the git program location needs to be set in the configure tab. > On MacOS it might need to be set, if script_manager can’t find it. > > After the scripts are installed from the repository, you can enable or > disable them with the click of a button. The scripts are divided into > “categories” based on the subdirectory they live in under the lua directory. > > For developers: You can create extra directories under the lua directory > such as development, testing, etc. You can also create symbolic links to > other places in your file system. When you are compiling you can click the > enable button for the script you are writing. If it doesn’t load because of > a coding error, you can just correct it and click the enable button again. > You can repeat this until you fix all the syntax errors and the script > loads. Changes after the script loads still require a darktable restart. > > Enjoy, > > Bill > > ____________________________________________________________________________ > darktable user mailing list to unsubscribe send a mail to > [email protected] > > > > > ____________________________________________________________________________ > darktable user mailing list to unsubscribe send a mail to > [email protected] > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
