kicad-developers team mailing list archive

[jp charras <jp.charras@xxxxxxxxxx>]

Le 18/11/2016 à 02:57, Ian Roth a écrit :
> 
> 
> On Mon, Nov 7, 2016 at 10:17 AM, Wayne Stambaugh <stambaughw@xxxxxxxxx
> <mailto:stambaughw@xxxxxxxxx>> wrote:
> 
>     On 11/2/2016 9:25 PM, Ian Roth wrote:
>     > I am working on an I/O plugin for eeschema and I would like to save
>     > wires in order of netlist, for example:
>     >
>     > netlist1
>     >   -wire1
>     >   -wire2
>     > netlist2
>     >   -wire3
>     >   -wire4
> 
>     What is your reasoning for doing this?  I could be wrong but I don't
>     think this would be a good idea for users who use a VCS to track their
>     designs.  When the netlist gets rebuilt, there is no guarantee that the
>     wires assigned to a net will not get reordered by netlist generator.
>     This would create a large delta when saving the schematic.  To make this
>     VCS friendly, you would have to ensure consistent net naming when
>     generating the netlist which could be pretty complicated.
> 
> 
> The reason is that I need a way of quickly drawing schematics for RF systems and exporting them as
> javascript for rendering in a web browser. I would not mind exporting the netlist at the same time
> as the schematic.

I am thinking you'll need a netlist because:
- Pins can be connected without wire (power pins, labels)
- In complex hierarchies, the same physical wire belongs to different nets (one by shared sheet).

and the knowledge of wires is not enough to build connections, even for basic cases.

>     >
>     > It looks like the schematic I/O manager passes the screen, but not the
>     > SCH_EDIT_FRAME that contains the netlist functions to the plugin save
>     > function. Is it possible to get the netlist in the plugin in order to
>     > sort the wires?
> 
>     This will not happen.  Adding any wxWindow knowledge to the schematic
>     I/O plugin is a poor design practice.  At some point (hopefully soon), I
>     will start working on a coherent SCHEMATIC object which will act as a
>     container for the entire schematic.  This will be the object that allows
>     you to generate the netlist, not SCH_EDIT_FRAME.
> 
> 
> Your solution sounds like it would work for my needs. Do you have an estimate on when the coherent
> schematic object will be in the kicad source? 
> 


-- 
Jean-Pierre CHARRAS