Re: [Kicad-developers] Documenting environment variables

[Adam Wolf]

Seconded.  We could use more focused but in-depth articles, even if they're
not perfectly appropriate for reference documentation.

Adam

On Sun, Jun 24, 2018, 5:10 PM hauptmech  wrote:

> Hi Eeli,
>
> It's really cool you wrote this up. I encourage you to publish this as a
> blog article, or an informational post on kicad.info once you are happy
> with it. Ironically it's more likely to be read and used there than the
> official documentation.
>
> -hauptmech
>
> On 25/06/18 08:30, Eeli Kaikkonen wrote:
>
> Thanks for the feedback. I don't feel need to aim this for the official
> documentation. I can of course host it where it is now or put it in a git
> service. And it certainly won't be "ready" for the 5.0 release. Right now
> the factual content is the most important. It's meant to help especially
> those who need to change configurations for e.g. KiCad 4 + 5 combination,
> so I just keep it available and try to enhance it little by little. If I'll
> get comments, I'll gather and store them for future editing sessions.
> Possible factual errors I try to fix immediately.
>
> Eeli Kaikkonen
>
> su 24. kesäk. 2018 klo 22.56 Wayne Stambaugh (stambau...@gmail.com)
> kirjoitti:
>
>> Hi Eeli,
>>
>> This is a good first start but it definitely needs some work before it's
>> ready for the kicad documentation.  I don't see this being ready for the
>> stable 5 release unless someone has some time to step up and clean up
>> the grammar and overly verbose writing.  I'm also not sure where this
>> document would live.  The KiCad documentation seems like a good choice
>> but it also might be reasonable to break it into specific app related
>> pieces.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 06/23/2018 06:45 AM, Eeli Kaikkonen wrote:
>> > As I have said earlier, I have written a document about KiCad and
>> > environment variables. It ended up being larger than I expected. It
>> > handles even some tangential subjects and my style is verbose. Still I
>> > hope it could be useful. I need feedback. Facts are of course the most
>> > important, but I also take constructive criticism about the content in
>> > general, structure and English grammar (I'm not a native speaker).
>> >
>> > It was suggested that maybe this could be added to the official
>> > documentation. I'm open to different possibilities. I'm ready to
>> convert
>> > the document to a different format.
>> >
>> > Here's the link:
>> >
>> https://docs.google.com/document/d/1Rq8i2Ay7qpGpffaj-AQmE-Xp88ikHhgyt0Ygpi8717o/edit?usp=sharing
>> >
>> > Eeli Kaikkonen
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] rc3

[Wayne Stambaugh]

Thanks Rene.  I'm going to hold off until tomorrow.  There are two bugs 
that probably need to be fixed before rc3 is tagged.  Hopefully we will 
get them resolved quickly.


On 06/24/2018 03:39 PM, Rene Pöschl wrote:
I just added the rc3 tag to the library. (A bit later than promised. 
Hope this is still ok.)


On 24/06/18 03:12, Rene Pöschl wrote:

I can add the rc3 tag to the library repos sometime Sunday afternoon.
(central European time)
A few minor corrections would still be nice to get into v5 but we do not
have any deal-breaker that would merit postponing v5 from our side.

On 23/06/18 17:15, Wayne Stambaugh wrote:

Let's try to get rc3 by tomorrow.  That will give us almost a week of
testing before the 30th.  If no major issues arise between now and then,
I will tag 5.0.0 on the 30th.  I will be traveling for vacation the
following week so this will give everyone time to get everything ready
for the stable 5 release.  I will make the release announcement after I
get back from vacation once everything is ready to go.  Thank you
everyone for your continued efforts and support of the KiCad project.

Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp






___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Documenting environment variables

[hauptmech]

Hi Eeli,

It's really cool you wrote this up. I encourage you to publish this as a 
blog article, or an informational post on kicad.info once you are happy 
with it. Ironically it's more likely to be read and used there than the 
official documentation.


-hauptmech

On 25/06/18 08:30, Eeli Kaikkonen wrote:
Thanks for the feedback. I don't feel need to aim this for the 
official documentation. I can of course host it where it is now or put 
it in a git service. And it certainly won't be "ready" for the 5.0 
release. Right now the factual content is the most important. It's 
meant to help especially those who need to change configurations for 
e.g. KiCad 4 + 5 combination, so I just keep it available and try to 
enhance it little by little. If I'll get comments, I'll gather and 
store them for future editing sessions. Possible factual errors I try 
to fix immediately.


Eeli Kaikkonen

su 24. kesäk. 2018 klo 22.56 Wayne Stambaugh (stambau...@gmail.com 
) kirjoitti:


Hi Eeli,

This is a good first start but it definitely needs some work
before it's
ready for the kicad documentation.  I don't see this being ready
for the
stable 5 release unless someone has some time to step up and clean up
the grammar and overly verbose writing.  I'm also not sure where this
document would live.  The KiCad documentation seems like a good
choice
but it also might be reasonable to break it into specific app related
pieces.

Cheers,

Wayne

On 06/23/2018 06:45 AM, Eeli Kaikkonen wrote:
> As I have said earlier, I have written a document about KiCad and
> environment variables. It ended up being larger than I expected. It
> handles even some tangential subjects and my style is verbose.
Still I
> hope it could be useful. I need feedback. Facts are of course
the most
> important, but I also take constructive criticism about the
content in
> general, structure and English grammar (I'm not a native speaker).
>
> It was suggested that maybe this could be added to the official
> documentation. I'm open to different possibilities. I'm ready to
convert
> the document to a different format.
>
> Here's the link:
>

https://docs.google.com/document/d/1Rq8i2Ay7qpGpffaj-AQmE-Xp88ikHhgyt0Ygpi8717o/edit?usp=sharing
>
> Eeli Kaikkonen
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers

> Post to     : kicad-developers@lists.launchpad.net

> Unsubscribe : https://launchpad.net/~kicad-developers

> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers

Post to     : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Documenting environment variables

[Eeli Kaikkonen]

Thanks for the feedback. I don't feel need to aim this for the official
documentation. I can of course host it where it is now or put it in a git
service. And it certainly won't be "ready" for the 5.0 release. Right now
the factual content is the most important. It's meant to help especially
those who need to change configurations for e.g. KiCad 4 + 5 combination,
so I just keep it available and try to enhance it little by little. If I'll
get comments, I'll gather and store them for future editing sessions.
Possible factual errors I try to fix immediately.

Eeli Kaikkonen

su 24. kesäk. 2018 klo 22.56 Wayne Stambaugh (stambau...@gmail.com)
kirjoitti:

> Hi Eeli,
>
> This is a good first start but it definitely needs some work before it's
> ready for the kicad documentation.  I don't see this being ready for the
> stable 5 release unless someone has some time to step up and clean up
> the grammar and overly verbose writing.  I'm also not sure where this
> document would live.  The KiCad documentation seems like a good choice
> but it also might be reasonable to break it into specific app related
> pieces.
>
> Cheers,
>
> Wayne
>
> On 06/23/2018 06:45 AM, Eeli Kaikkonen wrote:
> > As I have said earlier, I have written a document about KiCad and
> > environment variables. It ended up being larger than I expected. It
> > handles even some tangential subjects and my style is verbose. Still I
> > hope it could be useful. I need feedback. Facts are of course the most
> > important, but I also take constructive criticism about the content in
> > general, structure and English grammar (I'm not a native speaker).
> >
> > It was suggested that maybe this could be added to the official
> > documentation. I'm open to different possibilities. I'm ready to convert
> > the document to a different format.
> >
> > Here's the link:
> >
> https://docs.google.com/document/d/1Rq8i2Ay7qpGpffaj-AQmE-Xp88ikHhgyt0Ygpi8717o/edit?usp=sharing
> >
> > Eeli Kaikkonen
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Documenting environment variables

[Wayne Stambaugh]

Hi Eeli,

This is a good first start but it definitely needs some work before it's 
ready for the kicad documentation.  I don't see this being ready for the 
stable 5 release unless someone has some time to step up and clean up 
the grammar and overly verbose writing.  I'm also not sure where this 
document would live.  The KiCad documentation seems like a good choice 
but it also might be reasonable to break it into specific app related 
pieces.


Cheers,

Wayne

On 06/23/2018 06:45 AM, Eeli Kaikkonen wrote:
As I have said earlier, I have written a document about KiCad and 
environment variables. It ended up being larger than I expected. It 
handles even some tangential subjects and my style is verbose. Still I 
hope it could be useful. I need feedback. Facts are of course the most 
important, but I also take constructive criticism about the content in 
general, structure and English grammar (I'm not a native speaker).


It was suggested that maybe this could be added to the official 
documentation. I'm open to different possibilities. I'm ready to convert 
the document to a different format.


Here's the link: 
https://docs.google.com/document/d/1Rq8i2Ay7qpGpffaj-AQmE-Xp88ikHhgyt0Ygpi8717o/edit?usp=sharing


Eeli Kaikkonen


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] GAL: Draw hole even if pad has no layer

[Wayne Stambaugh]

Are we planning on fixing this for rc3?  If so, what is required.  I'm 
fine with waiting a day or two to tag rc3.


On 06/23/2018 04:42 PM, Seth Hillbrand wrote:

​Andrzej-

I would prefer that this be fixed when reading the malformed file, not 
displaying.​  We fix it there, the display issue goes away.  This also 
protects from unintended side effects rather than trying to code work 
arounds for a malformed board in multiple parts of the code.


-S


Am Sa., 23. Juni 2018 um 13:18 Uhr schrieb Andrzej Wolski 
mailto:awolski.ki...@gmail.com>>:


When you generate gerbers from a valid NPTH pad with hole size = pad
size, there will be no shape plotted on copper layers, so in my
opinion,
this pad does not exist on copper layers. But this is more
philosophical
discussion :)

Regarding clearance for router, you could just take the merged shape of
both pad and hole. This would solve problems you mentioned, and perhaps
some other edge cases.

This is just my opinion, I'm not proposing to change anything in kicad
(at least not in the near future).

So if you agree to GAL fix, can this patch be merged?

Cheers,
Andrzej


W dniu 2018-06-23 o 08:54, jp charras pisze:
 > Le 22/06/2018 à 21:54, Andrzej Wolski a écrit :
 >> No, this IS an error in the board :)
 >> If you open pad properties and click OK, it won't let you save
it as is, you will have to enable
 >> copper layers.
 >> NPTH pads also HAVE TO exists on copper layers (I don't
understand why, but they do).
 > Just because they *are* on these copper layers, regardless the
hole has removed the visible copper area.
 >
 > A pad is not only a copper area. It also define a clearance area,
that is not necessary the hole area.
 > If you say: this pad is not on this copper layer, it means you
have no obstacle to draw a track.
 > This is obviously false: the hole in on this layer.
 >
 > If a NPTH is removed from copper layers (malformed pad), the PnS
router will happily route a track
 > crossing the hole, because it is the mathematical result of "this
pad is not here".
 > You can think: there is a bug in PnS router.
 > But the Truth is the pad is broken and has incorrect layer
setting, therefore incorrect routing
 > constraints (and incorrect fill zone param).
 >
 > Therefore regardless the GAL fix, the malformed pad (like any
malformed item) need a fix when
 > reading the file, because it this king of issue can create
problems, even crashes.
 >
 > Of course, the GAL draw issue needs also to be fixed: it must
show the hole, even for malformed pads.
 >
 >> Also, as I already mentioned, current GAL behavior is different
from 4.0 GAL and legacy, so this is
 >> a regression.
 >>
 >> Andrzej
 >>
 >> W dniu 2018-06-22 o 21:44, Seth Hillbrand pisze:
 >>> Ah.  This is not an error in the board.  This is just an NPTH. 
If you click on it in GAL, you

 >>> will see it.
 >>>
 >>> I think the correct patch to this should check the pad type
instead of drawing one with no layers.
 >>>
 >>> -S
 >>>
 >>> Am Fr., 22. Juni 2018 um 12:33 Uhr schrieb Andrzej Wolski
mailto:awolski.ki...@gmail.com>
 >>> >>:
 >>>
 >>>      IIRC you have to leave (layers) to reproduce this.
 >>>
 >>>      This is a board where I found the issue:
 >>>

https://github.com/mntmn/reform/blob/master/electronics/reform-motherboard.kicad_pcb
 >>>      There are two mPCIE connectors in the center, they have
NPTH alignment holes, you can see them
 >>>      in legacy mode.
 >>>
 >>>      Andrzej
 >>>
 >>>      W dniu 2018-06-22 o 20:06, Seth Hillbrand pisze:
       Andrzej-
 
       I just tested this, editing a file to remove the layers
from a pad and KiCad automatically
       adds the pad back to all copper layers.  I see the pad in
pcbnew and can edit it.
 
       Can you provide a board that demonstrates the issue? 
Maybe it was only the test board I used?

 
       -S
 
       Am Fr., 22. Juni 2018 um 10:51 Uhr schrieb Andrzej Wolski
mailto:awolski.ki...@gmail.com>
       >>:
 
           Hi Seth,
 
           current behavior is that malformed pad holes are
always hidden, so you can't see on the
           screen something that exists on your PCB and will be
plotted in drill files. This patch
           makes those holes visible.
 
           Andrzej
 
           W dniu 2018-06-22 o 17:46, Seth Hillbrand pisze:
 >          ​Andrzej-
 >
 >          Can you e

Re: [Kicad-developers] rc3

[Rene Pöschl]

I just added the rc3 tag to the library. (A bit later than promised. 
Hope this is still ok.)


On 24/06/18 03:12, Rene Pöschl wrote:

I can add the rc3 tag to the library repos sometime Sunday afternoon.
(central European time)
A few minor corrections would still be nice to get into v5 but we do not
have any deal-breaker that would merit postponing v5 from our side.

On 23/06/18 17:15, Wayne Stambaugh wrote:

Let's try to get rc3 by tomorrow.  That will give us almost a week of
testing before the 30th.  If no major issues arise between now and then,
I will tag 5.0.0 on the 30th.  I will be traveling for vacation the
following week so this will give everyone time to get everything ready
for the stable 5 release.  I will make the release announcement after I
get back from vacation once everything is ready to go.  Thank you
everyone for your continued efforts and support of the KiCad project.

Cheers,

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] V5 upgrade documentation

[Wayne Stambaugh]

hauptmech,

I merged your patch and pushed the changes upstream to the kicad doc
repo.  Thank you for the help with the documentation.

Cheers,

Wayne

On 06/23/2018 08:54 PM, hauptmech wrote:
> 
> Attached
> 
> On 24/06/18 02:46, Wayne Stambaugh wrote:
>> Hey hauptmech
>>
>> For the most part I'm fine with these changes.  I think that the first
>> two paragraphs (sentences) in the "Schematic Symbol Libraries" section
>> of the version upgrade document could be merged into a single paragraph
>> since they are related.
>>
>> If no one else objects to these changes, please create a merge request
>> and I'll merge them into my repo and push them upstream today or
>> tomorrow.
>>
>> Thanks for the help.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 06/23/2018 12:15 AM, hauptmech wrote:
>>> Hi Wayne,
>>>
>>> Really awesome that you are creating this documentation!
>>>
>>> A couple thoughts:
>>> * No one reads documentation unless they have to. Usually after stabbing
>>> in the dark for a while.
>>> * If one has to read documentation, one wants it short and to the point.
>>> * Whatever basic knowledge you want the reader to have about how kicad
>>> works, they won't have it.
>>>
>>> With that in mind I did a little example editing with the following
>>> goals:
>>>
>>> * Link to any info that is a requirement for understanding this
>>> document. If you can't find any existing documentation to link to,
>>> that's a good clue that we need to fill in more info locally.
>>> * Leave out as many extra words as possible.
>>>
>>> https://github.com/hauptmech/kicad-doc/blob/master/src/kicad/kicad_upgrading_from_v4_to_v5.adoc
>>>
>>>
>>> https://github.com/hauptmech/kicad-doc/blob/master/src/eeschema/eeschema_symbol_library_table.adoc
>>>
>>>
>>>
>>> It's not formatted as a patch because I only edited a few paragraphs,
>>> and in those I rewrote things completely as an example of the above.
>>>
>>>
>>>
>>>
>>> On 23/06/18 04:10, Wayne Stambaugh wrote:
 I pushed the v5 upgrade document to my personal repo[1] on git hub.  I
 made it part of the KiCad documentation but I don't have a strong
 opinion about where to add it.  This just seemed like the most logic
 place.  Please review it when you get a chance.  If you find any issues
 let me know, send me a patch, or submit a pull request against my doc
 repo.  Keep in mind that this document is only to detail the changes
 that will effect project compatibility with older versions of kicad and
 the perils of symbol remapping.  Thanks in advance for the help.

 Cheers,

 Wayne

 [1]:
 https://github.com/stambaughw/kicad-doc/blob/master/src/kicad/kicad_upgrading_from_v4_to_v5.adoc



 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Fix overbar drawing for non-italic text

[Wayne Stambaugh]

Andrzej,

I merged your patch.  Thank you for your contribution to KiCad.

Cheers,

Wayne

On 06/22/2018 06:58 AM, Andrzej Wolski wrote:
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] explode an intersection, how to start?

[Greg Smith]

Look at KiCommand and construct a command string that 
1) copies the selected elements A and B
2) uses "cut" to cut A with copy B and B with copy A

KiCommand was created for this exact type of situation: easy 
command-line-driven geometry manipulations.

Greg S.

> On Jun 23, 2018, at 8:46 PM, jc  wrote:
> 
> I wish the developpers can provide this function. Or someone else can.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp