kicad-developers team mailing list archive

["jean-pierre.charras@..." <jean-pierre.charras@...>]

Damien Profeta a écrit :
> > Plot files from a command file is a *very* complex problem in some
> > cases, mainly in complex hierarchies.
> > Currently, this is possible only for the root sheet.
> > When loading others sheets, the eeschema configuration and the project
> > library cache cannot be loaded because sub hierarchy files do not store
> > the root file name (i.e. the project name)
> > (the default config kicad.pro) file will be loaded
> > (so some libraries coud be not loaded and some component could be 
> not found)
> > (This could be easily fixed by adding this info in all files)
> > Note : currently the schematic files store the list of libraries, but do
> > not really use this info (but do not store specific libraries paths).
> >
> > But the main problem is when using complex hierarchies: in this case, a
> > given file is used more than once in shematic.
> > The component reference depends on the sheet is opened in schematic, and
> > this file handles more than one reference by component.
> > The way to reach a given instance of the shared sheet can be seen like a
> > path.
> >
> > In this case we only load the full hierarchy and plot all sheets (they
> > are more than files).
> > If loading the shared file, more than one plot must be created (as many
> > plot as existing paths)
> >
> > So to be able to plot schematic files from a command line could be an
> > important work that also involves some (but minor) modifications in
> > files formats.
> >
> > --
> > Jean-Pierre CHARRAS
> > Maître de conférences
> > Directeur d'études 2ieme année.
> > Génie Electrique et Informatique Industrielle 2
> > Institut Universitaire de Technologie 1 de Grenoble
> > BP 67, 38402 St Martin d'Heres Cedex
>
> First thank you for the answer.
> I have more questions about that :
> - I understand (or almost undertand) that is quite complicated to get
> all the sheets to plot from a subhierarchy eeschema file. But I don't
> really see the difference between the command line and directly in the
> interface. If I try to open a subhierarchy files, I have the same
> problem. For me, it is another functionality. Did I miss something?
Yes, if you open a subhierarchy eeschema file, you have the same problem.
But this is not the right way to work on a project.
Usually, first you load the root file (and therefore all subsheets and 
libraries), and after you plot a sub hierarchy sheet,
so there is no problem to plot this sheet, because the whole project is 
loaded.

Moreover, in a complex hierarchy, if you do not load the root sheet 
(i.e. the full project),
you can have a broken schematic project.
> - Do you have an example of complex hierarchies? (especially one file
> more than one time) I tried to look at demos directory but did not
> find one.
I do not have a "free" schematic project using a complex hierarchy (only 
proprietary projects).
I'll try to create a demo.
> - I was trying to find an "easy" development to start contribution to
> kicad, but looks like I got a bad one. Do you think I should continue
> on it, or maybe you have another idea? I had a look at feature request
> but they all looks quite complicated to start with.
>
> Thanks
> Damien
If you want to learn the internal code of Kicad, this is a good way, and 
you can continue.

If you want to contribute on some more easier (to code) topics, in 
Gerbview there are some *very* interesting features to add:
- Mainly the ability to load and show the EXCELLON drill files (this is 
the most important feature to add)
Excellon files formats are near from Gerber files formats.
- A way to selected the order of displayed layers, and what layers are 
displayed ( enabling/disabling layers )
- An export gerber file command (for instance after loaded gerber files 
were edited or combined ).

Thanks for your help.

--
Jean-Pierre CHARRAS

Maître de conférences
Directeur d'études 2ieme année.
Génie Electrique et Informatique Industrielle 2
Institut Universitaire de Technologie 1 de Grenoble
BP 67, 38402 St Martin d'Heres Cedex

Recherche :
GIPSA-LAB - INPG
Rue de la Houille Blanche
38400 Saint Martin d'Heres