Open johnnychen94 opened 4 years ago
How about dropping the dependencies on the image-packages? They make this package a heavy dependency for users which do not use Images. Could maybe be hidden behind Requires.jl?
Yes, we did consider separating out ImageReferenceTest
to JuliaImages. Just that this package isn't targeted to end-users so with limited time contributing codes, I have to target higher priority tasks... 😢 If this dependency matters a lot and if you want to help with this, I can create an empty project in JuliaImages and maybe you can help it there?
No worries. What is the time frame on getting to 1.0? I probably don't have time right now, but it's definitely an itch I'd like to scratch.
No worries. What is the time frame on getting to 1.0?
Hmmm... It's probably never unless we get a bigger Julia community 🤣 . Just that this package isn't of very high priority on my to-do list and my main focus is still on JuliaImages. Hope you can understand...
Excellent, that means that I can take time to scratch my itch ;-)
And no worries, I do not expect you to do anything; after all, I'm not paying you!
I believe this package has proved its usefulness, and I'd like to push it to its 1.0 stage.
Here are what I have in mind that needs to be done before it's ready:
Core & API changes:
match_reference
that returns aBool
#9 #12match_reference
#47@test_reference
Extensions:
AbstractArray{<:Colorant}
, currently it's restricted to 2D matrixAbstractArray{<:Number}
(and maybe more) typesEtc:
Please comment if you have any other ideas.