3 ms·

I really don't want to bring you off your roadmap but I'm going to start working on my own startup in November and am planning how it should look like. I even c

I really don't want to bring you off your roadmap but I'm going to start working on my own startup in November and am planning how it should look like. I even created a spreadsheet with sub sheet functionality already (but canvas - not DOM based) --> but the sub sheets have a different purpose in my application. Some weeks ago a very smart friend was arguing with me about the necessity of the spreadsheet that is functioning as a "map". What he meant (I didn't have the opportunity to speak to him since), I think, was that there is no reason that the sub sheets cannot be moved around freely in the entire map but instead are placed within another spreadsheet. In your case the objects (to be placed) are: 1. table; 2. Object; 3. Array.. So the question I wanted to bring up before it's too late is: Why can't these 3 object be placed on an empty space instead of a parent spreadsheet?

repsilat 8y ago
At the moment all sheets in my program literally are objects, though the converse isn't true -- not all objects can be viewed as sheets. That might change in the future -- I think that being able to nest data arbitrarily is pretty important, and so is being able to visually explore that nested data. Maybe that means having "sheets in sheets in sheets". My program having a list of top-level sheets is slightly unsatisfying. I guess there could instead be a single top-level object/sheet to contain them, bringing everything "into the data model". I don't know if that extra bit of purity would actually make anyone's life better, though. I am quite hesitant to let anything "float in free space". I think the grid serves as a useful, lightweight structuring tool, like lines on a piece of paper. It provides a little constraint that rarely gets in your way, and often stops you from getting in your own way. Maybe the user should have the option of placing things in continuous space, but I don't think it's a good default. A good demo could convince me otherwise, though ;-).

repsilat 8y ago

At the moment all sheets in my program literally are objects, though the converse isn't true -- not all objects can be viewed as sheets. That might change in the future -- I think that being able to nest data arbitrarily is pretty important, and so is being able to visually explore that nested data. Maybe that means having "sheets in sheets in sheets". My program having a list of top-level sheets is slightly unsatisfying. I guess there could instead be a single top-level object/sheet to contain them, bringing everything "into the data model". I don't know if that extra bit of purity would actually make anyone's life better, though. I am quite hesitant to let anything "float in free space". I think the grid serves as a useful, lightweight structuring tool, like lines on a piece of paper. It provides a little constraint that rarely gets in your way, and often stops you from getting in your own way. Maybe the user should have the option of placing things in continuous space, but I don't think it's a good default. A good demo could convince me otherwise, though ;-).