ixjf / logic-rs Goto Github PK

Around 5MB right now. Mostly fonts, I guess. Any way I can remove them if I don't need them?

Since the algorithm doesn't foresee any patterns and always follows the same rules in the same order, some inputs may lead to trees that become stuck in an infinite EQ->UQ cycle. No clue how to solve. Haven't given it much thought yet. I mean, if it ends up in an infinite cycle, then the tree is open. The problem is: how do I know if I'm in an infinite loop?

Specific instances where it fails:

(∀x)(L¹x ⊃ (∃y)(F¹y & (∃z)(T¹z & P³xyz))),
(∃x)(L¹x)
∴ (∃x)(F¹x & (∃y)(T¹y & (∃z)(L¹z & P³zxy)))

{∀x((A¹x & B¹x) ⊃ ∀y(~C¹y ⊃ ∃z(A²zy & B¹z)))}

∀x(S¹x ⊃ (∃y)(F¹y & M²xy)),
F¹b
∴ ∃x(S¹x & H²bx)

∃x(C¹x & ~(∃y)(G¹y & E²xy))

TextEncoder is not supported (necessary for rustwasm).

There is a redundant if check there.

The call is there because for some reason without it the tree doesn't appear, but it should be unnecessary because the tree is automatically redrawn when resizing the container of the canvas.

CodeMirror seems to be keeping the text input via keyboard selected, so clicking on one of the editor toolbar's buttons replaces the text rather than append. Only happens on mobile.

& whatever is needed for docs.rs

...and then add docs.rs and crates.io badges to the README.

Take out all the arguments/statement sets/statements that are in the solutions of Meaning and Argument and Formal Logic and have a truth tree or whose validity/consistency/whatever is known to serve as integration tests and examples of how the library works.

While not a part of Meaning and Argument, it can be handy, writing the same thing twice is not nclean especially if it's a long expression.

• Sometimes Semantic UI/CodeMirror doesn't load
• Sometimes the Ionicons font doesn't load in time and thus the truth tree rendering needs to be redrawn.

Tested Chrome and Samsung Internet. Need to try to reproduce on PC.

vis.js currently requires rendering the tree multiple times to position it accurately. It also requires hacks to work for this particular type of tree, and it sometimes overlaps nodes. A custom renderer could easily solve all of these problems.

In TruthTree.