Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add TransitionOperator support for OCD arrays and dictionary namespaces #1

Open
ChrisRus opened this issue Feb 17, 2020 · 0 comments
Open
Labels
holarchy-cm @encapsule/holarchy-cm package issues.

Comments

@ChrisRus
Copy link
Member

Follow the same general pattern used in OCD value comparison I think. i.e. provide a single TransitionOperator that provides logical operations over an array namespace. This can start out with a small set of operations and grow as there are quite a few variants that we might want to support inside of a single TransitionOperator vs forcing developers to chain together multiple discrete array operations (less efficient). But, we'll see. Baseline is pretty easy and we'll start there.

@ChrisRus ChrisRus added the holarchy-cm @encapsule/holarchy-cm package issues. label Feb 17, 2020
ChrisRus added a commit that referenced this issue Feb 20, 2020
... build v0.1.00-alertbay that contains substantial refactoring
to rename the @encapsule/holarchy ObservableProcessModel class
to AbstractProcessModel instead. This was deep surgery and there's
likely some cleanup work still required (and maybe some bugs that
slipped through the existing tests). Lesson #1: holodeck is really
useful; it's so much better than manual tests as I can checkpoint
intermediate work and rely on git.
ChrisRus added a commit that referenced this issue Apr 27, 2020
left unfinished to be happy about). This is latest build that
includes a number of incremental changes on new platform RTL
functionality. Currently, open areas of platform effort:
- @encapsule/holarchy CellProcessor (sort of working, blocked on tests)
- @encapsule/holodeck v2 - nearly working but not done (blocking CellProcessor)
- @encapsule/holistic-app-common-cm - work-in-progress on ViewThemeProcess (much more work than I anticipated - won't summarize here but it's worth doing completely and well for a number of reasons. It's also a reasonable base example for learing how to think in terms of cell processes and finite automata
- @encapsule/holistic-app-client-cm - work-in-progress to integrate existing CellModels into a re-usable HTML5 app kernel that handles all backend communication, possibly sync to IndexDB (performance and/or offline cache), client-side hash ourting, encapsulation of React dynamic layout and streaming data content updates. Leveraging this new HTML5 client app kernel remains my #1 priority. However, it should be noted that existence of the core abstractions to _model_ data and dig into the deals of defining structures, and then dealing with the distributed asynchronous, versioned, data flow patterns required by your use cases already exist. You can't conveniently compose these models for execuction in the application runtime w/out hand-wiring. However, that doesn't mean you cannot use the idea of modeling a process to guide the systematic examination of system requirements through the lense of an abstraction that is flexible, precise, and aligns perfectly w/our app archicture.
ChrisRus added a commit that referenced this issue Aug 4, 2020
... THIS SHOULD BE CONSIDERED work-in-progress.

Too much to explain in a commit message...

Much progress. But, not quite to the point where we can apply the mechanism as completely as required.
ChrisRus added a commit that referenced this issue Feb 28, 2021
Part #1 of a few small but important changes to CellModelArtifactSpace.
ChrisRus added a commit that referenced this issue Mar 15, 2021
Round #1 of 2 (maybe 3) cleanup iterations on @encapsule/holarchy
CellModelArtifact, CellModelTemplate and derived artifacts in
@encapsule/holarchy-cm (DisplayView_T, ObservableValue_T).

This commit also includes an experimental patch to box DisplayView_T family cell's cached thisRef live React.Element reference in a toJSON function to avoid OCD serialization errors during test. Seems to work okay under the debugger but is not yet confirmed in tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
holarchy-cm @encapsule/holarchy-cm package issues.
Projects
None yet
Development

No branches or pull requests

1 participant