Re: [Geeqie-devel] Pay for feature
You can make a shell script like this to show textual representation of EXIF: #!/bin/sh exiftool "$1" \ | zenity --text-info --font=Monospace --width=800 --height=600 --title="$1" Or like this to copy it directly to clipboard: #!/bin/sh exiftool "$1" | xsel And then set this script as an external editor in Geeqie. You can also use another tools like exiv2 and customize output as you need using tool's options or grep/sed. Grant wrote, on 12.7.2017 14:54: > Hello, I need the ability to copy EXIF data to the clipboard from the > metadata viewer in Linux. Is anyone willing to work on this in > exchange for payment? > > Thanks, > Grant > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Geeqie-devel mailing list > Geeqie-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geeqie-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Geeqie++ fever dreams (+Win32)
Ian Zimmerman wrote, on 29.12.2016 02:26: > On this topic, would it be interesting to create pipelines for editors, > rather than just invoking them 1 by 1? For example, we could make it > possible to create a pipeline where an intricate batch imagemagick > command is called on the current image, the output is saved to a > temporary file, and then gimp is immediately called on the temporary to > allow for manual postprocessing. Can we imagine a GUI for defining such > pipelines? It would be very messy. Leave that to command line. What can be done quite easily is to invoke a command on a selection of images (something like xargs): 1. Select images 2. Hit "Batch processing" button 3. Dialog window will appear. User selects the command and reviews list of images. 4. Hit "Execute" button 5. Progress is shown in the dialog. 6. Go to 3. Question is about the form of the command selection. Geeqie has list of editor commands wich are available in the popup menu. These should be available here too. Maybe we can do the same as e-mail clients do with filters. It would look familiar, but also it would be limited just like these filter GUI are. Basically a list of commands may be sufficient, but it is hard to specify inputs and outputs. I think there is a better way, but it would be a bit more complicated to implement. I wonder if it is a bit too complex for a simple use-cases. It is called "block programming". It is quite an old idea: Each block (a filter) has inputs and outputs. These I/O are connected together and blocks form directed acyclic graph. User draws such graph using palette of predefined blocks and then executes it. I wrote a paper about modification of this approach for web applications, but it can be easily adapted to any non-interactive use, just like this one. See the paper: https://josef.kufner.cz/publications/2014.kufner.cascade.pdf Benefit over unix pipelines is in easy dealing with multiple inputs and outputs. You can have a block to merge multiple images with aplha channel, or to split color image into three by RGB channels and process them separately. If you want complex shell for batch processing, this is the way to go. If you want something simple, just run one command on a set of images. Have a nice day! Josef Kufner -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] GPS maps
Roger wrote, on 7.5.2016 04:24: >> Now I recompiled it completely with gtk-3 and gps support. >> >> Works that far. But it shows me why I never liked GTK-3. >> - - Mouse wheel is not working in lists anymore >> - - Buttons and layout are ugly >> - - Image display flickers when using map display >> >> So, recompiling it back with gtk-2. :-( > > Ditto concerning gtk-3. I love gtk, but gtk-3 support looks half-baked, or > half-usable. Might be considering recompiling all my applications back to > gtk-2 on this note. Hmm... how crazy idea it would be to port Geeqie to Qt5 ? :) -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Git repository workflow
Klaus Ethgen wrote, on 3.5.2016 15:18: > Am Di den 3. Mai 2016 um 13:06 schrieb Josef Kufner: >> Klaus Ethgen wrote, on 3.5.2016 12:30: >>> For Release this need to be set manually as before. Maybe I can make a >>> better solution or someone comes up with one. > >> Is there really a difference between release build and ordinary build? >> Does it have to be? > > I would say so: > - Release build must not fail So there must be a fallback for tarballs (directory name?). > - Release build has a version (not a hash number git describe produces very nice string: tag, number of commits from the tag and hash. If current commit is tagged, it produces only a tag name. > - Release build only receive stable and/or security patches That does not conflict with anything. Still all releases should be tagged (incrementing patch number), so it does not change anything. -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Git repository workflow
Klaus Ethgen wrote, on 3.5.2016 12:30: > For Release this need to be set manually as before. Maybe I can make a > better solution or someone comes up with one. Is there really a difference between release build and ordinary build? Does it have to be? -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Git repository workflow
> Am Mo den 2. Mai 2016 um 18:53 schrieb Josef Kufner: >> Git hooks are not the right tool for this task. It is better to run `git >> describe` during the build process to generate a version file, which >> will be compiled in and shown by `geeqie --version`. > >> It is easy to automatically generate version.h with few #define >> statements or something like that and include it wherever neccessary. > > Yes. That is also what I think about that. > > But there is a problem when people use the tarbal to build their > version. > > So the version has to be in the checked out file. There is some substs > that could be used eventually. But finally it has to be set with > checkin, so a hook. Unfortunately for a hook, every developer has to > have them in all the clones. There is no way to manage them within git. > > Nevertheless, it is easy to have just "master" in version information. Tarball from Github contains root directory named geeqie-1.2.3. So there is a reasonable fallback. Not perfect, but good enough. Simply force generation of version.h during build and it will be fine. Hooks are much more problematic. I use generated version info in all my projects and it works very well. My last Qt project used this in qmake project file: GIT_VERSION = $$system(git --git-dir $$PWD/.git --work-tree $$PWD \ describe --always --tags) DEFINES += GIT_VERSION=\\\"$$GIT_VERSION\\\" It results in gcc -DGIT_VERSION=\"1.2.3\" ... -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
Re: [Geeqie-devel] Git repository workflow
Git hooks are not the right tool for this task. It is better to run `git describe` during the build process to generate a version file, which will be compiled in and shown by `geeqie --version`. It is easy to automatically generate version.h with few #define statements or something like that and include it wherever neccessary. Colin Clark wrote, on 2.5.2016 19:46: > >> I'll post in the issues if appropriate: the question I have at the >> moment is that the about box seems woefully out of date, as is "geeqie >> --version". I am fairly sure I am compiling master HEAD. >> > Hi Klaus > > There have been quite a few updates to the repository recently, and > maybe a few more to come from me - e.g. copy/move with thumbnail preview > and simultaneous rename, additional search functions. > > I think people may try to keep up to date by downloading the master > rather than wait for a release, but that gives a problem when they > report problems - what have they compiled?. > > Is it a simple thing to use git hooks to run a command to update a file > in the repo at each commit, so that the About window can show not just > major/minor version, but also e.g. the output of "git describe" at the > time the last commit was made? > > If not, no problem. > > > Colin... > > > -- > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > ___ > Geeqie-devel mailing list > Geeqie-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geeqie-devel > -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
[Geeqie-devel] [patch] Fullscreen fix
Good news everyone, I managed to fix the fullscreen mode. At least it looks fixed for me :) -- Tested on multi-screen setup on KDE5. Here is the pull request: https://github.com/BestImageViewer/geeqie/pull/379 What do you say? Does it work for you? Have a nice day! Josef Kufner -- Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z ___ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
