Conversation
| [ "d", "SheetStr Demo" ], | ||
| [ "data", "Sheet1", "J", "25", "3" ], | ||
| [ "data", "Sheet1", "J", "26", "5" ], | ||
| [ "data", "Sheet1", "J", "27", "=SUM(J25:J26)" ] |
There was a problem hiding this comment.
are these formula's standardized? also what about custom formulas, are they out of scope for the nip?
|
It may be a good idea to choose a list to hold all sheet references the user is interested in, because one can't rely on authors filter and anyone can add the user to a |
Yep, I was thinking about an unbound list that just points to all "accepted" spreadsheets. |
| ["data", "<sheet name>", "<column letter>", "<row number>", "<value>"], | ||
| ["data", "<sheet name>", "<column letter>", "<row number>", "<value>", "<style>"], |
There was a problem hiding this comment.
instead of 3 tags and requiring the decoding of column letters => column number we could add a ["sheet", "Sheet Name"] tag, and then do 0:0:1 to refer to sheet tag 0, and the cell at position row 1 (y), column 0 (x)
There was a problem hiding this comment.
The issue is how to not break the map between these names and the formulas, since formulas use the names instead of indexes... If one client wants to start with A while others want to start with a letter of their alphabet, they wouldn't be able to translate indexes without mapping back to A first and then translating the formula.
5 participants
Adds a simple Spreadsheet format.
Demo: https://sheetstr.amethyst.social
Read here