Live data from Hacker News

Show HN: X-spreadsheet – A JavaScript canvas spreadsheet for web

github.com

101–108 of 108 posts

Re: Show HN: X-spreadsheet – A JavaScript canvas spreadsheet for web

#101
post #9
post #3

X Spread Sheet XSS probably not the best abbreviation

I have literally never seen spreadsheet abbreviated as SS. Spreadsheet is one word. Your comment comes off as trying too hard to be negative. Try some actual constructive feedback why don't ya?

I don't abbreviate it that way either, but the author does on the page itself!

Re: Show HN: X-spreadsheet – A JavaScript canvas spreadsheet for web

#102
post #9

Earlier quoted context omitted.

I have literally never seen spreadsheet abbreviated as SS. Spreadsheet is one word. Your comment comes off as trying too hard to be negative. Try some actual constructive feedback why don't ya?

>> I have literally never seen spreadsheet abbreviated as SS. I thought it was pretty common. I guess it depends on the environment you work in.

How should the spreadsheet be abbreviated ? 's' first letter

Re: Show HN: X-spreadsheet – A JavaScript canvas spreadsheet for web

#103
post #4

I think a description of why canvas was used would be nice in the README. My (probably naive) view is that browsers are pretty good at table-ish layouts so it’d be great to know why canvas was chosen.

Every DOM cell is a very large object with thousands of properties (most of which a spreadsheet will never use). A cell in a spreadsheet contains a handful of properties and immediate render works much better for less complex layouts (VS Code moved from DOM to Canvas in the terminal because layout performance was better with much less complexity).

Another big reason is wasm. It would be a big performance increase to write the layout engine in Rust/wasm. Native performance would be great.

Re: Show HN: X-spreadsheet – A JavaScript canvas spreadsheet for web

#104
post #92

Earlier quoted context omitted.

Although canvas does do grayscale anti-aliasing, this particular app is blurry because the canvas is being rendered at a lower resolution than your screen. To make it crisp, the author would have to set the canvas' javascript canvas.width property to be twice the canvas' css canvas.style.width property.

Yes, oversampling will reduce blurriness but it will be there anyway. ClearType is there for the purpose. Yet all that with the price of memory and CPU consumption - number of pixels to rasterize on 192 PPI monitor is four times of the one with "standard" 96 PPI.

It's not oversampling, it's native sampling. On high DPI displays browsers automatically apply a zoom to the page, so the canvas ends up being a smaller size that gets blown up. You have to detect this and create the canvas bigger to begin with to counteract this.

Re: Show HN: X-spreadsheet – A JavaScript canvas spreadsheet for web

#106

I really like this and I can see the potential, but I certainly miss being able to type directly into the cell as opposed to double-clicking on it first. F2 should also enable editing and toggle between Edit and Enter modes. It's hard to spend more than a few seconds on the demo when my very first interaction with it hits a major roadblock like that.

input a-z1-9 to edit or F2 or double-clicking

Re: Show HN: X-spreadsheet – A JavaScript canvas spreadsheet for web

#107
post #94

This is amazing! I'm doing a deep dive into the code now to see how the extensibility is done. Some folks here might be interested in Stencila Sheets too ( https://stenci.la/blog/2017-08-features-stencila-sheets/ , https://stenci.la/blog/introducing-sheets/ ), https://github.com/stencila/stencila/tree/develop/src/sheet . It's a web-based spreadsheets where cells can execute other programming languages, such as R or P…

What's happening with Stencila? I only found it recently, and it looks like a potentially fantastic project, but development seems to have slowed right down.

Hi yoz, Stencila dev here. Thank for your interest. We're definitely still around!

Development of the frontend has indeed slowed down while we focus on more lower-level "backend" tools for research reproduciblity (e.g. https://github.com/stencila/dockter).

But were currently recruiting for a frontend designer and an engineer. So will be definitely be getting back to the interfaces soon!

Post reply on HN