gEDA-dev: New diagram (attempt at UML)
John Doty
jpd at wispertel.net
Wed Apr 4 17:21:23 EDT 2007
On Apr 4, 2007, at 2:55 PM, Peter Clifton wrote:
> On Wed, 2007-04-04 at 00:19 -0700, Steve Meier wrote:
>> Peter,
>>
>> I am re-visiting the concepts of hierarchy and pages. I was forced to
>> since I started looking at the "hierarchy.c" file.
>>
>> Do you think that the page structure should include a list pages that
>> are one hierarchical level down? I think that this would allow the
>> construction of hierarchical branches.
>>
>> Steve Meier
>
> You could make such a list, but it is similarly easy to infer it from
> any "complex" objects belonging to the current page.
>
> Of course, a "complex" doesn't necessarily map to just one page, so
> I'm
> not sure exactly how it ought to be done.
>
> This is one thing I'd like to have a better concept of in gschem +
> libgeda - which files are pages of the same circuit?
>
> Alternatively, we could extend the file-format slightly to allow
> multiple pages per file (and make this the "official" way of
> defining a
> "circuit").
Years ago I suggested to Ales that an attribute ("pageframe")
attached to a rectangle could make that the frame for a page. I was
thinking of printing, but maybe it could help in other ways, too.
Unfortunately, a big flat design can run to dozens of pages (done one
like that), and I would worry about running out of space in a gschem
window if I couldn't use multiple files. Files also give you a way to
hang a subsystem name on a group of pages.
And then there's gEDA-style hierarchical design, which right now uses
a separate file for each "source". Or SPICE-style hierarchical
design, which is a bit more chaotic ;-)
>
> Peter
>
>
>
>
> _______________________________________________
> geda-dev mailing list
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
John Doty Noqsi Aerospace, Ltd.
jpd at noqsi.com
More information about the geda-dev
mailing list