kicad-developers team mailing list archive

[Russell Oliver <roliver8143@xxxxxxxxx>]

>From what I am reading John your call for acting on the files on disk
instead of memory is a call for a clear demarcation of actions that need to
be irrevocable and require the project data to be consistent.

In my opinion this doesn't necessarily require separate programs, just
consistent checks on the current state of the project and its data. A check
and dialog box to force the user to save the all schematic sheets before
exporting the netlist might be sufficient.

Likewise saving the pcb after changing say a selected footprint or changing
the reference or value of a component, would force a back annotation of the
schematic which would also be saved. A change would not be allowed to
persist without it being consistently applied across the project.






On Thu, 8 Mar 2018 15:22 Ouabache Designworks, <z3qmtr45@xxxxxxxxx> wrote:

>
>
> On Wed, Mar 7, 2018 at 8:01 PM, José Ignacio <jose.cyborg@xxxxxxxxx>
> wrote:
>
>> The separate program issue is just an implementation detail. The main
>> thing that Kicad is headed for is the refactoring slated for the 6.0 dev
>> cycle. The cleaner data structure foundation and subsequent decoupling of
>> the logic from the UI classes will allow all sorts of automation that are
>> currently very hard or impossible. The vision that was set since over 5
>> years ago was for Kicad to present a library-like interface to the outside
>> world. It kind of does now on PCBnew only, but things are slowly improving
>> as things get refactored and legacy code gets phased out.
>>
>> I honestly think the last thing Kicad needs right now is a chance of
>> direction, I speak as a user that has been using Kicad professionally for
>> just over 2 years now, working on dozens of PCB projects over that time.
>> The developments in the past few years have been nothing but awesome for a
>> project with Kicad's resources. We just need to be patient, or try to help
>> out in a constructive manner.
>>
>> Over the past couple years I have been using the dev version in
>> production to take advantage of the new features (dealing with
>> versions/instability was a small price to pay for me), I also helped a
>> little bit (as time allowed) with the occasional patch or grumpy bug
>> report. I'd like to thank everyone that has worked on the project so far;
>> It basically has made it possible for me to make a living doing what I
>> enjoy, and I really hope the project can retain the momentum it has built
>> up in the past few months, it just keeps getting better!
>>
>> Thanks,
>> Jose
>>
>>
>>
>
> Nothing that I am asking for is a change of direction. Instead of calling
> a function that operates on data in memory you call a program that operates
> on the same data in the file system.
> You see the same menu pick either way. This will fit in with the
> refactoring.
>
> If you are doing a PCB with a FPGA on it then you really want that FPGA
> designer to be using kicad to design their padring. Kicad could fill this
> niche and it would make your job a lot
> easier.
>
> John Eaton
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>