gEDA-dev: Parts DB API: the story so far

[Peter TB Brett]

On Thursday 20 December 2007 16:41:25 DJ Delorie wrote:

> Perhaps the "unique name" for symbols could be, say, an url?  We can
> make up our own protocols (http, ftp... psql, m4, etc) to point at the
> backends we offer.  Protocol chooses a plugin, host choses a source
> within that plugin, path chooses a symbol.

I like the idea of the name being "just a string" because it means that you 
could, for instance, have a local symbol directory that contains symbols from 
the database (automatically populated when you place them), but which is only 
used to source symbols when for some reason the database isn't down.

Of course, there's no reason that the name couldn't have special significance 
to the backend, but I wouldn't like to enforce anything! [1]

                                Peter

[1] Apart from that symbol names can't end in "EMBEDDED". *groan*

-- 
Peter Brett

Electronic Systems Engineer
Integral Informatics Ltd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.seul.org/pipermail/geda-dev/attachments/20071220/2a150314/attachment.pgp