[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: Parts DB API



Levente wrote:
> Peter TB Brett <peter@xxxxxxxxxxxxx> wrote:
>

>> - Each symbol (or part) has to be uniquely identified by a string, and each
>>  database/website/directory gets queried in reverse order of being added to
>>  the library.  This is as currently.

But not for all time.  can't it just stay in database only for its purposes of sifting?
Why have UUID numbers in the schematic?

>>
>>  For databases, this could just be a concatenation of the database name and
>>  some sort of unique identifier number.  The unique identifier string would
>>  be stored in the schematic file where the "symbol name" currently is.

along side of, not in place of.   So you can run without a website source of data.


>>
>>  This provides a way to store exactly which part was selected by the user
>>  in a backwards-compatible manner.
> 
> Yes, but I think we should copy the information coming from the database to
> have ability to read/process schematic off line, when there is no remote
> database seen. Or did I interpret something wrong?


Me too.  I don't want to get stuck inoperable without finding the mate to a long UUID style
string of identifier numbers.

John G
-- 
Ecosensory   Austin TX
tinyOS devel on:  ubuntu Linux;   tinyOS v2.0.2;   telosb ecosens1


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