On Nov 13, 2007 6:45 PM, Peter Clifton <[EMAIL PROTECTED]> wrote:
> > There's a factory per TOPLEVEL.  Not sure if that answers your question.
>
> I'm not sure it allows other non-integrated code the same chance to hook
> object creation, that is all.

I think as you describe below, one could add observers to a PAGE, that
will get notified when you add or remove an object.

> I wonder if we could register a handler for a particular class of
> signals. For example.. "page changed". Adding more detailed signals
> might give say, "object added", "object removed", "object changed" etc.

I like this idea.

> These would be attached to the TOPLEVEL / PAGE in question, rather than
[...]
> > My slotting changes separate the heaviness from the lightness in the
> > symbol library.  It lets you define light symbols with only abstract
> > pinfunction= attributes, and heavy symbols that have no pins of their
> > own, but have first-class slots into which you can fit light symbols.
> > The heavy symbol then completes the mapping from the abstract
> > pinfunction= attribute to the heavier pinnumber= attribute.  There's
> > also a pretty slot chooser dialog that presents a constrained choice
> > of available slots.  (To prevent you from putting a BPJ into an opamp
> > slot.)
>
> Cool, when you've got some, please post screen shots! I'm not fully
> picturing whether the schematic will just look like it has light symbols
> in, or if any graphical representation of the heavier symbol is made.

The schematic will look like just a bunch of light symbols.  You could
have the various opamp slots of an LM324 all over your schematic, and
the heavy part-level component off to the side (or even invisible?)  I
guess the schematic looks much the same as with the current slotting
mechanism, except I think the new slot chooser is very nice, and the
big difference is how your library looks.

> Do you have the user add attributes on instance of the light symbol to
> reference the heavy symbol, or do you instantiate both on the page?

You instantiate both.  The heavy symbol is a bit grotty at the moment,
you have to "just know" that it has slots (I bailed out of an attempt
to give slots a graphical representation _in the heavy slotholder
component_).  The slot chooser dialog frobs an attribute in the light
symbol and tells libgeda to recalculate pins etc.


_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to