This is what I see (update as you go) in other open source projects (openstack
related ones in my case).
Sometimes they do a major sweep for example, removing @author references and
stuff
like that, as authorship is already tracked by git.
Miguel Ángel Ajo
On Wednesday, 7 de January de
Dear all,
First of all thanks for all the good work, I recently switched to KiCAD
because of the added scripting support which I needed for scripted button
placement on a pcb.
To make it easier to get my work done I made some convenience functions and
classes wrapping the swig api to have a
On 1/7/2015 8:33 AM, Tomasz Wlostowski wrote:
On 07.01.2015 11:36, PTT wrote:
Dear all,
First of all thanks for all the good work, I recently switched to KiCAD
because of the added scripting support which I needed for scripted button
placement on a pcb.
Hi Piers,
Very nice work,
On 07.01.2015 11:36, PTT wrote:
Dear all,
First of all thanks for all the good work, I recently switched to KiCAD
because of the added scripting support which I needed for scripted button
placement on a pcb.
Hi Piers,
Very nice work, thanks! IMHO C++ APIs SWIGgged directly to python are
On 1/7/2015 5:34 AM, Blair Bonnett wrote:
On 7 January 2015 at 20:03, Cirilo Bernardo cirilo.berna...@gmail.com
mailto:cirilo.berna...@gmail.com wrote:
Do not replace the older dates with a newer date. Instead, as files
are modified
(and only as they're modified), add '2015'. So Copyright
Hey all, I've been using Kicad for several years now and I've finally
gotten around to pulling the source and building it myself. The latest
developments look really exciting. Anyway, I think I've found a few bugs in
the IDF export code. I currently have version 2014-12-16 BZR 5324. When
storing
Hi folks,
As you may know, it's harder than it seems to set an environment variable
on a bundle in OS X as a user.
I have a patch here for the OS X bundle that sets KISYSMOD to
/Library/Application Support/kicad/modules
Please let me know if there are any questions or comments.
Thanks!
Adam
Nice John, very interesting job, It could be very cool if you could visualize
pull requests, etc..
Very good point about the unregistered API limit.
The unregistered API limit is 60 req/hour. That should be enough
for a normal user (used for listing the repos) If that’s found to be
On Wed, Jan 7, 2015 at 11:35 PM, Miguel Ángel Ajo majop...@redhat.com
wrote:
Whoops :-), %s/LordBlick/PTT/g
Miguel Ángel Ajo
On Wednesday, 7 de January de 2015 at 23:31, LordBlick wrote:
In response to a message written on 07.01.2015, 23:07, from Miguel Ángel
Ajo:
Hi Lordblick, sorry, I
Hi,
Is the policy for braced case indentation as follows?
case SOMETHING:
{
int i = 0;
break;
}
This seems to be the case for tidying-up commits like r5288, but the
uncrustify.cfg rules call for:
case SOMETHING:
{
int i = 0;
break;
}
If this is in fact
On Wed, 2015-01-07 at 23:38 +0100, Miguel Ángel Ajo wrote:
Hi Jean Pierre, just an idea for your wizard work:
https://api.github.com/orgs/KiCad/repos
You could save the need to work with the HTML viewer and pagination
problems
using the above API endpoint, all the KiCad project
On 1/7/2015 3:44 PM, LordBlick wrote:
In response to a message written on 07.01.2015, 20:48, from Adam Wolf:
I have to stop responding to this thread, but it's official Python policy
that spaces are preferred over tabs, and has been for a while.
In response to a message written on 07.01.2015, 21:45, from Miguel Ángel Ajo:
PEP8 strongly recommends spaces: (I was about to link the same Adam did).
The reasoning is tabs is that change width from editor to editor or from
configuration to configuration. Spaces are always the same.
If
This patch fixes the issue reported by Chris: IDF component models are not
loaded when they are under a path specified by KISYS3DMOD.
- Cirilo
=== modified file 'pcbnew/exporters/export_idf.cpp'
--- pcbnew/exporters/export_idf.cpp 2015-01-05 21:51:47 +
+++ pcbnew/exporters/export_idf.cpp
I have to stop responding to this thread, but it's official Python policy
that spaces are preferred over tabs, and has been for a while.
https://www.python.org/dev/peps/pep-0008/#tabs-or-spaces
In other news, is anyone else from the KiCad community going to Pycon this
year?
Adam Wolf
Cofounder
On Thu, Jan 8, 2015 at 1:22 AM, Chris Anon chris.a...@gmail.com wrote:
Hey all, I've been using Kicad for several years now and I've finally
gotten around to pulling the source and building it myself. The latest
developments look really exciting. Anyway, I think I've found a few bugs in
the
On Thu, Jan 8, 2015 at 1:22 AM, Chris Anon chris.a...@gmail.com wrote:
Hey all, I've been using Kicad for several years now and I've finally
gotten around to pulling the source and building it myself. The latest
developments look really exciting. Anyway, I think I've found a few bugs in
the
In response to a message written on 07.01.2015, 21:54, from Wayne Stambaugh:
On 1/7/2015 3:44 PM, LordBlick wrote:
In response to a message written on 07.01.2015, 20:48, from Adam Wolf:
I have to stop responding to this thread, but it's official Python policy
that spaces are preferred over
PEP8 strongly recommends spaces:
(I was about to link the same Adam did).
The reasoning is tabs is that change width from editor to editor
or from configuration to configuration. Spaces are always the same.
Python syntax heavily relies on indenting for blocks, and that can result
in problems if
In response to a message written on 07.01.2015, 20:48, from Adam Wolf:
I have to stop responding to this thread, but it's official Python policy
that spaces are preferred over tabs, and has been for a while.
https://www.python.org/dev/peps/pep-0008/#tabs-or-spaces
OK, I appreciate that, but my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Miguel,
On 01/07/2015 11:07 PM, Miguel Ángel Ajo wrote:
[snip]
2) If C++ implementation changes, the available python scripts
break.
There might be another point that could be taken under consideration.
Currently, if the C++ implementation
Hi Lordblick, sorry, I was on a run before, and I actually didn’t look
into your code, but stepped into tabs vs spaces (thinking it was a discussion
about in-KiCad code).
Your python extra layer is very nice, actually, at the start I was very
reluctant
on adding another layer and reusing the C++
In response to a message written on 07.01.2015, 23:07, from Miguel Ángel Ajo:
Hi Lordblick, sorry, I was on a run before, and I actually didn’t look
into your code, but stepped into tabs vs spaces (thinking it was a discussion
about in-KiCad code).
Your python extra layer is very nice,
Whoops :-), %s/LordBlick/PTT/g
Miguel Ángel Ajo
On Wednesday, 7 de January de 2015 at 23:31, LordBlick wrote:
In response to a message written on 07.01.2015, 23:07, from Miguel Ángel Ajo:
Hi Lordblick, sorry, I was on a run before, and I actually didn’t look
into your code, but stepped
Hi Jean Pierre, just an idea for your wizard work:
https://api.github.com/orgs/KiCad/repos
You could save the need to work with the HTML viewer and pagination problems
using the above API endpoint, all the KiCad project repositories are listed
into it
in json format.
Best regards,
Miguel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
That is exactly what I was trying to say with my 2nd point :) and
I believe it’s something very valuable.
Sorry, I misread your statement. Now, all I can do is to admit that I
share your view ;)
Regards,
Orson
-BEGIN PGP SIGNATURE-
PTT,
I am looking to add plot support. It is something I use often.
What do you think of add this project to an external repository to let
people contribute and when you release stable/good version we ask KiCad
folks to integrate those releases.
Cheers,
2015-01-07 16:42 GMT-02:00 PTT
Adam,
I committed your patch in the product branch r5358.
Thanks,
Wayne
On 1/6/2015 12:45 PM, Adam Wolf wrote:
Hi everyone,
Attached is a patch that quiets the noname.pro http://noname.pro error
in the situation that the last history item isn't loadable, as well as
on first load of kicad
Thanks, Wayne!
On Wed, Jan 7, 2015 at 12:13 PM, Wayne Stambaugh stambau...@gmail.com
wrote:
Adam,
I committed your patch in the product branch r5358.
Thanks,
Wayne
On 1/6/2015 12:45 PM, Adam Wolf wrote:
Hi everyone,
Attached is a patch that quiets the noname.pro http://noname.pro
In response to a message written on 07.01.2015, 11:36, from PTT:
Please have a look and see if it is useful to somehow incorporate it in the main
branch.
pcbnew_easy.py
https://gist.github.com/pierstitus/7be2d9923da502c88ff1
Very good work for adding it to pcbnew/scripting/examples/, but it
In rev 5359, I added a specific layers manager to the footprint editor,
which allows user to select the technical layer which is used when
adding a new graphic text or outline to the current footprint.
The layer manager was already available in GAL mode, but it was the same
as the board editor,
On Wed, Jan 07, 2015 at 08:13:42PM +0100, jp charras wrote:
There is certainly room for enhancements, so I am waiting for your tests
and ideas.
Yay applause :D
Will test, I just need to do a board with new components next week. The
layer bar is almost mandatory when doing not-trivial pads,
I do intend to update and improve the parts that I use, though that won't
cover all use cases so I hope other people will extend it too.
Thanks for the remarks about formatting, I totally agree, that's updated
now.
On Wed, Jan 7, 2015 at 3:08 PM, Wayne Stambaugh stambau...@gmail.com
wrote:
On
Hi folks,
Good work!
I dunno, LordBlick, it looks pretty Pythonic to me!
Also, I do not think
dict(map(lambda lname: lname, layers_tuple.index(lname), layers_tuple))
is clearer than using a dictionary called layer_dict :)
Adam Wolf
Cofounder and Engineer
WL
On Wed, Jan 7, 2015 at 12:25
In response to a message written on 07.01.2015, 19:29, from Adam Wolf:
Hi folks,
Good work!
I dunno, LordBlick, it looks pretty Pythonic to me!
Also, I do not think
dict(map(lambda lname: lname, layers_tuple.index(lname), layers_tuple))
is clearer than using a dictionary called layer_dict
I committed this patch in the product branch r5357. I did fine some
trailing white space that I removed before I committed the patch. Thank
you for your contribution to KiCad.
Cheers,
Wayne
On 1/5/2015 9:34 PM, Adam Wolf wrote:
Hi,
There was a minor typo spotted by Bob in the patch. I
36 matches
Mail list logo
