dialog-polyfill
sciter
dialog-polyfill | sciter | |
---|---|---|
8 | 85 | |
2,432 | 2,560 | |
0.2% | -0.1% | |
0.0 | 0.0 | |
3 months ago | about 1 year ago | |
JavaScript | C++ | |
BSD 3-clause "New" or "Revised" License | - |
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.
dialog-polyfill
-
The <Dialog> Element
> - Z-index has no effect in the top-layer. No need to compete for a higher z-index.
This is the kind of boring feature that can end up saving huge amounts of developer time. Z-indexing in CSS is kind of annoying and I've seen projects just detach dialogs from their normal position in the DOM entirely to get around stacking errors before.
----
Minor question:
> - There is only one `top-layer` but it can have many children. Last opened === current element on top.
Is this true? The spec says:
> The top layer is an ordered set of elements, rendered in the order they appear in the set. The last element in the set is rendered last, and thus appears on top.
I'm still playing around with `dialog` elements, so you may well be right, I'm just having trouble finding the actual spec rules about what happens when there are multiple dialogs and they're being simultaneously manipulated.
----
> - Not supported in Safari <= 15.3
Worth noting that there is a polyfill (https://github.com/GoogleChrome/dialog-polyfill), but that the polyfill comes with some fairly large limitations, specifically that they don't advise dialogs be used as children of elements with their own stacking context.
This is reasonable, but also... my first thought when I originally ran into `dialog` was "finally I can stop worrying about which of my elements create new stacking contexts!" -- so it does decrease the usefulness quite a bit.
- La espera terminó: el elemento <dialog> alcanza pleno soporte
-
Is learning Vue instead of React a mistake?
Yeah, Safari is pretty often behind the other popular browsers. But, you can generally predict that by looking for any given feature on MDN and check the "Browser compatibility" section. Sometimes, there are polyfills available that sort of "force" a feature to work across every browser.
-
Can we use <dialog> yet?
(Searching for "polyfill " will usually get you good results - in this case the first result appears to be a library maintained by the Chrome team: https://github.com/GoogleChrome/dialog-polyfill )
-
New WebKit Features in Safari 15.4
This does not make sense. Of course new functionality won't work on old browsers. is easy to polyfill well: https://github.com/GoogleChrome/dialog-polyfill
-
Just a single tag can create this dialog box. <dialog> tag with open attribute created this simple styled centered box. => <dialog open>This is a dialog box</dialog>
GoogleChrome / dialog-polyfill
- Using for Menus and Dialogs Is an Interesting Idea
sciter
- Show HN: Open Source TailwindCSS UI Components
-
Show HN: Dropflow, a CSS layout engine for node or <canvas>
> wondering if css and svg could be used as abstraction over graphics and UI libraries
There's another project called Sciter that uses CSS to target native graphics libraries: https://sciter.com
> I wonder how hard it was to implement css. I've heard it can be pretty complex.
It was hard, but the biggest barrier is the obscurity of the knowledge.
Text layout is the hardest, because working with glyphs and iterating them in reverse for RTL is brain-breaking. And line wrapping gets really complicated. It's also the most obscure because nobody has written down everything you need to know in one place. After I finished block layout early on, I had to stop for a couple of years (only working a few hours a week though) and learn all of the ins, outs, dos, and don'ts around shaping and itemizing text. A lot of that I learned by reading Pango's [1] source code, and a lot I pieced together from Google searches.
But other than that, the W3C specifications cover almost everything. The CSS2 standard [2] is one of the most beautiful things I've ever read. It's internally consistent, concise, and obviously the result of years of deliberation, trial and error. (CSS3 is great, but CSS2 is the bedrock for everything).
[1] https://gitlab.gnome.org/GNOME/pango/
- Ask HN: Fastest cross-platform GUI stack/strategy
- Bringing Back Horizontal Rules in HTML Select Elements
-
Immediate Mode GUI Programming
otherwise, if we have only retained mode as in browsers, we will need to modify the DOM heavily and create temporary elements for handles.
[1] https://sciter.com
- This year in Servo: over 1000 pull requests and beyond
-
Rusty revenant Servo returns to render once more
I've still never used it but I've long been curious about Sciter:
https://sciter.com
- Ode to the M1
-
So you want to write a GUI framework (2021)
These bullet points are exactly what I did in Sciter (https://sciter.com)
- Windowing
-- Tabs
-- Menus
-- Painting
-- Animation
-- Text
-The compositor
-Handling input
-- Pointer input
-- Keyboard input
- Accessibility
- Internationalization and localization
- Cross-platform APIs
- The web view
- Native look and feel
On top of that DOM and CSS implementations to achieve declarative UI. And JS as a languuage behind UI - declarative in some sense way of defining UI behavior.
-
Servo, the parallel browser engine written in Rust
I'm not sure if it can support all the libraries but yes it can be used to make desktop apps. Theres also Sciter.
https://sciter.com/
What are some alternatives?
a11y-dialog - A very lightweight and flexible accessible modal dialog script.
webview - Tiny cross-platform webview library for C/C++. Uses WebKit (GTK/Cocoa) and Edge WebView2 (Windows).
kill-sticky - Bookmarklet to remove sticky elements and restore scrolling to web pages!
qt - Qt binding for Go (Golang) with support for Windows / macOS / Linux / FreeBSD / Android / iOS / Sailfish OS / Raspberry Pi / AsteroidOS / Ubuntu Touch / JavaScript / WebAssembly
autoprefixer - Parse CSS and add vendor prefixes to rules by Can I Use
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.
webmidi-test - 🎵 Web MIDI Test page with basic device hotplug support
flexboard - React component library for re-sizable sidebars
caniuse - Raw browser/feature support data from caniuse.com
RmlUi - RmlUi - The HTML/CSS User Interface library evolved
devadvance
NanoGUI - Minimalistic GUI library for OpenGL