Re: [Kicad-developers] Bump wx for OS X to 3.0.2 (with an extra patch?)
Hi, I think it is useful to collect all the various patches in the “patches” folder… so you don’t have to find them on the net yourself. I am not quite sure if they should be included in the small wxWidgets build script. Only goal of the script is to save some typing… if you put all the patches needed for one version in there you maybe can’t use it to build another version (where some parts of the patches might already be included). Regards, Bernhard On 28.10.2014, at 20:51, Adam Wolf adamw...@feelslikeburning.com wrote: Hi folks, Does anyone object to bumping wx to 3.0.2 for OS X, and adding the webdiff patch so it'll work on OS X 10.10, released last week (the week before?) If I don't hear anything, I'll prep a patch for the docs and the osx_build_wx.sh and send it in. Adam Wolf Cofounder and Engineer Wayne and Layne, LLC ___ 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] pcbnew export position file
Hello, I found small problem when generating position file. It was good before complete library name was used. It is shorted, and it is mainly impossible to understand which package has any footprint - there is mainly only part of library name. for example: # RefVal Package PosX PosYRot Side C5 1u Capacitor-sm_cap -0.1800 -1.2100 270.0F.Cu C8 100u/6.3VB Capacitor-sm_cap -0.1800 -1.0300 180.0F.Cu C9 100n Capacitor-sm_cap -0.1000 0.2150 180.0 F.Cu C12 100n Capacitor-sm_cap -0.0250 0.9550 0.0 F.Cu C13 100n Capacitor-sm_cap0.3200 0.8050 90.0 F.Cu C14 100n Capacitor-sm_cap0.4700 0.5100 270.0 F.Cu C16 100n Capacitor-sm_cap -0.4600 1.2600 0.0 F.Cu C17 T22u/10V Capacitor-sm_cap0.1000 0.2400 0.0 F.Cu C18 1u Capacitor-sm_cap -0.1250 1.0600 180.0 F.Cu C19 100n Capacitor-sm_cap -0.4500 -0.8150 180.0F.Cu Q1 IRLML0030libcms:SOT23GDS 0.0950 -0.6950 180.0F.Cu U1 LP2951 Vlastni-SM-IC:SO -0.4000 -1.2100 90.0F.Cu So after patch is visible only package, without library (I think that for machine component placing is library name not important). # RefVal Package PosX PosYRot Side C5 1u c_1206 -0.1800 -1.2100 270.0F.Cu C8 100u/6.3VB c_tant_B -0.1800 -1.0300 180.0F.Cu C9 100n c_0805 -0.1000 0.2150 180.0 F.Cu C12 100n c_0805 -0.0250 0.9550 0.0 F.Cu C13 100n c_0805 0.3200 0.8050 90.0 F.Cu C14 100n c_0805 0.4700 0.5100 270.0 F.Cu C16 100n c_0805 -0.4600 1.2600 0.0 F.Cu C17 T22u/10V c_tant_B0.1000 0.2400 0.0 F.Cu C18 1u c_1206 -0.1250 1.0600 180.0 F.Cu C19 100n c_0805 -0.4500 -0.8150 180.0F.Cu Q1 IRLML0030SOT23GDS0.0950 -0.6950 180.0F.Cu U1 LP2951 SOG8 -0.4000 -1.2100 90.0F.Cu Michal Jahelka === modified file 'pcbnew/exporters/gen_modules_placefile.cpp' --- pcbnew/exporters/gen_modules_placefile.cpp 2014-10-26 13:59:01 + +++ pcbnew/exporters/gen_modules_placefile.cpp 2014-10-29 08:58:24 + @@ -493,7 +493,7 @@ const wxString ref = list[ii].m_Reference; const wxString val = list[ii].m_Value; -const wxString pkg = list[ii].m_Module-GetFPID().Format(); +const wxString pkg = list[ii].m_Module-GetFPID().GetFootprintName(); sprintf( line, %-8.8s %-16.16s %-16.16s, TO_UTF8( ref ), TO_UTF8( val ), TO_UTF8( pkg ) ); ___ 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 documentation format
On Tue, Oct 28, 2014 at 12:12:52AM +0100, Guilherme Brondani Torri wrote: On 10/26/14, 12:17 AM, Marco Ciampa wrote: On Sat, Oct 25, 2014 at 10:52:54AM -0400, Wayne Stambaugh wrote: Marco, Great work on the conversion analysis. I finally go around to testing this and I have to say that I prefer the asciidoc format better than the markdown and rst formats for plain text readability. Almost everyone does it but please consider that readability is not the most important factor. As I said many people use rest because of sphinx. Please consider that sphinx integrate a search javascript function into the html generated, although maybe not so important. Hi there! Just a few comment of a casual user... I am also looking for alternatives for the Qucs documentation. Our manuals are in mostly in LaTex which is amazing for what it does, but is a bit of a pain to translate. I understand... I found the approach taken by OpenMOC rather interesting [1]. They use Sphinx and Doxygen combined. The whole documentation is automatically (re)generated at every commit, directly from the GitHub repository. These examples are _very_ interesting indeed. We could definitely build something similar. There is also this demo, [2] which combines Sphinx, Github, Transifex and publish in the Read the Docs. Apparently anyone with access to the fork can edit directly on the GitHub web editor and the documentation is rebuild. I never used Transifex, but it seems to work very well if someone takes responsibility to sync the translation files from time to time. I have yet to look for similar thinks with AsciiDoc... Me neither but, all in all, is just html pages automatically generated and commited into a git repo. Nothing that we couldn't afford with some simple scripting... Best regards, Guilherme [1] https://mit-crpg.github.io/OpenMOC/devguide/documentation.html http://masaori-sphinx-internationalization-example-en.readthedocs.org/en/latest/# Anyway I will take a look at it to see if there are some interesting details that I haven't seen... Many thanks! -- Marco Ciampa I know a joke about UDP, but you might not get it. ++ | 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] problems running kicad-install.sh
On 10/28/2014 4:51 PM, Marco Ciampa wrote: On Sun, Oct 26, 2014 at 10:59:20PM -0700, Jake wrote: [...] So i deleted the folder entirely with rm -rf ~/kicad_sources/kicad-lib.bzr/ and when i ran the script again, now it seems to be working. i don't know anything about how bzr works, i am just competent with git, so hopefully some bash scripting and bzr experts can think of a way to restructure the install script to more consistently deal with incomplete installations. I think that a less intrepid user than me (imagine!) would either have to delete all of ~/kicad_sources and start over, or give up entirely. please let me know if i should post this problem in the bugtracker or something else to make it easier to deal with, or if i have done it right. Bazaar is virtually dead. Its userbase decrease day by day. There are some bugs in it that presumably will never be fixed. For example, and this seems to be this case, if you stop a bzr up command abruptly, chances are that it will not be able to recover by himself, and you have to delete all and restart downloading afresh. I keep on thinking that a git migration of all kicad project repos should be considered for sometime in the (near?) future... Not until after the next stable release. Then we can discuss the matter further. I personally don't have a preference other than I don't want to be guy that has to do all of the work. I was around when we made the switch from subversion/sourceforge to bazaar/launchpad. It was not a trivial amount of work. bye ___ 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] Code cleaning.
Le 28/10/2014 20:59, Wayne Stambaugh a écrit :
I've been adding missing license statements to our source code and have
run into a few issues along the way.
Thanks.
PolyLine.h and PolyLine.cpp have this comment:
// PolyLine.cpp ... implementation of CPolyLine class from FreePCB.
at the top of the file with no other license information. Whoever added
this file please add the FreePCB license for this code so we are
compliant. I don't know what the FreePCB license is so I hope this is
not an issue. I believe the GPL does not allow for unlicensed source files.
I added the license information to these files in rev 5235.
There is no license issue: FreePCB is released under the GNU General
Public License V2 or later.
I noticed that the Python scripts in pcbnew/scripting/examples do not
get installed. Is there a reason we are not installing these files
along with the rest of kicad?
The kiface libraries are getting installed in ${prefix}/bin on Unix.
Aren't they supposed to be in ${prefix}/lib? Maybe our packagers are
running a script to move them to ${prefix}/lib but I think we should be
following convention here.
___
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
--
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] problems running kicad-install.sh
On 29 October 2014 12:18, Wayne Stambaugh stambau...@verizon.net wrote: On 10/28/2014 4:51 PM, Marco Ciampa wrote: On Sun, Oct 26, 2014 at 10:59:20PM -0700, Jake wrote: [...] So i deleted the folder entirely with rm -rf ~/kicad_sources/kicad-lib.bzr/ and when i ran the script again, now it seems to be working. i don't know anything about how bzr works, i am just competent with git, so hopefully some bash scripting and bzr experts can think of a way to restructure the install script to more consistently deal with incomplete installations. I think that a less intrepid user than me (imagine!) would either have to delete all of ~/kicad_sources and start over, or give up entirely. please let me know if i should post this problem in the bugtracker or something else to make it easier to deal with, or if i have done it right. Bazaar is virtually dead. Its userbase decrease day by day. There are some bugs in it that presumably will never be fixed. For example, and this seems to be this case, if you stop a bzr up command abruptly, chances are that it will not be able to recover by himself, and you have to delete all and restart downloading afresh. I keep on thinking that a git migration of all kicad project repos should be considered for sometime in the (near?) future... Not until after the next stable release. Then we can discuss the matter further. I personally don't have a preference other than I don't want to be guy that has to do all of the work. I was around when we made the switch from subversion/sourceforge to bazaar/launchpad. It was not a trivial amount of work. Also, this work is now compounded by the amount of bzr used during the build process in general. Several repos are created on-the-fly and patched and so on and so forth. I like git and particularly git patchsets for linux kernel work. I dislike git in most other circumstances as it just appears to obfuscate standard version control features in my opinion. However, that could be down to lack of experience with it really. Github however is something I really like. Best Regards, Brian. ___ 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] Code cleaning.
JP,
Thank you for taking care of this. I appreciate it.
Best Regards,
Wayne
On 10/29/2014 8:24 AM, jp charras wrote:
Le 28/10/2014 20:59, Wayne Stambaugh a écrit :
I've been adding missing license statements to our source code and have
run into a few issues along the way.
Thanks.
PolyLine.h and PolyLine.cpp have this comment:
// PolyLine.cpp ... implementation of CPolyLine class from FreePCB.
at the top of the file with no other license information. Whoever added
this file please add the FreePCB license for this code so we are
compliant. I don't know what the FreePCB license is so I hope this is
not an issue. I believe the GPL does not allow for unlicensed source files.
I added the license information to these files in rev 5235.
There is no license issue: FreePCB is released under the GNU General
Public License V2 or later.
I noticed that the Python scripts in pcbnew/scripting/examples do not
get installed. Is there a reason we are not installing these files
along with the rest of kicad?
The kiface libraries are getting installed in ${prefix}/bin on Unix.
Aren't they supposed to be in ${prefix}/lib? Maybe our packagers are
running a script to move them to ${prefix}/lib but I think we should be
following convention here.
___
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] pcbnew export position file
On 29 October 2014 09:15, Michal Jahelka michal.jahe...@pavelek.cz wrote: Hello, I found small problem when generating position file. It was good before complete library name was used. It is shorted, and it is mainly impossible to understand which package has any footprint - there is mainly only part of library name. for example: # RefVal Package PosX PosYRot Side C5 1u Capacitor-sm_cap -0.1800-1.2100 270.0 F.Cu C8 100u/6.3VB Capacitor-sm_cap -0.1800-1.0300 180.0 F.Cu C9 100n Capacitor-sm_cap -0.1000 0.2150 180.0 F.Cu C12 100n Capacitor-sm_cap -0.0250 0.9550 0.0 F.Cu C13 100n Capacitor-sm_cap0.3200 0.8050 90.0 F.Cu C14 100n Capacitor-sm_cap0.4700 0.5100 270.0 F.Cu C16 100n Capacitor-sm_cap -0.4600 1.2600 0.0 F.Cu C17 T22u/10V Capacitor-sm_cap0.1000 0.2400 0.0 F.Cu C18 1u Capacitor-sm_cap -0.1250 1.0600 180.0 F.Cu C19 100n Capacitor-sm_cap -0.4500-0.8150 180.0 F.Cu Q1 IRLML0030libcms:SOT23GDS 0.0950-0.6950 180.0 F.Cu U1 LP2951 Vlastni-SM-IC:SO -0.4000-1.2100 90.0 F.Cu So after patch is visible only package, without library (I think that for machine component placing is library name not important). # RefVal Package PosX PosYRot Side C5 1u c_1206 -0.1800-1.2100 270.0 F.Cu C8 100u/6.3VB c_tant_B -0.1800-1.0300 180.0 F.Cu C9 100n c_0805 -0.1000 0.2150 180.0 F.Cu C12 100n c_0805 -0.0250 0.9550 0.0 F.Cu C13 100n c_0805 0.3200 0.8050 90.0 F.Cu C14 100n c_0805 0.4700 0.5100 270.0 F.Cu C16 100n c_0805 -0.4600 1.2600 0.0 F.Cu C17 T22u/10V c_tant_B0.1000 0.2400 0.0 F.Cu C18 1u c_1206 -0.1250 1.0600 180.0 F.Cu C19 100n c_0805 -0.4500-0.8150 180.0 F.Cu Q1 IRLML0030SOT23GDS0.0950-0.6950 180.0 F.Cu U1 LP2951 SOG8 -0.4000-1.2100 90.0 F.Cu Michal Jahelka I agree. The package is what matters, the library that comes from is unknown to most people anyway. It is only a hint as to what to expect. The start of the library name doesn't really give you any hint at all. Perhaps some people aggregate all of the different Packages and Val combinations there are to roughly determine the number of reels they'll need to use on the machine. If no-one objects I'll commit the change for you. Best Regards, Brian. ___ 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] pcbnew export position file
Hi folks, This change looks great. I'm not sure if I ever announced it here, but here at Wayne and Layne, we developed a simple command line UI for creating files for our pick-and-place based on KiCad .pos files. http://www.wayneandlayne.com/blog/2014/09/21/kicad-converter-for-tm-240a-pick-and-place-machines/ Adam Wolf Cofounder and Engineer Wayne and Layne, LLC On Wed, Oct 29, 2014 at 7:47 AM, Brian Sidebotham brian.sidebot...@gmail.com wrote: On 29 October 2014 09:15, Michal Jahelka michal.jahe...@pavelek.cz wrote: Hello, I found small problem when generating position file. It was good before complete library name was used. It is shorted, and it is mainly impossible to understand which package has any footprint - there is mainly only part of library name. for example: # RefVal Package PosX PosYRot Side C5 1u Capacitor-sm_cap -0.1800-1.2100 270.0 F.Cu C8 100u/6.3VB Capacitor-sm_cap -0.1800-1.0300 180.0 F.Cu C9 100n Capacitor-sm_cap -0.1000 0.2150 180.0 F.Cu C12 100n Capacitor-sm_cap -0.0250 0.9550 0.0 F.Cu C13 100n Capacitor-sm_cap0.3200 0.8050 90.0 F.Cu C14 100n Capacitor-sm_cap0.4700 0.5100 270.0 F.Cu C16 100n Capacitor-sm_cap -0.4600 1.2600 0.0 F.Cu C17 T22u/10V Capacitor-sm_cap0.1000 0.2400 0.0 F.Cu C18 1u Capacitor-sm_cap -0.1250 1.0600 180.0 F.Cu C19 100n Capacitor-sm_cap -0.4500-0.8150 180.0 F.Cu Q1 IRLML0030libcms:SOT23GDS 0.0950-0.6950 180.0 F.Cu U1 LP2951 Vlastni-SM-IC:SO -0.4000-1.2100 90.0 F.Cu So after patch is visible only package, without library (I think that for machine component placing is library name not important). # RefVal Package PosX PosYRot Side C5 1u c_1206 -0.1800-1.2100 270.0 F.Cu C8 100u/6.3VB c_tant_B -0.1800-1.0300 180.0 F.Cu C9 100n c_0805 -0.1000 0.2150 180.0 F.Cu C12 100n c_0805 -0.0250 0.9550 0.0 F.Cu C13 100n c_0805 0.3200 0.8050 90.0 F.Cu C14 100n c_0805 0.4700 0.5100 270.0 F.Cu C16 100n c_0805 -0.4600 1.2600 0.0 F.Cu C17 T22u/10V c_tant_B0.1000 0.2400 0.0 F.Cu C18 1u c_1206 -0.1250 1.0600 180.0 F.Cu C19 100n c_0805 -0.4500-0.8150 180.0 F.Cu Q1 IRLML0030SOT23GDS0.0950-0.6950 180.0 F.Cu U1 LP2951 SOG8 -0.4000-1.2100 90.0 F.Cu Michal Jahelka I agree. The package is what matters, the library that comes from is unknown to most people anyway. It is only a hint as to what to expect. The start of the library name doesn't really give you any hint at all. Perhaps some people aggregate all of the different Packages and Val combinations there are to roughly determine the number of reels they'll need to use on the machine. If no-one objects I'll commit the change for you. Best Regards, Brian. ___ 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] new documentation format
On 10/25/2014 6:17 PM, Marco Ciampa wrote: On Sat, Oct 25, 2014 at 10:52:54AM -0400, Wayne Stambaugh wrote: Marco, Great work on the conversion analysis. I finally go around to testing this and I have to say that I prefer the asciidoc format better than the markdown and rst formats for plain text readability. Almost everyone does it but please consider that readability is not the most important factor. As I said many people use rest because of sphinx. Please consider that sphinx integrate a search javascript function into the html generated, although maybe not so important. My main issue with the rst formatting was the fact that odt2sphinx creating very long line which in some cases wrap more than once using a 100 character line width editor. This is a serious problem IMO. Looking at wrapped lines in a text editor makes my eyes bleed. I hope this is just the output formatting issue with odt2sphinx and not required by the rst format. Please don't underestimate the importance of plain text readability. If I have to struggle to figure out the file format, I will be less motivated to contribute to maintaining the documentation. My guess is that other potential contributers will feel the same way. That being said, rst would be tolerable if the formatting issues can be resolved. Are there features in rst that are not in asciidoc or markdown that are required to generate the kicad documentation? If so, then that tends to tip things in favor of rst. If not, then the less readable syntax would favor asciidoc. I also could not convert the asciidoc format to pdf using your example. I always get an error about dblatex failing even though I have it installed on my Debian partition. I use Ubuntu 14.04. Maybe Debian asciidoc or dblatex packages are bit older? 1. Please print the output error strings eventually augmenting verbosity. 2. try -L or --no-xmllint option, to disable xmllint check for sometimes xmmlint is too picky 3. try using asciidoctor to convert into xml first, exec a2x with -n or --dry-run to see the command line it execs to try to do it manually substituting ascidoc with asciidoctor TIA None of the section headers or table of contents were converted so there would obviously be some hand work involved. That's not a big deal for the cvpcb documentation but for all of the documentation there is a lot of work to do. Windows support is iffy. Even though MSYS2 has an asciidoc package, the optional bits to create pdfs is missing so that is an issue. I guess the next steps are: * Make the final decision on the format. ok * Pick a VCS and a host server. Obvious choices are bzr/launchpad and git/github. I am for git... * Convert all of the documentation over to asciidoc. I can do it... no problem. * Write CMake build configuration support to handle dependency checking, out building, translation file creation, and installation. I do not know cmake at all * Create initial repo and let the document fixing begin. ok Any volunteers? Count on me of course. ___ 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 documentation format
On Wed, Oct 29, 2014 at 10:21:55AM -0400, Wayne Stambaugh wrote: My main issue with the rst formatting was the fact that odt2sphinx creating very long line which in some cases wrap more than once using a 100 character line width editor. This is a serious problem IMO. Looking at wrapped lines in a text editor makes my eyes bleed. I hope No virtual autowrapping like in vim? bad editor then :D Just joking. Maybe a pipe thru fmt would help? -- 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] Rename instances of module to footprint for consistency
On Wed, Oct 08, 2014 at 02:37:40AM -0400, Mark Roszko wrote:
So from what I remember, Kicad used to call alot of pcb footprints as
modules. Sometimes it was module, other times footprint module
and now footprint. Footprint seems to have picked up in usage so
let's use it everywhere!
Right now new users just get confused and its a popular compliant. I
don't blame them, the inconsistency is annoying.
[...]
I see that in all this source the reference is on a module so I think
the programmer got tricked by this name and used it also for the message
strings, despite the source file name explicitely refers to footprints
and not modules.
Please apply this patch...
bzr diff
=== modified file 'pcbnew/autorouter/auto_place_footprints.cpp'
--- pcbnew/autorouter/auto_place_footprints.cpp 2014-10-06 01:18:24 +
+++ pcbnew/autorouter/auto_place_footprints.cpp 2014-10-29 15:54:50 +
@@ -278,7 +278,7 @@
while( ( Module = PickModule( this, DC ) ) != NULL )
{
// Display some info about activity, module placement can take a while:
-msg.Printf( _( Place module %d of %d ), cnt, moduleCount );
+msg.Printf( _( Place footprint %d of %d ), cnt, moduleCount );
SetStatusText( msg );
double initialOrient = Module-GetOrientation();
=== modified file 'pcbnew/autorouter/spread_footprints.cpp'
--- pcbnew/autorouter/spread_footprints.cpp 2014-03-05 17:57:13 +
+++ pcbnew/autorouter/spread_footprints.cpp 2014-10-29 15:52:07 +
@@ -174,7 +174,7 @@
if( aFootprintsOutsideBoardOnly !edgesExist )
{
DisplayError( this,
- _( Could not automatically place modules. No board
outlines detected. ) );
+ _( Could not automatically place footprints. No board
outlines detected. ) );
return;
}
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| 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] Bump wx for OS X to 3.0.2 (with an extra patch?)
On Oct 28, 2014, at 12:51 PM, Adam Wolf adamw...@feelslikeburning.com wrote: Hi folks, Does anyone object to bumping wx to 3.0.2 for OS X, and adding the webdiff patch so it'll work on OS X 10.10, released last week (the week before?) If I don't hear anything, I'll prep a patch for the docs and the osx_build_wx.sh and send it in. I tried to build 3.0.2 on 10.10 and it failed in some horrible way. Does your patch help that? I'm glad to test the patch, too. -a ___ 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] Bump wx for OS X to 3.0.2 (with an extra patch?)
Yes. The patch is here: https://trac.macports.org/raw-attachment/ticket/44524/patch-webview_webkit.mm.diff . I'll be sending in my bzr change in a minute. Adam Wolf Cofounder and Engineer, Wayne and Layne, LLC On Wed, Oct 29, 2014 at 12:47 PM, Andy Peters de...@latke.net wrote: On Oct 28, 2014, at 12:51 PM, Adam Wolf adamw...@feelslikeburning.com wrote: Hi folks, Does anyone object to bumping wx to 3.0.2 for OS X, and adding the webdiff patch so it'll work on OS X 10.10, released last week (the week before?) If I don't hear anything, I'll prep a patch for the docs and the osx_build_wx.sh and send it in. I tried to build 3.0.2 on 10.10 and it failed in some horrible way. Does your patch help that? I'm glad to test the patch, too. -a ___ 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] Bump wx for OS X to 3.0.2 (with an extra patch?)
Hi folks, Attached is a patch from the latest revision of KiCad to add a patch in the patches/ directory suitable for building wxwidgets 3 on OS X 10.10 (Yosemite). It does not add it to any build scripts in our tree per Bernhard. I used this as the commit message on my own branch. Added patch for wxwidgets-3.0.2 for Mac OSX 10.10 (Yosemite). The patch was taken from https://trac.macports.org/ticket/44524 for the upstream bug of http://trac.wxwidgets.org/ticket/16329.; Adam Wolf Cofounder and Engineer Wayne and Layne, LLC On Wed, Oct 29, 2014 at 1:10 PM, Adam Wolf adamw...@feelslikeburning.com wrote: Yes. The patch is here: https://trac.macports.org/raw-attachment/ticket/44524/patch-webview_webkit.mm.diff . I'll be sending in my bzr change in a minute. Adam Wolf Cofounder and Engineer, Wayne and Layne, LLC On Wed, Oct 29, 2014 at 12:47 PM, Andy Peters de...@latke.net wrote: On Oct 28, 2014, at 12:51 PM, Adam Wolf adamw...@feelslikeburning.com wrote: Hi folks, Does anyone object to bumping wx to 3.0.2 for OS X, and adding the webdiff patch so it'll work on OS X 10.10, released last week (the week before?) If I don't hear anything, I'll prep a patch for the docs and the osx_build_wx.sh and send it in. I tried to build 3.0.2 on 10.10 and it failed in some horrible way. Does your patch help that? I'm glad to test the patch, too. -a ___ 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 macosx_yosemite_wxwidgets_patch.patch Description: Binary data ___ 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] Rename instances of module to footprint for consistency
Another patch:
=== modified file 'pcbnew/class_pcb_layer_widget.cpp'
--- pcbnew/class_pcb_layer_widget.cpp 2014-09-14 15:34:37 +
+++ pcbnew/class_pcb_layer_widget.cpp 2014-10-29 22:52:43 +
@@ -73,8 +73,8 @@
RR( _( Anchors ), ANCHOR_VISIBLE, WHITE, _( Show
footprint and text origins as a cross ) ),
RR( _( Grid ),GRID_VISIBLE, WHITE, _( Show
the (x,y) grid dots ) ),
RR( _( No-Connects ), NO_CONNECTS_VISIBLE,UNSPECIFIED_COLOR, _(
Show a marker on pads which have no net connected ) ),
-RR( _( Modules Front ), MOD_FR_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprints that are on board's front) ),
-RR( _( Modules Back ),MOD_BK_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprints that are on board's back) ),
+RR( _( Footprints Front ), MOD_FR_VISIBLE, UNSPECIFIED_COLOR,
_( Show footprints that are on board's front) ),
+RR( _( Footprints Back ),MOD_BK_VISIBLE, UNSPECIFIED_COLOR,
_( Show footprints that are on board's back) ),
RR( _( Values ), MOD_VALUES_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprint's values) ),
RR( _( References ), MOD_REFERENCES_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprint's references) ),
};
=== modified file 'pcbnew/menubar_modedit.cpp'
--- pcbnew/menubar_modedit.cpp 2014-10-15 11:40:38 +
+++ pcbnew/menubar_modedit.cpp 2014-10-29 22:52:56 +
@@ -273,7 +273,7 @@
// Anchor
AddMenuItem( placeMenu, ID_MODEDIT_ANCHOR_TOOL,
_( Anchor ),
- _( Place footprint module reference anchor ),
+ _( Place footprint reference anchor ),
KiBitmap( anchor_xpm ) );
// Menu Help:
=== modified file 'pcbnew/muonde.cpp'
--- pcbnew/muonde.cpp 2014-08-24 07:05:07 +
+++ pcbnew/muonde.cpp 2014-10-29 22:52:53 +
@@ -1075,7 +1075,7 @@
if( pad == NULL )
{
-DisplayError( this, _( No pad for this module ) );
+DisplayError( this, _( No pad for this footprint ) );
return;
}
@@ -1083,7 +1083,7 @@
if( next_pad == NULL )
{
-DisplayError( this, _( Only one pad for this module ) );
+DisplayError( this, _( Only one pad for this footprint ) );
return;
}
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
++
| 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] [PATCH] Rename instances of module to footprint for consistency
On 29/10/2014 23:56, Marco Ciampa wrote:
Another patch:
=== modified file 'pcbnew/class_pcb_layer_widget.cpp'
--- pcbnew/class_pcb_layer_widget.cpp 2014-09-14 15:34:37 +
+++ pcbnew/class_pcb_layer_widget.cpp 2014-10-29 22:52:43 +
@@ -73,8 +73,8 @@
RR( _( Anchors ), ANCHOR_VISIBLE, WHITE, _( Show
footprint and text origins as a cross ) ),
RR( _( Grid ),GRID_VISIBLE, WHITE, _( Show the
(x,y) grid dots ) ),
RR( _( No-Connects ), NO_CONNECTS_VISIBLE,UNSPECIFIED_COLOR, _(
Show a marker on pads which have no net connected ) ),
-RR( _( Modules Front ), MOD_FR_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprints that are on board's front) ),
-RR( _( Modules Back ),MOD_BK_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprints that are on board's back) ),
+RR( _( Footprints Front ), MOD_FR_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprints that are on board's front) ),
+RR( _( Footprints Back ),MOD_BK_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprints that are on board's back) ),
RR( _( Values ), MOD_VALUES_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprint's values) ),
RR( _( References ), MOD_REFERENCES_VISIBLE, UNSPECIFIED_COLOR, _(
Show footprint's references) ),
};
Beware here, they are not footprint anymore when they are on the board,
have a value, a reference and so on... They are components.
Footprint is the right term for the standalone print a component will
drop on a PCB. You can name them so in the footprint library, in the
component propriety and so on... In the PCB editor, this object is a
Components and should be named so.
=== modified file 'pcbnew/menubar_modedit.cpp'
--- pcbnew/menubar_modedit.cpp 2014-10-15 11:40:38 +
+++ pcbnew/menubar_modedit.cpp 2014-10-29 22:52:56 +
@@ -273,7 +273,7 @@
// Anchor
AddMenuItem( placeMenu, ID_MODEDIT_ANCHOR_TOOL,
_( Anchor ),
- _( Place footprint module reference anchor ),
+ _( Place footprint reference anchor ),
KiBitmap( anchor_xpm ) );
// Menu Help:
=== modified file 'pcbnew/muonde.cpp'
--- pcbnew/muonde.cpp 2014-08-24 07:05:07 +
+++ pcbnew/muonde.cpp 2014-10-29 22:52:53 +
@@ -1075,7 +1075,7 @@
if( pad == NULL )
{
-DisplayError( this, _( No pad for this module ) );
+DisplayError( this, _( No pad for this footprint ) );
return;
}
@@ -1083,7 +1083,7 @@
if( next_pad == NULL )
{
-DisplayError( this, _( Only one pad for this module ) );
+DisplayError( this, _( Only one pad for this footprint ) );
return;
}
___
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
