Re: [Kicad-developers] Gerber output units?

2015-08-04 Thread Lorenzo Marcantonio
On Tue, 04 Aug 2015 05:38:26 +0200,
Chris Pavlina wrote:
 
 pcbnew used to be able to plot Gerbers in imperial units. What happened 
 to that? Some (particularly older and non-Asian) board houses still 
 expect those... Is there any reason they were removed, or did they just 
 fall out? And can they be put back in?

Since the new plotting infrastructure the gerber plotter already
supported both units; the IN was simply the compatibility default and it
only needed an UI option to be bound.

If someone changed the default without adding a radio button or
something then blame to him:P

AFAIK there would be no technical reason to not do inch plotting...

-- 
Lorenzo Marcantonio
Logos Srl

___
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] Skip redundant repetition of component name in component chooser

2015-08-04 Thread Carl Poirier
Hi,

This is just to let you know that this has been merged. Sorry for it taking
so long.

Regards,

Carl

On Fri, Jun 26, 2015 at 3:20 PM, Wayne Stambaugh stambau...@gmail.com
wrote:

 Indeed!  In fact my couple of beer suggestion is sounding like a pretty
 good idea right about now. :)

 On 6/26/2015 3:11 PM, Adam Wolf wrote:
  Not only does no good deed go unpunished, every change breaks someone's
  workflow :)
 
  https://xkcd.com/1172/
 
  Adam Wolf
  Cofounder and Engineer
  WL
 
  On Fri, Jun 26, 2015 at 2:09 PM, Wayne Stambaugh stambau...@gmail.com
  mailto:stambau...@gmail.com wrote:
 
  On 6/26/2015 2:59 PM, Vesa Solonen wrote:
   26/06/15, 21:54, Adam Wolf kirjoitti:
   I think it is unfortunate that a request to the library
 maintainers
   requested by Wayne is responded to with a one line dismissal of:
  
   You know my opinion and it is immutable. Sorry.
  
   Adam Wolf
   Cofounder and Engineer
   WL
  
   On Fri, Jun 26, 2015 at 11:08 AM, Henner Zeller h.zel...@acm.org
 mailto:h.zel...@acm.org
   mailto:h.zel...@acm.org mailto:h.zel...@acm.org wrote:
  
   ... Looks like library maintainers don't like it; see thread
 here:
   https://github.com/KiCad/kicad-library/pull/231
  
   -h
  
   Give it two days to sink in. Friday evenings may not be the best
 time
   either... ;)
  
   -Vesa
  
 
  Two days and a couple of beers. :)
 
  I'm going to avoid a pissing contest at this juncture in order to
 focus
  on the stable release.  I understand where Kerusey's frustration is
  coming from.  No one wants to see their efforts removed from the
 project
  but his response is not in the best interest of the project even if
 he
  is correct.  Henner, could you rework your patch to include a
 checkbox
  to hide the redundant description field information in your component
  search dialog.  Please make the default setting disabled so no one
 has a
  stroke.  No good deed goes unpunished.  Sig!
 
 
  ___
  Mailing list: https://launchpad.net/~kicad-developers
  Post to : kicad-developers@lists.launchpad.net
  mailto: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] Skip redundant repetition of component name in component chooser

2015-08-04 Thread Henner Zeller
On 4 August 2015 at 07:28, Carl Poirier carl.poirie...@gmail.com wrote:

 Hi,

 This is just to let you know that this has been merged. Sorry for it
 taking so long.


Thanks for merging my library cleanup patch! This way, we don't need the
(more hacky) workaround in the KiCAD application to 'manually' remove the
prefices there.

-h


 Regards,

 Carl

 On Fri, Jun 26, 2015 at 3:20 PM, Wayne Stambaugh stambau...@gmail.com
 wrote:

 Indeed!  In fact my couple of beer suggestion is sounding like a pretty
 good idea right about now. :)

 On 6/26/2015 3:11 PM, Adam Wolf wrote:
  Not only does no good deed go unpunished, every change breaks someone's
  workflow :)
 
  https://xkcd.com/1172/
 
  Adam Wolf
  Cofounder and Engineer
  WL
 
  On Fri, Jun 26, 2015 at 2:09 PM, Wayne Stambaugh stambau...@gmail.com
  mailto:stambau...@gmail.com wrote:
 
  On 6/26/2015 2:59 PM, Vesa Solonen wrote:
   26/06/15, 21:54, Adam Wolf kirjoitti:
   I think it is unfortunate that a request to the library
 maintainers
   requested by Wayne is responded to with a one line dismissal of:
  
   You know my opinion and it is immutable. Sorry.
  
   Adam Wolf
   Cofounder and Engineer
   WL
  
   On Fri, Jun 26, 2015 at 11:08 AM, Henner Zeller 
 h.zel...@acm.org mailto:h.zel...@acm.org
   mailto:h.zel...@acm.org mailto:h.zel...@acm.org wrote:
  
   ... Looks like library maintainers don't like it; see thread
 here:
   https://github.com/KiCad/kicad-library/pull/231
  
   -h
  
   Give it two days to sink in. Friday evenings may not be the best
 time
   either... ;)
  
   -Vesa
  
 
  Two days and a couple of beers. :)
 
  I'm going to avoid a pissing contest at this juncture in order to
 focus
  on the stable release.  I understand where Kerusey's frustration is
  coming from.  No one wants to see their efforts removed from the
 project
  but his response is not in the best interest of the project even if
 he
  is correct.  Henner, could you rework your patch to include a
 checkbox
  to hide the redundant description field information in your
 component
  search dialog.  Please make the default setting disabled so no one
 has a
  stroke.  No good deed goes unpunished.  Sig!
 
 
  ___
  Mailing list: https://launchpad.net/~kicad-developers
  Post to : kicad-developers@lists.launchpad.net
  mailto: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] Thanks to whoever done this :D

2015-08-04 Thread yann jautard



Le 02/08/2015 11:40, yann jautard a écrit :



Le 30/07/2015 15:10, Wayne Stambaugh a écrit :

If you or anyone else happens to find any other dialogs without a
default button, please report them as soon as possible so they can be
fixed for the stable release.




pcbnew change footprint window. I also noticed closing this window 
with the windowmanager close button instead of this window's close 
button closes also the parent window (edit footprint)


Well in fact even the close button closes the parent window. Changes 
made in the footprint properties window before opening the change 
footprint window are not saved when both windows are dismissed by 
close button in the change footprint window.


Escape key works but also close the footprint properties window as well.

___
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 update.

2015-08-04 Thread Carl Poirier
 I'd like this
https://github.com/KiCad/TO_SOT_Packages_SMD.pretty/issues/1 to be
merged. In a few words, it consists of merging some libraries dating back
from pre-github
 era into two cleaner ones: TO_SOT_Packages_SMD.pretty and
TO_SOT_Packages_THT.pretty. Possibly
 also renaming the _ThroughHole suffix to _THT for the other libraries.

Hi,

This is just to let you guys know that this has been merged. The
repositories to be deleted will be kept a while although they are marked as
deprecated. You should see no issue if you wait to update your
kicad-library and fp-lib-table.

Regards,

Carl

On Sun, Jun 21, 2015 at 12:21 PM, Wayne Stambaugh stambau...@gmail.com
wrote:

 On 6/20/2015 4:21 PM, Chris Pavlina wrote:
  On Sat, Jun 20, 2015 at 09:14:14PM +0100, David J S Briscoe wrote:
  [snip] I'm afraid I will screw up the files on Github so probably
  better for me to do it the old fashioned way. Who can I send the edited
  files to?
 
  If you do this, someone will have to convert them back to AsciiDoc *by
  hand*. The AsciiDoc is the original source now. You'll have to learn
  git.
 
  --
  Chris

 The official documentation is now https://github.com/KiCad/kicad-doc.
 Please do not make any changes to the legacy .odt documentation on
 launchpad as it will surely get lost.

 
 
  ___
  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


[Kicad-developers] PATCH: improve library install script a little

2015-08-04 Thread Henner Zeller
Hi,
Some small changes for the library-repos-install.sh script.

https://github.com/hzeller/kicad/compare/master...hzeller:script-no-grep-dependency.diff

Suggested commit message:

o library install script improvements
   - Make WORKING_TREES configurable with environment variable to
 simplify external install scripts.
   - Don't use grep but native sed functionality to find relevant
 lines in github JSON (grep can create trouble if there is a
 global --color=always setting)

(guess how I found out about the color setting haha).

-h
___
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] Export to Solidworks

2015-08-04 Thread Jose A. Saumell
Hello group,

I have been trying to export a 3D model of a populated PCB to Solidworks
and after a few days I want to ask you for help.

I've generated VRML files for each component and did an export in VRML
which I can open and see in FreeCAD correctly.

I need to interface with Mechanical Engineer that has their own Solidworks
model for the enclosure. He has been able to open the populated PCB on
Freecad as well. (To achieve this I had to use a text editor and modify all
the url entries on WRL file with an absolute path on his system containing
shapes3D folder, at least freecad does not seem to work with relative path)

What he was able to achieve so far is opening the empty PCB in solidworks
and load each individual component and placing manually on the board.

Is there any other way or tips you can provide? I've read about IDF and I
may go that route with the next design if it means easier interfacing with
Solidworks.

Thanks
___
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] Export to Solidworks

2015-08-04 Thread Cirilo Bernardo
There are a number of options:

1. Recently Maurice wrote a script which uses FreeCAD to create a
STEP modelusing the bare board IDF file and other data in the
.kicad_pcb file:

http://bazaar.launchpad.net/~easyw/kicad-stepup/trunk/files

No doubt there are still some issues but this is currently the best
method for exporting a detailed mechanical model.

2. IDF: If you do nothing and simply opt to export the board then
you only get a bare board - this step is necessary anyway if you
use Maurice's script to create a STEP model. If you wish for a more
detailed IDF model you will need to spend some time creating the
associated component outline files.  The official IDF documentation
is here:

https://github.com/ciampix/kicad-doc/tree/master/src/IDF_Exporter

but if you can't generate the documentation and want a PDF version
the original (more inaccurate) version is here:

https://drive.google.com/open?id=0By_XTJN-s8aXbkM5UTE0Zm5SN28

Now for Solidworks to process an IDF file you need CircuitWorks which
is only provided with Solidworks Premium - bummer. Fortunately you
can now convert IDF to IGES (which any MCAD can understand) using
the 'idf2igs' tool in the IGES library which is in development:

https://github.com/cbernardo/libIGES

There are also online tools to help such as:
https://www.ecad.io

That site provides all the functionality of CircuitWorks - you can
substitute real models for the simplistic IDF outlines. However, if the
simple IDF outlines are fine for your mechanical work then the
libIGES tool is a completely free solution.

Expect more MCAD exchange features in the future, though the wait
may be a little long due to limited resources. My libIGES already has
the capability to create models of the bare PCB and to add other
existing IGES models to the mechanical assembly and I plan to add
an IGES export to KiCad some time after the pending stable release.
Unfortunately I also need to do some major work on the KiCad code
base before I add this code so it could be another 6 months or more
before you see that feature in KiCad. There have also been discussions
on adding a STEP export facility using the OpenCascade libraries,
but this is also dependent on those code changes which I need to
make to KiCad. So for now, Maurice's scripts are really the best
option for creating a detailed mechanical model.

- Cirilo


On Wed, Aug 5, 2015 at 7:21 AM, Jose A. Saumell saumell.j...@gmail.com
wrote:

 Hello group,

 I have been trying to export a 3D model of a populated PCB to Solidworks
 and after a few days I want to ask you for help.

 I've generated VRML files for each component and did an export in VRML
 which I can open and see in FreeCAD correctly.

 I need to interface with Mechanical Engineer that has their own Solidworks
 model for the enclosure. He has been able to open the populated PCB on
 Freecad as well. (To achieve this I had to use a text editor and modify all
 the url entries on WRL file with an absolute path on his system containing
 shapes3D folder, at least freecad does not seem to work with relative path)

 What he was able to achieve so far is opening the empty PCB in solidworks
 and load each individual component and placing manually on the board.

 Is there any other way or tips you can provide? I've read about IDF and I
 may go that route with the next design if it means easier interfacing with
 Solidworks.

 Thanks

 ___
 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] Skip redundant repetition of component name in component chooser

2015-08-04 Thread Henner Zeller
[Adding kicad-devel back; context:
https://github.com/KiCad/kicad-library/pull/231 ]

On 4 August 2015 at 08:41, Kerusey Karyu keruseyka...@o2.pl wrote:

 Henner Zeller w dniu Tue, 4 Aug 2015 07:48:54 -0700 napisał:

  Thanks for merging my library cleanup patch! This way, we don't need
  the (more hacky) workaround in the KiCAD application to 'manually'
  remove the prefices there.
 

 Let me speak the final words:
 And in this way the group got rid one of a translator, library
 maintainer and contributor. Every revolution destroys their children...

 Best Regards
 Kerusey Karyu


I am sorry that you feel that way and I am probably not too qualified to
respond here as I am just contributing a patch without knowledge of
possible prior context around - I guess you didn't mean to privately send
it to me, so I added the devel group back. I certainly didn't mean to
create any bad feelings here, just propose a reasonable patch.

My reason for this change is simple: it removes redundancy (which is always
good when maintaining data). And with that, it allows to show more relevant
information in the limited space in the component chooser. Several KiCAD
developers felt the same way.

The redundant data didn't serve any apparent purpose; in the pull request,
you were vehemently against the change, but couldn't state a reason why it
would be useful to keep it the way it was. Maybe everybody is blind to the
actual reason, but if you don't state it, people will go with the more
reasonable choice for them.

I presume that you spent quite some time in the past adding these as
searching used to be very tedious - which is the what you said in the pull
request. And of course that means that you are attached to the work that
went into it. But shouldn't we all be happy to be able to remove a
workaround when the original problem (tedious searching) is fixed ?

I can't comment on your decision to stop contributing, the group is
probably more qualified for it. If this pull request is the trigger, then
this is a sad outcome. As a user, I thank you for your tremendous
contribution to the KiCAD libraries and wish that some healthy discussion
can keep you on-board.

Thanks,
  Henner.
___
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] Eeschema config keyboard mnemonics

2015-08-04 Thread Wayne Stambaugh
On 8/3/2015 1:02 PM, Chris Pavlina wrote:
 Hi,
 
 The keyboard mnemonics (underlined letters) in the eeschema and libedit 
 config boxes are a bit messy. There is at least one conflict (two items 
 sharing L), and many items missing mnemonics.
 
 I could easily patch this, but I'd rather discuss: perhaps they should 
 be removed? It is not usual to have mnemonics in large, complicated 
 dialogs like this - they're not particularly useful there, and they are 
 error-prone as the current state demonstrates. People forget to add 
 them, or miss conflicts. Mnemonics are much more useful in dialogs that 
 are used frequently like text edit dialogs, where a user might want, for 
 example, to jump quickly to the text size field. With so many options, 
 nobody is going to remember the mnemonics anyway (note what mnemonic 
 means: it's a memory aid!), and it doesn't save any time when one has to 
 squint at all the options to find the underlined letter.
 
 Of course the possibility for inconsistency goes even farther: I haven't 
 even checked the localizations to see how they behave.
 
 Anybody else in favor of just removing them from these two dialogs? The 
 pcbnew and modedit dialogs already do not use them, and most other GUI 
 applications that I checked now also do not use them in their 
 Preferences boxes.
 
 
 --
 Chris
 

While your logic make sense, my preference is to keep the mnemonics, fix
any duplicates, and add the missing ones in any offending dialogs.  I
realize on some complex dialogs, it can be difficult to set unique
mnemonics but that's pretty rare.  There are still a lot of us old
timers around who prefer our keyboards over reaching for the mouse
whenever possible.  I know it's passe and quaint but I'm not ready to
give it up just yet :)

___
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] Gerber output units?

2015-08-04 Thread jp charras
Le 04/08/2015 08:29, Lorenzo Marcantonio a écrit :
 On Tue, 04 Aug 2015 05:38:26 +0200,
 Chris Pavlina wrote:

 pcbnew used to be able to plot Gerbers in imperial units. What happened 
 to that? Some (particularly older and non-Asian) board houses still 
 expect those... Is there any reason they were removed, or did they just 
 fall out? And can they be put back in?
 
 Since the new plotting infrastructure the gerber plotter already
 supported both units; the IN was simply the compatibility default and it
 only needed an UI option to be bound.
 
 If someone changed the default without adding a radio button or
 something then blame to him:P
 
 AFAIK there would be no technical reason to not do inch plotting...
 

There is a technical reason to not do inch plotting.
I recently explained it.

Pcbnew internally uses nanometers, corresponding to 6 digits mantissa in
Gerber.

If we use a 6 digits mantissa and mm in Gerber, there is no rounding issue.
If we convert these values to inches, I am pretty sure rounding issues
will appear.

For most of coordinates, a rounding issue has no matter.
However, for complex polygons (copper zones) rounding coordinates can
create self intersecting polygons from non intersecting polygons.
Self intersecting polygons are not allowed in Gerber files (see gerber
file format spec).

The advice from Ucamco is (especially for this issue) is:
use the max resolution for coordinates (see also the gerber file format
spec).


The only one reason the 5 digits mantissa option exists in Pcbnew is the
fact Ucamco told me a few Gerbers tools do not accept the 6 digits.

I verified some Gerber files which are OK with 6 digits mantissa create
self intersecting polygons when using 5 digits from the same board.
(Tests with GC-Preview)

(to tell the True, the Gerber image on screen was the same)

We already have a bug report about self intersecting polygons in Gerber
files from Kicad.

It also explains why a Gerber reader can gives warnings about that
issue, and an other Gerber reader does not find any issue: it depends
also on internal units of the reader.


Therefore, until someone give me a *very good reason* why inches are
better than mm in Gerber files, I *do not want* a inch option in Gerber
plot menu ( or, if this option exists, commit an algo to avoid self
intersecting polygons).

-- 
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


[Kicad-developers] Gerber output units?

2015-08-04 Thread Ben Kempke
+1 from me for adding back imperial Gerber support. There was a recent
discussion regarding this in the following ticket. A small patch is
included as well to add the option for imperial output into the UI.

https://bugs.launchpad.net/bugs/1475730
On Aug 4, 2015 2:31 AM, Lorenzo Marcantonio l.marcanto...@logossrl.com
javascript:_e(%7B%7D,'cvml','l.marcanto...@logossrl.com'); wrote:

 On Tue, 04 Aug 2015 05:38:26 +0200,
 Chris Pavlina wrote:
 
  pcbnew used to be able to plot Gerbers in imperial units. What happened
  to that? Some (particularly older and non-Asian) board houses still
  expect those... Is there any reason they were removed, or did they just
  fall out? And can they be put back in?

 Since the new plotting infrastructure the gerber plotter already
 supported both units; the IN was simply the compatibility default and it
 only needed an UI option to be bound.

 If someone changed the default without adding a radio button or
 something then blame to him:P

 AFAIK there would be no technical reason to not do inch plotting...

 --
 Lorenzo Marcantonio
 Logos Srl

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 javascript:_e(%7B%7D,'cvml','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] Eeschema config keyboard mnemonics

2015-08-04 Thread Chris Pavlina
Gah, mailing list fail, sent directly to Wayne.

On Tue, Aug 04, 2015 at 02:32:53PM -0400, Chris Pavlina wrote:
 Hey, I'm one of those old timers in everything but age! I navigate 
 even my browser almost exclusively by keyboard using Vimium... The thing 
 is, I just never found them useful in a large dialog anyway because 
 they're so damned hard to read - they're good if you get used to them, 
 but you're not going to get used to the assignments in a dialog you 
 almost never use and which has so many mnemonics that it's nearly 
 running out of letters. It's more efficient to just thwack Tab a few 
 times.
 
 But that's okay, I'm not on the warpath to remove mnemonics or anything! 
 I'll tidy up the mnemonics in that dialog and perhaps a few others and 
 submit a patch soon.
 
 
 On Tue, Aug 04, 2015 at 02:28:47PM -0400, Wayne Stambaugh wrote:
  On 8/3/2015 1:02 PM, Chris Pavlina wrote:
   Hi,
   
   The keyboard mnemonics (underlined letters) in the eeschema and libedit 
   config boxes are a bit messy. There is at least one conflict (two items 
   sharing L), and many items missing mnemonics.
   
   I could easily patch this, but I'd rather discuss: perhaps they should 
   be removed? It is not usual to have mnemonics in large, complicated 
   dialogs like this - they're not particularly useful there, and they are 
   error-prone as the current state demonstrates. People forget to add 
   them, or miss conflicts. Mnemonics are much more useful in dialogs that 
   are used frequently like text edit dialogs, where a user might want, for 
   example, to jump quickly to the text size field. With so many options, 
   nobody is going to remember the mnemonics anyway (note what mnemonic 
   means: it's a memory aid!), and it doesn't save any time when one has to 
   squint at all the options to find the underlined letter.
   
   Of course the possibility for inconsistency goes even farther: I haven't 
   even checked the localizations to see how they behave.
   
   Anybody else in favor of just removing them from these two dialogs? The 
   pcbnew and modedit dialogs already do not use them, and most other GUI 
   applications that I checked now also do not use them in their 
   Preferences boxes.
   
   
   --
   Chris
   
  
  While your logic make sense, my preference is to keep the mnemonics, fix
  any duplicates, and add the missing ones in any offending dialogs.  I
  realize on some complex dialogs, it can be difficult to set unique
  mnemonics but that's pretty rare.  There are still a lot of us old
  timers around who prefer our keyboards over reaching for the mouse
  whenever possible.  I know it's passe and quaint but I'm not ready to
  give it up just yet :)
  
  ___
  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] Skip redundant repetition of component name in component chooser

2015-08-04 Thread Chris Pavlina
Kerusey, it's unfortunate that you feel this way. While I can understand 
your frustration, this emotional, and frankly, melodramatic reaction to 
a simple patch is exactly the sort of thing that puts off would-be new 
developers. Sometimes, when working on a large project, one must 
compromise. There are a ton of changes /I/ want to make to KiCad and its 
libs too, but I recognize that even if I were the Dictator of KiCad, I'd 
have to put up with it being not quite exactly what I want if I want to 
actually have users and developers.

It's unfortunate to lose a library maintainer and translator, but if 
your attitude was such that someone wanting to remove some tags from 
component descriptions makes you decide it's time to leave, blaming the 
rest of us for not quite agreeing with you, perhaps that attitude was 
keeping out more than one potential new developer, maintainer and 
translator. It certainly puts me off. That attitude from *other* unnamed 
developers kept me from submitting patches for quite a long time until 
the grouchy dev in question finally backed off a bit and I felt my 
contributions were welcome.

Some people just don't want to compromise on certain things. I know I 
don't - this is why I don't use or contribute to KiCad's official 
libraries. I disagree with the way they're done in many ways. So I solve 
this problem by maintaining my own libraries, which other people are 
welcome to use if they like, but which are not official and so I don't 
have to play nicely if they want to change things in ways I don't like. 
That might be a better way for you to approach library maintenance.


On Aug 4, 2015 1:05 PM, Henner Zeller h.zel...@acm.org wrote:

 [Adding kicad-devel back; context: 
 https://github.com/KiCad/kicad-library/pull/231 ]

 On 4 August 2015 at 08:41, Kerusey Karyu keruseyka...@o2.pl wrote:

 Henner Zeller w dniu Tue, 4 Aug 2015 07:48:54 -0700 napisał:

  Thanks for merging my library cleanup patch! This way, we don't need
  the (more hacky) workaround in the KiCAD application to 'manually'
  remove the prefices there.
 

 Let me speak the final words:
 And in this way the group got rid one of a translator, library
 maintainer and contributor. Every revolution destroys their children...

 Best Regards
 Kerusey Karyu


 I am sorry that you feel that way and I am probably not too qualified to 
 respond here as I am just contributing a patch without knowledge of 
 possible prior context around - I guess you didn't mean to privately send 
 it to me, so I added the devel group back. I certainly didn't mean to 
 create any bad feelings here, just propose a reasonable patch.

 My reason for this change is simple: it removes redundancy (which is 
 always good when maintaining data). And with that, it allows to show more 
 relevant information in the limited space in the component chooser. Several 
 KiCAD developers felt the same way.

 The redundant data didn't serve any apparent purpose; in the pull request, 
 you were vehemently against the change, but couldn't state a reason why it 
 would be useful to keep it the way it was. Maybe everybody is blind to the 
 actual reason, but if you don't state it, people will go with the more 
 reasonable choice for them.

 I presume that you spent quite some time in the past adding these as 
 searching used to be very tedious - which is the what you said in the pull 
 request. And of course that means that you are attached to the work that 
 went into it. But shouldn't we all be happy to be able to remove a 
 workaround when the original problem (tedious searching) is fixed ?

 I can't comment on your decision to stop contributing, the group is 
 probably more qualified for it. If this pull request is the trigger, then 
 this is a sad outcome. As a user, I thank you for your tremendous 
 contribution to the KiCAD libraries and wish that some healthy discussion 
 can keep you on-board.

 Thanks,
   Henner.

 ___
 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