Mail Archives: geda-user/2013/06/27/14:00:41
On 06/26/2013 03:01 PM, Hannu Vuolasaho wrote:
> I tried both of them with the test cases and liked.
I'm glad you find it useful.
>
> My 2 cents and feature request.
>
> Now that there are tools collect off page nets, output them to djboxsym file from the each page and create outline/contents page.
Well, but page boundaries don't necessarily correspond to block
boundaries, and off-page I/O doesn't correspond to block I/O. What I
could see, though, is making a different component for "block I/O" and
construct the block from that.
> Unfortunately it would require some autorouting stuff to make the full schematics
That too.... many years ago I was involved in a project to do an
auto-router for schematic nets. It turns out that it is a different
problem from PCB auto-route -- a PCB route is mainly a connectivity
issue. A schematic auto-route is a readability and aesthetic problem...
very different strategies required.
> and might confuse netlister
So... don't send the block diagram sheets to the netlister. You don't
have to netlist *.sch
> but for documentation purposes it would be highly valuable tool for block diagram generation or even hierarchy handling.
I'm going to leave hierarchy to somebody else.
A related tool that I've though about, though, is a "signal
dictionary". Given an agreed-upon 'sheetnum' attribute, it would be
easy to scan sheets for 'netname' attributes and build a dictionary of
all named nets, not just those that go off-page. A sorted list of
signals and sheets where they appear could be printed as a report or
turned into a schematic sheet full of text.
-dave
>
> Best regards,
> Hannu Vuolasaho
>
- Raw text -