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] [PATCH] Rework footprint selection filtering to improve behavior

Fixed that issue, and pushed to master. Thanks for testing, Andrzej! On Mon, Mar 5, 2018 at 12:57 PM, Andrzej Wolski wrote: > Hi Jon, > > another small issue: if only enabled layer is In1.Cu, THT pads are > visible, but footprint cannot be selected. > I think that

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] Selection filtering, and other missing GAL functionality

That one is already in launchpad too: https://bugs.launchpad.net/kicad/+bug/1743099 Anything else not in launchpad? On Wed, Mar 7, 2018 at 6:03 PM, Tomasz Wlostowski wrote: > On 07/03/18 23:59, Jeff Young wrote: > > Drag Footprint. > > Working on that :) > > Don't

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] Selection filtering, and other missing GAL functionality

On 07/03/18 23:59, Jeff Young wrote: > Drag Footprint. Working on that :) Don't expect miracles, but basic P footprint dragging should be in early V6. Tom > >> On 7 Mar 2018, at 22:20, Jon Evans wrote: >> >> Hi all, >> >> As part of preparing a new 6.0 roadmap, I want to

Re: [Kicad-developers] Selection filtering, and other missing GAL functionality

Drag Footprint. > On 7 Mar 2018, at 22:20, Jon Evans wrote: > > Hi all, > > As part of preparing a new 6.0 roadmap, I want to make sure we have all > functionality that only exists in Legacy mode captured on Launchpad so we > don't forget about it. José just reminded me

[Kicad-developers] Selection filtering, and other missing GAL functionality

Hi all, As part of preparing a new 6.0 roadmap, I want to make sure we have all functionality that only exists in Legacy mode captured on Launchpad so we don't forget about it. José just reminded me that Legacy mode in PcbNew has some selection filtering features that don't exist in GAL, so

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] [PATCH] - File format shim for clearance data

Hi Thomasz, I hope I'm able to address you concerns. I'm stuck using kicad stable in many situations. I brought clearances up for discussion last July but no one moved on it, nor are they required to. Clearance management is a major pain point for me so I wrote a fix. This patch will let us

Re: [Kicad-developers] KiCad 5 and the Github footprint wizard?

On 07/03/18 17:09, Thomas Pointhuber wrote: Hi, at least in the nightly it is still possible to add GitHub libraries using "Append with Wizard". Will this change? Because when someone uses this feature, it only references to the old legacy repositories, without a clue about that. Regards,

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

[Kicad-developers] KiCad 5 and the Github footprint wizard?

Hi, at least in the nightly it is still possible to add GitHub libraries using "Append with Wizard". Will this change? Because when someone uses this feature, it only references to the old legacy repositories, without a clue about that. Regards, Thomas signature.asc Description: OpenPGP

Re: [Kicad-developers] Potential issue with 49486b83

The fix is good. I also noted that on the launchpad bug. Thanks for resolving this issue. Steve On 03/06/2018 04:08 PM, Jeff Young wrote: > It’s up, Kevin. Thanks for offering to test. > > Cheers, > Jeff. > > >> On 6 Mar 2018, at 20:33, Kevin Cozens wrote: >> >>

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] [PATCH] - File format shim for clearance data

Hi! On 2018-03-07 13:44, Tomasz Wlostowski wrote: > I'm not totally opposed to hauptmech's change, I just think it's too > early to merge it. We should discuss such ideas before writing code. My > goal for V6 DRC is to be able to define clearance rules for at least: > - per-net & per-netclass > -

Re: [Kicad-developers] [PATCH] - File format shim for clearance data

Le 07/03/2018 à 14:02, Wayne Stambaugh a écrit : > On 3/7/2018 7:44 AM, Tomasz Wlostowski wrote: >> On 07/03/18 12:10, Russell Oliver wrote: >>> Forgive my ignorance but why would storing the clearance for each track >>> segment (if required to by design intent) conflict with a sophisticated >>>

Re: [Kicad-developers] [PATCH] - File format shim for clearance data

On 07/03/18 14:02, Wayne Stambaugh wrote: > It will save us a lot of grief in the > long run. I can't agree more! Tom ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] [PATCH] - File format shim for clearance data

On 3/7/2018 7:44 AM, Tomasz Wlostowski wrote: > On 07/03/18 12:10, Russell Oliver wrote: >> Forgive my ignorance but why would storing the clearance for each track >> segment (if required to by design intent) conflict with a sophisticated >> design rule management system?  > > For example: what

Re: [Kicad-developers] [PATCH] - File format shim for clearance data

On 07/03/18 12:10, Russell Oliver wrote: > Forgive my ignorance but why would storing the clearance for each track > segment (if required to by design intent) conflict with a sophisticated > design rule management system?  For example: what would happen to the clearance of the segment/via if it

Re: [Kicad-developers] [PATCH] - File format shim for clearance data

Forgive my ignorance but why would storing the clearance for each track segment (if required to by design intent) conflict with a sophisticated design rule management system? As a general approach shouldn't KiCad allow freedom of design when the intention of the designer is clear? Russell On

Re: [Kicad-developers] [PATCH] - File format shim for clearance data

On 07/03/18 11:02, hauptmech wrote: > I have a patch for treating track clearance the same as track width. The > user can already specify a track width that is an exception to the > netclass width, and now do the same for clearance. ( > https://youtu.be/05vfAvYwDio ) Hi hauptmech, I'm sorry but

Re: [Kicad-developers] Board Edge clearance problem

On 07/03/18 06:34, Strontium wrote: > My second "show stopper" bug for me, using V5 RC2 > > I also reported this in the bug tracker, again sorry for the double up. > > I was trying to layout a board, but Kicad is refusing to let me lay > tracks or vias in close proximity to the board edge.  Its

[Kicad-developers] [PATCH] - File format shim for clearance data

I have a patch for treating track clearance the same as track width. The user can already specify a track width that is an exception to the netclass width, and now do the same for clearance. ( https://youtu.be/05vfAvYwDio ) This is not that patch. This is a small shim for the file format

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] Zone filling problems

Hi Steven, Good catch, thank you for the report. It should be already fixed (a3562b35 and later). Regards, Orson On 03/07/2018 06:28 AM, Strontium wrote: > Sorry for posting this, AND also posting a bug report, but i know you > guys are close to releasing a V5 and i have been testing RC2 from >