[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: gEDA-dev: SoC Hopeful
Hi Dj,
I looked up the webpage you mention and have the following remarks.
1)
Is it possible to decide beforehand upon a fixed order of columns for
the csv files involved.
This would allow for easy merging of contribs by other
users/developers/maintainers.
2)
No mentioning of gnetlist backend, pcb HID or gnucap specific fields so
far.
3)
I could imagine that a certain part/package can be sold by different
vendors with different prices (due to currency and/or location as in
Europe, USA, Asia etc.)
4)
IMHO a third database file/table is required for local determined
entries (vendor, currency, price etc.).
I could think of "vendors_and_prices_NL-nl.csv" localisation scheme.
5)
What is the use of the "author" entry in the first database file/table.
What if you happen to have an author-1 for the footprint and an author-2
for the symbol and an author-3 for the gnucap model etc.
It's supposed to be just an entry linking to other files.
Or is this ment for the person entering this specific entry ?
Just my EUR 0.02
Kind regards,
Bert Timmerman.
-----Original Message-----
From: geda-dev-bounces@moria.seul.org
[mailto:geda-dev-bounces@moria.seul.org] On Behalf Of DJ Delorie
Sent: Monday, March 19, 2007 3:39 AM
To: geda-dev@moria.seul.org
Subject: Re: gEDA-dev: SoC Hopeful
In addition to Dan's comments, I'd like to add some ideas of my own,
mostly details but they may be useful to think about during the design
phase.
I would like to see the database be multi-table and
cross-referencable. What I mean by this, is that I'd like to have one
database that maps symbols and footprints to manufacturer parts, and a
second database that maps manufacturer parts to vendor (digikey,
mouser) parts and pricing. It makes it easier to update/import vendor
info. The ability to split it up other ways may be beneficial also,
so, for example, caps in one database, resistors in another.
See http://www.gedasymbols.org/csv.html for some column names we've
loosely decided on for such tables (gedasymbols knows how to display
these tables).
In gschem, I'd like to be able to be able to specify only the info I
know at the time, and let gschem keep track of what the legal values
for the remaining attributes are. For example, I put in a resistor
and choose a value later, but I know I want 0603 packaging. Later I
want to choose a value, it tells me all the values that are available
in 0603 packaging (perhaps, limited to my inventory). When I go to
order parts, it tells me which vendors supply that value. If I want
to choose a different vendor than what's available, I have to clear
something else (value, perhaps), choose the vendor, then see what
values are available from that vendor. The key is, gschem keeps track
of what values are possible for the remaining attributes, based on
which attributes I've already specified.
It would be nice if the database could be served from various sources,
such as an SQL database, a web server, a text file, etc. Maybe not
all at once, maybe not even a runtime option, but if the sources were
set up to easily allow switching, that would be a good design choice.
_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev