Re: [Kicad-developers] Proposed roadmap changes

Are there plans to add Constraint Manager to KiCad? In Allegro, CM allows Design Engineers to specify physical, electrical and spacing rules for classes, groups and nets, so that the PCB Layout Engineer will be constrained by these definitions when working on the layout. It's an explicit

Re: [Kicad-developers] Proposed roadmap changes

Le 08/03/2018 à 19:02, Ouabache Designworks a écrit : > > > On Thu, Mar 8, 2018 at 9:47 AM, Jon Evans > wrote: > > Netlist export is a key feature of every schematic editor. So is > multi-sheet support. These > aren't random extra

Re: [Kicad-developers] Proposed roadmap changes

On Thu, Mar 8, 2018 at 9:47 AM, Jon Evans wrote: > Netlist export is a key feature of every schematic editor. So is > multi-sheet support. These aren't random extra features, they are a normal > part of any modern schematic editor. > > Yes they are necessary features. My

Re: [Kicad-developers] Proposed roadmap changes

On 08/03/18 18:45, Ouabache Designworks wrote: > > > On Thu, Mar 8, 2018 at 9:21 AM, Tomasz Wlostowski > > wrote: > > > Please, give me a single argument what benefits Kicad would get by > having a netlist generator as a

Re: [Kicad-developers] Proposed roadmap changes

Netlist export is a key feature of every schematic editor. So is multi-sheet support. These aren't random extra features, they are a normal part of any modern schematic editor. On Thu, Mar 8, 2018, 12:45 Ouabache Designworks wrote: > > > On Thu, Mar 8, 2018 at 9:21 AM,

Re: [Kicad-developers] Proposed roadmap changes

On Thu, Mar 8, 2018 at 9:21 AM, Tomasz Wlostowski wrote: > > Please, give me a single argument what benefits Kicad would get by > having a netlist generator as a separate program. I also asked you for > an example of a successful graphical editing application

Re: [Kicad-developers] Proposed roadmap changes

On Thu, Mar 8, 2018 at 8:26 AM, Andy Peters wrote: > > > On Mar 7, 2018, at 9:22 PM, Ouabache Designworks > wrote: > > > > > > 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

Re: [Kicad-developers] Proposed roadmap changes

On 08/03/18 03:21, Ouabache Designworks wrote: > > What happens if you edit a schematic, export the netlist and are > interrupted before you can save the schematic? I guess in this case a crash happens sometime after the netlist export if the user can't save the schematic anymore... Which is

Re: [Kicad-developers] Proposed roadmap changes

On Mar 8, 2018, at 9:21 AM, Ouabache Designworks wrote: > > Why don't we run PCB layout on the schematic file and let it call the > netlister program every time it runs. This is a simpler process flow with > fewer cases where you make the user jump through hoops to get

Re: [Kicad-developers] Proposed roadmap changes

> On Mar 7, 2018, at 9:22 PM, Ouabache Designworks wrote: > > > 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. If only it

Re: [Kicad-developers] Proposed roadmap changes

On Wed, Mar 7, 2018 at 11:59 PM, Russell Oliver wrote: > 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. > >

Re: [Kicad-developers] Proposed roadmap changes

> > Are these users professional users who are using KiCad at there day job > and is there any way to confirm this? > It's self reporting, but their email domains, LinkedIn profiles and product listings seem to bear it out > I am currently surveying that group and will be returning with some >

Re: [Kicad-developers] Proposed roadmap changes

>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

Re: [Kicad-developers] Proposed roadmap changes

On Wed, Mar 7, 2018 at 8:01 PM, José Ignacio 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

Re: [Kicad-developers] Proposed roadmap changes

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

Re: [Kicad-developers] Proposed roadmap changes

On Wed, Mar 7, 2018 at 3:08 PM, Tomasz Wlostowski wrote: > > Which features you think should go to separate programs? > Export netlist for one. It is a simple addition as long as your design fits completely on the sheet that you are editing but what happens if you

Re: [Kicad-developers] Proposed roadmap changes

Chris, I saw your previous message, I've just been busy getting v5 stuff ready. On 3/7/2018 4:23 PM, Chris Gammell wrote: > Hi Everyone, > > /(tried sending this once but saw on the archive that it didn't go through)/ > > I'm pretty quiet on this list since I have zero ability to talk about >

Re: [Kicad-developers] Proposed roadmap changes

On 07/03/18 23:04, Ouabache Designworks wrote: > > > On Mon, Mar 5, 2018 at 9:57 AM, Jon Evans > wrote: > > Hi all, > > Since my day job involves a lot of engineering > planning/timelines/etc, I've had this rolling around in my

Re: [Kicad-developers] Proposed roadmap changes

> On Mar 7, 2018, at 3:04 PM, Ouabache Designworks wrote: > > > > On Mon, Mar 5, 2018 at 9:57 AM, Jon Evans > wrote: > Hi all, > > Since my day job involves a lot of engineering planning/timelines/etc, I've > had this

Re: [Kicad-developers] Proposed roadmap changes

On Mon, Mar 5, 2018 at 9:57 AM, Jon Evans wrote: > Hi all, > > Since my day job involves a lot of engineering planning/timelines/etc, > I've had this rolling around in my head... > I started brainstorming some proposed changes to the roadmaps. > > I am using Google drive

Re: [Kicad-developers] Proposed roadmap changes

Hi Everyone, *(tried sending this once but saw on the archive that it didn't go through)* I'm pretty quiet on this list since I have zero ability to talk about the actual development. The future roadmap stuff seems relevant though. After chatting with the team at FOSDEM and Javier mentioning the

Re: [Kicad-developers] Proposed roadmap changes

On Mar 7, 2018, at 11:46 AM, Seth Hillbrand wrote: > > You should take a look at Mitja Nemec's action plugin here: > https://github.com/MitjaNemec/Kicad_action_plugins > > I think the replicate layout covers a lot of the functionality you are > looking for. Wow,

Re: [Kicad-developers] Proposed roadmap changes

You should take a look at Mitja Nemec's action plugin here: https://github.com/MitjaNemec/Kicad_action_plugins I think the replicate layout covers a lot of the functionality you are looking for. -S 2018-03-07 10:25 GMT-08:00 Andrey Kuznetsov : > Not sure how you would turn

Re: [Kicad-developers] Proposed roadmap changes

There has already been discussion on this some time ago. I would not us the Altium room moniker. The last time we discussed this, the term "group" was used so that you can associate items in the schematic with items on the board by a group name rather than limit this two individual sheets. On

Re: [Kicad-developers] Proposed roadmap changes

On Mar 7, 2018, at 11:25 AM, Andrey Kuznetsov wrote: > > Not sure how you would turn this into an effortless feature, but a few months > ago I’ve designed just that, replicated channels using the same subsheet, on > layout I did it once, then copy pasted and manually

Re: [Kicad-developers] Proposed roadmap changes

Not sure how you would turn this into an effortless feature, but a few months ago I’ve designed just that, replicated channels using the same subsheet, on layout I did it once, then copy pasted and manually renamed each component based on each channel number component. On Wed, Mar 7, 2018 at 8:42

Re: [Kicad-developers] Proposed roadmap changes

> On Mar 5, 2018, at 10:57 AM, Jon Evans wrote: > > Hi all, > > Since my day job involves a lot of engineering planning/timelines/etc, I've > had this rolling around in my head... > I started brainstorming some proposed changes to the roadmaps. > > I am using Google drive

Re: [Kicad-developers] Proposed roadmap changes

I think copy/paste is a good feature to have, it's not just you! Re. roadmap, I have now gone through my document and assigned priorities based on my guess, and owners (i.e. primary developers) also based on my guess. Developers who are going to work on things for V6, please comment or email me

Re: [Kicad-developers] Proposed roadmap changes

Hello, as Andy mentioned, I consider quite important to have schematic components embedded into schematic file. This will allow people to share small schematic sheets and schematic snippets without painful lib cache file. In Eagle and in Altium the "make library from schematic" capability is/was

Re: [Kicad-developers] Proposed roadmap changes

I will be sure to send a proposed update to the official doc after there is no more churn on my scratch pad doc. I am not allowing anyone to edit, only I can edit (anyone can comment, and I have been incorporating changes based on people's comments) I think the next pass (now that it has been a

Re: [Kicad-developers] Proposed roadmap changes

Only jon can edit, our "edits" are just suggestions, which can be accepted or rejected. On Tue, Mar 6, 2018 at 1:33 PM, Wayne Stambaugh wrote: > I'm fine with using this for bike shedding as long as the results get > updated in the actual road map and this is not the

Re: [Kicad-developers] Proposed roadmap changes

I'm fine with using this for bike shedding as long as the results get updated in the actual road map and this is not the official road map. One caveat, by allowing anyone to edit this file, you may loose control of it's content. That's one of the things I don't like about launchpads blueprints.

Re: [Kicad-developers] Proposed roadmap changes

On 3/5/2018 1:15 PM, Jon Evans wrote: > I believe embedded symbols is part of the file format / library format > change heading. It is part of the new schematic file format. > > Back-annotation support in general is under the heading of "Pin and Part > Swapping" in the roadmap, and it's a good

Re: [Kicad-developers] Proposed roadmap changes

I believe embedded symbols is part of the file format / library format change heading. Back-annotation support in general is under the heading of "Pin and Part Swapping" in the roadmap, and it's a good idea to include re-annotating components as part of that. On Mon, Mar 5, 2018 at 1:11 PM, Andy

Re: [Kicad-developers] Proposed roadmap changes

> On Mar 5, 2018, at 10:57 AM, Jon Evans wrote: > > Hi all, > > Since my day job involves a lot of engineering planning/timelines/etc, I've > had this rolling around in my head... > I started brainstorming some proposed changes to the roadmaps. > > I am using Google

[Kicad-developers] Proposed roadmap changes

Hi all, Since my day job involves a lot of engineering planning/timelines/etc, I've had this rolling around in my head... I started brainstorming some proposed changes to the roadmaps. I am using Google drive because that's what is easiest for me to play with; I'm happy to send patches against