synth-android
rfcs
| synth-android | rfcs | |
|---|---|---|
| 4 | 1 | |
| 996 | 75 | |
| 0.0% | - | |
| 0.0 | 6.7 | |
| about 3 years ago | 9 days ago | |
| Kotlin | ||
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
synth-android
-
Show HN: Dropflow, a CSS layout engine for node or <canvas>
CRED had it in their app for a while, their library is open source
https://github.com/CRED-CLUB/synth-android
-
Anyone knows a good neumorphism type UI library in Android Kotlin I could use for inspiration or just use outright in the app.
There's https://github.com/CRED-CLUB/synth-android
- Any Idea how to achieve this stacking behaviour, this is not bottom sheet dialog
- We at CRED have launched our first open-source library: Synth - the UI Kit that powers our neumorphic design. Feedback and contributions are much appreciated!
rfcs
-
Show HN: Dropflow, a CSS layout engine for node or <canvas>
To reply mostly with my WPT Core Team hat off, mostly summarising the history of how we've ended up here:
A build script used by significant swaths of the test suite is almost certainly out; it turns out people like being able to edit the tests they're actually running. (We _do_ have some build scripts — but they're mostly just mechanically generating lots of similar tests.
A lot of the goal of WPT (and the HTML Test Suite, which it effectively grew out of) has been to have a test suite that browsers are actually running in CI: historically, most standards test suites haven't been particularly amenable to automation (often a lot of, or exclusively, manual tests, little concern for flakiness, etc.), and with a lot of policy choices that effectively made browser vendors choose to write tests for themselves and not add new tests to the shared test suite: if you make it notably harder to write tests for the shared test suite, most engineers at a given vendor are simply going to not bother.
As such, there's a lot of hesitancy towards anything that regresses the developer experience for browser engineers (and realistically, browser engineers, by virtue of sheer number, are the ones who are writing the most tests for web technologies).
That said, there are probably ways we could make things better: a decent number of tests for things like Grid use check-layout-th.js (e.g., https://github.com/web-platform-tests/wpt/blob/f763dd7d7b7ed...).
One could definitely imagine a world in which these are a test type of their own, and the test logic (in check-layout-th.js) can be rewritten in a custom test harness to do the same comparisons in an implementation without any JS support.
The other challenge for things like Taffy only targeting flexbox and grid is we're unlikely to add any easy way to distinguish tests which are testing interactions with other layout features (`position: absolute` comes to mind!).
My suggestion would probably be to start with an issue at https://github.com/web-platform-tests/rfcs/issues, describing the rough constraints, and potentially with one or two possible solutions.
What are some alternatives?
neumorphism - Try to Neumorphism in Android (Just experimental!! 🧪)
Alerter - An Android Alerting Library
Spotlight - Android Library that lights items for tutorials or walk-throughs etc...
neumorphism-ui-bootstrap - Neumorphism inspired UI Kit: web components, sections and pages in neumorphic style built with Bootstrap CSS Framework
Aesthetic Dialogs for Android 📱 - 📱 An Android Library for 💫fluid, 😍beautiful, 🎨custom Dialogs.
yoga - Yoga is an embeddable layout engine targeting web standards.
wpt - Test suites for Web platform specs — including WHATWG, W3C, and others
sciter - Sciter: the Embeddable HTML/CSS/JS engine for modern UI development