Re: gEDA-dev: netlist route styles

[John Doty <jpd@xxxxxxxxxxxxx>]

On Jun 3, 2008, at 11:11 AM, Amans,Ross wrote:

> That only applies to the geda library. Many of my symbols are  
> custom, as
> the geda lib is not complete. Also, I put attributes on my symbols,  
> like
> internal part number, so my schematic can generate a bom.

Yes, exactly.

> Putting those
> attributes on each schematic symbol is out of the question when I have
> thousands of instances to attribute in my schematic, and many  
> attributes
> to add. So all my library symbols are modified from the main  
> release. I
> have yet to figure out how to handle a release symbol update, so  
> all my
> symbols are in a local library.

"Project symbol repository". I would call a "local library" a read- 
only source of locally defined symbols, not project specific.

>
> Ross Amans
> Hardware Design Engineer
> Biometric Access Co
> 512-426-9252 (cell)
>
> -----Original Message-----
> From: geda-dev-bounces@xxxxxxxxxxxxxx
> [mailto:geda-dev-bounces@xxxxxxxxxxxxxx] On Behalf Of John Doty
> Sent: Tuesday, June 03, 2008 12:04 PM
> To: gEDA developer mailing list
> Subject: Re: gEDA-dev: netlist route styles
>
>
> On Jun 3, 2008, at 10:56 AM, Amans,Ross wrote:
>
>> In Orcad Capture, when you have finished editing a symbol, and
>> close it to save, it does ask if you want to update that symbol in
>> your design. It only updates the latest, previously edited version
>> of that symbol, so it is common for your design to wind up with
>> multiple versions of a symbol. So the gschem symbol tool should ask
>> if you want to update, and list versions of that symbol. At the
>> same time, the Orcad tool does not ask if you want to update the
>> library version of that symbol, so you usually wind up with the
>> library having out-of-date symbols. So the gschem symbol tool
>> should also ask if you want to update the library symbol, as well.
>
> The library symbol comes from the gEDA distribution, and is normally
> write protected. It is dangerous to unprotect and edit these, as your
> next gEDA update will probably revert you to the old symbol.  Of
> course, it's also dangerous to *use* these as your next gEDA update
> may change the symbol to "fix" an attribute that's right for your
> design, but wrong for someone else's.
>
> That's why we need the concept of a project symbol repository between
> the library and the schematic.
>
>>
>> Ross Amans
>> Hardware Design Engineer
>> Biometric Access Co
>> 512-426-9252 (cell)
>>
>> -----Original Message-----
>> From: geda-dev-bounces@xxxxxxxxxxxxxx [mailto:geda-dev-
>> bounces@xxxxxxxxxxxxxx] On Behalf Of Peter Clifton
>> Sent: Tuesday, June 03, 2008 11:35 AM
>> To: gEDA developer mailing list
>> Subject: Re: gEDA-dev: netlist route styles
>>
>> On Tue, 2008-06-03 at 16:19 +0000, Kai-Martin Knaak wrote:
>>> On Tue, 03 Jun 2008 08:41:09 -0600, John Doty wrote:
>>>
>>>>> stderr / stdout warning that there might be out-dated footprints
>>>>> for
>>>>> certain files.
>>>>
>>>> Unacceptable. In a large project, such warnings are lost in the
>>>> spew.
>>>
>>> Those, who actually work on large projects will easily adapt and
>>> look for
>>> these warnings, if they prove to contain critical information.
>>> grep and
>>> awk are no rocket science.
>>>
>>>
>>>> When I change a symbol to fix a pin assignment, part number,
>>>> footprint,
>>>> underlying hierarchical schematic, etc., I expect that change to
>>>> propagate.
>>>
>>> I don't -- at least not automatically and by default. This kind of
>>> change
>>> all too easily breaks existing schematics or layouts. Because of
>>> this, I
>>> prefer an update of symbols or footprints only if I explicitly  
>>> choose
>>> so.
>>
>> Given a fictional "Project environment", it should be possible (after
>> editing a symbol file), that the tool you just closed would then
>> pop up
>> some dialog:
>>
>> /----------------------------------------\
>> | Update schematics                    |x|
>> |----------------------------------------|
>> | Update schematics with new version of  |
>> | heuristic-algorithm-unit.sym           |
>> |                                        |
>> | hal9000.sch                    [x]     |
>> | sal9000.sch                    [x]     |
>> |                                        |
>> |----------------------------------------|
>> |   |Deselect all| |Select all| | OK  |  |
>> \________________________________________/
>>
>>
>>
>> -- 
>> Peter Clifton
>>
>> Electrical Engineering Division,
>> Engineering Department,
>> University of Cambridge,
>> 9, JJ Thomson Avenue,
>> Cambridge
>> CB3 0FA
>>
>> Tel: +44 (0)7729 980173 - (No signal in the lab!)
>>
>>
>>
>> _______________________________________________
>> geda-dev mailing list
>> geda-dev@xxxxxxxxxxxxxx
>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>>
>>
>> _______________________________________________
>> geda-dev mailing list
>> geda-dev@xxxxxxxxxxxxxx
>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>
> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd@xxxxxxxxx
>
>
>
>
> _______________________________________________
> geda-dev mailing list
> geda-dev@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
>
>
> _______________________________________________
> geda-dev mailing list
> geda-dev@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd@xxxxxxxxx




_______________________________________________
geda-dev mailing list
geda-dev@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev