Re: [Kicad-developers] 5.1 branch

[Nick Østergaard]

Can you edit anything on them? Can you provide a screenshot of the
preferences dialog?

søn. 15. jul. 2018 23.15 skrev Eeli Kaikkonen :

>
>
> su 15. heinäk. 2018 klo 14.39 Jeff Young (j...@rokeby.ie) kirjoitti:
>
>> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
>>
>> Has anyone had a chance to try out the paged dialogs (Preferences and
>> Board Setup) on Windows or Linux?  They weren’t working for Nick (disabled
>> panels).
>>
>
> Works here in Ubuntu 17.10.
>
> Application: kicad
> Version: (5.0.0-rc3-dev-86-g2eeed8ee3-dirty), release build
> Libraries:
> wxWidgets 3.0.3
> libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0
> (+libidn2/2.0.2) librtmp/2.3
> Platform: Linux 4.13.0-46-generic x86_64, 64 bit, Little endian, wxGTK
> Build Info:
> wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
> Boost: 1.62.0
> OpenCASCADE Community Edition: 6.8.0
> Curl: 7.55.1
> Compiler: GCC 7.2.0 with C++ ABI 1011
>
> Build settings:
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=OFF
> KICAD_SCRIPTING=ON
> KICAD_SCRIPTING_MODULES=ON
> KICAD_SCRIPTING_WXPYTHON=ON
> KICAD_SCRIPTING_ACTION_MENU=OFF
> BUILD_GITHUB_PLUGIN=ON
> KICAD_USE_OCE=ON
> KICAD_USE_OCC=OFF
> KICAD_SPICE=OFF
>
> ___
> 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] 5.1 preview

[Jeff Young]

I have pushed changes that should fix Eeli’s and JP’s compile issues, and might 
fix the Paged Dialog issue that some are seeing.

Note that the branch was also renamed from “6.0” to “5.1”.

If anyone has a chance to re-spin and test, that would be great.

Cheers,
Jeff.


> On 15 Jul 2018, at 21:39, Eeli Kaikkonen  wrote:
> 
> This was a false positive - I had the "master" branch checked out instead of 
> 6.0. However, I now fetched 5.1 and tried modifying it. All I had to do was 
> adding two includes in one file:
> 
> #include 
> #include 
> 
> into eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp. Then it could 
> be compiled.
> 
> pe 13. heinäk. 2018 klo 23.18 Eeli Kaikkonen (eeli.kaikko...@gmail.com 
> ) kirjoitti:
> After many experiments I deleted and re-did everything, both source and build 
> directory, and reconfigured. Now it is ready and installed and can be run.
> 
> 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

Re: [Kicad-developers] How sophisticated is the bug closure script?

[Jeff Young]

Hi Orson,

I was asking about the Fix Committed -> Fix Released script (assuming it is a 
script), rather than the *** -> Fix Committed script.

Although your answer does bring up the question, do we want to setup the 
Janitor script to handle the 5.1 branch as well, or just do them by hand?

Cheers,
Jeff.

> On 15 Jul 2018, at 22:11, Maciej Suminski  wrote:
> 
> Hi Jeff,
> 
> KiCad Janitor follows only the master branch and does not take tags or
> target milestones into account. The rules are very simple: whenever
> there is a "fixes" line, change the correlated bug status to "Fixed".
> Have a look at the script [1], I will be happy to improve it.
> 
> Cheers,
> Orson
> 
> 1. https://git.launchpad.net/kicad-git-hook/tree/hook.py
> 
> On 07/15/2018 05:43 PM, Jeff Young wrote:
>> In particular, can I go ahead and make commits that have “fixes” lines (as 
>> long as the bugs are tagged 5.1), or do I need to wait till be auto-close 
>> the 5.0 bugs?
>> ___
>> 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] 5.1 branch

[Eeli Kaikkonen]

su 15. heinäk. 2018 klo 14.39 Jeff Young (j...@rokeby.ie) kirjoitti:

> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
>
> Has anyone had a chance to try out the paged dialogs (Preferences and
> Board Setup) on Windows or Linux?  They weren’t working for Nick (disabled
> panels).
>

Works here in Ubuntu 17.10.

Application: kicad
Version: (5.0.0-rc3-dev-86-g2eeed8ee3-dirty), release build
Libraries:
wxWidgets 3.0.3
libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0
(+libidn2/2.0.2) librtmp/2.3
Platform: Linux 4.13.0-46-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
Boost: 1.62.0
OpenCASCADE Community Edition: 6.8.0
Curl: 7.55.1
Compiler: GCC 7.2.0 with C++ ABI 1011

Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_ACTION_MENU=OFF
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=OFF
___
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] How sophisticated is the bug closure script?

[Maciej Suminski]

Hi Jeff,

KiCad Janitor follows only the master branch and does not take tags or
target milestones into account. The rules are very simple: whenever
there is a "fixes" line, change the correlated bug status to "Fixed".
Have a look at the script [1], I will be happy to improve it.

Cheers,
Orson

1. https://git.launchpad.net/kicad-git-hook/tree/hook.py

On 07/15/2018 05:43 PM, Jeff Young wrote:
> In particular, can I go ahead and make commits that have “fixes” lines (as 
> long as the bugs are tagged 5.1), or do I need to wait till be auto-close the 
> 5.0 bugs?
> ___
> 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] 5.1 preview

[Eeli Kaikkonen]

This was a false positive - I had the "master" branch checked out instead
of 6.0. However, I now fetched 5.1 and tried modifying it. All I had to do
was adding two includes in one file:

#include 
#include 

into eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp. Then it could
be compiled.

pe 13. heinäk. 2018 klo 23.18 Eeli Kaikkonen (eeli.kaikko...@gmail.com)
kirjoitti:

> After many experiments I deleted and re-did everything, both source and
> build directory, and reconfigured. Now it is ready and installed and can be
> run.
>
> 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

[Kicad-developers] How sophisticated is the bug closure script?

[Jeff Young]

In particular, can I go ahead and make commits that have “fixes” lines (as long 
as the bugs are tagged 5.1), or do I need to wait till be auto-close the 5.0 
bugs?
___
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] Stable version 5 tagged.

[Marco Ciampa]

On Fri, Jul 13, 2018 at 05:12:31PM -0500, Adam Wolf wrote:
> Great, thanks!
> 
> Sorry if I put anyone in a panic.

Great! I was in a panic! But don't worry! It was just for the few secs it
took to read the full thread... :-P

I'm at the seaside on vacation with my family till the end of this week
and perhaps a few days more; I brought with me my laptop just in case but
there is a terrible connection here ...

Anyway Italian strings should be updated...

Many many thanks to you all for making this possible!

--


Marco Ciampa

I know a joke about UDP, but you might not get it.



 GNU/Linux User #78271
 FSFE fellow #364




___
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] kicad version and install location

[Adam Wolf]

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 that installs to
/Applications/KiCad5 and /Library/Application Support/kicad?

Adam

On Sun, Jul 15, 2018, 2:41 AM Eeli Kaikkonen 
wrote:

> There are some people in the user forum who have spent time with these
> v4->v5 problems, including me and Rene. The consensus about the environment
> variables seems to be what Rene already said, that they should not (without
> explicit user intervention) be set for the system, but from KiCad itself.
> Nick confirmed that the current v5 installer won't set them by default.
> They are still a problem if they have been set by v4 installer.
>
> su 15. heinäk. 2018 klo 5.04 Strontium (strnty...@gmail.com) kirjoitti:
>
>> I honestly think each major revision of KiCad should be considered a NEW
>> program, installs to a new place has its configuration and libraries all
>> in a new location.  Only Incremental updates 5.0 -> 5.1 should be
>> considered upgrades.
>>
>>
> I agree. It's probable that many users will want to continue with v4 for
> old projects but v5 for new, and in the future the same thing will be true
> for v5 vs. v6, because they break the file/project compatibility. But where
> the compatibility is kept it's more likely to be considered as just an
> upgrade.
>
>
>> Kicad configuration isn't complex or onerous so if a user wants to bring
>> a Kicad4 config into Kicad5 or 6 or whatever, then they do that
>> themselves, otherwise after install Kicad5 is a fresh blank sheet with
>> no relationship to anything that happened on the users computer in
>> Kicad4.  I am not familiar with the issues on Windows, but I would have
>> thought now this is mostly a packaging issue only??
>>
>>
> I tried modifying the Windows installer, I only needed to replace some of
> "KiCad" strings with "KiCad5" and it can install v5 alongside v4
> independently. The only problem is the configuration and the environment
> variables set by v4. They can be handled with a startup script. See
> https://forum.kicad.info/t/does-v5-have-to-overwrite-on-install/11282 for
> some details.
>
> I also agree if it can't work this way now on Windows, then its all a
>> bit late for V5, but maybe V6 can consider itself a new program distinct
>> from V5.  This would also help with testing, because users could use V5
>> for daily work, but also easily install a V6 daily side by side.
>>
>
> All this could be done with the Windows installer, provided that a startup
> script would be offered.
>
> To make this all, at least the startup script, as simple as possible I
> would suggest one (or three) small changes to KiCad (for 5.1, or even
> 5.0.1?). Add command line options --config=/path/to/config and
> --ignore-env-vars. The former is obvious and would override
> KICAD_CONFIG_HOME system environment variable. The latter would make KiCad
> ignore all system environment variables and use the current internal logic
> and the path settings UI instead. That way the old variables could be left
> for v4 and the newer versions would be completely independent if the
> command line switches were used. The command line switch for the config
> path would be mostly for convenience. In Windows starting a program with
> custom environment variables is tedious and error prone to write (see the
> above mentioned thread). Command line switches are much easier.
>
> It could also be possible to make --ignore-env-vars=true by default.
> Sharing the environment variables would be a special case if the user wants
> that.
>
> The general problem with using system environment variables is that they
> are good for situations when there's only one version of a program on the
> system, and/or several processes share the same variable values. Neither of
> them is true for parallel installations of KiCad.
>
> 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] 5.1 branch

[jp charras]

Le 15/07/2018 à 13:39, Jeff Young a écrit :
> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
> 
> Has anyone had a chance to try out the paged dialogs (Preferences and Board 
> Setup) on Windows or Linux?  They weren’t working for Nick (disabled panels).
> 
> Cheers,
> Jeff.

These dialogs are not working for me (W7 32 bits).
I confirm panels are disabled.

A strange behavior of the About dialog:
It works fine called from Kicad manager.
But called from eeschema, pcbnew or page layour editor, the first and last 
pages (information and
license) are incorrectly shown:
the Html text looks like it could be displayed in a usual wxTextControl, not a 
html window.
However none of html tags are displayed, so it is not displayed as a ASCII text.
Other pages are correctly displayed.


-- 
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] New Kicad Features

[Tom Kulaga]

Hi All,

I wanted to find out if any of the following features are in the Kicad
pipeline

-Multi Board projects  with consolidated BOM and panelisation features
-Also having multi board assemblies for system visualisation
-Multiple stacks-up per board for rigid flex work

I'd be happy to contribute with some guidance.
___
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] 5.1 branch

[Jeff Young]

I renamed my 6.0 branch to 5.1, since most of what it contains goes there.

Has anyone had a chance to try out the paged dialogs (Preferences and Board 
Setup) on Windows or Linux?  They weren’t working for Nick (disabled panels).

Cheers,
Jeff.
___
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] 5.1 tag

[Nick Østergaard]

I guess Jeff's reasoning is to stabilize it a bit before braching. We all
know that changing the dialogs often leads to cross platform issues. But
either way is fine for me.

lør. 14. jul. 2018 01.59 skrev Wayne Stambaugh :

> That would prevent us from adding new features such as the new schematic
> file formats and eeschema gal to development branch so I would prefer
> not to limit ourselves in the master branch.
>
> On 07/13/2018 06:45 PM, Jeff Young wrote:
> > Would it make more sense to keep 5.1 on master for a while, and then
> branch it so master can become 6.0?
> >
> > (Sent from the Denver airport, so any response may be delayed till I get
> back to Ireland.)
> > ___
> > 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] kicad version and install location

[Eeli Kaikkonen]

There are some people in the user forum who have spent time with these
v4->v5 problems, including me and Rene. The consensus about the environment
variables seems to be what Rene already said, that they should not (without
explicit user intervention) be set for the system, but from KiCad itself.
Nick confirmed that the current v5 installer won't set them by default.
They are still a problem if they have been set by v4 installer.

su 15. heinäk. 2018 klo 5.04 Strontium (strnty...@gmail.com) kirjoitti:

> I honestly think each major revision of KiCad should be considered a NEW
> program, installs to a new place has its configuration and libraries all
> in a new location.  Only Incremental updates 5.0 -> 5.1 should be
> considered upgrades.
>
>
I agree. It's probable that many users will want to continue with v4 for
old projects but v5 for new, and in the future the same thing will be true
for v5 vs. v6, because they break the file/project compatibility. But where
the compatibility is kept it's more likely to be considered as just an
upgrade.


> Kicad configuration isn't complex or onerous so if a user wants to bring
> a Kicad4 config into Kicad5 or 6 or whatever, then they do that
> themselves, otherwise after install Kicad5 is a fresh blank sheet with
> no relationship to anything that happened on the users computer in
> Kicad4.  I am not familiar with the issues on Windows, but I would have
> thought now this is mostly a packaging issue only??
>
>
I tried modifying the Windows installer, I only needed to replace some of
"KiCad" strings with "KiCad5" and it can install v5 alongside v4
independently. The only problem is the configuration and the environment
variables set by v4. They can be handled with a startup script. See
https://forum.kicad.info/t/does-v5-have-to-overwrite-on-install/11282 for
some details.

I also agree if it can't work this way now on Windows, then its all a
> bit late for V5, but maybe V6 can consider itself a new program distinct
> from V5.  This would also help with testing, because users could use V5
> for daily work, but also easily install a V6 daily side by side.
>

All this could be done with the Windows installer, provided that a startup
script would be offered.

To make this all, at least the startup script, as simple as possible I
would suggest one (or three) small changes to KiCad (for 5.1, or even
5.0.1?). Add command line options --config=/path/to/config and
--ignore-env-vars. The former is obvious and would override
KICAD_CONFIG_HOME system environment variable. The latter would make KiCad
ignore all system environment variables and use the current internal logic
and the path settings UI instead. That way the old variables could be left
for v4 and the newer versions would be completely independent if the
command line switches were used. The command line switch for the config
path would be mostly for convenience. In Windows starting a program with
custom environment variables is tedious and error prone to write (see the
above mentioned thread). Command line switches are much easier.

It could also be possible to make --ignore-env-vars=true by default.
Sharing the environment variables would be a special case if the user wants
that.

The general problem with using system environment variables is that they
are good for situations when there's only one version of a program on the
system, and/or several processes share the same variable values. Neither of
them is true for parallel installations of KiCad.

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