Re: [Kicad-developers] 5.1 UI feedback

There is a proposal document from Jon Evans that would add the ability to have more powerful design rule system. It would really be good to keep working on that and getting something similarly powerful added to KiCad.

Re: [Kicad-developers] 5.1 UI feedback

Right, but that will be beyond the scope of 5.1 as it involves new features. You can see the proposed v6 ERC/DRC roadmap here https://docs.google.com/document/d/1qvCH9aHwCzp5qtKTna4jJXuloNU0b96gAxAHSKPuXpU/edit?usp=sharing Feel free to suggest where you feel it could be improved. Am Mo., 16.

Re: [Kicad-developers] 5.1 UI feedback

On 16/07/18 23:44, hauptmech wrote: > Just a friendly reminder that net classes are not a good approach for > some of us. > > I have never used net classes because they make the assumption that one > want's constant trace/space on a net. > > Most of my boards these days are using components with

Re: [Kicad-developers] 5.1 UI feedback

Just a friendly reminder that net classes are not a good approach for some of us. I have never used net classes because they make the assumption that one want's constant trace/space on a net. Most of my boards these days are using components with BGA or LGA pad spacing tighter than I want

Re: [Kicad-developers] Version 5 source update

This bug is annoying but not terribly important. There is also bug in one of the footprint editor dialogs that also needs fixed so we might as well queue a few bug fixes up for a 5.0.1 release in a few weeks and get the 5.0.0 release out on time. On 7/16/2018 3:10 PM, Seth Hillbrand wrote: >

Re: [Kicad-developers] 5.1 branch

Whew, I think that was ~1200 bugs fixed/feature requests handled. Well done, team! Now let's sweep our mailboxes.. Cheers, Orson On 07/16/2018 06:14 PM, Jeff Young wrote: > I started doing some by hand and Orson is right: tedious isn’t the half of > it. I’ll wait for his script. ;) > > >> On

Re: [Kicad-developers] Version 5 source update

Should we just tag v5.0.1 right now then and ignore 5.0.0? Is there any reason not to do that? Am Mo., 16. Juli 2018 um 11:55 Uhr schrieb Wayne Stambaugh < stambau...@gmail.com>: > Hey Carsten, > > On 7/16/2018 2:46 PM, Carsten Schoenert wrote: > > Hello Wayne, > > > > Am 16.07.18 um 20:20

Re: [Kicad-developers] 5.1 UI feedback

Le 16/07/2018 à 18:25, Jeff Young a écrit : > Hi JP, > > Thanks for the feedback. > >> On 16 Jul 2018, at 16:05, jp charras wrote: >> >> Hi Jeff, >> >> I just played with a few of your 5.1 changes. >> >> Many are good, but the new netclass management is not as efficient as the >> current

Re: [Kicad-developers] Version 5 source update

Hey Carsten, On 7/16/2018 2:46 PM, Carsten Schoenert wrote: > Hello Wayne, > > Am 16.07.18 um 20:20 schrieb Wayne Stambaugh: >> There is a fix for a bug[1] that I thought we had taken care that >> slipped through the cracks. This really should have been fixed as part >> of the v5 release. If

Re: [Kicad-developers] Version 5 source update

Hello Wayne, Am 16.07.18 um 20:20 schrieb Wayne Stambaugh: > There is a fix for a bug[1] that I thought we had taken care that > slipped through the cracks. This really should have been fixed as part > of the v5 release. If there are no objections, I'm going to revert the > v5 tags and version

Re: [Kicad-developers] Version 5 source update

No worries. I can merge first to master this way and then pull back to 5.1. > On 16 Jul 2018, at 19:20, Wayne Stambaugh wrote: > > There is a fix for a bug[1] that I thought we had taken care that > slipped through the cracks. This really should have been fixed as part > of the v5 release.

Re: [Kicad-developers] 5.1 UI feedback

Le 16/07/2018 à 19:57, Jeff Young a écrit : > > >> On 16 Jul 2018, at 17:56, jp charras > > wrote: >> >> Le 16/07/2018 à 18:25, Jeff Young a écrit : >>> Hi JP, >>> >>> Thanks for the feedback. >>> On 16 Jul 2018, at 16:05, jp charras >>>

[Kicad-developers] Version 5 source update

There is a fix for a bug[1] that I thought we had taken care that slipped through the cracks. This really should have been fixed as part of the v5 release. If there are no objections, I'm going to revert the v5 tags and version string and add this patch to v5. Until then, please do not merge

Re: [Kicad-developers] 5.1 UI feedback

> On 16 Jul 2018, at 17:56, jp charras wrote: > > Le 16/07/2018 à 18:25, Jeff Young a écrit : >> Hi JP, >> >> Thanks for the feedback. >> >>> On 16 Jul 2018, at 16:05, jp charras wrote: >>> >>> Hi Jeff, >>> >>> I just played with a few of your 5.1 changes. >>> >>> Many are good, but the

Re: [Kicad-developers] kicad version and install location

On Jul 16, 2018, at 10:22 AM, Mark Roszko wrote: > > Yeathats what I proposed too. > > Every program on Windows that needs side-by-side installs just > versions both the config and install locations. Thats it. > > EAGLE does it. > Visual Studio does. > Altium does it. > CLion does it. >

Re: [Kicad-developers] 5.1 branch

I have the script ready to run. It will just change all KiCad bug statuses from 'Fix Committed' to 'Fix Release'. I assume there are no bugs that are marked as 'Fix Committed', but not actually in the master branch, right? Are you ready for an infinite stream of bug tracker notifications? :>

Re: [Kicad-developers] kicad version and install location

Yeathats what I proposed too. Every program on Windows that needs side-by-side installs just versions both the config and install locations. Thats it. EAGLE does it. Visual Studio does. Altium does it. CLion does it. All of Jetbrains other product do it. Microsoft Word does it Adobe does it.

Re: [Kicad-developers] 5.1 branch

Le 16/07/2018 à 17:54, Wayne Stambaugh a écrit : > I was really hoping just to fix the wxDC issues with GTK3 rather than > implement GAL unless Tom implemented a wxDC GAL and that is all we > expose for 5.1. The primary goal here is to fix the GTK3 rendering > issues so we can enable wxPython

[Kicad-developers] 5.1 UI feedback

Hi JP, Thanks for the feedback. > On 16 Jul 2018, at 16:05, jp charras wrote: > > Hi Jeff, > > I just played with a few of your 5.1 changes. > > Many are good, but the new netclass management is not as efficient as the > current dialog: > > - Modifying the netclass of a lot of nets is very

Re: [Kicad-developers] 5.1 branch

I started doing some by hand and Orson is right: tedious isn’t the half of it. I’ll wait for his script. ;) > On 16 Jul 2018, at 16:59, Wayne Stambaugh wrote: > > My finger is on the delete key. Fire when ready! > > On 7/16/2018 11:48 AM, Maciej Sumiński wrote: >> I have the script ready

Re: [Kicad-developers] 5.1 branch

My finger is on the delete key. Fire when ready! On 7/16/2018 11:48 AM, Maciej Sumiński wrote: > I have the script ready to run. It will just change all KiCad bug > statuses from 'Fix Committed' to 'Fix Release'. I assume there are no > bugs that are marked as 'Fix Committed', but not actually

Re: [Kicad-developers] 5.1 branch

No time like the present! -S Am Mo., 16. Juli 2018 um 08:49 Uhr schrieb Maciej Sumiński < maciej.sumin...@cern.ch>: > I have the script ready to run. It will just change all KiCad bug > statuses from 'Fix Committed' to 'Fix Release'. I assume there are no > bugs that are marked as 'Fix

Re: [Kicad-developers] 5.1 branch

I was really hoping just to fix the wxDC issues with GTK3 rather than implement GAL unless Tom implemented a wxDC GAL and that is all we expose for 5.1. The primary goal here is to fix the GTK3 rendering issues so we can enable wxPython support again. We need to limit our risk exposure for 5.1.

Re: [Kicad-developers] 5.1 branch

Tom has already prepared a proof-of-concept eeschema with GAL rendering, which still uses the legacy tools. I have some promising results switching the printing system to Cairo GAL. Obviously we will face some unexpected obstacles, but I have high hopes. Cheers, Orson On 07/16/2018 03:40 PM,

Re: [Kicad-developers] 5.1 branch

That would probably be the easiest solution with the least amount of risk. Although you could not run it for point releases because bugs that are only valid for the development branch would get set to fix released which would not be correct. On 7/16/2018 11:08 AM, Maciej Sumiński wrote: > It is

Re: [Kicad-developers] 5.1 branch

It is terribly tedious to go through the bug list and change statuses one by one, so I offer to help with the bug report status fiddling. We may employ Janitor, but I guess it would be better to execute a simple script to change Fix Committed->Fix Released whenever we release a new version.

Re: [Kicad-developers] Questions on 6.0 eeschema file format

Even though I'm not quite ready to start discussing the new file formats just yet, here a few of my thoughts on inheritance: Inheritance will be implemented in a second phase during the development of the new file formats and possibly pushed into the version 7 release. The reason is that there is

Re: [Kicad-developers] 5.1 branch

Hi Jeff, I just played with a few of your 5.1 changes. Many are good, but the new netclass management is not as efficient as the current dialog: - Modifying the netclass of a lot of nets is very tedious: the change must be done for each net (this is the major issue). - we cannot see easily

Re: [Kicad-developers] 5.1 branch

On 7/16/2018 10:37 AM, jp charras wrote: > Le 16/07/2018 à 16:09, Jeff Young a écrit : >> I keep seeing issues with “incorrect” ratsnests on the kicad.info >>  forums.  Can >> we put the curved ratsnests into 5.1? > > This artifact exists only in Legacy mode, due to the XOR

Re: [Kicad-developers] 5.1 branch

Le 16/07/2018 à 16:09, Jeff Young a écrit : > I keep seeing issues with “incorrect” ratsnests on the kicad.info >  forums.  Can > we put the curved ratsnests into 5.1? This artifact exists only in Legacy mode, due to the XOR mode used to draw them. curved ratsnests (it can be

Re: [Kicad-developers] kicad version and install location

This also doesn't help user with environment variables set in their config files. Installing kicad in a different folder will not resolve this issue. We have the rather posix like method of setting XDG_USER_CONFIG variable to point to a different user config path but that isn't really windows

Re: [Kicad-developers] Questions on 6.0 eeschema file format

My guess would be maintainability. Having some way of sharing parts of different symbols with each other makes it way easier to manage large libs. (Nobody would be forced to use these features but they can make live easier for library maintainers. We could then for example provide a single

Re: [Kicad-developers] 5.1 branch

I can't think of any reason not to change the fix committed bug reports to fix released so if you have the time, have at it. On 7/16/2018 9:54 AM, Jeff Young wrote: > Cool. I’ll wait a few more days to make sure everything is settled down and > then merge the 5.1 stuff to master. > > Should we

Re: [Kicad-developers] Questions on 6.0 eeschema file format

On 16/07/18 16:04, Jeff Young wrote: > Thinking more about it, we could probably auto-convert existing aliases to > inheritance when we read them in. Why do we need any inheritance at all? My only guess is to make Kicad even more hackerish and difficult to understand. Tom

Re: [Kicad-developers] kicad version and install location

This only helps users who never had system environment variables set. They overwrite the settings coming from the config folders. (So all default windows installation are not helped with this.) On 16/07/18 16:16, Nick Østergaard wrote: Why does this need to be so complicated? I think we

Re: [Kicad-developers] kicad version and install location

Why does this need to be so complicated? I think we could just rename the kicad config folder created and searched by kicad from "kicad" to "kicad5" and be happy in the 5.x branches. Den man. 16. jul. 2018 kl. 15.11 skrev Bob Gustafson : > > There is a tool which allows developers to quickly

Re: [Kicad-developers] 5.1 branch

I keep seeing issues with “incorrect” ratsnests on the kicad.info forums. Can we put the curved ratsnests into 5.1? > On 16 Jul 2018, at 14:54, Jeff Young wrote: > > Cool. I’ll wait a few more days to make sure everything is settled down and > then merge the 5.1 stuff

Re: [Kicad-developers] Questions on 6.0 eeschema file format

Thinking more about it, we could probably auto-convert existing aliases to inheritance when we read them in. It would certainly be easier to support only one UI (and the alias UI is problematic anyway). Wayne sent out a proposal on the dev list a while back. I know I read them so they must

Re: [Kicad-developers] 5.1 branch

Yes, assuming we can get that to work without dragging in Phoenix. On 7/16/2018 9:27 AM, Jeff Young wrote: > 5.1 is also for the GTK3 fixes, right? > >> On 16 Jul 2018, at 14:23, Wayne Stambaugh wrote: >> >> On 7/16/2018 9:19 AM, Simon Richter wrote: >>> Hi, >>> >>> On 15.07.2018 13:39, Jeff

Re: [Kicad-developers] 5.1 branch

Cool. I’ll wait a few more days to make sure everything is settled down and then merge the 5.1 stuff to master. Should we go ahead and start making the Fix Committed bugs Fix Released, or do we want to wait for the release announcement? > On 16 Jul 2018, at 14:30, Wayne Stambaugh wrote: > >

Re: [Kicad-developers] 5.1 branch

Hey Jeff, We have been manually changing the bug status from fix committed to fix released after a new stable release. AFAIK, the janitor does not handle this. I suppose the janitor could be modified to test for a new release and change the tag for all bugs associated with that release. That

Re: [Kicad-developers] Questions on 6.0 eeschema file format

Hi, On 16.07.2018 11:19, Jeff Young wrote: > Do we plan on having inheritance replace aliases? I do, but you might have noticed that with all my other commitments that isn't worth much. Do we have a spec document beyond what was discussed on IRC? > If so, what do we do with old symbols?

Re: [Kicad-developers] 5.1 branch

5.1 is also for the GTK3 fixes, right? > On 16 Jul 2018, at 14:23, Wayne Stambaugh wrote: > > On 7/16/2018 9:19 AM, Simon Richter wrote: >> Hi, >> >> On 15.07.2018 13:39, Jeff Young wrote: >> >>> I renamed my 6.0 branch to 5.1, since most of what it contains goes there. >> >> What is the

Re: [Kicad-developers] 5.1 branch

On 7/16/2018 9:19 AM, Simon Richter wrote: > Hi, > > On 15.07.2018 13:39, Jeff Young wrote: > >> I renamed my 6.0 branch to 5.1, since most of what it contains goes there. > > What is the difference between 5.1 and 6.0? What goes into which branch? > >Simon > 5.1 is only for the UI

Re: [Kicad-developers] 5.1 branch

Hi Wayne, The other issue is that the Janitor is going to mark my fixes as Fix Committed, and I don’t know if the auto-bug-release facility is smart enough to check the milestone before converting Fix Committed to Fix Released. So we may need to do that first too. Cheers, Jeff. > On 16 Jul

Re: [Kicad-developers] 5.1 branch

Hi, On 15.07.2018 13:39, Jeff Young wrote: > I renamed my 6.0 branch to 5.1, since most of what it contains goes there. What is the difference between 5.1 and 6.0? What goes into which branch? Simon signature.asc Description: OpenPGP digital signature

Re: [Kicad-developers] 5.1 branch

Jeff, As a general rule, we merge changes into the development branch and then merge them into the stable release branch after they have been tested. In the past this has only been bug fixes so your case is slightly different. The problem I see with merging your changes into the 5.1 branch first

Re: [Kicad-developers] kicad version and install location

There is a tool which allows developers to quickly switch between different versions of Ruby (and their associated gemsets). Perhaps it could be used for KiCad? Or perhaps just some of RVM's ideas could be adapted for KiCad https://rvm.io/ On 07/15/2018 09:52 AM, Adam Wolf wrote: I guess

Re: [Kicad-developers] kicad version and install location

Hi Wayne, I'll see what I can do. It's possible this is a really quick change, to change the macos basename from kicad to kicad5, and that would even have it read different config files, I think! There are only 2 remaining macOS changes to make this week, and they're both documentation changes

Re: [Kicad-developers] kicad version and install location

As long as we are not pushing the b5 release schedule back I'm fine with this. On 7/15/2018 10:52 AM, Adam Wolf wrote: > I guess the fact that environment variables are tricky to set for > graphical applications for the Mac may be a blessing here :) > > Should we try to package a macOS version

Re: [Kicad-developers] Translation of dialog_bom_help.html

I noticed that the environment variables config dialog also has html-based help message. So I changed eeschema/dialogs/dialog_bom.cpp in the same manear as it done in common/dialogs/dialog_env_var_config.cpp. сб, 14 июл. 2018 г. в 10:01, jp charras : > Le 12/07/2018 à 14:59, Simon Richter a

[Kicad-developers] Questions on 6.0 eeschema file format

Do we plan on having inheritance replace aliases? If so, what do we do with old symbols? (Will we have to support both paradigms?) ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe

Re: [Kicad-developers] 5.1 branch

Thanks, JP! I’ll make the fix. > On 16 Jul 2018, at 09:24, jp charras wrote: > > Le 16/07/2018 à 10:10, Jeff Young a écrit : >> Well, rats. I couldn’t figure out why "git rebase —interactive" wasn’t >> showing me any of my >> commits, and it turns out that I somehow accidentally merged them

Re: [Kicad-developers] 5.1 branch

Le 16/07/2018 à 10:10, Jeff Young a écrit : > Well, rats.  I couldn’t figure out why "git rebase —interactive" wasn’t > showing me any of my > commits, and it turns out that I somehow accidentally merged them all to > origin/5.1 sometime last > night.  Anyway, you don’t have to fetch my private

Re: [Kicad-developers] 5.1 branch

Well, rats. I couldn’t figure out why "git rebase —interactive" wasn’t showing me any of my commits, and it turns out that I somehow accidentally merged them all to origin/5.1 sometime last night. Anyway, you don’t have to fetch my private branch to test it anymore; the kicad 5.1 branch will

Re: [Kicad-developers] New Kicad Features

Hi Tom, You can see our plan in the v6 roadmap [1], but the only related topic is the board stack up editor, which appears to be a prerequisite for the mentioned features. Obviously, it does not mean we are limited by the roadmap, but we need additional contributors for that to happen. We are

Re: [Kicad-developers] 5.1 branch

ma 16. heinäk. 2018 klo 8.48 Nick Østergaard (oe.n...@gmail.com) kirjoitti: > Can you edit anything on them? Can you provide a screenshot of the > preferences dialog? > > https://drive.google.com/file/d/1eq26OWT7TDeBTnbyAfUpUckT5V6MuwU8/view?usp=sharing