I spent about 20 minutes with the Walker, trying to determine what was going
wrong during the sqlite init-db. I could not do that before I had to
discontinue the exercise. I will get back to it after I clear up some basic
GUI needs. There was, however, near the throwing of the exception an error
(I think) "call- effect-unsafe".
The Walker differs from a typical debugger by showing multiple word calls
(stack frames) at once with the right-arrows ("->") inserted before the word
you are in or about to call. Has a one-character "arrow" been considered
so that the text doesn't jump around? What about just highlighting the
current word(s)? I'm still having some trouble making good use of the
Walker, but that is mostly because I don't know at face value already what
many of the words are doing. The jumping about of the text is also a little
disorienting.
Has a one-view-per-stack-frame scheme been tried in the Walker? Does that
strategy remove too much context? I would like to make the Walker show one
word-definition per view, along with a stack of calls. One practical effect
is that the view of a word definition in the debugger will be the same as in
the GUI I'm considering. That GUI would divide the environment into a pane
that lists all vocabularies, a second that lists all words in the selected
vocabulary, a third that shows the definition of each selected word, and a
fourth pane listing the current vocabulary search path.
If I create a vocab search path I don't want (which I have accidentally
done), how do I clear it? What if I don't know the exact name/spelling of
the vocab that was shown to me in an earlier exception (the one in which I
chose the wrong vocab). I would need to be able to clear or restore the
search path order, so that I could see the original error, and choose the
right vocab. Am I expected always to add to the path incrementally to fix
any ordering problem? I thought being able to see the actual search path
all the time and being able to reorder it graphically would be useful.
If the search path is shown by the GUI, it could also color blocked words
light grey (or some other appropriate color) when the current search order
does not allow access to them. That way, while browsing, you can read,
study, compare, and know that some words cannot currently be reached by an
immediate evaluable. You could even have a switchable option (check box)
to remove from the word list all unreachable words (to reduce clutter, if
you are already aware of them).
Evaluables would be entered in a fifth pane, which could also show the data
stack, or a separate dockable window could show the data stack.
Shaping
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
