[snip]
>> What do people think of the whole idea of running an external program
>> (like Cvpcb) to assign footprint information?
>
>What, like gattrib?  ;-)

        Ehrm, except that gattrib doesn't know about pin mapping, pin
seq, footprint names, etc...   I don't know/think that gattrib should
be educated with that sort of information.  I like that it is just 
an simple editor.

>
>I've stated this before, but to recap...
>
>The schematic symbols should be as light as possible, with some
>database mapping symbols to physical devices, so that the user can go
>through some multiple choices to choose the device from the symbol.
>That implies a range of attributes, such as footprint, pin mapping,
>manufacturer, etc.  Gschem would need a way of keeping track of which
>attributes were user-selected and which were implied by database
>search results.

        gschem should do the mapping?   Hmmm.  I'll have to consider that.
Is that what people really want?

Option A. Inside of gschem

        Plop down a light component.  Open up some sort of dialog which
allows you do specify the footprint and the appropriate logical to
physical mapping is applied. Save schematic, run gnetlist, and then
layout.

Option B. External program

        Plop down a light component.  Save the schematic.  Run an
external program to specify the footprint and the appropriate logical
to physical mapping is applied. Run gnetlist, and then layout.

I have always been under the impression that people would prefer B since
they could replace the default/supplied mapping program with something of
their own choosing.  If it was built into gschem, it would be harder to
replace/modify/etc...  But what do I know, I've been known to be wrong
often enough.

                        -Ales




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

Reply via email to