Re: [Kicad-developers] GitLab migration

2019-11-09 Thread Andrew Lutsenko
I second Seth's opinion, this is fantastic. One suggestion: create a service account for the bot and name it something self-evident like "Migration Bot" to avoid possible confusion about authorship. Regards, Andrew On Sat, Nov 9, 2019 at 2:40 PM Seth Hillbrand wrote: > On 2019-11-09 14:08, Maci

Re: [Kicad-developers] Symbol library code changes

2019-11-09 Thread Brian Piccioni
Sorry the link to the symbol library format doesn’t seem to work. Can you supply a link which works and maybe a link to the PCB file format? I’ve been dying to know ... From: Wayne Stambaugh Sent: November 9, 2019 3:42 PM To: kicad-developers@lists.launchpad.net Subject: Re: [Kicad-developers]

Re: [Kicad-developers] GitLab migration

2019-11-09 Thread Seth Hillbrand
On 2019-11-09 14:08, Maciej Suminski wrote: I have fixed all issues, taking into account the ones reported on the mailing list and Ian's 'Gitlab Issue Tracker Guidelines' [1]. In my opinion, the bug tracker is ready to be moved to Gitlab. You can check out the latest bug tracker migration in my t

Re: [Kicad-developers] GitLab migration

2019-11-09 Thread Maciej Suminski
I have fixed all issues, taking into account the ones reported on the mailing list and Ian's 'Gitlab Issue Tracker Guidelines' [1]. In my opinion, the bug tracker is ready to be moved to Gitlab. You can check out the latest bug tracker migration in my test project [2]. Cheers, Orson 1. https://do

Re: [Kicad-developers] Project save as

2019-11-09 Thread Jeff Young
He he… I know our users. I can be sure of a bug report even if I get it right. ;) > This is exactly why I never tackled this one. Anytime your are trying > to deal with complex relative path changes, the code gets rather messy. > I doubt this will affect many users but you can be rest assured o

Re: [Kicad-developers] Symbol library code changes

2019-11-09 Thread Wayne Stambaugh
Hi Brian, On 11/7/2019 3:39 PM, Brian wrote: > From the peanut gallery: > I know 6.0 symbol library handling has many significant differences > versus 5.x.  Eventually, if I want to keep myself at or near the > bleeding edge, I'll have to port my ODBC stuff to the 6.0 way of doing > things.  A cou

Re: [Kicad-developers] Project save as

2019-11-09 Thread Wayne Stambaugh
On 11/9/2019 2:18 PM, Jeff Young wrote: > Hi Wayne, > >> On 9 Nov 2019, at 19:05, Wayne Stambaugh wrote: >> >> Hey Jeff, >> >> On 11/9/2019 12:06 PM, Jeff Young wrote: >>> I’m working through the project Save As feature. >>> >>> I currently have it renaming the top-level files, updating the symbo

Re: [Kicad-developers] Project save as

2019-11-09 Thread Jeff Young
Hi Wayne, > On 9 Nov 2019, at 19:05, Wayne Stambaugh wrote: > > Hey Jeff, > > On 11/9/2019 12:06 PM, Jeff Young wrote: >> I’m working through the project Save As feature. >> >> I currently have it renaming the top-level files, updating the symbol and >> footprint lib tables, updating paths in

Re: [Kicad-developers] Project save as

2019-11-09 Thread Wayne Stambaugh
Hey Jeff, On 11/9/2019 12:06 PM, Jeff Young wrote: > I’m working through the project Save As feature. > > I currently have it renaming the top-level files, updating the symbol and > footprint lib tables, updating paths in Gerber job files, and updating paths > and filenames in the netlist. >

[Kicad-developers] Project save as

2019-11-09 Thread Jeff Young
I’m working through the project Save As feature. I currently have it renaming the top-level files, updating the symbol and footprint lib tables, updating paths in Gerber job files, and updating paths and filenames in the netlist. A couple of questions: 1) The netlist I’m handling is a .net f