Commits

sk  committed 64fe997

Fixed inspector bugs.

  • Participants
  • Parent commits edefb9d

Comments (0)

Files changed (1)

 
 
 
-// next step 
+// next step 
+
+
+
+
+
+
+---------------
+internals of inspector:
+
+ConsoleConfiguration->ReplInspectHover->getHoverInfo2()
+on hover calls resolve() function of varResolver field of repl (LispConsoleViewer)
+and sends variable name and id (as described in inspectable)
+
+resolve() function calls LispImplementation.inspectReplResult()
+(see ReplConsolePage.createControl)
+
+The function returns a LispVariable.
+LispVariable creates its LispValue. Each LispVariable and LispValue
+knows which other LispValue or LispVariable is its parent.
+There are two constructors for LispValue: the one where value string is
+supplied and without. When value is not supplied, inspect is called to
+find it out.
+
+To inspect a variable which is not at top level, the swank inspector has
+to be walked to corresponding level of inspecting tree (at each branch
+it goes deeper with inspeckNthPart command). So when the inspect is called
+on a value, it first calls inspect of its parent (which is corresponding
+variable), which first calls inspect of its parent (which is a value) etc.
+until root of the tree. Root of the tree is entered through inspectable, which
+has unique id.
+
+
+-----------------
+
+Add swank event viewer.
+
+Change thread label to reflect why paused (through presentation model - see
+PDAMOdelPresentation)
+