[...]
                > Again there is the opacity problem.  What does the
"~vector~" mean?  
                > And why would I ever want to read such a general
description of a 
                > 2-vector?  It doesn't say much about what is in the tree.

                You're complaining about the fact that two different objects
that you've built have uninformative representations when displayed on the
stack.

                Taking the parser first, it seems that no-one has written a
specific prettyprint implementation for the parser tuple. If you fancy doing
so, it's not that much work: see [1].

I've discovered the inspector recently.  It is a good inspector, at least as
interesting as the Smalltalk inspectors.  The GUI is not polished visually,
but it actually works better than most of the stuff that MS produces:  there
is no flicker at all during resize, and all movements seems to occur at the
pixel level.  Impressive overall.

                For the second, consider the following snippet:

                  100 [ 0 ] V{ } replicate-as dup 2array

                This makes two vectors containing 100 zeros and then sticks
them together in an array. They display on the stack as

                  { ~vector~ ~vector~ }

                What would you prefer? If you want to see them in all their
glory, now type "." ... and that's why that representation isn't used on the
stack!
                
The default vector vertical formatting is okay.  The default stack-view
brevity is good.  Selecting the entire stack item for inspection can be
tricky. You have to position the cursor in-between cells.

                For more information on what controls how the contents of
the stack are printed short, look at the definition of s. . This ends up
using pprint-short, which you can find online at [2].


                [1]
http://docs.factorcode.org/content/article-prettyprint-extension.html
                [2]
http://docs.factorcode.org/content/word-pprint-short%2Cprettyprint.html
                
How do I use the keyboard keys to cycle back through old expressions?
Currently I have to scroll to the old position and double-click to re-enter
it.


Thanks.

Shaping
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk

Reply via email to