![]() ![]() Sorry, a valid argument looks different.Īt the end of the day it all boils down to the question whether we want to follow the route GIMP and other open source software went. Do they promote our software? Yes, to other Windows users which generate noise, too. Do they support me coding the program? Hardly. Then, what are the benefits from adding Windows to the pool of supported platforms you might ask? The standard answer always given is “you get so many new users”. So in the end we would need to have our own installer, bundle all the needed libraries, maybe add some automated checking for new versions, you name it. Well, Windows recently introduced some means of online updates for third party software, but that’s beyond our scope. That makes it easy to distribute a program and keep it up to date. While Linux has tons of different flavours, nowadays most of them come with a working package management. The next problem with Windows is the lack of package managers. Don’t believe me? Go looking at support forums for GIMP. And since they know that, they are really good in demanding everything while giving back nothing. They are a bunch of consumers which only take what you give them. Some might not know what you are talking about, yet it’s not too hard to give simple instructions. With Linux users you can give the advice to run gdb and generate a backtrace. Even more if the users have not the slightest clue what’s going on. Maintaining a code base which none of the developers can run, test or debug is a nightmare. ![]() Followed by no longer adding an alpha channel to new layers. And now, well, let me phrase it this way: I strongly believe that porting GIMP to windows was the biggest mistake these guys ever made. I remember when GIMP was suddenly available for Windows (yes, I’m that old). Code wise it’s only a really small change, but the implications might be huge. The hard part is the question “Shall I commit it to git?”. It took me about two days of hacking to have our code in a shape which is eaten by mingw (I cross-compiled under Debian). I managed to compile darktable for Windows. However, if you are a Windows user and feel easily offended, then stop reading now. Since a few people didn’t like that at all I want to assure you that this is no joke at all. en.wikipedia.The last time I posted to this blog it was my April Fool’s Joke about a file manager (which happened to be just an embedded shell). I don’t know if it possible to ensure that the same drive letter gets assigned with commands inside a batch file. The only problem is the drive letter as mentioned. The batch file or the shortcut can resist on your external drive and can be started by double-click. If it is only is only a onliner like this you can use an icon/shortcut and put this in the “field execute” or so (I have no English Windows version so this field might have a different name). This would use an existing or if it does not exist create a new database called dt.db and put all created previews and other stuff the needs caching in the directory cache. "C:\Program Files\darktable\bin\darktable.exe" -library :\dt.db -cachedir :\cache to start darktable with the two options -library and -cachedirat the same time. ![]() On windows you can create batch files or use shortcuts to do this. Multiple of this options can be used at the same time to invoke darktable. to see the output/startoptions you have to look at this log file in the manual. That’s what does not work, because the output is written to some log file on disk. So if you start darktable like: "C:\Program Files\darktable\bin\darktable.exe" -help to see some documentation about startoptions nothing happens. However, there is no logging output shown at the command prompt. Starting darktable with "C:\Program Files\darktable\bin\darktable.exe" -library d:\tmp\dt.db at the windows command prompt ( cmd.exe) creates a new database for me in d:\tmp\ as already mentioned.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |