mini_exiftool | Exiftool command-line application | Document Editor library

by janfri Ruby Version: Current License: LGPL-2.1

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | mini_exiftool Summary

mini_exiftool is a Ruby library typically used in Editor, Document Editor applications. mini_exiftool has no bugs, it has no vulnerabilities, it has a Weak Copyleft License and it has low support. You can download it from GitHub.

This library is a wrapper for the Exiftool command-line application (written by Phil Harvey. It provides the full power of Exiftool to Ruby: reading and writing of EXIF-data, IPTC-data and XMP-data. Branch master is for actual development and branch compatibility-version is for compatibility with Ruby 1.8 and exiftool versions prior 7.65.

Support

Quality

Security

License

Reuse

Support

mini_exiftool has a low active ecosystem.

It has 193 star(s) with 46 fork(s). There are 7 watchers for this library.

It had no major release in the last 6 months.

There are 2 open issues and 23 have been closed. On average issues are closed in 86 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of mini_exiftool is current.

Quality

mini_exiftool has 0 bugs and 5 code smells.

Security

mini_exiftool has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

mini_exiftool code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

mini_exiftool is licensed under the LGPL-2.1 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

mini_exiftool releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

mini_exiftool saves you 598 person hours of effort in developing the same functionality from scratch.

It has 1394 lines of code, 143 functions and 28 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of mini_exiftool

Get all kandi verified functions for this library.

mini_exiftool Key Features

No Key Features are available at this moment for mini_exiftool.

mini_exiftool Examples and Code Snippets

No Code Snippets are available at this moment for mini_exiftool.

Community Discussions

Trending Discussions on mini_exiftool

gem locations in macOS with chruby and TextMate preferences

Jekyll - access plugin object from Liquid

QUESTION

gem locations in macOS with chruby and TextMate preferences

Asked 2019-Jun-14 at 05:08

I having trouble getting Ruby gems to work right with TextMate (TM) and chruby on macOS.

Clean install of Mojave (now v10.14.4) on a 2017 iMac about six months ago.

Trying to use Ruby-2.6.2, although earlier versions have been installed. System Ruby is v2.3.7

I have ended up with gems in at least three locations:

~/.rubies/ruby-2.6.2/lib/ruby/gems/2.6.0/gems/
~/.gem/ruby/2.6.2/gems/
/Library/Ruby/Gems/2.3.0/gems/

TextMate relies on its Preferences for gem and Ruby locations. As a start I have the following: GEM_HOME is unset because I don't see why it's needed, although I've frequently read to set it as shown or similar. GEM_HOME and GEM_PATH are defined as

GEM_PATH provides the locations (there may be several) where gems can be found.

GEM_HOME is where gems will be installed (by default).

The problem is that when I run this script (after the error not included) in TM

...

ANSWER

Answered 2019-Jun-14 at 05:08

Changed GEM_HOME and GEM_PATH to $HOME/.gem/ruby/2.6.2:$HOME/.rubies/ruby-2.6.2/lib/ruby/gems/2.6.0 based on copying the those variables from what showing up when running from the terminal. Lu's comment made me look a little harder at what was being reported. Basically I was missing $HOME/ in the second path (after the colon). I have been fiddling with this for months

Source https://stackoverflow.com/questions/55719818

QUESTION

Jekyll - access plugin object from Liquid

Asked 2017-Apr-13 at 08:09

I have a list of images, on which I run mini_exiftool to extract various properties from images (EXIF & IPTC). I have successfully created a LiquidTag. It accepts the path and the EXIF property I want, and returns that as (what I assume is) a string.

However, mini_exiftool is slow. Currently I insert the tag multiple times per image. I would like to run it once per image and store all the data (array? object?) in a variable. Small disclaimer - I hardly know any Ruby, apart from what I learned trying to understand this issue.

This is how I use the plugin:

...

ANSWER

Answered 2017-Apr-12 at 18:32

From how you described the plugin, I would say it does what you want. The plugin returns a specific property from (a photo?) and returns it as a string.

But it sounds as you want to to it one time only and store it somewhere else. In this case you might want to consider doing it a bit different. Esp when you say the property reading is slow.

You could in example use a generator to create the data you need based on all images before a run. Details on generators: http://jekyllrb.com/docs/plugins/#generators

You could have a similar approach like I have for sorting languages:

Source https://stackoverflow.com/questions/43328097

Community Discussions, Code Snippets contain sources that include Stack Exchange Network