Hi Kevin,
I'll help you. I'm working on getting all of the scripts to run cross platform. Do you have git on your system? If not, go to https://gitforwindows.org and download it. Install it and make sure you check the add git to path option. The included git bash shell is great for debugging your scripts. Once git is installed, open a command prompt then create a directory for code somewhere. Go into that directory and do git clone https://github.com/darktable-org/lua-scripts.git That will pull the current version of the darktable lua scripts into a directory named lua-scripts. If you open the file lua-scripts\contrib\gimp.lua you will see an example of how to do a cross platform compatible script. It utilizes the libraries a cross platform version of check_if_bin_exists plus lots of other pieces of code to ease development. You can e-mail me direct with questions. You might want to set up a github account if you don't have one. Bill On Thu, Mar 15, 2018 at 3:19 PM, Kevin Ertel <ker...@g.clemson.edu> wrote: > All, > > Over the past few days I have worked on the following two scripts for > windows: > HDRMerge - adds HDRMerge as an option under "Selected Images" > enfuse_pro_w - hacked up version of Holger's enfuse_pro to run on windows > (I reached out to Holger prior to sharing this) > > Please note that I am not a skilled developer, my programming skills are > still fairly elementary, so much of what I have done is not the most > elegant or preferred way to do things. I recognize this, but I did what I > could. The enfuse_pro script is far more complex, and thus has much more > work still needed to it, but both scripts DO run on my windows 10 machine. > > Issues I have with both scripts: > 1) I have not been able to figure out a way to pass the binaries to > dt.control.execute() if their path location contains a SPACE, thus these > scripts require their dependencies to be install to a specific location, > instead of the default "Program Files", solving this and then dynamically > finding the binary location would obviously be preferred. I don't know how > to do this. > > 2) When calling binaries through dt.control.execute() a command window > pops up. How can this be suppressed? > > 3) Scripts are now windows specific. I don't think it would take much to > make the HDRMerge one cross-platform compatible. Due to the complexities of > the enfuse_pro script this may require more work. > > There are other, smaller, issues respective to each individual file > briefly noted in the header comments if you are curious. Much of the > functionality of the enfuse_pro script remains untested. > > I also must call attention to the fact that the enfuse_pro script deletes > the temporary files, however, I had to completely rewrite this > functionality. I would appreciate someone more knowledgeable than myself > check over this code and ensure what I am doing does not have any risks of > deleting the wrong files, or anything like that. > > I have quickly reached the limits of my abilities. Is anyone here > able/willing to assist, or how do you advise I go about soliciting help, > pixls.us and GitHub? > > -Kevin > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org