Fab button as been changed to a '+' icon for not using same icons at different place. In addition, it could help to understand the action behind the FAB.

for kids :

default :

I was looking for a color picker in F-Droid for an app I'm writing, and it would be perfect to use CameraColorPicker, so I implemented the OpenIntents PICK_COLOR action for the ColorPickerActivity. Hopefully this can be useful to others as well.

http://www.openintents.org/action/org-openintents-action-pick-color/

This MR adapt the palette list for kids.

In the kids version of the app, the palettes are now displayed in a grid. The names of the palette are no longer shown.

Here is a screenshot of the default version:

Here is a screenshot of the kids version:

@tbarthel-fr Compared to my last MR for the color items, I managed to share more code between product flavors. If this is OK for you, I will probably factorize the code for the color items =)

This MR is an attempt to adapt the color item lists for kids.

In the kids version of the app, the color items are now displayed as a grid. The hexadecimal codes are no longer shown. And long press actions for copying the hexa codes to the clip board has been disabled.

Here are some screenshots of the default version:

And here are some screenshots of the kids version:

Once this MR is validated, I will adapt the palette lists in the same way =)

Animations has been added for every users.

In addition, drop figure has been added for kids and used in the ic_launcher as well as empty view indicator.

icons:

for kids :

default :

In the kid version, the color details display the quantity of red, green and blue in the selected color.

In the adult version, the color details display the hexadecimal, rgb and hsv code.

In the kid version, the instruction is represented as an image, and a default name is used.

In the default version, the instruction is in plain text, and the name of the palette is choose by the user from a dialog.

Note: the floating action button is now only displayed when at least one color has been added to the palette creator.

In the kid version of the app, the dialog displayed to confirm the deletion of a color or of a palette are now text free.

Default version:

Version for kids:

Using your camera to pick a color is a great capability that could be utilized by other apps. The pull request https://github.com/tvbarthel/CameraColorPicker/pull/32 is one way to do that implementation that does not get in the way of the existing behavior of CameraColorPicker. Should that be merged in, or is there a better solution?

The xxxActivityFlavor are hooked to the activity methods to change the title or the menu.

For the kid version, the activity (except the MainActivity) have no titles. For the kid version, the ColorDetailActivity and the PaletteDetailActivity no longer display a share action nor an edit action.

There is a release of version 0.0.7 of Camera Color Picker in Play Store that has no tag here on GitHub. In order to release the app on F-Droid it would be nice to have tags for every version that should be released (every stable version). The process could then be automated.

Thanks!

Describe the bug I found that when I put the phone on the table and turn on the flash before sampling the color, I can only collect black

Context

• Device: [galaxy a6s]
• OS version: [Android 8.1.0]
• App version: [0.0.7]

How to reproduce Steps to reproduce the behavior:

1. Install CameraColorPicker and open
2. Click the sampling button in the lower right corner
3. put the phone on the table
4. Turn on the flashlight
5. Sampling color

Expected behavior The color should be sampled as normally as when the flashlight is not on.

Screenshots Recorded video see attachment (This is a comparison video. The first half is when the flashlight is not on, and the second half is when the flashlight is on) 20191218152301.zip

I wrote below code for getting top left color but it is not working as expected.

addColorFromYUV420(data, mSelectedTopLeftColor, (i * POINTER_RADIUS + j + 1), POINTER_RADIUS, POINTER_RADIUS, mPreviewSize.width, mPreviewSize.height);

:app:compileFossAdultReleaseSources
:app:lintVitalFossAdultRelease
/CameraColorPicker_tvbarthel/CameraColorPicker/app/src/main/res/values/strings.xml:6: Error: "main_activity_title" is not translated in "fr" (French) [MissingTranslation]
    <string name="main_activity_title">@string/app_name</string>
            ~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "MissingTranslation":
   If an application has more than one locale, then all the strings declared
   in one language should also be translated in all other languages.

   If the string should not be translated, you can add the attribute
   translatable="false" on the <string> element, or you can define all your
   non-translatable strings in a resource file called donottranslate.xml. Or,
   you can ignore the issue with a tools:ignore="MissingTranslation"
   attribute.

   By default this detector allows regions of a language to just provide a
   subset of the strings and fall back to the standard language strings. You
   can require all regions to provide a full translation by setting the
   environment variable ANDROID_LINT_COMPLETE_REGIONS.

   You can tell lint (and other tools) which language is the default language
   in your res/values/ folder by specifying tools:locale="languageCode" for
   the root <resources> element in your resource file. (The tools prefix
   refers to the namespace declaration http://schemas.android.com/tools.)

1 errors, 0 warnings
:app:lintVitalFossAdultRelease FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:lintVitalFossAdultRelease'.
> Lint found fatal errors while assembling a release target.
  
  To proceed, either fix the issues identified by lint, or modify your build script as follows:
  ...
  android {
      lintOptions {
          checkReleaseBuilds false
          // Or, if you prefer, you can continue to check for errors in release builds,
          // but continue the build even when errors are found:
          abortOnError false
      }
  }
  ...

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

I have no idea how publishing to F-Droid works, but I just noticed that the resolution of #33 is not published there. It would be nice to have that in F-Droid.