Re: [Kicad-developers] Bezier curves in DRAWSEGMENT class

[jp charras]

Le 14/09/2016 à 01:19, Tomasz Wlostowski a écrit :
> On 14.09.2016 00:00, Cirilo Bernardo wrote:
>> I think it would be nice to support Bezier curves but aside from adding
>> support for editing those curves, I think we need a good enough 2D
>> geometry kernel so that we can improve zone outlines and perhaps
>> even allow tracks to be straight, arc, or Bezier curve. In general though
>> I think good support for "PolyLine" would be of more general use; after
>> all any 2D Bezier curve can be easily approximated with a series of
>> circular arcs (which a Polyline can do).
> 
> Cirilo, JP,
> 
> I agree we need copper layer arc support. I'm reluctant to add Bezier
> curves unless they are approximated as polylines because of the
> complexity of necessary DRC functions. Writing an accurate arc-to-arc or
> arc-to-segment collision/distance check is already quite difficult.
> 
> Besides, what would be the use of such curves for PCB design other than
> fancy graphics (silkscreen, etc)?
> 
> Tom

AFAIK, it was never intended to be used on copper layers, only for fancy 
graphics.
It is not yet in use because the cost to use Bezier curves is high (editor, 
locate functions ...)
and the benefit is low.


-- 
Jean-Pierre CHARRAS

___
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 v2] Add KICAD_INSTALL_DEMOS CMake option

[Chris Pavlina]

He used 'git send-email', which also gives 'git am'-compatible patches.
You can merge this the same as usual, but you have to save the entire
email and then pass that to 'git am'. I just tested it, works fine.

On Tue, Sep 13, 2016 at 07:45:35PM -0400, Wayne Stambaugh wrote:
> Jose,
> 
> Please use `git format-patch` for submitting patches.  It makes it
> easier for me to merger your patches.
> 
> Thanks,
> 
> Wayne
> 
> On 9/8/2016 2:59 PM, José Ignacio Romero wrote:
> > 
> > It is ON by default, determines wether to install the bundled demos
> > and examples.
> > ---
> > 
> > This version has the required documentation changes.
> > 
> > ---
> >  CMakeLists.txt | 6 ++
> >  Documentation/development/compiling.md | 7 +++
> >  2 files changed, 13 insertions(+)
> > 
> > 
> > 
> > ___
> > 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] translation code rework

[Wayne Stambaugh]

On 9/11/2016 3:22 PM, Nick Østergaard wrote:
> 2016-09-09 16:02 GMT+02:00 Wayne Stambaugh :
>> On 9/7/2016 2:27 PM, Nick Østergaard wrote:
>>> 2016-03-12 1:37 GMT+01:00 Simon Wells :
 As part of the translation code rework that i am working on (and
 auto-detection) part of it is moving the need for changing anything in
 code to add a new language. As part of this involves the flags i was
 wondering whether anyone would be against moving them into the i18n
 repo (and distributed in the individual language folders, so that if
 kicad is compiled with having icons enabled in the menu they could
 still be used but they will be pulled at runtime so no addtional code
 nor icons required in the kicad tree

>>>
>>> This discussion seem to be related to the other thread:
>>> https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg17648.html
>>>
>>> It does not seem anyone is directly against removing the flags all together.
>>
>> As I stated in the previous thread I'm OK with removing the flags.  I'm
>> just concerned about what text we will use in the language menu.
>> Translated, English, always the current locale, or something else?  I
>> still haven't seen a good solution to that issue.
>>
> 
> Maybe have it both? Like:
> 
> Français (French)

Seem plausible.  We can always try it and change it if we don't like it.

> 
> Then you have it "easily readable for the native" and still easy for
> others to understand?
> 
> I still think it is nice to keep the menu, or at least the
> fucntionality. I may not need to be a seperate menu from the top bar
> menu as is now, it might actually be more appropiate in "normal"
> settings dialogs. I know those are not the same for eeschema and
> pcbnew, but maybe more similar in the future. This is just some
> ideas/proposals for the future.
> 
>>>
>>> I like the idea of validating the available languages runtime as
>>> mentioned in the related thread.
>>
>> Makes sense to me.  I see no reason to add entries in the language menu
>> for translations that are not available.
>>
>>>
 Something unrelated to the flags but similar is do we need the
 translations tab with all the translators in the about box? or would a
 better place be in the i18n repo on github and linked from the website
 and only the current translation information provided in the about
 dialog. This can be pulled at runtime from the po files using the
 Language-Team header in the po file. There are a few ways this could
 be left how it is, including having a list of all INSTALLED
 translations in the translations tab instead of only showing current,
 would just require the program at startup processing all the language
 files to get the header information.

 for example the one in the ru po file is
 "Language-Team: Russian KiCad Translation Team: Andrey Fedorushkov, Eldar "
 "Khayrullin, Igor Plyatov \n"

 As i only know english i haven't had the oppurtunity to use the po
 utility but i have been advised this is a setting rather than just
 something that is edited manually

 the one in the fr po file is
 "Language-Team: jp-charras\n"

 which if this idea is implemented jp might need to change his to be a
 bit more informative, (at least being his full name or something)

 I think i have mentioned before about making the language list in
 preferences reliant on whether the i18n files have been installed so
 that people don't get caught up with wondering why no other languages
 work.

>>>
>>> Lets assume that all contributors have "proper" names here.
>>>
>>> What will happen with translators which work might not even be present
>>> anymore, how are we supposed to detect that? Or are we just going to
>>> count all contributors from epoch?
>>>
 Mainly i am looking for arguments against moving the flags into the
 i18n repo as that may prove that most of my code is not possible.
 seeing as some people seem to be against just ditching the flags

>>>
>>> Remove the flags. :P
>>>
>>> I don't know if the languages maybe sould be written in their
>>> localized form, maybe?
>>>
 thanks

 Simon

 ___
 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

Re: [Kicad-developers] Bezier curves in DRAWSEGMENT class

[Cirilo Bernardo]

On Wed, Sep 14, 2016 at 9:19 AM, Tomasz Wlostowski <
tomasz.wlostow...@cern.ch> wrote:

> On 14.09.2016 00:00, Cirilo Bernardo wrote:
> > I think it would be nice to support Bezier curves but aside from adding
> > support for editing those curves, I think we need a good enough 2D
> > geometry kernel so that we can improve zone outlines and perhaps
> > even allow tracks to be straight, arc, or Bezier curve. In general though
> > I think good support for "PolyLine" would be of more general use; after
> > all any 2D Bezier curve can be easily approximated with a series of
> > circular arcs (which a Polyline can do).
>
> Cirilo, JP,
>
> I agree we need copper layer arc support. I'm reluctant to add Bezier
> curves unless they are approximated as polylines because of the
> complexity of necessary DRC functions. Writing an accurate arc-to-arc or
> arc-to-segment collision/distance check is already quite difficult.
>
>
I agree regarding the copper layer arc and DRC; I forgot to mention before
that I do prefer approximating Beziers with circular arcs because the
collision
checks are trivial in comparison. Maybe for now leave the Bezier code and
consider deprecating/removing it in the future when we have PolyLine
support?

In my mind, tracks are open polylines and fill zones are closed polylines.
When doing DRC checks, a closed polyline can be created to represent a
track (or region) and its min. clearance. Checking for collisions between
closed polylines is easy - of course it's a little more complex than our
current collision code for straight segments, but in cases where we
currently
represent arcs by short segment approximations I expect the polyline
approach to reduce the number of calculations by a significant amount.


> Besides, what would be the use of such curves for PCB design other than
> fancy graphics (silkscreen, etc)?
>
> Tom
>
>
Sometimes (though personally I know of extremely few examples) people
like to use strange curves for the board outline, but as I said we can
replace
Beziers with circular arcs. In fact I don't believe DXF supports Beziers so
if people are exporting strange board shapes via MCAD we will have a
polyline or similar.

- Cirilo



>
> >
> > - Cirilo
> >
> >
> > On Wed, Sep 14, 2016 at 4:03 AM, jp charras  > > wrote:
> >
> > Le 13/09/2016 à 11:36, Tomasz Wlostowski a écrit :
> > > Hi all,
> > >
> > > Looking at the sources of the DRAWSEGMENT class (with the hopes of
> > > refactoring it a bit to enable arbitrary copper shapes), I noticed
> that
> > > it supports Bezier curves. They are also supported by the file
> format
> > > parser/writer. There's however no drawing tool for these. Is this
> some
> > > outdated code that can be removed or do we plan to support Bezier
> curves
> > > in PCBnew?
> > >
> > > Cheers,
> > > Tom
> >
> > In fact, this is not an outdated code, but a not-yet-used code.
> > A long time ago, we planned to support Bezier curves in Kicad, but
> > this is still on a todo list.
> >
> > --
> > Jean-Pierre CHARRAS
> >
> > ___
> > 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 v2] Add KICAD_INSTALL_DEMOS CMake option

[Wayne Stambaugh]

Jose,

Please use `git format-patch` for submitting patches.  It makes it
easier for me to merger your patches.

Thanks,

Wayne

On 9/8/2016 2:59 PM, José Ignacio Romero wrote:
> 
> It is ON by default, determines wether to install the bundled demos
> and examples.
> ---
> 
> This version has the required documentation changes.
> 
> ---
>  CMakeLists.txt | 6 ++
>  Documentation/development/compiling.md | 7 +++
>  2 files changed, 13 insertions(+)
> 
> 
> 
> ___
> 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] Bezier curves in DRAWSEGMENT class

[Tomasz Wlostowski]

On 14.09.2016 00:00, Cirilo Bernardo wrote:
> I think it would be nice to support Bezier curves but aside from adding
> support for editing those curves, I think we need a good enough 2D
> geometry kernel so that we can improve zone outlines and perhaps
> even allow tracks to be straight, arc, or Bezier curve. In general though
> I think good support for "PolyLine" would be of more general use; after
> all any 2D Bezier curve can be easily approximated with a series of
> circular arcs (which a Polyline can do).

Cirilo, JP,

I agree we need copper layer arc support. I'm reluctant to add Bezier
curves unless they are approximated as polylines because of the
complexity of necessary DRC functions. Writing an accurate arc-to-arc or
arc-to-segment collision/distance check is already quite difficult.

Besides, what would be the use of such curves for PCB design other than
fancy graphics (silkscreen, etc)?

Tom


> 
> - Cirilo
> 
> 
> On Wed, Sep 14, 2016 at 4:03 AM, jp charras  > wrote:
> 
> Le 13/09/2016 à 11:36, Tomasz Wlostowski a écrit :
> > Hi all,
> >
> > Looking at the sources of the DRAWSEGMENT class (with the hopes of
> > refactoring it a bit to enable arbitrary copper shapes), I noticed that
> > it supports Bezier curves. They are also supported by the file format
> > parser/writer. There's however no drawing tool for these. Is this some
> > outdated code that can be removed or do we plan to support Bezier curves
> > in PCBnew?
> >
> > Cheers,
> > Tom
> 
> In fact, this is not an outdated code, but a not-yet-used code.
> A long time ago, we planned to support Bezier curves in Kicad, but
> this is still on a todo list.
> 
> --
> Jean-Pierre CHARRAS
> 
> ___
> 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] add missing parentheses in page layout templates

[Wayne Stambaugh]

Werner,

When I attempt to merge this patch, `git am` is complaining about the
patch format not being recognized.  Did you create this patch using `git
format-patch`?  If not, please use `git format-patch`.  It makes my life
much easier that using patch and copying your commit message to commit
the patch.

Thanks,

Wayne

On 9/8/2016 2:56 PM, Werner Almesberger wrote:
> The default and logo page layout templates are missing some opening
> parentheses. Eeschema's parser accepts them anyway, but it tripped
> my s-expr parser.
> 
> The gost templates and the built-in default in
> common/page_layout/page_layout_default_description.cpp
> are both correct.
> 
> - Werner
> 
> 
> 
> ___
> 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] Bezier curves in DRAWSEGMENT class

[Cirilo Bernardo]

I think it would be nice to support Bezier curves but aside from adding
support for editing those curves, I think we need a good enough 2D
geometry kernel so that we can improve zone outlines and perhaps
even allow tracks to be straight, arc, or Bezier curve. In general though
I think good support for "PolyLine" would be of more general use; after
all any 2D Bezier curve can be easily approximated with a series of
circular arcs (which a Polyline can do).

- Cirilo


On Wed, Sep 14, 2016 at 4:03 AM, jp charras  wrote:

> Le 13/09/2016 à 11:36, Tomasz Wlostowski a écrit :
> > Hi all,
> >
> > Looking at the sources of the DRAWSEGMENT class (with the hopes of
> > refactoring it a bit to enable arbitrary copper shapes), I noticed that
> > it supports Bezier curves. They are also supported by the file format
> > parser/writer. There's however no drawing tool for these. Is this some
> > outdated code that can be removed or do we plan to support Bezier curves
> > in PCBnew?
> >
> > Cheers,
> > Tom
>
> In fact, this is not an outdated code, but a not-yet-used code.
> A long time ago, we planned to support Bezier curves in Kicad, but this is
> still on a todo list.
>
> --
> Jean-Pierre CHARRAS
>
> ___
> 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

[Kicad-developers] [PATCH] [Build] Remove redundant data in defines.

[Niki Guldbrand]

* Using CMAKE_INSTALL_PREFIX in KICAD_* install paths is redundant,
  because they are allready relative to CMAKE_INSTALL_PREFIX when no
  absolute path is given.
  Using an absolute path makes it harder to change the install
  path on the fly, without either rebuilding, or manually editing
  CMakeCache.txt

Signed-off-by: Niki Guldbrand 
---
 CMakeLists.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 14325dd..3972a0b 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -325,7 +325,7 @@ set( KIFACE_PREFIX  "_" )
 #
 if( NOT APPLE )
 # Everything without leading / is relative to CMAKE_INSTALL_PREFIX.
-set( KICAD_BIN ${CMAKE_INSTALL_PREFIX}/bin
+set( KICAD_BIN bin
 CACHE PATH "Location of KiCad binaries." )
 
 if( WIN32 )
@@ -341,10 +341,10 @@ if( NOT APPLE )
 set( KICAD_PLUGINS lib/kicad/plugins
 CACHE PATH "Location of KiCad plugins." )
 
-set( KICAD_LIB ${CMAKE_INSTALL_PREFIX}/lib
+set( KICAD_LIB lib
 CACHE PATH "Location of KiCad shared objects" )
 
-set( KICAD_USER_PLUGIN ${CMAKE_INSTALL_PREFIX}/lib/kicad/plugins
+set( KICAD_USER_PLUGIN lib/kicad/plugins
 CACHE PATH "Location of KiCad user-loaded plugins" )
 endif()
 
___
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] Bezier curves in DRAWSEGMENT class

[jp charras]

Le 13/09/2016 à 11:36, Tomasz Wlostowski a écrit :
> Hi all,
> 
> Looking at the sources of the DRAWSEGMENT class (with the hopes of
> refactoring it a bit to enable arbitrary copper shapes), I noticed that
> it supports Bezier curves. They are also supported by the file format
> parser/writer. There's however no drawing tool for these. Is this some
> outdated code that can be removed or do we plan to support Bezier curves
> in PCBnew?
> 
> Cheers,
> Tom

In fact, this is not an outdated code, but a not-yet-used code.
A long time ago, we planned to support Bezier curves in Kicad, but this is 
still on a todo list.

-- 
Jean-Pierre CHARRAS

___
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] "Multichannel signed distance field" font rendering

[Michael Steinberg]

Hello all!

Thank you very much for the feedback. As I understand the technique 
works well enough on many different hardware levels (I'm using it myself 
in an i5 iGPU), so that's good to know. I tweaked the character 
placement to get in accordance with what the truetype font specifies. 
Beside other issues, this fixes the reported GND baseline problem, still 
their bounding boxes are not bottom-aligned, but their baselines are. 
These changes were pushed to the sdf branch.
There are some issues left that I would call minor (some special chars 
show slight glitches), but I would think that should not be a 
showstopper for now, I will still eventually try to address them. So 
unless there are important issues left I would polish the codestyle and 
get in touch with Orson for inclusion?


The atlas tool is now available on Github with CMake support (thank you 
very much José!), so there should be no "blackbox"-problem remaining.


Cheers!
Michael

___
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] Bezier curves in DRAWSEGMENT class

[Nick Østergaard]

It seems it has been there for long, there are only few mentions of it
on the list while I have been subscribed, but I find:

https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg20577.html
https://lists.launchpad.net/kicad-developers/msg20046.html

It does not really mention anything about the intention. But by the
fact that there have been some implementation to support it for a
decade is probably an indicator that someone wanted to support it at
some poiny, but never got the time to finish it.

I hope someone else can comment further on this.

2016-09-13 11:36 GMT+02:00 Tomasz Wlostowski :
> Hi all,
>
> Looking at the sources of the DRAWSEGMENT class (with the hopes of
> refactoring it a bit to enable arbitrary copper shapes), I noticed that
> it supports Bezier curves. They are also supported by the file format
> parser/writer. There's however no drawing tool for these. Is this some
> outdated code that can be removed or do we plan to support Bezier curves
> in PCBnew?
>
> Cheers,
> Tom
>
> ___
> 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] announcing eeshow (schematics renderer and viewer)

[Roman Pavelka]

Tested on Fedora 24 on two bigger projects, no problems at all.

Dependencies were installed by invoking:

sudo dnf install gtk3-devel cairo-devel libgit2-devel transfig ImageMagick

-- 
Roman Pavelka
http://kmlinux.fjfi.cvut.cz/~pavelro1
___
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

[Kicad-developers] Bezier curves in DRAWSEGMENT class

[Tomasz Wlostowski]

Hi all,

Looking at the sources of the DRAWSEGMENT class (with the hopes of
refactoring it a bit to enable arbitrary copper shapes), I noticed that
it supports Bezier curves. They are also supported by the file format
parser/writer. There's however no drawing tool for these. Is this some
outdated code that can be removed or do we plan to support Bezier curves
in PCBnew?

Cheers,
Tom

___
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