Given the current state of sanctity of even the comment layer names (for
which I can't find a good reason different than "Dick doesn't like it",
since copper layers are renameable anyway so most probably in my tree
I'll allow it), since most of the work for adding layers is in place
(the big thing
I wrote a patch for cmake against the latest git version, and sent it
to the cmake list. If I can fix this upstream for Ubuntu, Fedora et
al, I should do it there. This affects many, many more projects than
Kicad.
Adam Wolf
Wayne and Layne, LLC
On Fri, Apr 12, 2013 at 4:01 PM, Wayne Stambaugh
On 4/12/2013 4:17 PM, Adam Wolf wrote:
Hi Wayne,
It looks like CMake doesn't extract the library version number from
the interpreter--it just finds the highest python version libraries
installed. Someone wrote up a new FindPythonLibs.cmake that does look
at the running interpreter, and it was r
Hi Wayne,
It looks like CMake doesn't extract the library version number from
the interpreter--it just finds the highest python version libraries
installed. Someone wrote up a new FindPythonLibs.cmake that does look
at the running interpreter, and it was rejected in 2011. This may be
part of why
Investigating the FindPythonInterp/Libs issue:
the if(PythonLibs_FIND_VERSION)block is evaluating false (on my
machine), which makes the Python version list simply be all the Python
3 versions, then the Python 2 versions, then the Python 1 versions.
The rest of the file just finds the first set of
Most people who are paid to write python do not ever use
site-packages/dist-packages. Most people who are paid to write python
don't use distribution-specific packages for their dependencies.
Using tools like pip and virtualenv, dependency wrangling is basically
non-existent, and different applic
On 04/11/2013 02:35 PM, Lorenzo Marcantonio wrote:
> The templates have nothing to do with the code base... in fact they
> *depends* on the component library...
>
Not a bad idea, maybe we'd get more templates that way.
I used a template yesterday and it came with its own library, so your statem
When doing Python a-mingw-us, and also looking at what the python package
maintainers are
doing for modern linux, I came away disappointed, both with python raw, and
python on
linux as far as packaging is concerned and where they park libraries.
The problem with linux is that nobody wants to co
On 04/12/2013 11:29 AM, Kaspar Bumke wrote:
> I am finding it useful to have edge cuts drawings in modules as well. I have
> just been
> editing the files with a text-editor to change the layer and haven't
> encountered any
> issues. Would be good to (re?) enable selecting the Edge.Cuts layer in
On 4/12/2013 2:59 PM, Adam Wolf wrote:
Hi Wayne,
In order to get a "legal" Debian/Ubuntu package, you have to do a
bunch of trickery anyway, so I'm not concerned about this at all from
a packaging point of view. (For example, you need to run pyversions
to find out which python versions are arou
On 04/12/2013 12:02 PM, Karl Schmidt wrote:
> I've used a system that stored the colors in the board file and it caused
> =>LOTS<= of problems. At
> the very least, you want a way to easily override with a user preference. (
> It is good to be able to
> reset colors anyway ).
>
> For a default
I speak too soon. It isn't just Ubuntu. Fedora now has it in its
bugtracker as well.
https://bugzilla.redhat.com/show_bug.cgi?id=876118
Adam Wolf
Wayne and Layne, LLC
On Fri, Apr 12, 2013 at 1:59 PM, Adam Wolf
wrote:
> Hi Wayne,
>
> In order to get a "legal" Debian/Ubuntu package, you have to
Hi Wayne,
In order to get a "legal" Debian/Ubuntu package, you have to do a
bunch of trickery anyway, so I'm not concerned about this at all from
a packaging point of view. (For example, you need to run pyversions
to find out which python versions are around, and then iterate over
that, creating
On 4/12/2013 8:28 AM, Adam Wolf wrote:
As part of setting up the build server, I've been taking a harder look
at the Ubuntu packages.
CMake isn't detecting the right Python libs on some systems, including
Ubuntu 12.10. I'm not sure if the issue is in CMake, or Ubuntu, or
Python, or whatever els
On Fri, Apr 12, 2013 at 12:02:16PM -0500, Karl Schmidt wrote:
> For a default color pallet - tradition (and what is on several other
> systems) goes back to when we used red and blue tape - Red for
> Top_Copper and blue for Bottom_copper. (white(or light gray for
> silk and black for holes is also
On Fri, Apr 12, 2013 at 05:29:41PM +0100, Kaspar Bumke wrote:
> I am finding it useful to have edge cuts drawings in modules as well. I
> have just been editing the files with a text-editor to change the layer and
> haven't encountered any issues. Would be good to (re?) enable selecting the
> Edge.
I've used a system that stored the colors in the board file and it caused =>LOTS<= of problems. At
the very least, you want a way to easily override with a user preference. ( It is good to be able to
reset colors anyway ).
For a default color pallet - tradition (and what is on several other sys
I am finding it useful to have edge cuts drawings in modules as well. I
have just been editing the files with a text-editor to change the layer and
haven't encountered any issues. Would be good to (re?) enable selecting the
Edge.Cuts layer in the module editor.
On 17 December 2012 15:30, Younes M
On 04/12/2013 02:26 PM, Adam Wolf wrote:
CERN folks, I'd be glad to talk about #7 on your roadmap and see if
there's anything I/Wayne and Layne can do to help the situation.
Hi Adam,
This is great news!
The proposal we discussed with the main devs some time ago is to first
turn Kicad apps i
On Fri, Apr 12, 2013 at 08:17:50AM -0500, Dick Hollenbeck wrote:
> Doesn't matter. This is a land mine, and you have been warned.
Sorry but I don't know what evil could come from allowing the user to
rename the ECO1 layer to something more useful. Since you can rename
copper layers there is no re
On Fri, Apr 12, 2013 at 08:34:04AM -0500, Dick Hollenbeck wrote:
> Clarification, a paraphrase of something I wrote a week or so ago, which is a
> metaphor of
> only moderate quality, is this:
Too much complicate as a metaphore for my english :D I'd like to
shorten it as 'it's implementation depe
On 04/12/2013 12:28 AM, Lorenzo Marcantonio wrote:
> On Thu, Apr 11, 2013 at 04:11:51PM -0500, Dick Hollenbeck wrote:
>
>> No, I don't agree, since it is behind an interface and only accessors use it.
>
> My question could be rephrased as: there is a need to put colours in the board
> interface?
On 4/12/2013 8:52 AM, Dick Hollenbeck wrote:
My question could be rephrased as: there is a need to put colours in the board
interface?
If we do, please add a switch to disable it to fall back to my preferred
color settings. I don't want the color scheme for every board I open
from other user
On 12 April 2013 11:19, Javier Serrano wrote:
> On Fri, Apr 12, 2013 at 11:42 AM, Brian Sidebotham <
> brian.sidebot...@gmail.com> wrote:
>
>> It's really nice that you've put so much effort into explaining where you
>> are coming from and what you are prepared to do for KiCad. Thank-you for
>> ta
On 12 April 2013 13:52, Dick Hollenbeck wrote:
>
> >> My question could be rephrased as: there is a need to put colours in
> the board
> >> interface?
> >
> > If we do, please add a switch to disable it to fall back to my preferred
> > color settings. I don't want the color scheme for every boar
On 04/11/2013 09:49 AM, Lorenzo Marcantonio wrote:
> On Thu, Apr 11, 2013 at 09:45:52AM -0500, Dick Hollenbeck wrote:
>> Layer naming is fine as is. If someone commits a change to layer
>> naming without first getting agreement from me, then I will revoke his
>> commit privileges.
>
> We're not t
On 04/12/2013 12:28 AM, Lorenzo Marcantonio wrote:
> On Thu, Apr 11, 2013 at 04:11:51PM -0500, Dick Hollenbeck wrote:
>
>> No, I don't agree, since it is behind an interface and only accessors use it.
>
> My question could be rephrased as: there is a need to put colours in the board
> interface?
On 04/12/2013 12:17 AM, Lorenzo Marcantonio wrote:
> On Thu, Apr 11, 2013 at 04:17:15PM -0400, Wayne Stambaugh wrote:
>
>> This isn't a bad thing unless the pointer to g_colorSettings changes.
>> It hides the fact the color settings in Pcbnew are a global variable (it
>> seems to me that they shou
>> My question could be rephrased as: there is a need to put colours in the
>> board
>> interface?
>
> If we do, please add a switch to disable it to fall back to my preferred
> color settings. I don't want the color scheme for every board I open
> from other users to look different.
How mu
On 04/12/2013 02:23 PM, Wayne Stambaugh wrote:
On 4/12/2013 1:28 AM, Lorenzo Marcantonio wrote:
On Thu, Apr 11, 2013 at 04:11:51PM -0500, Dick Hollenbeck wrote:
No, I don't agree, since it is behind an interface and only accessors
use it.
My question could be rephrased as: there is a need to
As part of setting up the build server, I've been taking a harder look
at the Ubuntu packages.
CMake isn't detecting the right Python libs on some systems, including
Ubuntu 12.10. I'm not sure if the issue is in CMake, or Ubuntu, or
Python, or whatever else, but there's a simple enough workaround
I created a GAL PPA for Ubuntu. It's located at
https://code.launchpad.net/~adamwolf/+archive/kicad-gal-testing-daily,
and I have included instructions for switching to it or reverting
back if you don't like the package. It works the same as my other
PPAs.
Every night, it checks to see if there
On 4/12/2013 1:28 AM, Lorenzo Marcantonio wrote:
On Thu, Apr 11, 2013 at 04:11:51PM -0500, Dick Hollenbeck wrote:
No, I don't agree, since it is behind an interface and only accessors use it.
My question could be rephrased as: there is a need to put colours in the board
interface?
If we do,
On 4/12/2013 1:17 AM, Lorenzo Marcantonio wrote:
On Thu, Apr 11, 2013 at 04:17:15PM -0400, Wayne Stambaugh wrote:
This isn't a bad thing unless the pointer to g_colorSettings changes.
It hides the fact the color settings in Pcbnew are a global variable (it
seems to me that they should be a memb
On Fri, Apr 12, 2013 at 11:46:01AM +0200, jp charras wrote:
> Do you mean show user name + original name in layer manager ?
No, not in the layer manager bar, in the layer setup dialog, where you
rename the stuff. I used the wrong terminology.
> filenames were using the user layer name or the tra
On Fri, Apr 12, 2013 at 11:42 AM, Brian Sidebotham <
brian.sidebot...@gmail.com> wrote:
> It's really nice that you've put so much effort into explaining where you
> are coming from and what you are prepared to do for KiCad. Thank-you for
> taking the time to put the email together and letting us
Le 12/04/2013 08:44, Lorenzo Marcantonio a écrit :
After long meditation my plan is this:
First idea (really good but has issues)
- Internal and names do not change (I myself am tired of
these renames)
- Default layer names for a board are the the internal ones
- In the layer setup the use
Javier,
Thanks a lot for leading this from CERN,
I think this can only be good for KiCad.
Also thanks to Maciej and Tomasz for working on the technical side.
Miguel Angel Ajo
http://www.nbee.es (http://www.nbee.es/)
+34911407752
skype: ajoajoajo
On Friday, 12 de April de
Hi Javier,
Thank-you for your email, it's very exciting news for KiCad.
I have already got projects underway using the CERN Open Hardware Licence.
That is a great initiative!
It's really nice that you've put so much effort into explaining where you
are coming from and what you are prepared to do
> Tests will continue soon on Intel and older Ati hardware.
Worst performance of all as has been the case previously. PCBnew alternate
renderer works fine. Great work!
Renderer (glxinfo):
OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on ATI RV370
OpenGL version str
40 matches
Mail list logo
