Edward K. Ream wrote:
http://www.cs.brown.edu/people/acb/codebubbles_site.htm
<quote>
We propose a novel
user interface metaphor for code understanding and maintanence based
on collections of lightweight, editable fragments called bubbles,
which form concurrently visible working sets.
I've been thinking about related topics for the last month or so.
It's time to continue adding the best features of
Emacs, Vim, Eclipse and Mathematica to Leo.
I've noticed in my leo readings that some code exists or is proposed
that could form nodes on the fly based on operations of running code,
data in, data out -- all generated from or received by leo.
What if you could make a code bubble view of the "code in use as it runs"
determined by settings of the program through it's command inputs, GUI inputs,
and states?
Then you could use that view for sharing ideas about the code, and debugging
and adding to it. The view could change to suit the task being done with
the program, thus simplifying understanding it. When you considered enough
cases of the program running for differnet uses, you would see by intersection
of sets what code can be grouped/separated vs. what is needed by all modes or
running.
John
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
