mirror of
https://github.com/block/buzz.git
synced 2026-11-01 06:51:17 +00:00
85edc0572a
Brings the Flutter app's emoji and thread surfaces up to desktop parity. ## Emoji - **Full emoji-mart dataset** generated from the same `@emoji-mart/data` set desktop uses (1,870 emoji, 8 categories), committed as an asset — so shortcodes, names, and keywords are identical across clients. `just mobile-emoji-data` regenerates it. - **Rebuilt the tray**: search (a Dart port of desktop's tiered `emojiSearch` ranking, extended to names and keywords), a frequently-used section, and one continuous scroll with pinned section headers. The category rail is a shortcut into that list, not a page switcher, and spans the full width the search field uses. Custom emoji share the native glyph size and cell. - **Reaction pills** match desktop's geometry, and the count shows at 1. - **Emoji-only messages** render at 36px with 1.45em inline custom emoji, matching desktop's `emojiOnly` treatment. - **Positive-emoji burst** ported from desktop's `EmojiBurstProvider`, suppressed under reduced motion. ## Threads - **Top-down layout** — head first under the app bar, replies flowing down, like desktop's thread panel. The old reversed list bottom-anchored the content and jammed the head against the composer. - **Tap a channel message to open its thread**; long-press still opens the action sheet. - **Live reactions.** The thread's relay query is one-shot and its `kinds` filter carries only content rows, so a reaction event could not reach an open thread at all, and `allMessages` was a snapshot frozen when the route was pushed — a new pill only appeared after leaving and re-entering, which refetched. The live channel events are now unioned into the thread's list. The burst is also route-guarded, since the channel timeline stays mounted underneath and was claiming it first. - The `+` affordance follows the channel: replies stay bare until they carry a reaction, and the head keeps a standing `+`. ## Keyboard A deliberate downward drag past ~48px dismisses the keyboard; short scrolls leave it alone. Applies to the channel list, the thread list, and the compose bar (via a raw `Listener`, so it can't steal the field's tap or selection drags). True finger-tracking dismissal is out of scope — Flutter only offers `manual`/`onDrag`, and 1:1 tracking needs a native `UIScrollView` proxy plus Android's `WindowInsetsAnimationController`. ## Testing `just mobile-check` and `just mobile-test` pass (965 tests). New coverage for emoji search ranking, dataset parsing, the emoji-only predicate, tray scroll/rail behavior, reaction pills and the burst, and both thread fixes above. `just ci` green. --------- Signed-off-by: kenny lopez <klopez4212@gmail.com> Signed-off-by: npub12zsjdqx8dud99s9h47xmk9lq93vryf7zjrae8wdrmma52cg5yglseyulst <50a12680c76f1a52c0b7af8dbb17e02c583227c290fb93b9a3defb456114223f@buzz.block.builderlab.xyz> Signed-off-by: klopez4212 <klopez4212@gmail.com> Co-authored-by: npub12zsjdqx8dud99s9h47xmk9lq93vryf7zjrae8wdrmma52cg5yglseyulst <50a12680c76f1a52c0b7af8dbb17e02c583227c290fb93b9a3defb456114223f@buzz.block.builderlab.xyz>
92 lines
2.7 KiB
Dart
92 lines
2.7 KiB
Dart
/// The emoji that earn a particle burst.
|
|
///
|
|
/// Ported verbatim from `POSITIVE_EMOJI_PARTICLES` in
|
|
/// `desktop/src/shared/ui/EmojiBurstProvider.tsx`. Only affirmation reacts
|
|
/// celebrate — a 😢 or 👎 shouldn't throw confetti — so the three groups below
|
|
/// are the whole gate, and both clients must agree on them or the same reaction
|
|
/// bursts on one device and not the other.
|
|
library;
|
|
|
|
const heartParticleEmojis = <String>[
|
|
'\u{2764}\u{FE0F}', // ❤️
|
|
'\u{1FA77}', // 🩷
|
|
'\u{1F9E1}', // 🧡
|
|
'\u{1F49B}', // 💛
|
|
'\u{1F49A}', // 💚
|
|
'\u{1FA75}', // 🩵
|
|
'\u{1F499}', // 💙
|
|
'\u{1F49C}', // 💜
|
|
'\u{1F90E}', // 🤎
|
|
'\u{1F5A4}', // 🖤
|
|
'\u{1FA76}', // 🩶
|
|
'\u{1F90D}', // 🤍
|
|
'\u{2764}\u{FE0F}\u{200D}\u{1F525}', // ❤️🔥
|
|
'\u{2764}\u{FE0F}\u{200D}\u{1FA79}', // ❤️🩹
|
|
'\u{1F496}', // 💖
|
|
'\u{1F495}', // 💕
|
|
'\u{1F497}', // 💗
|
|
'\u{1F493}', // 💓
|
|
'\u{1F49E}', // 💞
|
|
'\u{1F498}', // 💘
|
|
'\u{1F49D}', // 💝
|
|
'\u{2763}\u{FE0F}', // ❣️
|
|
'\u{2665}\u{FE0F}', // ♥️
|
|
];
|
|
|
|
const positiveReactionParticleEmojis = <String>[
|
|
'\u{1F44D}', // 👍
|
|
'\u{1F44F}', // 👏
|
|
'\u{1F64C}', // 🙌
|
|
'\u{1F64F}', // 🙏
|
|
'\u{1F4AF}', // 💯
|
|
'\u{1F525}', // 🔥
|
|
'\u{2728}', // ✨
|
|
'\u{2B50}', // ⭐
|
|
'\u{1F31F}', // 🌟
|
|
'\u{1F389}', // 🎉
|
|
'\u{1F38A}', // 🎊
|
|
'\u{1F973}', // 🥳
|
|
'\u{1F680}', // 🚀
|
|
'\u{1F4AA}', // 💪
|
|
];
|
|
|
|
const positiveFaceParticleEmojis = <String>[
|
|
'\u{1F600}', // 😀
|
|
'\u{1F603}', // 😃
|
|
'\u{1F604}', // 😄
|
|
'\u{1F601}', // 😁
|
|
'\u{1F60A}', // 😊
|
|
'\u{1F607}', // 😇
|
|
'\u{1F642}', // 🙂
|
|
'\u{1F60D}', // 😍
|
|
'\u{1F929}', // 🤩
|
|
'\u{1F970}', // 🥰
|
|
'\u{1F618}', // 😘
|
|
'\u{1F60B}', // 😋
|
|
'\u{1F60E}', // 😎
|
|
'\u{1F602}', // 😂
|
|
'\u{1F923}', // 🤣
|
|
];
|
|
|
|
const positiveEmojiParticles = <String>[
|
|
...heartParticleEmojis,
|
|
...positiveReactionParticleEmojis,
|
|
...positiveFaceParticleEmojis,
|
|
];
|
|
|
|
/// Emoji presentation selectors carry no meaning for this comparison, and the
|
|
/// same emoji reaches us with and without one depending on where it came from
|
|
/// (the emoji-mart dataset, a hand-typed reaction, an older client). Desktop
|
|
/// gets away with exact set membership because its picker is the only producer;
|
|
/// mobile reactions also arrive off the wire, so fold the selector away.
|
|
String _foldSelectors(String emoji) =>
|
|
emoji.trim().replaceAll('\u{FE0F}', '').replaceAll('\u{FE0E}', '');
|
|
|
|
final Set<String> _positiveEmojiParticleSet = {
|
|
for (final emoji in positiveEmojiParticles) _foldSelectors(emoji),
|
|
};
|
|
|
|
/// Whether [emoji] should burst. Mirrors desktop's `isPositiveEmojiParticle`.
|
|
bool isPositiveEmojiParticle(String emoji) =>
|
|
_positiveEmojiParticleSet.contains(_foldSelectors(emoji));
|