image_voodoo 0.8.7 → 0.9.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +5 -5
- data/.gitignore +4 -0
- data/.rubocop.yml +165 -0
- data/.travis.yml +17 -0
- data/Gemfile +5 -0
- data/Jars.lock +3 -0
- data/LICENSE-2.0.txt +202 -0
- data/README.exif +18 -0
- data/README.md +1 -0
- data/Rakefile +21 -0
- data/bin/image_voodoo +81 -72
- data/image_voodoo.gemspec +14 -7
- data/lib/image_science.rb +3 -1
- data/lib/image_voodoo/awt/core_ext/buffered_image.rb +15 -0
- data/lib/image_voodoo/awt/core_ext/graphics2d.rb +15 -0
- data/lib/image_voodoo/awt/shapes.rb +41 -3
- data/lib/image_voodoo/awt.rb +177 -124
- data/lib/image_voodoo/gae.rb +12 -6
- data/lib/image_voodoo/metadata.rb +1689 -0
- data/lib/image_voodoo/needs_head.rb +3 -0
- data/lib/image_voodoo/version.rb +3 -1
- data/lib/image_voodoo.rb +77 -90
- data/samples/bench.rb +30 -36
- data/samples/file_greyscale.rb +2 -0
- data/samples/file_thumbnail.rb +2 -0
- data/samples/file_view.rb +4 -1
- data/samples/{in-memory.rb → in_memory.rb} +2 -0
- data/samples/lossy.rb +2 -0
- data/test/test_image_science.rb +34 -74
- data/test/test_image_voodoo.rb +84 -0
- data/test/test_metadata.rb +65 -0
- data/test/test_shapes.rb +23 -0
- data/tools/gen.rb +68 -0
- metadata +94 -7
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
|
-
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 5028b379cc34f48eb0851549a5f49a9ebd2495385d5fdbfe09d6b9fb0bdd006c
|
4
|
+
data.tar.gz: 873525e43dbfb68a86b664b19d19fa49d522e5312945f86d1939386d17369f94
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: ee3af809b508d7cf1e4d880e155e487c19ce9579298d132b02d494edf2e63c681b0deed07b891b8d430f75fc6e3058c12fe7ad98fee47f704acdf4bc5abf8087
|
7
|
+
data.tar.gz: 50fd50f6ba4d34afc4b6585dfdeaeb2077a380ef1073522641253f89f7b2e5aa956174019e8275ee674a7cbad8287d22e42cd50fe2af5a576624bd0b577ce4e6
|
data/.gitignore
CHANGED
data/.rubocop.yml
ADDED
@@ -0,0 +1,165 @@
|
|
1
|
+
# Experiment to tweak source based on what rubocop wanted me to. I basically
|
2
|
+
# gave up and made the following exceptions. Personally, I find the tool did
|
3
|
+
# find many interesting/questionable code Qs in the project but it is soooo
|
4
|
+
# opinionated in pretty unimportant ways (like who cares how I write my
|
5
|
+
# comments, or why can't I use kind_of? or why give me a fail for a less
|
6
|
+
# readable but more performant pattern).
|
7
|
+
#
|
8
|
+
# I can obviously tweak rules (like below) but I keep hearing of people pulling
|
9
|
+
# their hair out over all the unimportant rules; I question why this project is
|
10
|
+
# "all-in" on it's rules versus leaving most of the style rules as some preset
|
11
|
+
# profiles people can opt in to.
|
12
|
+
#
|
13
|
+
# So I am committing this and I will try and run this every now and then to
|
14
|
+
# see what it thinks about what I wrote but you will not see this as a
|
15
|
+
# requirement for commits since I think by the time I configured it to my
|
16
|
+
# liking I could have finished implementing this library. Perhaps if I
|
17
|
+
# continue using this here and there I will end up with a profile I find
|
18
|
+
# acceptable? I did find value but all the piddly shit just made me angry.
|
19
|
+
# I will reflect on it some more...
|
20
|
+
|
21
|
+
# This is a Java AWT call. It is not what the tool thinks it is...which
|
22
|
+
# might be an issue for users interacting with Java from JRuby.
|
23
|
+
Lint/UselessSetterCall:
|
24
|
+
Exclude:
|
25
|
+
- 'lib/image_voodoo/awt.rb'
|
26
|
+
|
27
|
+
# This is just impossible for them to call properly. I am doing something
|
28
|
+
# like rotate_impl and it is a bunch of reasonably simple math. If you look
|
29
|
+
# for this transformation in a text book it will look like this code. Putting
|
30
|
+
# a bunch of math within different methods would get the score down but
|
31
|
+
# it would not help readability. (addendum: I did try and break it apart more
|
32
|
+
# and never reached 15 but got closer. I felt this rule is neat but the
|
33
|
+
# score really depends on what it is.
|
34
|
+
Metrics/AbcSize:
|
35
|
+
Max: 16.5
|
36
|
+
|
37
|
+
# This is triggered for correct_orientation_impl. I could put these transforms
|
38
|
+
# in a table and then execute lambdas for each orientation but this is much
|
39
|
+
# more clear.
|
40
|
+
Metrics/CyclomaticComplexity:
|
41
|
+
Max: 10
|
42
|
+
|
43
|
+
# A bunch of fields in a hash are basically generated data. Correcting them
|
44
|
+
# for column seems much too pedantic. I guess exclude is the right thing for
|
45
|
+
# an unusual file?
|
46
|
+
Layout/LineLength:
|
47
|
+
Max: 132
|
48
|
+
Exclude:
|
49
|
+
- 'lib/image_voodoo/metadata.rb'
|
50
|
+
|
51
|
+
# Metadata classes have data in them. awt.rb is big and perhaps could be
|
52
|
+
# shrunk but it is not a hard file to navigate and the cleaving points are
|
53
|
+
# not super obvious. These sorts of rules feel very arbitrary and if I have
|
54
|
+
# n highly related things and they do not fit into a more restrictive
|
55
|
+
# taxonomy why would the file being longer matter? I do understand the
|
56
|
+
# motivation here but as a default rule this feels wrong to me.
|
57
|
+
Metrics/ClassLength:
|
58
|
+
Max: 250
|
59
|
+
|
60
|
+
# I do not find this very useful. There is no performance difference and
|
61
|
+
# sometimes I want to highlight this string does not involve interpolation.
|
62
|
+
# Other times it is not worth pointing out.
|
63
|
+
Style/StringLiterals:
|
64
|
+
Enabled: false
|
65
|
+
|
66
|
+
# require 'english' is a step too far for $! which is so baked into my
|
67
|
+
# head I do not want to change :)
|
68
|
+
Style/SpecialGlobalVars:
|
69
|
+
Enabled: false
|
70
|
+
|
71
|
+
# I am grouping math and using lack of whitespace for separation.
|
72
|
+
Layout/SpaceAroundOperators:
|
73
|
+
Enabled: false
|
74
|
+
|
75
|
+
# I prefer tight assignment for opt args.
|
76
|
+
Layout/SpaceAroundEqualsInParameterDefault:
|
77
|
+
Enabled: false
|
78
|
+
|
79
|
+
# Java methods which override or implement Java method names cannot be switched
|
80
|
+
# to snake case. Do we really need this as a rule anyways? I have never seen
|
81
|
+
# a Rubyist do this as a preferred style?
|
82
|
+
Naming/MethodName:
|
83
|
+
Enabled: false
|
84
|
+
|
85
|
+
# bin/image_voodoo main options block.
|
86
|
+
Metrics/BlockLength:
|
87
|
+
Exclude:
|
88
|
+
- 'bin/image_voodoo'
|
89
|
+
|
90
|
+
# Hash rocket looks much more natural in a rakefile for its deps.
|
91
|
+
Style/HashSyntax:
|
92
|
+
Exclude:
|
93
|
+
- 'Rakefile'
|
94
|
+
|
95
|
+
# Forget it. I do parallel assignment and you will have to peel it out of
|
96
|
+
# my cold dead hands.
|
97
|
+
Style/ParallelAssignment:
|
98
|
+
Enabled: false
|
99
|
+
|
100
|
+
# FIXME: consider keywords for shapes.
|
101
|
+
# I might switch these to keyword args if I ever revisit shapes support.
|
102
|
+
# In general lots of params do suck and are hard to remember. This library
|
103
|
+
# still is supposed to work in 1.8 but I can probably soon major rev this
|
104
|
+
# and switch over to keywords.
|
105
|
+
Metrics/ParameterLists:
|
106
|
+
Exclude:
|
107
|
+
- 'lib/image_voodoo/awt/shapes.rb'
|
108
|
+
|
109
|
+
# This is complaining that 'x' and 'y' are bad names because they are less
|
110
|
+
# than 3 chars. Silly rule even if I appreciate what it is trying to
|
111
|
+
# accomplish. Interestingly, in image_voodoo I do use h for height and
|
112
|
+
# w for width. Those probably could be written out but they are so common
|
113
|
+
# I am basically opting for short-hand. This is something I rarely do except
|
114
|
+
# domain-driven code like this (x,y,h,w).
|
115
|
+
Naming/MethodParameterName:
|
116
|
+
Enabled: false
|
117
|
+
|
118
|
+
# This represents one of those frustrating dogmatic rules where if I followed
|
119
|
+
# this advice I would then violate the column length rule. I specifically
|
120
|
+
# use traditional if indented block in cases where if_mod doesn't fit.
|
121
|
+
# Gramatically, if_mod can be across two lines but I hate how that looks. The
|
122
|
+
# second solution of logical &&/|| change for a raise is alien to for all but
|
123
|
+
# assignment.
|
124
|
+
Style/IfUnlessModifier:
|
125
|
+
Enabled: false
|
126
|
+
|
127
|
+
# What the hell. Really telling people that encoding: utf-8 should not happen
|
128
|
+
# because there are no multi-byte utf-8 characters in it? Why add this noise?
|
129
|
+
Style/Encoding:
|
130
|
+
Enabled: false
|
131
|
+
|
132
|
+
# FIXME:
|
133
|
+
# This is an unknown error which I should figure out. It must be some
|
134
|
+
# StandardError (which is what nothing explicit means) but I should actually
|
135
|
+
# be more explicit here.
|
136
|
+
Style/RescueStandardError:
|
137
|
+
Exclude:
|
138
|
+
- 'lib/image_voodoo.rb'
|
139
|
+
|
140
|
+
|
141
|
+
# This was complaining metadata_impl should use @metadata_impl instead of
|
142
|
+
# @metadata. I disagree and am unsure why I need to follow this programs
|
143
|
+
# opinion on what a good name is? What is commentable is if I change the
|
144
|
+
# variable name to @gorgon it still tells me I need to use @metadata_impl.
|
145
|
+
# So if I conditionally add any state in any method it will tell me I am
|
146
|
+
# memoizing and have to use same ivar as the name of the method? Is it more
|
147
|
+
# sophisticated than that? Should I have spent 2-3 minutes trying to figure
|
148
|
+
# out how this rule was implemented? :)
|
149
|
+
Naming/MemoizedInstanceVariableName:
|
150
|
+
Enabled: false
|
151
|
+
|
152
|
+
# I have two modes of use for private. If it is a small number of individual
|
153
|
+
# methods I am explicit and inline the private. If it is a large number of
|
154
|
+
# methods especially when the name is fairly obvious that those will be private
|
155
|
+
# (like render_impl) then I use block private. Not sure telling me I can only
|
156
|
+
# use a single style is very useful.
|
157
|
+
Style/AccessModifierDeclarations:
|
158
|
+
Enabled: false
|
159
|
+
|
160
|
+
# I feel for the tiny amount of generation here a better name would not help
|
161
|
+
# me understand it better. This is one of those naming rules I feel is
|
162
|
+
# probably helpful a minority of the time. Also I have never been confused
|
163
|
+
# by what a heredoc text represents because of my heredoc terminator?
|
164
|
+
Naming/HeredocDelimiterNaming:
|
165
|
+
Enabled: false
|
data/.travis.yml
ADDED
@@ -0,0 +1,17 @@
|
|
1
|
+
language: ruby
|
2
|
+
|
3
|
+
sudo: false
|
4
|
+
|
5
|
+
rvm:
|
6
|
+
- jruby-head
|
7
|
+
|
8
|
+
before_install:
|
9
|
+
- mkdir rvm_tmp
|
10
|
+
- cd rvm_tmp
|
11
|
+
|
12
|
+
before_script:
|
13
|
+
- cd ..
|
14
|
+
- git clone --depth 1 https://github.com/drewnoakes/metadata-extractor-images.git ../metadata-extractor-images
|
15
|
+
|
16
|
+
install: JRUBY_OPTS=--dev jruby --dev -S bundle install --jobs=3 --retry=3
|
17
|
+
|
data/Gemfile
ADDED
data/Jars.lock
ADDED
data/LICENSE-2.0.txt
ADDED
@@ -0,0 +1,202 @@
|
|
1
|
+
|
2
|
+
Apache License
|
3
|
+
Version 2.0, January 2004
|
4
|
+
http://www.apache.org/licenses/
|
5
|
+
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
7
|
+
|
8
|
+
1. Definitions.
|
9
|
+
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
12
|
+
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
14
|
+
the copyright owner that is granting the License.
|
15
|
+
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
17
|
+
other entities that control, are controlled by, or are under common
|
18
|
+
control with that entity. For the purposes of this definition,
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
20
|
+
direction or management of such entity, whether by contract or
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
23
|
+
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
25
|
+
exercising permissions granted by this License.
|
26
|
+
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
28
|
+
including but not limited to software source code, documentation
|
29
|
+
source, and configuration files.
|
30
|
+
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
32
|
+
transformation or translation of a Source form, including but
|
33
|
+
not limited to compiled object code, generated documentation,
|
34
|
+
and conversions to other media types.
|
35
|
+
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
37
|
+
Object form, made available under the License, as indicated by a
|
38
|
+
copyright notice that is included in or attached to the work
|
39
|
+
(an example is provided in the Appendix below).
|
40
|
+
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
47
|
+
the Work and Derivative Works thereof.
|
48
|
+
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
50
|
+
the original version of the Work and any modifications or additions
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
62
|
+
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
65
|
+
subsequently incorporated within the Work.
|
66
|
+
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
73
|
+
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
79
|
+
where such license applies only to those patent claims licensable
|
80
|
+
by such Contributor that are necessarily infringed by their
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
83
|
+
institute patent litigation against any entity (including a
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
86
|
+
or contributory patent infringement, then any patent licenses
|
87
|
+
granted to You under this License for that Work shall terminate
|
88
|
+
as of the date such litigation is filed.
|
89
|
+
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
92
|
+
modifications, and in Source or Object form, provided that You
|
93
|
+
meet the following conditions:
|
94
|
+
|
95
|
+
(a) You must give any other recipients of the Work or
|
96
|
+
Derivative Works a copy of this License; and
|
97
|
+
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
99
|
+
stating that You changed the files; and
|
100
|
+
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
103
|
+
attribution notices from the Source form of the Work,
|
104
|
+
excluding those notices that do not pertain to any part of
|
105
|
+
the Derivative Works; and
|
106
|
+
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
109
|
+
include a readable copy of the attribution notices contained
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
112
|
+
of the following places: within a NOTICE text file distributed
|
113
|
+
as part of the Derivative Works; within the Source form or
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
115
|
+
within a display generated by the Derivative Works, if and
|
116
|
+
wherever such third-party notices normally appear. The contents
|
117
|
+
of the NOTICE file are for informational purposes only and
|
118
|
+
do not modify the License. You may add Your own attribution
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
121
|
+
that such additional attribution notices cannot be construed
|
122
|
+
as modifying the License.
|
123
|
+
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
125
|
+
may provide additional or different license terms and conditions
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
129
|
+
the conditions stated in this License.
|
130
|
+
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
134
|
+
this License, without any additional terms or conditions.
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
136
|
+
the terms of any separate license agreement you may have executed
|
137
|
+
with Licensor regarding such Contributions.
|
138
|
+
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
141
|
+
except as required for reasonable and customary use in describing the
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
143
|
+
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
153
|
+
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
159
|
+
incidental, or consequential damages of any character arising as a
|
160
|
+
result of this License or out of the use or inability to use the
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
163
|
+
other commercial damages or losses), even if such Contributor
|
164
|
+
has been advised of the possibility of such damages.
|
165
|
+
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
169
|
+
or other liability obligations and/or rights consistent with this
|
170
|
+
License. However, in accepting such obligations, You may act only
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
175
|
+
of your accepting any such warranty or additional liability.
|
176
|
+
|
177
|
+
END OF TERMS AND CONDITIONS
|
178
|
+
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
180
|
+
|
181
|
+
To apply the Apache License to your work, attach the following
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
183
|
+
replaced with your own identifying information. (Don't include
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
185
|
+
comment syntax for the file format. We also recommend that a
|
186
|
+
file or class name and description of purpose be included on the
|
187
|
+
same "printed page" as the copyright notice for easier
|
188
|
+
identification within third-party archives.
|
189
|
+
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
191
|
+
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
193
|
+
you may not use this file except in compliance with the License.
|
194
|
+
You may obtain a copy of the License at
|
195
|
+
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
197
|
+
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
201
|
+
See the License for the specific language governing permissions and
|
202
|
+
limitations under the License.
|
data/README.exif
ADDED
@@ -0,0 +1,18 @@
|
|
1
|
+
Copyright 2002-2012 Drew Noakes
|
2
|
+
|
3
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
4
|
+
you may not use this file except in compliance with the License.
|
5
|
+
You may obtain a copy of the License at
|
6
|
+
|
7
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
8
|
+
|
9
|
+
Unless required by applicable law or agreed to in writing, software
|
10
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
11
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
12
|
+
See the License for the specific language governing permissions and
|
13
|
+
limitations under the License.
|
14
|
+
|
15
|
+
More information about this project is available at:
|
16
|
+
|
17
|
+
http://drewnoakes.com/code/exif/
|
18
|
+
http://code.google.com/p/metadata-extractor/
|
data/README.md
CHANGED
@@ -13,6 +13,7 @@ http://github.com/jruby/image_voodoo
|
|
13
13
|
* Includes image_voodoo command-line utility for quick resizing of images, "image_voodoo --help" for usage.
|
14
14
|
* Due to lack of TIFF support in ImageIO it is also not supported yet by image_voodoo. If you need it, create an issue in GitHub.
|
15
15
|
* **JPEG CMYK support** is thanks to work of Werner Randelshofer and [Monte Media Library](http://www.randelshofer.ch/monte/). Monte Media Library is provided under [CC BY 3.0](http://creativecommons.org/licenses/by/3.0/) license.
|
16
|
+
* Now supports reading a variety of EXIF data. This also supports new function --orient based on how phones typically save photo data.
|
16
17
|
|
17
18
|
## SYNOPSIS:
|
18
19
|
|
data/Rakefile
CHANGED
@@ -1,2 +1,23 @@
|
|
1
|
+
# frozen_string_literal: true
|
2
|
+
|
1
3
|
require 'bundler'
|
4
|
+
require 'rake/testtask'
|
5
|
+
require 'jars/installer'
|
2
6
|
Bundler::GemHelper.install_tasks
|
7
|
+
Bundler.setup
|
8
|
+
|
9
|
+
task :default => %i[vendor_jars test]
|
10
|
+
|
11
|
+
desc 'Vendor Jars'
|
12
|
+
task :vendor_jars do
|
13
|
+
test_file = File.expand_path File.join('lib', 'image_voodoo_jars.rb'), __dir__
|
14
|
+
Jars::Installer.vendor_jars! unless File.exist? test_file
|
15
|
+
end
|
16
|
+
|
17
|
+
desc 'Run tests'
|
18
|
+
task :test => :vendor_jars do
|
19
|
+
Rake::TestTask.new do |t|
|
20
|
+
t.libs << 'lib:vendor'
|
21
|
+
t.test_files = FileList['test/test*.rb']
|
22
|
+
end
|
23
|
+
end
|