date:20170824

Re: [Kicad-developers] Python script offered as example for Action Plugin and wxFormBuilder integration

2017-08-24 Thread Greg Smith

I have placed the KiCad Python Style Guide in 
https://github.com/HiGregSmith/kicad-python-style-guidefor comment. It is not 
formatted particularly well, but captures everything mentioned in this thread. 
I thought it was important to include the "Logistics" section because that is 
hard to find otherwise.
I do think this should be merged into the Development Pcbnew Plugins document 
after it's honed and 
polished:http://docs.kicad-pcb.org/doxygen/md_Documentation_development_pcbnew-plugins.html
I also think the "Resources" section is important at the top in bullet format 
instead of in a narrative. The links are less difficult to overlook, IMHO.
Taking comments on content at the moment. 

On Monday, August 14, 2017 7:55 AM, Wayne Stambaugh  
wrote:
 

 On 8/12/2017 11:59 AM, Greg Smith wrote:
> Where should I submit a (likely short) style guide for review? 

The KiCad developer's mailing list.

> 
> I have recently reviewed PEP8 and updated the code for KiPadCheck and 
> LayerViewSet to be compliant, so I can write a short document about the KiCad 
> Python style for others to review.

Our developer docs are written using Doxygen's markdown format.  Once
you have you initial draft, please submit it to this mailing list for
review.  Once we have it finalized, it can be merged into the master
branch.  Thank you taking on this task.  It's one of those things we
knew we would have to address at some point.

> 
> There are other guides similar to style guides that might be relevant as well.
> 
> PEP8 is great, and it already allows the main exception KiCad will probably 
> need to specify: case of function names. PEP8 primarily suggests 
> lower_case_with_underscore_separators, yet many of KiCad python methods seems 
> to be specified as CamelCase.

This is most likely because our C++ source policy is CamelCase or
lower_case_with_underscore_separators.  The same policy seems reasonable
for the kicad python code as well.

> 
> PEP8 essentially recommends "do this [specific thing], unless you need to do 
> something else for consistency".
> 
> Greg S.
> 
>> On Aug 12, 2017, at 10:43 AM, Adam Wolf  
>> wrote:
>>
>> I think PEP8 is great for us.  Let's just add a line that says "We use
>> PEP8 as our Python style guide."
>>
>> Adam Wolf
>>
>>> On Sat, Aug 12, 2017 at 10:27 AM, Strontium  wrote:
>>> Hello Wayne and Greg,
>>>
>>> Can I suggest just adopting PEP8 for Python code formatting.  Its clean,
>>> well documented, and there are plenty of linters to check conformance.  And
>>> if there is anything in PEP8 that is annoying for KiCad development (cant
>>> imagine what) just specify an exclusion or exception.
>>>
>>> Steven
>>>
 On 12/08/17 22:15, Wayne Stambaugh wrote:

 On 8/11/2017 10:08 PM, Greg Smith wrote:
>>>
>>> ...
>
> Suggestions on coding style, functionality, integration technique are
> welcome!

 We have not defined a Python coding style.  It's something that needs to
 be done but no one has had the time to do it.  Please look at some of
 the existing Python code in the KiCad source repo and follow what others
 have done.  The last time I looked (which admittedly has been a while),
 the formatting of our Python code was pretty consistent.
>>>
>>> ...
>>>
>>>
>>>
>>> ___
>>> 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] Stable release 4.0.7 status.

2017-08-24 Thread Simon Richter

Hi,

On 25.08.2017 00:48, Wayne Stambaugh wrote:

> Great work everyone!  Lets fire up those package builders.

http://kiwi.hogyros.de:8080/job/windows-kicad-msys2-stable/11/console

This will upload to

http://downloads.kicad-pcb.org/windows/testing/

   Simon



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

Re: [Kicad-developers] Stable release 4.0.7 status.

2017-08-24 Thread Wayne Stambaugh

Great work everyone!  Lets fire up those package builders.

Cheers,

Wayne

On 8/24/2017 6:33 PM, Nick Østergaard wrote:
> Thank you. IIRC that means that everything is tagged finally :)
> 
> 2017-08-25 0:27 GMT+02:00 Rene Pöschl  >:
> 
> On 24/08/17 21:03, Nick ^ wrote:
> 
> I have now added the Librarians team as write for those four
> repos. Please tag appropiately. I can tag them if HEAD is good
> enough.
> 
> Thanks. I pushed the tags.
> 
> 
> 
> 
> ___
> 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] Stable release 4.0.7 status.

2017-08-24 Thread Nick Østergaard

Thank you. IIRC that means that everything is tagged finally :)

2017-08-25 0:27 GMT+02:00 Rene Pöschl :

> On 24/08/17 21:03, Nick ^ wrote:
>
>> I have now added the Librarians team as write for those four repos.
>> Please tag appropiately. I can tag them if HEAD is good enough.
>>
>> Thanks. I pushed the tags.
>
>
>
>
> ___
> 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] Stable release 4.0.7 status.

2017-08-24 Thread Rene Pöschl


On 24/08/17 21:03, Nick ^ wrote:
I have now added the Librarians team as write for those four repos. 
Please tag appropiately. I can tag them if HEAD is good enough.



Thanks. I pushed the tags.



___
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] Change track width setting to dropbox

2017-08-24 Thread Mathias Grimmberger


Hi all,

Mathias Grimmberger  writes:
>
> Hi Wayne,
>
> Wayne Stambaugh  writes:
>
>> Rather than add a wxComboBox to the WX_UNIT_BINDER object, wouldn't be
>> be cleaner to change wxTextCtrl* to wxTextEntry* which wxComboBox and
>> wxTextCtrl (along with several others) are derived from?
>
> Yes, of course, I will change that.

Here is the version of the patch with a nicer modification to
WX_UNIT_BINDER.

BTW, I noticed that displaying e.g. track width in inches feels somehow
strange, would people like having selected values displayed in mils?


Have fun,

MGri

diff --git a/common/wx_unit_binder.cpp b/common/wx_unit_binder.cpp
index 6a9236b32..c1f0fef50 100644
--- a/common/wx_unit_binder.cpp
+++ b/common/wx_unit_binder.cpp
@@ -24,7 +24,7 @@
 
 #include 
 #include 
-#include 
+#include 
 #include 
 #include 
 #include 
@@ -33,9 +33,9 @@
 
 #include "wx_unit_binder.h"
 
-WX_UNIT_BINDER::WX_UNIT_BINDER( wxWindow* aParent, wxTextCtrl* aTextInput,
+WX_UNIT_BINDER::WX_UNIT_BINDER( wxWindow* aParent, wxTextEntry* aTextInput,
 wxStaticText* aUnitLabel, wxSpinButton* aSpinButton ) :
-m_textCtrl( aTextInput ),
+m_textEntry( aTextInput ),
 m_unitLabel( aUnitLabel ),
 m_units( g_UserUnit ),
 m_step( 1 ),
@@ -43,7 +43,7 @@ WX_UNIT_BINDER::WX_UNIT_BINDER( wxWindow* aParent, wxTextCtrl* aTextInput,
 m_max( 1 )
 {
 // Use the currently selected units
-m_textCtrl->SetValue( wxT( "0" ) );
+m_textEntry->SetValue( wxT( "0" ) );
 m_unitLabel->SetLabel( GetAbbreviatedUnitsLabel( m_units ) );
 }
 
@@ -57,7 +57,7 @@ void WX_UNIT_BINDER::SetValue( int aValue )
 {
 wxString s = StringFromValue( m_units, aValue, false );
 
-m_textCtrl->SetValue( s );
+m_textEntry->SetValue( s );
 
 m_unitLabel->SetLabel( GetAbbreviatedUnitsLabel( m_units ) );
 }
@@ -65,7 +65,7 @@ void WX_UNIT_BINDER::SetValue( int aValue )
 
 int WX_UNIT_BINDER::GetValue() const
 {
-wxString s = m_textCtrl->GetValue();
+wxString s = m_textEntry->GetValue();
 
 return ValueFromString( m_units, s );
 }
@@ -75,12 +75,14 @@ bool WX_UNIT_BINDER::Valid() const
 {
 double dummy;
 
-return m_textCtrl->GetValue().ToDouble( &dummy );
+return m_textEntry->GetValue().ToDouble( &dummy );
 }
 
 
 void WX_UNIT_BINDER::Enable( bool aEnable )
 {
-m_textCtrl->Enable( aEnable );
+wxWindow* wxWin = dynamic_cast ( m_textEntry );
+wxWin->Enable( aEnable );
 m_unitLabel->Enable( aEnable );
 }
+
diff --git a/include/wx_unit_binder.h b/include/wx_unit_binder.h
index ad4741d56..7639c8494 100644
--- a/include/wx_unit_binder.h
+++ b/include/wx_unit_binder.h
@@ -28,7 +28,7 @@
 #include 
 #include 
 
-class wxTextCtrl;
+class wxTextEntry;
 class wxSpinButton;
 class wxStaticText;
 
@@ -39,11 +39,11 @@ public:
 /**
  * Constructor.
  * @param aParent is the parent window.
- * @param aTextInput is the text input widget used to edit the given value.
+ * @param aTextInput is the text input widget used to edit the given value (wxTextCtrl, wxComboBox, ...).
  * @param aUnitLabel is the units label displayed next to the text field.
  * @param aSpinButton is an optional spin button (for adjusting the input value)
  */
-WX_UNIT_BINDER( wxWindow* aParent, wxTextCtrl* aTextInput, wxStaticText* aUnitLabel, wxSpinButton* aSpinButton = NULL );
+WX_UNIT_BINDER( wxWindow* aParent, wxTextEntry* aTextInput, wxStaticText* aUnitLabel, wxSpinButton* aSpinButton = NULL );
 
 virtual ~WX_UNIT_BINDER();
 
@@ -77,7 +77,7 @@ protected:
 void onTextChanged( wxEvent& aEvent );
 
 ///> Text input control.
-wxTextCtrl*   m_textCtrl;
+wxTextEntry*   m_textEntry;
 
 ///> Label showing currently used units.
 wxStaticText* m_unitLabel;
diff --git a/pcbnew/dialogs/dialog_track_via_properties.cpp b/pcbnew/dialogs/dialog_track_via_properties.cpp
index 4a2c69a26..28d4c1b30 100644
--- a/pcbnew/dialogs/dialog_track_via_properties.cpp
+++ b/pcbnew/dialogs/dialog_track_via_properties.cpp
@@ -204,6 +204,13 @@ DIALOG_TRACK_VIA_PROPERTIES::DIALOG_TRACK_VIA_PROPERTIES( PCB_BASE_FRAME* aParen
 setCommonVal( trackEndY, m_TrackEndYCtrl, m_trackEndY );
 setCommonVal( trackWidth, m_TrackWidthCtrl, m_trackWidth );
 
+for( unsigned ii = 0; ii < aParent->GetDesignSettings().m_TrackWidthList.size(); ii++ )
+{
+int width = aParent->GetDesignSettings().m_TrackWidthList[ii];
+wxString msg = StringFromValue( g_UserUnit, width, false );
+m_TrackWidthCtrl->Append( msg );
+}
+
 m_TrackLayerCtrl->SetLayersHotkeys( false );
 m_TrackLayerCtrl->SetLayerSet( LSET::AllNonCuMask() );
 m_TrackLayerCtrl->SetBoardFrame( aParent );
diff --git a/pcbnew/dialogs/dialog_track_via_properties.h b/pcbnew/dialogs/dialog_track_via_properties.h
index 3be7d4d77..14e15518c 100644
--- a/pcbnew/dialogs/dialog_track_via_properties.h
+++ b/pcbnew/dialogs/dialog_track_via_properties.h
@@ -5

Re: [Kicad-developers] should we change control in 3d-viewer

2017-08-24 Thread Nick Østergaard

What version o kicad are you talking about?

It is pretty easy to use in master.

2017-08-22 11:39 GMT+02:00 liyoubdu :

> it is hard to move and roll pcb board in 3d-viewer. why not design the
> control as same as a game. that is a very intuitive and natural way to
> control the object in a game.
> ___
> 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] Stable release 4.0.7 status.

2017-08-24 Thread Nick Østergaard

I have now added the Librarians team as write for those four repos. Please
tag appropiately. I can tag them if HEAD is good enough.

2017-08-24 20:59 GMT+02:00 Nick Østergaard :

> My script tells me this:
> ### SUMMARY ###
> Repos to be removed from release tar: 0 Air_Coils_SML_NEOSID.pretty
> Choke_Axial_ThroughHole.pretty Choke_Radial_ThroughHole.pretty
> Choke_SMD.pretty Choke_Toroid_ThroughHole.pretty
> Choke_Common-Mode_Wurth.pretty Filters_HF_Coils_NEOSID.pretty
> Inductors.pretty Inductors_NEOSID.pretty NF-Transformers_ETAL.pretty
> Oddities.pretty Sockets_MOLEX_KK-System.pretty
> Transformers_SMPS_ThroughHole.pretty Transformers_CHK.pretty
> Connectors_Amphenol.pretty TerminalBlocks_WAGO.pretty
> TerminalBlocks_Phoenix.pretty divers.pretty discret.pretty labels.pretty
> RF_Antennas.pretty Connectors_Card.pretty
> Repos to be included to the release tar: 82
> Repos expected to be included from the fp-lib-table:86
> 8d7
> < Connectors_Card.pretty
> 69d67
> < RF_Antennas.pretty
> 76,77d73
> < TerminalBlocks_Phoenix.pretty
> < TerminalBlocks_WAGO.pretty
>
>
> 2017-08-24 16:59 GMT+02:00 Oliver Walters 
> :
>
>> Rene, which libs are you missing write access for? I can fix that for you
>> :)
>>
>> On 24 Aug 2017 08:55, "Wayne Stambaugh"  wrote:
>>
>>> Thank you Rene!
>>>
>>> What else needs to be done so we can get the packages built?
>>>
>>> On 8/23/2017 6:51 PM, Rene Pöschl wrote:
>>> > On 22/08/17 14:53, Wayne Stambaugh wrote:
>>> >> Sorry about the delay but I was dealing with a family emergency all
>>> last
>>> >> week.  Now that I'm getting caught up I really need to get stable
>>> >> version 4.0.7 released.  Are there any outstanding issue remaining
>>> >> before I make the release announcement?  I'm shooting for Friday or
>>> >> Saturday.
>>> >>
>>> >> On 8/17/2017 8:45 AM, Rene Pöschl wrote:
>>> >>> On 16/08/17 01:35, Wayne Stambaugh wrote:
>>>  AFAIK we intend to use the 4.0.6 tag for libraries, docs, and i18n.
>>>  The
>>>  libraries in particular have changed significantly and I think it's
>>> a
>>>  bad idea to break users schematics on a point release.
>>> >>> Does the default setup of kicad use the github plugin to get up do
>>> date
>>> >>> footprints?
>>> >> Github.
>>> >>
>>> >>> If so this will create inconsistencies within the lib. (If the symbol
>>> >>> and 3d model libs are not updated as well)
>>> >> I hadn't thought about that but you are correct.  Maybe it makes sense
>>> >> to tag the library repo where it stands right now.  That being said,
>>> as
>>> >> the footprints and library repo change, they may (will) eventually get
>>> >> out of sync so this isn't an ideal solution.
>>> >
>>> > I created the 4.0.7 tag on all our libs. (Well 4 footprint libs do not
>>> > have tags yet because i do not have write access to these 4 libs. The
>>> > good news is that these are very new libs with only a handful of
>>> > footprints in them.)
>>> >
>>> >>
>>> >>> In particular there might be a problem if either a footprint has been
>>> >>> renamed.
>>> >>> (Footprint field or footprint filters of a symbol is now wrong.)
>>> >>>
>>> >>> Or if the scaling, offset or rotation of 3d models changed within a
>>> >>> footprints 3d model settings.
>>> >>> (We got a lot of new correctly scaled models since the 4.0.6 release)
>>> >>>
>>> >>> In my opinion it would be best if users can control when they receive
>>> >>> new libraries.
>>> >>> Each update should make sure that all 3 types of libraries are
>>> updated
>>> >>> at the same time. (to the same version)
>>> >> Unfortunately, we are not set up to handle this at the moment and I
>>> >> would not ask our package devs to fix this for the 4.0.7 release.  It
>>> is
>>> >> certainly something worth considering for the 5 stable release.
>>> > I am aware of the fact that over time the libs will again get out of
>>> > sync. (I think everyone involved with the library is aware of this
>>> fact.)
>>> > The impact of our scaling changes will be reduced if users get an
>>> update
>>> > of the 3d lib.
>>> >
>>> >
>>> >
>>> > ___
>>> > 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/

Re: [Kicad-developers] Stable release 4.0.7 status.

2017-08-24 Thread Nick Østergaard

My script tells me this:
### SUMMARY ###
Repos to be removed from release tar: 0 Air_Coils_SML_NEOSID.pretty
Choke_Axial_ThroughHole.pretty Choke_Radial_ThroughHole.pretty
Choke_SMD.pretty Choke_Toroid_ThroughHole.pretty
Choke_Common-Mode_Wurth.pretty Filters_HF_Coils_NEOSID.pretty
Inductors.pretty Inductors_NEOSID.pretty NF-Transformers_ETAL.pretty
Oddities.pretty Sockets_MOLEX_KK-System.pretty
Transformers_SMPS_ThroughHole.pretty Transformers_CHK.pretty
Connectors_Amphenol.pretty TerminalBlocks_WAGO.pretty
TerminalBlocks_Phoenix.pretty divers.pretty discret.pretty labels.pretty
RF_Antennas.pretty Connectors_Card.pretty
Repos to be included to the release tar: 82
Repos expected to be included from the fp-lib-table:86
8d7
< Connectors_Card.pretty
69d67
< RF_Antennas.pretty
76,77d73
< TerminalBlocks_Phoenix.pretty
< TerminalBlocks_WAGO.pretty


2017-08-24 16:59 GMT+02:00 Oliver Walters :

> Rene, which libs are you missing write access for? I can fix that for you
> :)
>
> On 24 Aug 2017 08:55, "Wayne Stambaugh"  wrote:
>
>> Thank you Rene!
>>
>> What else needs to be done so we can get the packages built?
>>
>> On 8/23/2017 6:51 PM, Rene Pöschl wrote:
>> > On 22/08/17 14:53, Wayne Stambaugh wrote:
>> >> Sorry about the delay but I was dealing with a family emergency all
>> last
>> >> week.  Now that I'm getting caught up I really need to get stable
>> >> version 4.0.7 released.  Are there any outstanding issue remaining
>> >> before I make the release announcement?  I'm shooting for Friday or
>> >> Saturday.
>> >>
>> >> On 8/17/2017 8:45 AM, Rene Pöschl wrote:
>> >>> On 16/08/17 01:35, Wayne Stambaugh wrote:
>>  AFAIK we intend to use the 4.0.6 tag for libraries, docs, and i18n.
>>  The
>>  libraries in particular have changed significantly and I think it's a
>>  bad idea to break users schematics on a point release.
>> >>> Does the default setup of kicad use the github plugin to get up do
>> date
>> >>> footprints?
>> >> Github.
>> >>
>> >>> If so this will create inconsistencies within the lib. (If the symbol
>> >>> and 3d model libs are not updated as well)
>> >> I hadn't thought about that but you are correct.  Maybe it makes sense
>> >> to tag the library repo where it stands right now.  That being said, as
>> >> the footprints and library repo change, they may (will) eventually get
>> >> out of sync so this isn't an ideal solution.
>> >
>> > I created the 4.0.7 tag on all our libs. (Well 4 footprint libs do not
>> > have tags yet because i do not have write access to these 4 libs. The
>> > good news is that these are very new libs with only a handful of
>> > footprints in them.)
>> >
>> >>
>> >>> In particular there might be a problem if either a footprint has been
>> >>> renamed.
>> >>> (Footprint field or footprint filters of a symbol is now wrong.)
>> >>>
>> >>> Or if the scaling, offset or rotation of 3d models changed within a
>> >>> footprints 3d model settings.
>> >>> (We got a lot of new correctly scaled models since the 4.0.6 release)
>> >>>
>> >>> In my opinion it would be best if users can control when they receive
>> >>> new libraries.
>> >>> Each update should make sure that all 3 types of libraries are updated
>> >>> at the same time. (to the same version)
>> >> Unfortunately, we are not set up to handle this at the moment and I
>> >> would not ask our package devs to fix this for the 4.0.7 release.  It
>> is
>> >> certainly something worth considering for the 5 stable release.
>> > I am aware of the fact that over time the libs will again get out of
>> > sync. (I think everyone involved with the library is aware of this
>> fact.)
>> > The impact of our scaling changes will be reduced if users get an update
>> > of the 3d lib.
>> >
>> >
>> >
>> > ___
>> > 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] Stable release 4.0.7 status.

2017-08-24 Thread Oliver Walters

Rene, which libs are you missing write access for? I can fix that for you
:)

On 24 Aug 2017 08:55, "Wayne Stambaugh"  wrote:

> Thank you Rene!
>
> What else needs to be done so we can get the packages built?
>
> On 8/23/2017 6:51 PM, Rene Pöschl wrote:
> > On 22/08/17 14:53, Wayne Stambaugh wrote:
> >> Sorry about the delay but I was dealing with a family emergency all last
> >> week.  Now that I'm getting caught up I really need to get stable
> >> version 4.0.7 released.  Are there any outstanding issue remaining
> >> before I make the release announcement?  I'm shooting for Friday or
> >> Saturday.
> >>
> >> On 8/17/2017 8:45 AM, Rene Pöschl wrote:
> >>> On 16/08/17 01:35, Wayne Stambaugh wrote:
>  AFAIK we intend to use the 4.0.6 tag for libraries, docs, and i18n.
>  The
>  libraries in particular have changed significantly and I think it's a
>  bad idea to break users schematics on a point release.
> >>> Does the default setup of kicad use the github plugin to get up do date
> >>> footprints?
> >> Github.
> >>
> >>> If so this will create inconsistencies within the lib. (If the symbol
> >>> and 3d model libs are not updated as well)
> >> I hadn't thought about that but you are correct.  Maybe it makes sense
> >> to tag the library repo where it stands right now.  That being said, as
> >> the footprints and library repo change, they may (will) eventually get
> >> out of sync so this isn't an ideal solution.
> >
> > I created the 4.0.7 tag on all our libs. (Well 4 footprint libs do not
> > have tags yet because i do not have write access to these 4 libs. The
> > good news is that these are very new libs with only a handful of
> > footprints in them.)
> >
> >>
> >>> In particular there might be a problem if either a footprint has been
> >>> renamed.
> >>> (Footprint field or footprint filters of a symbol is now wrong.)
> >>>
> >>> Or if the scaling, offset or rotation of 3d models changed within a
> >>> footprints 3d model settings.
> >>> (We got a lot of new correctly scaled models since the 4.0.6 release)
> >>>
> >>> In my opinion it would be best if users can control when they receive
> >>> new libraries.
> >>> Each update should make sure that all 3 types of libraries are updated
> >>> at the same time. (to the same version)
> >> Unfortunately, we are not set up to handle this at the moment and I
> >> would not ask our package devs to fix this for the 4.0.7 release.  It is
> >> certainly something worth considering for the 5 stable release.
> > I am aware of the fact that over time the libs will again get out of
> > sync. (I think everyone involved with the library is aware of this fact.)
> > The impact of our scaling changes will be reduced if users get an update
> > of the 3d lib.
> >
> >
> >
> > ___
> > 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] Python script offered as example for Action Plugin and wxFormBuilder integration

Re: [Kicad-developers] Stable release 4.0.7 status.

Re: [Kicad-developers] Stable release 4.0.7 status.

Re: [Kicad-developers] Stable release 4.0.7 status.

Re: [Kicad-developers] Stable release 4.0.7 status.

Re: [Kicad-developers] [PATCH] Change track width setting to dropbox

Re: [Kicad-developers] should we change control in 3d-viewer

Re: [Kicad-developers] Stable release 4.0.7 status.

Re: [Kicad-developers] Stable release 4.0.7 status.

Re: [Kicad-developers] Stable release 4.0.7 status.

10 matches

Site Navigation

Mail list logo

Footer information