2023/05/01/DataPorts redesign

From Woozle Writes Code
Revision as of 12:37, 2 May 2023 by Woozle (talk | contribs) (Created page with "{{nav/codeblog}} Thinking overnight about the current stashing problem, here's what I came up with: # Stash should be a Unit-type instead of a special object in the Feature. # Each Row should have both an input and output dataset. ("read" ops come from the input set, "write" ops go to the output) # The dataset should be in arrays in the Row objects; Units should be strictly for translation. I think there ''might'' have been one more, or maybe I...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Codeblog

Thinking overnight about the current stashing problem, here's what I came up with:

  1. Stash should be a Unit-type instead of a special object in the Feature.
  2. Each Row should have both an input and output dataset. ("read" ops come from the input set, "write" ops go to the output)
  3. The dataset should be in arrays in the Row objects; Units should be strictly for translation.

I think there might have been one more, or maybe I was counting differently. Either way, if I've missed anything, it's probably a logical consequence of the first two decisions and will (therefore) become evident after I implement them.