Android specific opencv helper

[lu-zero]

The current code works in android but since some optional parts use awt and that triggers lots of misleading warnings and the debugger is set on hold for each awt import.

Probably would be possible either replace the helper with a version w/out the awt code or replace such code with android-specific one (Rect vs Rectangle and such).

[saudet]

Would you have more concrete proposals? There is no such thing as a preprocessor in Java.

[lu-zero]

The simplest way is to add to the build system either the awt_helper or the
android_helper depending on the target and inherit from a common_helper
with the shared part.

On Wed, Jul 30, 2014 at 3:25 PM, Samuel Audet notifications@github.com
wrote:

Would you have more concrete proposals? There is no such thing as a
preprocessor in Java.

—
Reply to this email directly or view it on GitHub
#12 (comment)
.

[saudet]

Could you explain more concretely what is it you are proposing? Would we have like opencv-common.jar and mutually exclusive opencv-awt_helper.jar and opencv-android_helper.jar? How would that work with Maven?

[lu-zero]

Something along the lines of

<excludes>
   <exclude>**/android*.java</exclude>
</excludes>

and

<excludes>
   <exclude>**/awt*.java</exclude>
</excludes>

[saudet]

I meant, what are we going to do with the generated artifacts on the repository? I guess we could create submodules, so what directory structure do you propose to put the pom.xml files in? javacpp-presets/opencv/android_helper and javacpp-presets/opencv/awt_helper? Please be more specific, thank you

[lu-zero]

probably we can have a pattern like javacpp-presets/{library}/resource/{platform}/code

[saudet]

Resources cannot be Java code. That must go in the java subdirectory.

Anyway, creating submodules just for that isn't worth the trouble. I should have created that as a utility class from the start. This way, in Java SE we use the AWT class, and not on Android, so we don't get warnings or errors. Tell you what, if you come up with equivalent code for Android, we'll break backward compatibility and put the AWT code in its own utility class, because it's a feature people have been wanting for years:
https://code.google.com/p/javacv/issues/detail?id=67
https://code.google.com/p/javacv/issues/detail?id=68
Breaking compatibility for a feature that everyone wants is worth it I think. :)

[lu-zero]

I do agree!

[saudet]

Hi, it's been a while, but I've finally figured out something nice. Let me know what you think of the latest changes in these commits: 0574e66
bytedeco/javacv@7ee75f8
Thanks!!

[lu-zero]

I had been horribly busy as well =/ I'll try to check if the people using JavaCV can update to this version and try. Thanks a lot!

[saudet]

Changes included in the -0.11 release. Check out the details here: http://bytedeco.org/news/2015/04/04/javacv-frame-converters/ Let me know when you have some free time to work on something, thanks!