On 10/10/2011 12:03 PM, Edward K. Ream wrote:
This could be the tip of an iceberg.
The more I think about the light/heavy distinction, the more I think
it is getting close to what makes Leo special. For example, clones
(and nodes, for that matter) drastically lighten the apparent
complexity of programs or data.
Edward
I use the gEDA tools for hardware design, and we have a light/heavy
discussion that is different, but related, I think. The usual
hardware design meaning is light == lightly defined symbols that
you add detail to later on in the process, just as in developing
sections of code in outline nodes. The symbols ultimately
have data flows between them as they connect, and sometimes it gets
to be more than symbolic when a verilog language section is what is
inside the connections to a symbol, and all the symbol pins are
data flow pipes of various bit widths.
Some kinds of hardware design benefit from graphical representations
without code inside them -- that's generally called analog system parts.
But even analog system parts sometimes are modeled by code...and
another feature of schematic symbols used in hardware design tools
is that they can contain links to different representations and the
processing of a schematic can use different reps to get a netlist result
for simulation.
Other kinds of system parts are logic and they can be represented by
very simple graphics that is generic rectangles with inputs/outputs
and they always have code inside.
So part of the iceberg or "ocean" you're thinking of the tip of is
maybe hardware design. Especially if tags can be added some way separate from
the code in a section, (and I think there are some sentinels ready to do this),
for purposes of choosing which to use. Also the Leo way of editing has to
respect
any file format ways of doing the same. The schematics I am mentioning are
always
in many multiple files and often the various representations are in file folders
in a tree structure, but don't have to be.
Is there an easy way within Leo's range to make translators for such design
file and directory tree formats into the Leo outline way? If so, the FOSS
project
gEDA might be an iceberg to think about
John Griessen
--
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.
