Message-ID: <1427942592.32608.80.camel@benjamin-hp-g70>
Subject: Re: [geda-user] PCB and gschem libraries
From: "Benjamin L. Naber" <benjamin AT project23d DOT com>
To: geda-user AT delorie DOT com
Date: Wed, 01 Apr 2015 22:43:12 -0400
In-Reply-To: <1427905808.32608.60.camel@benjamin-hp-g70>
References: <1427905808 DOT 32608 DOT 60 DOT camel AT benjamin-hp-g70>
Organization: Project23 Development, Inc.
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

I think we are on the right track now.

I'd like to say thank you to those whom have made the symbols and
footprints and shared them with the rest of us. Without you, some of us,
like this guy, would be pulling our hair out. Just because we make a
schematic design, doesn't mean we know or what to know how to make
symbols.

I really like the idea of some kind of database; whether it is MySQL,
PostgreSQL, CouchDB, sqlite is a matter of semantics.

What does need to have defined is the file naming convention.

We can have 10 or 1,000 individual footprints and symbols, but if they
are not following any kind of naming convention, then trying to have
some sort of automated databasing is not going to work.

Perhaps it may go like this:
IC_RF_Motorola_MC145158-2_SOG16.sym/.fp

Naming convention could be as follows:
Family: IC, passive, switch, connector, etc
Type: logic, RF, analog, etc
Part number: for those with part numbers, or values for passive
components: 1.5k, 10uF, 100pF, .1mH,....
Package type: IC- DIP8, PLCC18, .25W, 1A, SOT23, TO-220......

Where do we find what parts belong to what family?
Digikey, Mouser, Newark, wikipedia

I understand there is a very fine line between what is considered too
lose or too many restrictions. We are not trying to be a government.
But, we do need to have some kind of organization that will be most
benefit to most of the users. In essence, if it works for a lot of
people, good, as no matter what we do, one person is always going to be
pissed off. But when you have a lot of pissed off users, then it might
be time to do some changing.

~Benjamin 

On Wed, 2015-04-01 at 12:30 -0400, Benjamin L. Naber wrote:
> Alright,
> 
> So there has been a rather long discussion of how much the library
> organization totally sucks for both programs. And it really isn't
> getting anywhere.
> 
> Currently, I am wasting my life going through each and every user folder
> on the CVS system, and it has become apparent to me that I am not the
> only one frustrated with the methods presently in place to download and
> use symbols and footprints by other users. I say this because there are
> MANY users that have made symbols and footprints for the same exact
> components. While there is some apparent slight visual differences, the
> end results are identical.
> 
> I make a notion that if a user wishes to place their symbols/footprints
> on the CVS system for public download, they will follow a simple
> standards of organization.
> 
> For example.
> 
> A symbol and footprint was made for the MC145158 PLL IC. 
> It would be filed under:
> IC - RF - MC145158.sym/.fp
> 
> Clearly, this needs more definition, but the idea is there.
> 
> 
> Not this current hokus pokus method of whatever I feel like doing, and
> screw everyone else because I'm too lazy to follow a simple
> classification system. If the symbols and footprints are going to made
> available for the benefit of others, then why not make it reasonably
> accessible?
> 
> Also, users that do not have any symbols or footprints on the CVS system
> should not be downloaded. Currently, it's apparent all users are
> downloaded, whether they have created stuff or not.
> 
> ~Benjamin
>