Re: [Kicad-developers] wrong formated string in kicad/common/dialog/dialog_global_lib_table_config.cpp

2019-01-25 Thread Carsten Schoenert
Hi again,

one more thing that happen now around these l10n changes I can see is
the missing translation for the substituted strings in the modified
splash dialog window if KiCad is starting with an non existing file
'sym-lib-table' in the local configuration folder of KiCad.

I can see the intention behind these changes, to make the dialog more
consistent for the symbol and footprint library table, but this needs a
bit rework.

I append a screenshot from the GUI dialog windows about to setup the
symbol and footprint library table. The word 'symbol' would needed to be
displayed as the translated German string 'Bauteil'. The current state
is a bit unfortunate.

Or in short, there is some ability needed to make the substituted string
in theses dialogs also make translatable.

-- 
Regards
Carsten
___
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] FOSDEM KiCad dinner.

2019-01-25 Thread Frank Severinsen
Hi Wayne

Added you to the group


Den 26. januar 2019 kl. 01.31.46 +01.00, skrev Wayne Stambaugh 
:

> Frank,
> 
> My phone number is 1-757-880-5981.
> 
> Cheers,
> 
> Wayne
> 
> On 1/25/19 7:15 PM, Frank Severinsen wrote:
> 
> > To the ones coming to Fosdem in a week.
> > I made a whatsapp group for all the Kicad people going.
> > It can be used for dinner planning, barcrawl, hangout, hackerspace meetups, 
> > or just finding each other at Fosdem (I was quite surprised how crowded it 
> > was last year).
> > Drop me an email with your phonenumber if you would like to be added to the 
> > group.
> > Kindest regards
> > Frank Severinsen
> > Den 7. januar 2019 kl. 18.40.00 +01.00, skrev Wayne Stambaugh 
> > <>:
> > 
> > > For those of you who don't know, the last few years at FOSDEM we have
> > > had a KiCad dinner on Saturday evening which was open to all. Last year
> > > we had well over 30 attendees which was very not manageable. This year
> > > we have decided to limit the size to 15. So far we have 4 confirmed
> > > attendees from the lead development team. I am now opening up requests
> > > to the developers on the development mailing list. This includes our
> > > library, documentation, and translation developers. Please RSVP me as
> > > soon as possible if you are interested. Resevations will be on a first
> > > come first serve basis until all 15 spots are reserved. Any remaining
> > > spots will be open to sponsors and then to the general public.
> > > 
> > > Cheers,
> > > 
> > > Wayne
> > > 
> > > ___
> > > Mailing list: 
> > > Post to :  
> > > >
> > > Unsubscribe : 
> > > More help : 
> > > 

___
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] FOSDEM KiCad dinner.

2019-01-25 Thread Wayne Stambaugh

Frank,

My phone number is 1-757-880-5981.

Cheers,

Wayne

On 1/25/19 7:15 PM, Frank Severinsen wrote:

To the ones coming to Fosdem in a week.

I made a whatsapp group for all the Kicad people going.
It can be used for dinner planning, barcrawl, hangout, hackerspace 
meetups, or just finding each other at Fosdem (I was quite surprised how 
crowded it was last year).
Drop me an email with your phonenumber if you would like to be added to 
the group.


Kindest regards
Frank Severinsen


Den 7. januar 2019 kl. 18.40.00 +01.00, skrev Wayne Stambaugh 
:

For those of you who don't know, the last few years at FOSDEM we have
had a KiCad dinner on Saturday evening which was open to all. Last year
we had well over 30 attendees which was very not manageable. This year
we have decided to limit the size to 15. So far we have 4 confirmed
attendees from the lead development team. I am now opening up requests
to the developers on the development mailing list. This includes our
library, documentation, and translation developers. Please RSVP me as
soon as possible if you are interested. Resevations will be on a first
come first serve basis until all 15 spots are reserved. Any remaining
spots will be open to sponsors and then to the general public.

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


[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #4572

2019-01-25 Thread Miguel Angel Ajo
See 



___
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] Build failed in Jenkins: linux-kicad-full-gcc-head #4571

2019-01-25 Thread Miguel Angel Ajo
See 


Changes:

[hillbrand] pcbnew: Fix via snapping to multiple tracks

--
[...truncated 154.33 KB...]
[ 84%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/drawing_tool.cpp.o
[ 85%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/sch_validators.cpp.o
[ 85%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/edit_constraints.cpp.o
[ 85%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/schedit.cpp.o
[ 85%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/edit_points.cpp.o
[ 85%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/schematic_undo_redo.cpp.o
[ 85%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/edit_tool.cpp.o
[ 85%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/sch_edit_frame.cpp.o
[ 85%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/grid_helper.cpp.o
[ 85%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/selpart.cpp.o
[ 85%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/microwave_tool.cpp.o
[ 85%] Building CXX object eeschema/CMakeFiles/eeschema_kiface.dir/sheet.cpp.o
[ 85%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/sheetlab.cpp.o
[ 85%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/footprint_editor_tools.cpp.o
[ 85%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/symbol_lib_table.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pad_tool.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/symbol_tree_model_adapter.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_actions.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/symbol_tree_synchronizing_adapter.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_bright_box.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/template_fieldnames.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/template_fieldnames_keywords.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_editor_control.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/tool_sch.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_selection_conditions.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/tool_viewlib.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/transform.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcb_tool.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/viewlib_frame.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/pcbnew_control.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/viewlibs.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/picker_tool.cpp.o
[ 86%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/netlist_exporters/netlist_exporter.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/netlist_exporters/netlist_exporter_cadstar.cpp.o
[ 86%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/placement_tool.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/netlist_exporters/netlist_exporter_generic.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/netlist_exporters/netlist_exporter_kicad.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/point_editor.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/netlist_exporters/netlist_exporter_orcadpcb2.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/position_relative_tool.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/netlist_exporters/netlist_exporter_pspice.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/selection.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/__/common/dialogs/dialog_page_settings.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/__/common/base_screen.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/selection_tool.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/__/common/base_units.cpp.o
[ 87%] Building CXX object 
eeschema/CMakeFiles/eeschema_kiface.dir/__/common/eda_text.cpp.o
[ 87%] Building CXX object 
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/tools/tool_event_utils.cpp.o
[ 87%] Building CXX object 

[Kicad-developers] [PATCH] Further QA consolidation

2019-01-25 Thread John Beard
Hi,

Here are a few more patches to finish up consolidating most of the
rest of the QA tools.

1) Adds some very basic dev-docs about the utility programs
2) Housekeeping in qa_utils (hide some code in KI_TEST)
3) qa_shape_factor_refactor is now only SHAPE_POLY_SET tests (the
CPolyline stuff is gone), so move to qa_common where pure geom tests
belong. Kill off this test executable.
4) Reinstate the polygon triangulation util under qa_pcbnew_tools
5) qa_pcbnew_tools: reuse common board reading code (useful when
quickly prototyping with utilities)

The only outstanding broken PCB-related QA things now should be:

* pcb_test_window: what is this for and can it be fixed? Can it be
made into a sub-tool, or does it need its own executable for the
wxApp?

Cheers,

John
From 8efadbfef50cd441f624f0ef3db9e2915924209e Mon Sep 17 00:00:00 2001
From: John Beard 
Date: Thu, 24 Jan 2019 11:33:22 +
Subject: [PATCH 1/6] Docs: Describe QA util programs in the testing docs

---
 Documentation/development/testing.md | 35 
 1 file changed, 30 insertions(+), 5 deletions(-)

diff --git a/Documentation/development/testing.md b/Documentation/development/testing.md
index 6030d986d..5130dad0a 100644
--- a/Documentation/development/testing.md
+++ b/Documentation/development/testing.md
@@ -39,7 +39,7 @@ Common useful patterns:
 * ` -t "Utf8/UniIterNull"` runs only a single test in a specific suite.
 * ` -l all` adds more verbose debugging to the output.
 * ` --list_content` lists the test suites and test cases within the
-test program. You can use these for arguments to `-l`.
+test program. You can use these for arguments to `-t`.
 
 You can rebuild just a specific test with CMake to avoid rebuilding
 everything when working on a small area, e.g. `make qa_common`.
@@ -149,6 +149,30 @@ You can run the tests in GDB to trace this:
 If the test segfaults, you will get a familiar backtrace, just like
 if you were running pcbnew under GDB.
 
+# Utility programs {#utility-programs}
+
+KiCad includes some utility programs that can be used for debugging, profiling,
+analysing or developing certain parts of the code without having to invoke the full
+GUI program.
+
+Generally, they are part of the `qa_*_tools` QA executables, each one containing
+the relevant tools for that library. To list the tools in a given program, pass
+the `-l` parameter. Most tools provide help with the `-h` argument.
+To invoke a program:
+
+qa__tools  [-h] [tool arguments]
+
+Below is a brief outline of some available tools. For full information and command-line
+parameters, refer to the tools' usage test (`-h`).
+
+* `common_tools` (the common library and core functions):
+* `coroutine`: A simple coroutine example
+* `io_benchmark`: Show relative speeds of reading files using various IO techniques.
+* `qa_pcbnew_tools` (pcbnew-related functions):
+* `drc`: Run and benchmark certain DRC functions on a user-provided `.kicad_pcb` files
+* `pcb_parser`: Parse user-provided `.kicad_pcb` files
+* `polygon_generator`: Dump polygons found on a PCB to the console
+
 # Fuzz testing {#fuzz-testing}
 
 It is possible to run fuzz testing on some parts of KiCad. To do this for a
@@ -164,12 +188,13 @@ For example, to use the [AFL fuzzing tool][], you will need:
 * To compile this executable with an AFL compiler, to enable the instrumentation
   that allows the fuzzer to detect the fuzzing state.
 
-For example, the `qa_pcb_parse_input` executable can be compiled like this:
+For example, the `qa_pcbnew_tools` executable (which contains `pcb_parser`,
+a fuzz testing tool for `.kicad_pcb` file parsing) can be compiled like this:
 
 mkdir build
 cd build
 cmake -DCMAKE_CXX_COMPILER=/usr/bin/afl-clang-fast++ -DCMAKE_C_COMPILER=/usr/bin/afl-clang-fast ../kicad_src
-make qa_pcb_parse_input
+make qa_pcbnew_tools
 
 You may need to disable core dumps and CPU frequency scaling on your system (AFL
 will warn you if you should do this). For example, as root:
@@ -177,9 +202,9 @@ will warn you if you should do this). For example, as root:
 # echo core >/proc/sys/kernel/core_pattern
 # echo performance | tee cpu*/cpufreq/scaling_governor
 
-To fuzz:
+To fuzz, run the executable via `afl-fuzz`:
 
-afl-fuzz -i fuzzin -o fuzzout -m500 qa/pcb_parse_input/qa_pcb_parse_input
+afl-fuzz -i fuzzin -o fuzzout -m500 qa/pcbnew_tools/qa_pcbnew_tools pcb_parser
 
 where:
 
-- 
2.20.1

From 0871074a1d09a80a8225ba22178fbc62c4acf1fd Mon Sep 17 00:00:00 2001
From: John Beard 
Date: Thu, 24 Jan 2019 12:12:25 +
Subject: [PATCH 2/6] QA: Put UTILITY_PROGRAM in KI_TEST

Also expand some documentation of some other KI_TEST functions.
---
 qa/common_tools/main.cpp  |  4 +--
 .../tools/coroutines/coroutine_tools.h|  2 +-
 .../tools/coroutines/coroutines.cpp   |  6 ++--
 .../tools/io_benchmark/io_benchmark.cpp   |  6 ++--
 .../tools/io_benchmark/io_benchmark.h |  2 +-
 

Re: [Kicad-developers] Servers migration

2019-01-25 Thread Maciej Suminski
Hi Andrew,

We are working on setting up a Gitlab instance (Community Edition) to
host some other projects at CERN. Perhaps KiCad could also fit there,
but let's reevaluate the possibilities once we have everything in place.
Switching source code hosting platforms is trivial only for git
repositories, but then you need to also migrate the bug tracker,
blueprints, mailing list, etc.

In any case, I would rather not deploy another instance exclusively
dedicated to KiCad. The main problem is that we would need an
administrator who could take care of the system.

Cheers,
Orson

On 1/25/19 1:38 AM, Andrew Lutsenko wrote:
> This is great news!
> Hopefully this means some progress can be made on setting up a gitlab
> instance and moving off launchpad?
> 
> Regards,
> Andrew
> 
> On Thu, Jan 24, 2019 at 5:13 AM Wayne Stambaugh 
> wrote:
> 
>> I couldn't agree more!  Thank you Mark and Nick for the helping out with
>> the server moves.  Thank you Miguel for your support of the KiCad
>> website hosting.  I appreciate your efforts.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 1/24/2019 2:21 AM, Maciej Suminski wrote:
>>> Hi,
>>>
>>> Good news! We have been granted some space at CERN servers to host KiCad
>>> website, documentation and downloads. It means larger storage and
>>> hopefully faster data transfers.
>>>
>>> Thanks to Mark Roszko and Nick Ostergaard, most of the services have
>>> been already migrated to the CERN servers. One remaining change is to
>>> switch the build machines to upload the output binaries to the new
>>> download server and update the download links. It is expected to happen
>>> by the end of the month.
>>>
>>> It is also the right moment to express gratitude for Miguel Angel Ajo,
>>> who kindly funded and supervised KiCad servers for the past several
>>> years. Skilled administrators are frequently underappreciated, as their
>>> work goes unnoticed when well performed, so this time it is loud and
>>> clear: thank you for the excellent service!
>>>
>>> Cheers,
>>> Orson
>>>
>>>
>>> ___
>>> 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
> 



signature.asc
Description: OpenPGP digital signature
___
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