kicad-developers team mailing list archive
Mailing list archive
Re: Fileformats and library
Tue, 01 Apr 2008 22:59:02 -0000
>Am Montag 31 MÃ¤rz 2008 23:27:17 schrieb Richard A Burton:
>> > c) updates of the library
> > > -------------------------
> > > * Really hard to notice, if the default libraries (which comes
> > > with kicad) has any new device inside.
> > Probably each symbol needs a version number (incremented for any
> > non-trivial change), which is stored in the kicad file when it's used.
> > That way if you load a kicad file that used old version of symbols
> > (e.g. after an update to kicad that used included new symbols) you can
> > be warned of the change.
>How about including all symbols, footprints etc., which are used in a
>kicad schematic/pcb in the kicad file itself? This way, you always
have the correct version of library components packaged with the
>document itself. This would greatly simplify sharing of files and
>also removes the need of versioning of library components.
>This could be implemented by simply zipping the document together
>with all used library components together during file save (assuming
>that we do split the components in separate files). Of course, this
>sort of wastes some space, but this shouldn't be that much, esp. when
>zipped. The components in the document archive then would take
>precedence over the files in the library directories.
>Just a thought...
Including symbols, footprints, 3Dshapes in the project file can
prevent components missing in later releases of the libraries; then,
you can re-open a project X years later without problems.
But, for libraries managing, the versionning infos are still usefull.
It has been said that library files must be « human readable ». It is
possible to relativize that question : « human readable » means
readable using a text editor. « Human unreadable » means that you need
another tool to be able to « read » the file...At last, there is a
very thin difference between the two points of view.
But, « human readable » means big files for less information. To
avoid this, sure that you can zip these files. Finally, reading
« large but human readable » files with a text editor or « compact
specialised » files with a specially designed library editor... The
real question is : what is the more efficient in use, what is to be
considered by programmers?
If a library manager / editor is to be considered, the following
features can be incorporated (gradually) :
library browsing, exploring, searching in « official » and in personal
libraries with criterias, using tags in the files (SMD0805, SMD0201,
EIA7343-xx, through hole, melf, IPC-xxxx, etc) and some kind of image
cache (for symbol or the footprint) or contact sheet.
library browsing, exploring, searching... on the internet, on
dedicated sites such as kicadlib.org and all the others already existing.
Able to incorporate component evolutions (for example : new packages).
Component (symbol, footprint, ...) designing, copying, importing from
kicad libs or other formats, exporting...
About schematics and pcb format...another stupid idea : because PC can
handle more and more datas, I imagine an « all-in-one » project file
with chapters : schematic, pcb, components, etc. Big, too big? Usefull?
OK, Dick...I'm a dreamer :-) There are not enough programmers on