Refactor for embedding support

[olynch]

No description provided.

[netlify]

❌ Deploy Preview for semagrams failed.

Name	Link
🔨 Latest commit	fbedd77
🔍 Latest deploy log	https://app.netlify.com/sites/semagrams/deploys/64d6df4ffb11240008bbaebb

[olynch]

Some thoughts on the direction that this is going.

1. We need a trial application that we embed Semagrams in for me to figure out what the API should be, or how things would work at all.
2. Now that a Semagram is more directly just the display of the actual ACSet, I think it makes sense to eliminate the Entity/Part distinction, @sjbreiner should be happy about that. What used to be the UI viewport is now just going to be handled outside of the Semagram, in a way that doesn't have to conform to the Semagrams paradigm.
3. The way that I'm redesigning bindings by splitting up the "hook" and the "action", it should be easier to automatically generate a help message.

[olynch]

Most actions should only need the stuff in here:

Semagrams.jl/scala/apps/graph/src/Main.scala

Line 61 in 34b2e4c

case class Resources(

. Does it make sense to have this class?

We have a trait that we extend in order to make the display. Should we also have a trait that we extend in order to make the control process? How does the control process interact with the rest of the app?

[olynch]

replaced by dev