These functions build the test assemblies we've been playing with: the "General" assembly that appears when you load the page, and the "Low-curvature" assembly that you can pick from the drop-down…
The main branch has diverged from the branch to be merged because of the changes we made to while reviewing #15. Those changes have been incorporated in #19, which supersedes this pull request.
Just like in Numberscope when you enter invalid input for a parameter, it should not disable the associated entity, it should simply not (yet at that point) update it (so the last valid value…
Oh and I guess there's one more item: putting engine/assembly in a different directory from views. That one is not critical at this point
To simplify future merges, I'd prefer to do this…
for this PR, please add a test that verifies, in some reasonably nontrivial case, that when the row/col of a frozen coordinate is set to 00100, the step comes out precisely 0 in that coordinate;…
is this the string like 0.5 that represents the specified lorentz_prod of the constraint in the outline view?
Yes. More generally, it's the reactive string that represents the Lorentz product…
I've replaced rep with lorentz_prod in all the Constraint field names. We can streamline the names later if they get too unwieldy.
Marking this as WIP until I make these changes, which came up during review of pull request #15:
- Make
Element::indexprivate, as discussed here - Use the new…
Pull request updated and ready for more review! I think I've made all of the changes you requested; let me know if I missed anything.