31–40 of 108 posts
-"You've built a web app, but your users stick to Excel" I feel that if your users are not using your web app, it's not because they miss the (dated, not exactly intuitive) Excel interface. Seems to me like the wrong solution for the problem
The performance here is amazing. Well done! I'm desperately searching for a way to replace old Handsontable (before they closed source), but the license here for DataGrid XL makes it impossible to easily bring into a large FOSS project. Some ideas for licensing: dual license MIT and commercial. Feed advanced features and support into the commercial while keeping the MIT version fast, performant, extendable.
I think it was handsontable I burned myself on: got client to sponsor/pay for support for a nice open source tool and shortly after they went closed source. Same with caddy, except that time it was my money. Some times I wonder if I should avoid giving money to open source projects because it seems to trigger the idea that one can make a whole lot of more money by selling out.
It's also not very performant. Rendering often forces multiple style/layout recalculations, which is nearly always solvable by having your rendering code better organized. Version 8, when they rewrote cell meta, caused certain cell meta APIs we were calling to take _seconds_ on large tables. Version 9 did not document that the "beforeManualColumnMove" changed the meaning of the indices from "before columns" to "after columns". Undo/redo is implemented incorrectly too, so we had to write that ourselves. These caused real problems that affected our users.
As soon as we get the capacity to switch to something like Datagridxl2 we will.
What's a good FOSS alternative to this for non-commercial projects? I'd like to have a spreadsheet on my site for personal use.
Accessibility is a strong gating factor for some (including me). I don't see it in the docs. The whole thing seems to be missing any ARIA (see https://www.w3.org/TR/wai-aria-practices/examples/grid/dataG... ) Let me know if you want help.
What's a good FOSS alternative to this for non-commercial projects? I'd like to have a spreadsheet on my site for personal use.
I'm impressed by the lack of dependencies and single-file download. One of my use-cases is for offline use, and not via a web app installation -- only assets in an ordinary filesystem directory. Mega-components in single js files are a good step towards that.
Not sure I understand this. Every web app I build is just a set of HTML/CSS/JS files that are served in a static fashion, which means that you could just plop that static folder onto your hard drive, click "index.html", and interact with it normally. I guess routing concerns maybe exist if you just naively hope the URL-based-routing works but it'd be easy to work around this
Accessibility is a strong gating factor for some (including me). I don't see it in the docs. The whole thing seems to be missing any ARIA (see https://www.w3.org/TR/wai-aria-practices/examples/grid/dataG... ) Let me know if you want help.
Do you happen to know of best practices for simulating different disabilities, or some recording of somebody actually using some example well-designed accessible software? A video recording, to me as somebody who can see and hear and move just fine (for now), would help me understand what interaction methods don't work or are a struggle, which interaction methods are intuitive and effective, and which types of conten…
The web accessibility world is complex enough that simulating different methods of access like using screen readers or different font-sizes and doing manual tests for compliance is not particularly feasible if you want to make your content accessible to all.
[1] https://developers.google.com/web/tools/lighthouse [2] https://web.dev/accessibility-scoring/
Earlier quoted context omitted.
Do you happen to know of best practices for simulating different disabilities, or some recording of somebody actually using some example well-designed accessible software? A video recording, to me as somebody who can see and hear and move just fine (for now), would help me understand what interaction methods don't work or are a struggle, which interaction methods are intuitive and effective, and which types of conten…
Lighthouse [1][2] Accessibility audit/ scores can be a good tool to check A11Y issues automatically, and it is fairly easy to integrate into your CI/CD Pipelines to get the report automatically to check for issues/ regression. The web accessibility world is complex enough that simulating different methods of access like using screen readers or different font-sizes and doing manual tests for compliance is not particul…
Looks interesting. I've just been looking at a couple of alternatives to this. We're adding a CSV import feature for our store finder, and the idea is to provide a spreadsheet-like interface where you can just copy and paste your location data instead of uploading a CSV where you need to deal with different delimiters and getting the column orders right etc.