Copying Library Symbols

Am 25.02.2011 14:17, schrieb jmorley@endeavour-usa.com:

Hi All,

 

I'm a new Eagle user, and I'm trying to make a custom library of the parts

I will be using the most. I'd like to take some of the existing symbols

(only) from libraries supplied with Eagle, and use them to create my own

library. I will be making the package, and device definitions myself while

using the these existing symbols.

 

Is this possible? It appears (from browsing the forum) that symbols are

somehow unique, and may need a 'Group-Copy-Paste' approach rather than a

'Right-click&  Save to Library' or 'Drag-n-Drop' approach, but I have been

able to make anything work yet!

 

Thanks,

 

John

I would export a library as script, edit it with text editor and

scratching out everything except the sym definitions. Then import into

new library.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Am 25.02.2011 14:17, schrieb jmorley@endeavour-usa.com:

Hi All,

 

I'm a new Eagle user, and I'm trying to make a custom library of the parts

I will be using the most. I'd like to take some of the existing symbols

(only) from libraries supplied with Eagle, and use them to create my own

library. I will be making the package, and device definitions myself while

using the these existing symbols.

 

Is this possible? It appears (from browsing the forum) that symbols are

somehow unique, and may need a 'Group-Copy-Paste' approach rather than a

'Right-click&  Save to Library' or 'Drag-n-Drop' approach, but I have been

able to make anything work yet!

 

Thanks,

 

John

I would export a library as script, edit it with text editor and

scratching out everything except the sym definitions. Then import into

new library.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

"Joern Paschedag" <jpaschedag@t-online.de> wrote in message

news:ik8csv$mg3$1@cheetah.cadsoft.de...

 

I would export a library as script, edit it with text editor and

scratching out everything except the sym definitions. Then import into new

library.

That's probably the cleanest way to go. That method though is more for an

experienced user who better knows the system - not the relative nubie .

    just my $0.02 worth.

On Fri, 25 Feb 2011, Oppie wrote to us saying :

>"Joern Paschedag" <jpaschedag@t-online.de> wrote in message

>news:ik8csv$mg3$1@cheetah.cadsoft.de...

>>

>> I would export a library as script, edit it with text editor and

>>scratching out everything except the sym definitions. Then import into

>>new  library.

>That's probably the cleanest way to go. That method though is more for

>an experienced user who better knows the system - not the relative

>nubie .

Depends what sort of newbie. If he's new to Eagle (and possibly even to

CAD systems) but has experience with programming and scripting

languages, then this method may feel like second-nature. I know for

creating new parts I often find it easier to write a Python script to

generate an SCR to import.

--

Rob Pearce                       http://www.bdt-home.demon.co.uk

The contents of     | All power corrupts, but we need electricity.

this message are    |

purely my opinion.  |

Don't believe a     |

word.               |

On Fri, 25 Feb 2011, Oppie wrote to us saying :

>"Joern Paschedag" <jpaschedag@t-online.de> wrote in message

>news:ik8csv$mg3$1@cheetah.cadsoft.de...

>>

>> I would export a library as script, edit it with text editor and

>>scratching out everything except the sym definitions. Then import into

>>new  library.

>That's probably the cleanest way to go. That method though is more for

>an experienced user who better knows the system - not the relative

>nubie .

Depends what sort of newbie. If he's new to Eagle (and possibly even to

CAD systems) but has experience with programming and scripting

languages, then this method may feel like second-nature. I know for

creating new parts I often find it easier to write a Python script to

generate an SCR to import.

--

Rob Pearce                       http://www.bdt-home.demon.co.uk

The contents of     | All power corrupts, but we need electricity.

this message are    |

purely my opinion.  |

Don't believe a     |

word.               |

Am 26.02.2011 10:30, schrieb Robert Pearce:

On Fri, 25 Feb 2011, Oppie wrote to us saying :

>> "Joern Paschedag" <jpaschedag@t-online.de> wrote in message

>> news:ik8csv$mg3$1@cheetah.cadsoft.de...

>>>

>>> I would export a library as script, edit it with text editor and

>>> scratching out everything except the sym definitions. Then import

>>> into new library.

>>

>> That's probably the cleanest way to go. That method though is more for

>> an experienced user who better knows the system - not the relative

>> nubie .

 

Depends what sort of newbie. If he's new to Eagle (and possibly even to

CAD systems) but has experience with programming and scripting

languages, then this method may feel like second-nature. I know for

creating new parts I often find it easier to write a Python script to

generate an SCR to import.

Actually the whole thing has little to do with eagle, except the ex- and

import of the script file. It is just editing a plain text file

and, if you have made errors, the Import will give you a warning showing

the faulty line number

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag