Show HN: React-data sheet, Excel-like spreadsheet component • Hacker News Board

Re: Show HN: React-data sheet, Excel-like spreadsheet component

#91

Post by aargh_aargh » Wed, Apr 05, 2017, 2:23 PM UTC

audiotalo wrote: post #34

Nice! Lately I have been looking into javascript grid components and have not found a good solution. What would be a good javascript grid component that satisfies the following: 1. Integrates easily with Vue 2. Has sorting 3. Has grouping 4. Has inline editing (formulas are not required)? OTOH I would be happy with a software that is basically a web frontend for Postgres that can be customised in a way that a client…

> OTOH I would be happy with a software that is basically a web frontend for Postgres that can be customised in a way that a client can only see and edit specific fields based on assigned rights.

Take a look at Adminer [1] and their Adminer Editor [2] (the later is what you're asking for).

[1] http://adminer.org/ [2] https://www.adminer.org/en/editor/

Re: Show HN: React-data sheet, Excel-like spreadsheet component

#92

Post by chrishere » Wed, Apr 05, 2017, 5:03 PM UTC

Chris Spilka, CEO at Handsontable here.

It's great to see that Nadim started to work on this spreadsheet for React. It's for sure an ambitious project and will require a lot of community support and love;) We at Handsontable benefit from the open source since 2012 and most of ~3400 closed issues to date were reported by users who actually care about our product and/or make a good use of it.

Here are some thoughts which anyone who attempt to create an online spreadsheet from scratch should take into account:

- Separate data logic from the view. Sounds like a cliché but actually it will save you plenty of time when you start adding more and more features to the pile. - Get to know how people want to use your app. Focus on their workflow not on your (false) assumptions. - Don't mix up features typical for grids with those present in spreadsheets. Focus on what's important, not on Excel's blows and whistles. Grouping is OK. Parent-child structure not necessarily. - Don't underestimate the effort connected with building such component. Ask the community for help. Give them a great product in return. - At some point your "data engine" will work just like a small, specialised database (CRUD + search/filter/sort). - Think of how you will scale your solution both horizontally (new technologies) and vertically (new features). Our customers have completely remote requirements in terms of using Handsontable with specific databases, back-ends, JS/CSS frameworks, devices (not to mention different formats of numbers, languages etc.)

Offtopic: In the contemporary history we have seen a lot of attempts to make an ultimate online spreadsheet. Most of those projects are now long gone (see https://www.lifewire.com/best-free-online-spreadsheets-34862...). That was before Google acquired 2Web Technologies and created its own, free solution upon it. The trend is to create spreadsheet-based projects for certain use cases just like Quip, Smartsheet, Airtable and more.

Anyway, fingers crossed for your project. I will be happy to share with you our best practices and thoughts from our work with Handsontable (write @ chris [at] handsoncode.net).

Cheers, Chris

Re: Show HN: React-data sheet, Excel-like spreadsheet component

#93

Post by kamranasif » Fri, Apr 07, 2017, 6:52 PM UTC

TheAceOfHearts wrote: post #74

kamranasif wrote: post #60

Earlier quoted context omitted.

Maintainer of FDT2 here. One of the reasons we decided to maintain this library is that it does virtualize both columns and rows. We use it at Schrodinger for our enterprise platform and have demo'd support of billions of rows. This is possible because we don't use a wrapper DOM element to handle scrolling. Right now we are migrating all the state to Redux for better maintainability and performance and hope to make e…

I've gotta admit I'm weary of the usefulness of a table with billions of rows. Doesn't that just drown the user with noise? Have you explored alternative means of presenting the data? Billions of anything sounds like too much information for any human to make sense of and process. Could you explain a bit about your use-case?

Our application is similar to excel/google spreadsheets. We don't expect the user to scroll through all that data, but we give tools to do sorting, filtering, plotting, etc. over that data.