How do you propose to solve it?

=9A;I see some ways o= f solve problem, but the best of these I think is placing symbol informatio= n in scheme file.

That makes more sense than the current &= quot;Embed Component in schem" mode.=9A Right now if you instantiate a= component multiple times then a complete copy of the symbol is inserted fo= r each instance. Your way only saves one copy.

But it is not the best solution.

40 year= s ago you could design a printed circuit board or an IC using the same sche= matic entry system. All you did was change libraries. But IC designers have= long since dumped schematic entry because most schematic entry tools are s= imply not able to handle large designs.=9A PC boards have grown about 1 or = 2 orders of magnitude more complex over the last 40 years while IC have gro= wn 6 or 8 orders. You are now having to deal with designs where you have co= mponent name collisions and your tools do not work. IC designers hit that b= ump 30 years ago.

Might I suggest that we see how they solved this problem and do t= he same?

You cannot select a component with only it's = component name. IC tools require the component name, library name, vendor n= ame ,revision number and variant name. You will have cases where you need t= wo different revisions of the same component at the same time.

The biggest problem with your solution is that it makes a cop= y of the design data. When you are dealing with big designs you never copy = anything. Everything is assigned a unique location and any time it is neede= d then it is fetched from that location. If you don't follow this rule = then your data can go viral as it is passed around,reused, modified and=9A = fixed. Then you try to do a design with components that contain non-matchin= g viral copies of some original component.

You will want to have a local copy of all your designs in your de= sign environment but these are always clones of an RCS database from the or= iginal source.=9A You also do periodic checks to see if there is a newer ve= rsion available from the vendor.

John Eaton

=9A

=9A

On Tue, Jan 28, 2014 at 6:55 AM, =E1=CC=C5=CB=D3=C5=CA =E8=C1=D2=D8=CB=CF= =D7=D3=CB=C9=CA <svetonomer AT gmail DOT com> wrote:

2014/1/28 <karl AT aspodata DOT se>

How do you propose to solve it?

I see some ways of so= lve problem, but the best of these I think is placing symbol information in= scheme file.

Small example:

Scheme file need split into 2 parts.

1 part is scheme.

-------LIBRARY------

2 part i= s library.

In part No2 (library section) gschem c= opy added symbols wholly:

C .......... = triac-1.sym
{

P....
{

T...

L...

}

P....
....

L....

}
C .... .... .. .. descriptor_1
......
C .... .... .. .. descript= or_2
.....

But in first part (sheme part) all as at present:
<= /div>

C 53500 46700 1 0 0 triac-1.sym
=9A {
=9A T 54600 47500 5 10 1 1 0 0 1
=9A refdes=3DTR?
=9A T 53500 46700 5 10 0 1 0 0 1
=9A footprint=3DTO220
=9A }

C.....
....

C.....

and others= .

When gschem opens .SCH file, it reads characters not from the symbol files (component-librar= y-path), but from LIBRARY section of this .SCH file.

--001a11c308d6e1e11f04f10bef4f--