Fintasys / emoji_picker_flutter

A Flutter package that provides an Emoji picker widget with 1500+ emojis in 8 categories.

MIT License

154 stars 114 forks source link

Version 2.0 #183

Closed Fintasys closed 5 months ago

Fintasys commented 6 months ago

Version 2.0 (WIP)

https://pub.dev/packages/emoji_picker_flutter/versions/2.0.0-dev.6

Addresses

Closes #142 Closes #163 Closes #165 Closes #166 Closes #170 Closes #176 Closes #177 Closes #156

Improvements

[x] Better customization
[x] Better support for emoji and custom font
[x] Restructure of configurations
[x] Added Search View
[x] Update examples (Also added WhatsApp example)
[x] Add auto-scroll support
[x] Add long-press backspace support
[x] Improve SkinTone Overlay
[x] Updated Readme
[x] Update License to MIT
[x] Add tests

emesterhazy commented 6 months ago

This is marked as closing #171. Can you explain what you did to solve it? In my testing the only way I could fix the issue was by using the Google Fonts library and specifying the Noto Color Emoji Font (i.e. GoogleFonts.notoColorEmoji()). Using the Google Fonts library is a big of a heavyweight solution since it has to load the font separately, and it's around 30 mb.

I tried specifying the Noto Color Emoji font using a string literal thinking that Flutter on Android should be able to access it, at least on Pixel phones, but that didn't fix the issue. Curious to know if you found a workaround.

Fintasys commented 6 months ago

@emesterhazy Ah I get your point. FallbackFonts alone didn't solve the issue unfortunately. Even on my pixel 8 it seems the font is not pre-installed. Adding Google fonts adds around ~15mb, but it's the only way I found it working supporting e.g. frowning face. On iOS although the fallbackFont trick fixed it and plenty of emoji are displayed correctly. To be precise you might be right, it does not fix #171 completely without workaround that already exists.

emesterhazy commented 5 months ago

RE: https://github.com/Fintasys/emoji_picker_flutter/pull/183#issuecomment-1873870976, that's what I suspected 😔. Let's leave #171 open if you don't mind in case we're able to figure out a real fix that doesn't require bundling the font or loading it in via the GoogleFonts library.