Several none breaking improvement proposals.

[rydmike]

Included updates

• AppBars foreground and background colors can be fully customized, but follow active Theme by default. This also also applies to the image cropper plugin for Android.
• Migrated all usage of deprecated FlatButton to TextButton, while keeping the deprecated buttons used style. The deprecated buttons will be totally removed from Flutter SDK soon.
• Changed the print in LogUtil to debugPrint, so it does not drop some print outs,. Also added build mode check so it does not log in release builds. The console console can also be seen in release builds, so we usually do not want any prints in it then.
• Removed new keyword found in a few places, since it is not recommended to be used in Dart anymore.
• Used dartfmt in all files to not loose points on not using it the pub.dev score. Tried to catch all, maybe still issues in some places in the file. Pub.dev will point is in the direction for any remaining fixes. Let's try to get the pub.dev score a bit higher. :)
• I added more public API comments to increase doc coverage % in pub.dev score.
• Made some minor typo corrections whenever I noticed them.
• Gitignore addition with .idea and fvm and some other things to ignore

Suggestions for future improvements (not included here)

• Add a though linter setup so we catch some minor code smells and minor issues in the code, and fix them. Some fixes (like const usage) could potentially even improve performance a bit, not that it is really needed, it is not slow now either. I can help you with this if you want to. This can be done as a none breaking change as well.
• Consider changing the singleton configuration file to be just a final const constructor configuration class that you just pass in. This would be more inline with the Flutter style and patterns. Introducing this would be breaking change. I can help you with this too if you like.
• Perhaps for consistency with the image cropper, the close without selecting any images could use the (x) icon and the (Select) button could be just the check icon, like the image cropper. It would be less text and things to translate. This would be a breaking change in the sense the Select txt is no longer needed, nor its separate color. Style wise it would also be a minor change.

[rydmike]

By the way I just noticed the camera plugin by Flutter team just today got a spanking new version 0.9.0. We should probably try it out as well and upgrade to it too. Apparently the new plugin is an Android rewrite with many fixes. https://pub.dev/packages/camera/changelog

[weta-vn]

@rydmike Thank you very much about commit and a lot of improvement suggestions. We'll confirm & merge your commit into next release!

[rydmike]

Thanks @weta-vn for merging my pull request. I noticed you already tested camera 0.9.1, I just did as well and noticed it seemed to work OK and not have any compatibility issues.

I also noticed you are working on many other improvements, that you also just merged, nice work keep it up!

I will open another issue where we can discuss if you want to make a linting setup for this package, I can explain and demonstrate what is involved, unless you are already very familiar with Dart and Flutter linting of course, then I obviously don't need to explain it.

I really like this package that you have made, it composes existing native packages nicely for a use case with combined camera and photo library in the way it should be. Well it fits most of my my use cases very well. I have not seen any other good ones like it. I was thinking of writing one myself when I found this one. A friend and I are considering using your package in a small indie production side-project of ours.

I think this package has a lot of potential to become much more popular and generally used. If you want that, I could help you with it. I think it needs some additions on:

• Good linting, to help with finding some minor code/style potential issues.
• Write tests and use automated test coverage report. Yeah I know, writing tests is a pain, but really good to have once they are done. I could potentially help a bit.
• A CI/CD build test pipe with GitHub actions, to automatically build it and run tests when merging pulls or pushing updates.
• When you think the package is more ready for broader recognition, you could promote it a bit more too. I'd be happy to help a bit. I'm no Flutter superstar, but I do know quite a few of them and probably 90% of my +2000 Twitter followers are Flutter developers, so I could promote it on Twitter later too if you like.

Are you on Twitter? We could talk more there in direct messages if you are interested. My Twitter handle is same as here @RydMike (https://twitter.com/RydMike).

Just some ideas for further collaboration if you are interested.

[rydmike]

Cool @weta-vn I just saw that you published a new version with the above pull and your own improvements, plus the new camera package - nice work, thanks! 👍🏻

The score also got up 10 points as I expected, plus it now has a bit more API doc comments too. Those are of course easy to improve further by adding more comments to public APIs. BTW the linter I suggested also detects where they are missing and can tell you about missing ones.

I compared the score and API doc coverage before and after this update, just out of curiosity 😃 :

[weta-vn]

@rydmike Thank you very much. Sorry about late reply because we have urgent tasks in other project. We'll confirm your suggestion as soon as possible then discuss with you about improvement points. Of course, we want to make package better, and more people know and use it to make amazing apps. We're not on Twitter, but we'll join it soon. Thank you again.