Glide Data Grid
greenfield
Glide Data Grid | greenfield | |
---|---|---|
17 | 17 | |
3,423 | 880 | |
1.7% | 1.8% | |
8.9 | 6.6 | |
3 days ago | 6 days ago | |
TypeScript | TypeScript | |
MIT License | GNU Affero General Public License v3.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.
Glide Data Grid
-
The Design Philosophy of Great Tables (Software Package)
Why do you want to render to canvas?
Perspective seems to be the most performant html table. It is more focused on extremely fast updates than styling, although it looks good.
Glide is a newcomer that also renders to canvas.
https://github.com/finos/perspective
https://github.com/glideapps/glide-data-grid
-
Rendering a Million Rows in React by Drawing
What we are trying to build is a component that will help us to render a million rows in a ReactJs App. We make use of several techniques that are being used by other products such as google sheets and glide data grid app to achieve it.
-
New Renderers for GTK
Can you give examples of better JS renderers?
What is needed for performance of traditional GUI app rendering? I'm particularly interested in table rendering. Glide and Perspective are both canvas based renderers, but I haven't dug into the internals.
[1] https://github.com/glideapps/glide-data-grid
[2] https://github.com/finos/perspective
-
React Data Grid VS Glide Data Grid - a user suggested alternative
2 projects | 8 Jun 2022
-
Glide Data Grid 4.0! Thank you all for your help :)
Much much more...
-
Show HN: Datagridxl2.js – No-nonsense fast Excel-like data table library
We ran into the same issue! We actually implemented a feature we joking call clown-car scrolling to handle this. If you want to steal the basics of it you can see it here: https://github.com/glideapps/glide-data-grid/blob/main/packa...
Feel free to steal and improve, we only enable the clown-car mode when the desired scrollable area is larger than what a browser can support. With our implementation scrolling is still handled by the browser, but the scroll location can be subtly recomputed as you go from time to time. We only do this when interacting with the scrollbar directly to avoid weird artifacts like scrolling feeling faster than normal.
-
Synchronous scrolling for two or more data grids
I maintain glide-data-grid. I'd love to be in consideration for your use case. If you have features that are not supported in our current or the upcoming 4.0.0 release I would love to hear about it.
-
Looking for the best React table component to implement.
Try Glide data grid
-
Data Grid 3.0 — bigger, better, faster!
Homepage
-
Fast, smooth React Data Grid
Home Page / try it now
greenfield
-
New Renderers for GTK
There's Greenfield, an HTML5 Wayland compositor. https://github.com/udevbe/greenfield
There's some fancy bridging modes to run apps in a browser, but the author has also been working on a way to make wasm Wayland apps run directly in the browser tol.
-
Container2wasm: Convert Containers to WASM Blobs
Do any GUI frameworks support WASM?
I've been looking for a way to run GUI applications remotely for a while, specifically on a wlroots compositor. Projects like this (maybe one day) and https://github.com/udevbe/greenfield are interesting since they essentially make access universally accessible.
-
The new desktop Outlook is a bad idea. Here's why
Palm Pre's webOS (2009) is the most famous. After an acquisition by HP (2010-2013), it was acquired by LG's (with patents going to Qualcomm).
Before that was a neat Linux project Pyrodesktop (2007) which was an x11 window manager using Firefox guts to render. There was also a trend of trying to mate Javascript technologies to gnome back then, with efforts like gjs seeing some adoption. I don't know how popular it is, but a spinoff of css was/is used for styling in GNOME for a while.
These days there's tons of web desktop projects. https://github.com/syxanash/awesome-web-desktops . Only sort of in the spirit but i quite adore Greenfield, an html5 Wayland desktop/compositor. https://github.com/udevbe/greenfield
- Kera Desktop: open-source, cross-platform, web-based desktop environment
-
Broadway – support for displaying GTK applications in a web browser
The network is thr computer, yay!
Lower level, but there's also a Wayland compositor being written for the web. Many caveats apply, different effort, but also interesting, https://github.com/udevbe/greenfield
- D3wasm 0.4 – Doom 3 in WASM
-
Think twice before abandoning Xorg. Wayland breaks everything!
> A Wayland-style compositor, on the other hand, seems to be a much higher barrier to entry. ... I don't recall ever seeing "You have to use TWM because AfterStep won't work with your Trident 9440 video card" back in 1998.
All in all, the basics of Wayland are a pretty tight package. https://wayland-book.com/ goes through the pieces, and it's not a super thick read. The system of passing around surfaces is comprehensible, tight, makes sense, and there is very little fluff or barriers here, imo.
Wayland has a common core, but absolutely I'd grant that the various protocols do indeed make it a much less tightly coupled thing, with different compositors having different sets of protocols they support. So yes, some apps that require advanced capabilities run much better in some compositors than others; the compositor choice matters. Sometimes there are multiple competing protocols for the same feature-sets, but usually/historically, wayland-protocols hammers stuff out reasonably quickly & most of this is a matter of time.
Still, this is often easier than the past, where apps would have to each test for extensions & have various fast/regular/fallback codepaths depending on available extensions; not necessarily a hindrance to the window-manager, but a bundle of complexity for everyone else trying to use X11 adequately. The Wayland common primitives, on the other hand, are fairly universally performant & well chosen.
In terms of complexity for window-manager/compositor, the situation is not unlike X11 itself, where yes, a simple window manager (or compositor) is possible to spin up relatively quickly, but where there is a sea of different standards to implement to do a good job. Window manager hints, extended window manager hints, and a plethora of other standards existed around X11 that were up to the window-manager to tackle, and implementing each of those took a lot of time too, if you wanted good support for all apps. Different Wayland compositors also have different support for different protocols, and those are a bit deeper rooted, less superficial than many of the X11 hints (which, if ignored, were less likely to impede use), but the idea is the same: real support to really be decent took work in X11, and it takes work in Wayland.
Where I disagree highly is calling out the hardware here. Wayland is closely tied to kernel fundamentals; any reasonably supported video card will perform adequately under any compositor. (Generally. Certainly some compositors could demand higher standards, such as some of the experimental compositors requiring Vulkan, but generally compositors have very similar, very common requirements.)
> I wonder if it would have made more sense to go with a paired approach-- a single master compositor implementation, with the complicated and more hardware-sensitive stuff involved, and a pluggable window manager that spoke to it.
I like where we are, where there are various toolkits/libraries for implementing. Wlroots, which underpins chiefly Sway (the i3 replacement), has given rise to a variety of other compositors, spanning the gamut from quick/fast/experimental to rich/deep/powerful. libwayland still defines some core ideas, if not implementations. Weston is still available as a reference, although yes it's designed (more or less) to be forked & enhanced, not built to be preserved & built (extensibly) on top of. Wlroots & other alternative toolkits fill this need, & provide a diversity of ideas for how we might get going. Projects like Greenfield, the HTML5 compositor (https://github.com/udevbe/greenfield) demonstrate the diversity we get from not having a single common core technology, are possible because of this belief in protocol & standards over implementations, eased though implementations might be from promoting something like Weston to the one-and-only implementation.
> The whole "nVidia works, but only with the GNOME compositor" sort of stuff reads as a sign that there's way too much involved in there.
We can't look at a anti-plays-well-with-others entity like Nvidia to assess what is/isn't a good idea. Nvidia spent nearly a decade stomping their feet & demanding only their way was ok. The fact that OpenGL itself, what the rock their obstinacy was built around, is somewhat on the way out further should stress how foolish & self-centered this vendor has been. This discompatibility indicates nothing, is no sign, except an indicator of what kind of a company Nvidia is/was (one that obstructed any implementations of well known & common kernel constructs).
- I just learned about a new project called greenfield. We can probably use it to run computer games on android once it is more polished.
- Running GUI apps within Docker containers
-
I want to be able to drag a window from one computer to another
Now consider something like greenfield, a wayland compositor that runs on the browser.
What are some alternatives?
React Data Grid - Feature-rich and customizable data grid React component
daedalOS - Desktop environment in the browser
ag-Grid - The best JavaScript Data Table for building Enterprise Applications. Supports React / Angular / Vue / Plain JavaScript.
ubuntu-vnc-xfce-g3 - Headless Ubuntu/Xfce containers with VNC/noVNC (G3v5).
react-data-table - A responsive table library with built-in sorting, pagination, selection, expandable rows, and customizable styling.
wayvnc - A VNC server for wlroots based Wayland compositors
react-cool-virtual - 😎 ♻️ A tiny React hook for rendering large datasets like a breeze.
gnome-shell - Read-only mirror of https://gitlab.gnome.org/GNOME/gnome-shell
ka-table - Lightweight MIT React Table component with Sorting, Filtering, Grouping, Virtualization, Editing and many more
docker-handbrake - Docker container for HandBrake
canvas-datagrid - Canvas based data grid web component. Capable of displaying millions of contiguous hierarchical rows and columns without paging or loading, on a single canvas element.
awesome-web-desktops - Websites, web apps, portfolios which look like desktop operating systems