#41 Expand Arrows

[Aaron Powers]

This is an HCI issue (not a bug per se).

Code compression/expansion arrows (for compressing
"if/the" blocks, etc. arrows need several fixes before
they can be usable prime-time:
a) Their state needs to be saved between
saves/commits. I.e. I'll compress a chunk of code but
I want it to stay compressed after I save the fragment,
or when I come back to it later -- I never compress
things now because the state changes so shortly
afterwards that the compression is usually too inefficient.
b) You need to be able to see better visually that a
chunk of code is no longer visible and is hidden
somewher -- a simple arrow isn't enough, since
programmers are very unused to this. First, if a user
put a brace { at the end of the line, it should no
longer be visible after compression. Second, something
as simple as a black line below the "if (problem)" line
could work.
c) Tentative (could bear discussion as to whether
this is a immediate need) -- it needs to be clear how
much code is going to be compressed before the
compression happens. The best way to do this would be
to draw a box around the code in a block, or some sort
of illustration to group that chunk of code together
with the if statement itself.