Hazel exolivelit wrapper #739
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
epatters
added
frontend
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a minimal proof of concept for integrating CatColab into Hazel as an exolivelit. I've made a wrapper around a ModelPane as discussed. Right now this is specialized to schemas, and doesn't send over the whole model, just a record of two fields showing the object/morphism count. Demo video below.
Screen.Recording.2025-09-25.at.6.44.05.PM.mov
This is the relevant hazel branch:
hazelgrove/hazel#1970
It should be possible to reproduce the above by cloning and building hazel, running it in a browser, and using the lower-right projector panel to place a CatColab exolivelit on any existing syntax (it just ignores and overrides it for now).
I think my integration is probably pretty messy... I seem to have also broken your CSS somehow. Next steps besides cleaning that up would be moving to support some more meaningful subset of your data model rather than merely the object/morphism summary shown. The /hazel/ subdir is more or less unchanged from previous integrations; contentful integration is all in CatColabHazelApp.tsx.