I've been away from the coal face for so long. I've just been catching up
with the list and can't wait to compile the latest!
Good work to all who've been doing some amazing work recently!
Hopefully I'll be able to start contributing again soon. :)
Brian.
On 10 May 2017 at 10:41, Maciej
Hi Kasper,
Sorry - I've been out of action with regards to KiCad for a long while.
Just about getting back up to speed.
Is there any reason you can't use Template Field Names for this:
http://docs.kicad-pcb.org/stable/en/eeschema.html#options-of-the-schematic-editor
This allows you to specify
I would create the plugin as a separate project. That's really the
idea of plugins afterall. I wouldn't bother rolling much more than the
bare essential plugins into the KiCad source. This would be a great
example of how to externally develop a plugin.
Best Regards,
Brian.
On 10 March 2016 at
It's up here...
On 28 January 2016 at 01:08, Adam Wolf wrote:
> It probably won't last long, but if you get any users having issues today,
> before starting complicated troubleshooting, check to see if Github is back
> up.
>
> Adam Wolf
>
>
>
On 21 January 2016 at 13:42, Tomasz Wlostowski
wrote:
> Hi,
>
> This patch replaces boost::context with a small library called
> libcontext (derived from boost::context sources). It drops the
> dependency on boost for the cost of one additional header file and cpp
>
Excellent News! Welcome Chris! :D
On 7 January 2016 at 15:53, Duane Johnson wrote:
> Go Chris! And go Kicad!
>
> Thanks for all you devs are doing.
>
> Duane Johnson
>
> On Jan 7, 2016 8:47 AM, "Adam Wolf" wrote:
>>
>> Congrats!
>>
>> On
Instructions for translators are here:
https://github.com/KiCad/kicad-doc/blob/master/translation_instructions.adoc
Hopefully everything you need should be there.
Best Regards,
Brian.
On 21 December 2015 at 11:02, André S. wrote:
> Hi everyone!
>
> I'm planning
t; translation_instructions are made for a different installation...
>
> Regards,
> André
>
> may be right for the GUI translation, but in the documentation there is no
> makefile
>
>
> Am 21.12.2015 um 12:12 schrieb Brian Sidebotham:
>>
>>
As a packager, you get good control over what happens. Solving this
problem could be done with a batch file:
@ECHO OFF
IF "%KISYSMOD%"=="" SET KISYSMOD=%~dp0\..\share\kicad\modules
IF "%KISYS3DMOD%"=="" SET KISYS3DMOD=%~dp0\..\share\kicad\modules\packages3d
start kicad.exe
which fixes the
I haven't had a look at the patch, but I'm a fan of libcurl and use it
quite a lot - it's been great for implementing cloud services for me.
So I'm in favour of the switch!
Best Regards,
Brian.
On 3 December 2015 at 13:28, Kristian Nielsen wrote:
> Mark Roszko
Hi Mark,
SetProcessDpiAware (Now SetProcessDpiAwareness) can be overidden by
including a manifest that says the app is not DPI aware - and
wxWidgets with bitmap icons certainly isn't DPI aware - god knows why
they thought they were!
Anyway, I've attached a manifest file which may or may not help
Wayne, You've released the source tarball against the RC1 milestone.
I'd delete it from there and re-release it against the RC2 milestone.
Best Regards,
Brian.
On 9 November 2015 at 08:17, Nick Østergaard wrote:
> I just jumped directly to https://launchpad.net/kicad and
I've just killed KiCad-Winbuilder on launchpad (
https://launchpad.net/kicad-winbuilder ), but fear not!
Nick Østergaard is now maintaining the MSYS2/mingw-w64 version of
KiCad-Winbuilder on GitHub (
https://github.com/nickoe/KiCad-Winbuilder )
Thanks to Nick who's been working on the MSYS2
On 30 September 2015 at 21:19, Wayne Stambaugh wrote:
> I just committed a fix so at least the python plugins will get installed
> in share/kicad/scripting which seems to work properly on msys2/mingw64
> builds. I'll test it on Linux when I get a chance. I'm going to pass
On 29 September 2015 at 14:03, LordBlick <lordbl...@gmail.com> wrote:
> In response to a message written on 29.09.2015, 10:46, from Brian
> Sidebotham:
>>
>> For Windows, we can package the contents of
>> kicad-source/pcbnew/scripting/plugins into the bin/scripting/
.
Best Regards,
Brian.
On 18 September 2015 at 00:40, Cirilo Bernardo
<cirilo.berna...@gmail.com> wrote:
>
>
> On Fri, Sep 18, 2015 at 8:20 AM, Brian Sidebotham
> <brian.sidebot...@gmail.com> wrote:
>>
>> As mentioned in the bug report here
>> https:/
> first entry in the search stack when it's defined and it should be.
> User defined paths should *always* take precedence.
>
> >
> > On Fri, Sep 18, 2015 at 6:03 AM, Brian Sidebotham
> > <brian.sidebot...@gmail.com> wrote:
> >> GetExecutablePath() has a
As mentioned in the bug report here
https://bugs.launchpad.net/kicad/4.0/+bug/1496049 there's a problem
with paths on the Windows 4.0.0-RC1.
So far the paths that don't work:
(1) Searching for help files fails
(2) Default paths in the "Path configuration" dialog all point to
places in
.
Best Regards,
Brian.
On 15 September 2015 at 15:37, Brian Sidebotham
<brian.sidebot...@gmail.com> wrote:
> On 15 September 2015 at 15:03, Wayne Stambaugh <stambau...@gmail.com> wrote:
>>
>>
>> On 9/14/2015 1:08 AM, Joseph Chen wrote:
>>> On
I filed a bug report for the Windows version so people using RC1 may
trip over the bug report.
https://bugs.launchpad.net/kicad/+bug/1496049
Best Regards,
Brian.
On 15 September 2015 at 17:04, Brian Sidebotham
<brian.sidebot...@gmail.com> wrote:
> As a PS - I think RC2 looks like
Dan, you may run http://www.dependencywalker.com/ to see if there's
anything funny going on with your system in particular. Perhaps some
runtime component is being picked up outside of the KiCad install
that's causing a bit of instability.
Post the results if you're not used to the output so we
September 2015 at 17:01, Brian Sidebotham
<brian.sidebot...@gmail.com> wrote:
> Actually the help documentation is broken on Windows too in the RC.
>
> The help is at C:\Program Files\KiCad\share\doc\kicad\help\en\kicad.pdf
>
> The searched paths are like this:
>
> P
On 15 September 2015 at 15:03, Wayne Stambaugh wrote:
>
>
> On 9/14/2015 1:08 AM, Joseph Chen wrote:
>> On 09/13/2015 01:36 PM, Wayne Stambaugh wrote:
>> The failure above is inevitable, because the running pcbnew is looking
>> for file name "pcbnew.pdf", while the actual
My humble suggestion is to just create the RC1 branch now because I've
been through all of those bugs, and they're all either incomplete or
not repeatable for me. In which case we need more information in order
to be able to fix them.
In order to get more information, it's better to have a larger
On 4 September 2015 at 08:43, Jon Neal wrote:
> I'm a stickler for code that uses the same conventions when possible.
> m_drawatzero should be camelCase instead of all lowercase. :)
I'll change that, no worries.
> +switch( m_style & 0xFF )
> I'm curious as to what
To match functionality of the Legacy canvas I propose we extend the
GAL ORIGIN_VIEWITEM class to allow us to add an axis origin marker
when using the Footprint Editor. I'm sure even while in the stable
feature-lock this is okay to commit, but an ack will be good before I
go ahead.
Also, Orson,
Just wanted to say - Thank-you so much everyone who's contributed to
the new site because it looks great! Static makes so much sense. It's
a great effort and I can't wait for that to become live - it should
sort out all of the confusion users have with where KiCAD is at and
has a well-focussed
Hi Martin,
Thanks for the report!
Could you please copy this into an issue on the kicad-doc github repo
please? https://github.com/ciampix/kicad-doc/issues
Best Regards,
Brian.
On 21 June 2015 at 00:00, Martin d'Allens martin.dall...@gmail.com wrote:
Hi all,
It seems that po4a-updatepo
On 31 May 2015 at 23:25, Cirilo Bernardo cirilo.berna...@gmail.com wrote:
Hi Brian,
I suggest we leave the scaling etc until after the stable release; it's a
nightmare.
Historically the scaling allowed users to reuse similar models if they
didn't already
have a suitable model, for
On 1 June 2015 at 10:46, Brian Sidebotham brian.sidebot...@gmail.com
wrote:
On 31 May 2015 at 23:25, Cirilo Bernardo cirilo.berna...@gmail.com
wrote:
Hi Brian,
I suggest we leave the scaling etc until after the stable release; it's
a
nightmare.
Historically the scaling allowed users
Hey guys,
I only just got round to using 3D with KiCad. Mainly because I
normally use Solid Edge for 3D solid modelling, and I could never be
bothered to use FreeCAD at home because, well, it's not Solid Edge!
Anyway, I just compiled FreeCAD on my Mint box and I have to say it
works really well
On 31 May 2015 at 21:19, Brian Sidebotham brian.sidebot...@gmail.com wrote:
On 31 May 2015 at 21:16, Nick Østergaard oe.n...@gmail.com wrote:
Den 31/05/2015 22.11 skrev Brian Sidebotham brian.sidebot...@gmail.com:
Hey guys,
I only just got round to using 3D with KiCad. Mainly because I
On 31 May 2015 at 21:38, easyw ea...@katamail.com wrote:
Hi Brian,
just a question for 3d modeling...
Do you use to export 3d vrml plain pcb plus modules to Solid Edge?
Do you convert them in some way to manipulate the board in SE? (e.g. step or
iges)
thank you
Maurice
Hi Maurice,
I've
On 31 May 2015 at 21:16, Nick Østergaard oe.n...@gmail.com wrote:
Den 31/05/2015 22.11 skrev Brian Sidebotham brian.sidebot...@gmail.com:
Hey guys,
I only just got round to using 3D with KiCad. Mainly because I
normally use Solid Edge for 3D solid modelling, and I could never be
bothered
The CMake documentation build system is now pretty much complete. I
have a pull request nearly ready for dealing with images in FOP where
we need to blanket them with scale-down-to-fit so that they fit on
the page properly. Currently you could consider the FOP build to be
broken because images
On 27 May 2015 at 09:42, Brian Sidebotham brian.sidebot...@gmail.com wrote:
The CMake documentation build system is now pretty much complete. I
have a pull request nearly ready for dealing with images in FOP where
we need to blanket them with scale-down-to-fit so that they fit on
the page
On 18 April 2015 at 17:36, Wayne Stambaugh stambau...@gmail.com wrote:
Brian,
How did you get po4a to build? I tried everything I could think of (I'm
no Perl expert so take that with the appropriate grain of salt) but no
luck. I did manage to get the some of the dependencies to build using
dblatex tool
chain seutp on Windows is a bit of a pain!
Best Regards,
Brian.
On 14 April 2015 at 00:52, Nick Østergaard oe.n...@gmail.com wrote:
Great.
Den 13/04/2015 22.57 skrev Brian Sidebotham brian.sidebot...@gmail.com:
I sync'd with Marco's repo so that's now reflected in my repo.
I
I just tested with VRML 1 and VRML 2 and stuff has appeared not to
break, so I just committed this change.
I opted for the boost::shared_ptr as we're not yet C++11 and there is
quite a bit of standard container work going on.
Best Regards,
Brian.
On 11 April 2015 at 00:04, Brian Sidebotham
13:48 GMT+02:00 Nick Østergaard oe.n...@gmail.com:
So now is a good time to remove the src/markdown and src/rest and move
src/asciidoc to src?
If so, I can do that now, such that you can pull those changes.
2015-04-11 13:43 GMT+02:00 Brian Sidebotham brian.sidebot...@gmail.com:
On 11 April
On 11 April 2015 at 12:11, Nick Østergaard oe.n...@gmail.com wrote:
Great. I just looked briefly on the cmake setup. It seems to me like
you intend to include a CMakeLists.txt inside each doc dir with the
only change being the name or path of the root adoc file. Would it not
mere more sense to
On 11 April 2015 at 12:32, Brian Sidebotham brian.sidebot...@gmail.com wrote:
On 11 April 2015 at 12:11, Nick Østergaard oe.n...@gmail.com wrote:
Great. I just looked briefly on the cmake setup. It seems to me like
you intend to include a CMakeLists.txt inside each doc dir with the
only change
Hi Guys,
Could someone who has access to both vrml1 and vrml2 models please
test the attached patch which uses a smart pointer rather than
S3D_MESH* to get rid of some coverity issues and feedback whether it
makes your computer explode, or carry on working normally?
Alternatively, could someone
On 8 April 2015 at 14:08, Wayne Stambaugh stambau...@gmail.com wrote:
On 4/8/2015 4:51 AM, Brian Sidebotham wrote:
On 4 April 2015 at 16:23, Wayne Stambaugh stambau...@gmail.com wrote:
Now that we are in feature freeze, I need an update on where we stand as
far as the asciidoc documentation
On 4 April 2015 at 16:23, Wayne Stambaugh stambau...@gmail.com wrote:
Now that we are in feature freeze, I need an update on where we stand as
far as the asciidoc documentation conversion process is concerned. I
did a git pull yesterday and now `make html` fails for a missing po
directory. I
On 31 March 2015 at 21:53, Wayne Stambaugh stambau...@gmail.com wrote:
On 3/31/2015 4:03 PM, Simon Richter wrote:
Hi,
On 31.03.2015 13:29, Brian Sidebotham wrote:
delete m_model;
should really be:
delete m_model;
m_model = NULL;
Other functions (namely read_DEF) make
I've just been going through the Coverity thing during a break at work
and tagged a few things ready to fix at home. The second I noticed is
because we use delete on a member variable pointer without
re-assignment.
I think it would be good policy to say unless the scope of the pointer
variable is
On 12 March 2015 at 20:53, Wayne Stambaugh stambau...@gmail.com wrote:
On 3/12/2015 2:10 PM, Nick Østergaard wrote:
But now to my real comment on this: I don't think we should do this. I
might seem like a great concept at first, but rember the limited man
power, and not to forget it will not
On 3 March 2015 at 13:44, Tomasz Wlostowski tomasz.wlostow...@cern.ch wrote:
Dear all,
We've just merged the new features of the Interactive Router to the
product branch:
- Routing differential pairs (in pushshove mode too).
- Tuning trace length.
- Tuning differential pair length and skew.
On 22 February 2015 at 03:00, Mark Roszko mark.ros...@gmail.com wrote:
Fixes some cases where n-1 bytes was used as a size but snprintf
protects against that internally. Also some hardcoded constant sizes
changed to sizeof()
And made a case where sprintf was used into snprintf as the path
On 18 February 2015 at 14:26, Miguel Ángel Ajo majop...@redhat.com wrote:
Hmm, this crashes in the fedora nightly build during pcbnew startup, I need
to investigate why.
On 16 February 2015 at 17:44, Wayne Stambaugh stambau...@gmail.com wrote:
On 2/16/2015 11:44 AM, Brian Sidebotham wrote:
On 16 February 2015 at 15:42, Brian Sidebotham
brian.sidebot...@gmail.com wrote:
On 16 February 2015 at 14:17, Wayne Stambaugh stambau...@gmail.com wrote:
Brian,
How
On 16 February 2015 at 15:42, Brian Sidebotham
brian.sidebot...@gmail.com wrote:
On 16 February 2015 at 14:17, Wayne Stambaugh stambau...@gmail.com wrote:
Brian,
How are you telling the kicad configuration where wxPython build is
located during you winbuilder configuration? Would Garth's
On 15 February 2015 at 20:11, Wayne Stambaugh stambau...@gmail.com wrote:
Mark Roszko was kind enough to set up a Coverity scan for KiCad at
https://scan.coverity.com/projects/3606?tab=analysis_settings. Thank
you Mark. I would at least like my lead developers to sign up and have
Mark give
On 16 February 2015 at 13:18, Wayne Stambaugh stambau...@gmail.com wrote:
On 2/16/2015 7:15 AM, Brian Sidebotham wrote:
On 15 February 2015 at 20:11, Wayne Stambaugh stambau...@gmail.com wrote:
Mark Roszko was kind enough to set up a Coverity scan for KiCad at
https://scan.coverity.com
On 16 February 2015 at 14:17, Wayne Stambaugh stambau...@gmail.com wrote:
Brian,
How are you telling the kicad configuration where wxPython build is
located during you winbuilder configuration? Would Garth's solution
below solve your problem? The only issue I see with Garth's solution is
On 13 February 2015 at 22:36, Marco Ciampa ciam...@libero.it wrote:
On Fri, Feb 13, 2015 at 08:52:28PM +, Brian Sidebotham wrote:
Hi Marco,
To bring more people in on the documentation effort, I'd like to
create a GitHub repo under the KiCad organisation so that people know
it's
On 14 February 2015 at 19:25, Nick Østergaard oe.n...@gmail.com wrote:
2015-02-14 17:43 GMT+01:00 Fat-Zer fatz...@gmail.com:
2015-02-13 14:17 GMT+03:00 Brian Sidebotham brian.sidebot...@gmail.com:
Hi Guys,
I was going to start the CMake stuff soon for the asciidoc
documentation, but I'd like
On 14 February 2015 at 16:43, Fat-Zer fatz...@gmail.com wrote:
2015-02-13 14:17 GMT+03:00 Brian Sidebotham brian.sidebot...@gmail.com:
Hi Guys,
I was going to start the CMake stuff soon for the asciidoc
documentation, but I'd like to know what toolchains people want to
support. I'll start
This commit broke KiCad-Winbuilder because of the same reason as
Garth. wxPython is not installed in the compilation environment. It
gets installed by the build system. We will be installing wxPython
locally to the KiCad installation on Windows, there's no other way to
distribute it.
I haven't
Hi Guys,
I was going to start the CMake stuff soon for the asciidoc
documentation, but I'd like to know what toolchains people want to
support. I'll start a Github repo and we can get stuck in. I'll try
and base it on Fat-Zer's starting point where possible.
HTML can be done via:
asciidoc
On 9 February 2015 at 11:01, Marco Ciampa ciam...@libero.it wrote:
On Mon, Feb 09, 2015 at 10:09:04AM +, Brian Sidebotham wrote:
On 7 February 2015 at 00:09, Marco Ciampa ciam...@libero.it wrote:
On Sat, Feb 07, 2015 at 09:56:36AM +1100, Cirilo Bernardo wrote:
What a nuisance that po4a
On 7 February 2015 at 00:09, Marco Ciampa ciam...@libero.it wrote:
On Sat, Feb 07, 2015 at 09:56:36AM +1100, Cirilo Bernardo wrote:
What a nuisance that po4a does not recognize include. Maybe we should
submit a patch to po4a?
That would be the best thing to do.
Otherwise my own preference
On 9 February 2015 at 12:46, Brian Sidebotham
brian.sidebot...@gmail.com wrote:
I didn't see an /official/ announcement so I wanted to just put it out
there clearly, that AsciiDoc is the chosen format for KiCad's
documentation (user manuals and the like).
More information about asciidoc can
I didn't see an /official/ announcement so I wanted to just put it out
there clearly, that AsciiDoc is the chosen format for KiCad's
documentation (user manuals and the like).
More information about asciidoc can be is available from the asciidoc
homepage: http://www.methods.co.nz/asciidoc/
..and
On 5 February 2015 at 10:03, Fat-Zer fatz...@gmail.com wrote:
2015-02-04 19:52 GMT+03:00 Wayne Stambaugh stambau...@gmail.com:
CMake should be used as the build configuration tool which is used to
verify all of the required tools are installed on the system and
automatically generate the
On 5 February 2015 at 10:54, Miguel Ángel Ajo majop...@redhat.com wrote:
https://github.com/Fat-Zer/kicad-doc/tree/cmake
It’s in a separate branch :-)
Miguel Ángel Ajo
Ah, I was missing something! lol.
Thanks Miguel...
Best Regards,
Brian.
___
On 15 January 2015 at 10:20, Miguel Ángel Ajo majop...@redhat.com wrote:
Yesterday I wrote a proposal for discussion here:
http://pads.kicad-pcb.org/p/kicad-scripting-layer (please write your name
for your color
using the top right icon, so what you write can be identified to you).
I tried
On 6 January 2015 at 14:08, Wayne Stambaugh stambau...@gmail.com wrote:
A bug report and patch has been submitted to add a .gitignore file to
the repo. I think it's a good idea to make life easier for our
developers using git so I'm OK with committing the patch. Before I do
so, I want to
On 8 January 2015 at 13:44, Wayne Stambaugh stambau...@gmail.com wrote:
Fully defined paths can be used in the fp-lib-table if that is your
preference. Environment variable substitution is optional. You are
free to use any environment variable you want. KISYSMOD is merely the
variable name
Hi Guys,
Sorry I've been AWOL for so long. The new year has been extremely
hectic for me. I hope everyone had a good new year.
I've tried to fit FOSDEM into my schedule, but it would be flying out
early Saturday morning and flying back late Sunday and then back to
work on Monday which is not
Here's my musing on the subject ( which we'll have to visit after a
stable release ):
Firstly, the version control system - any distributed system is fine
really for me. bzr is not dead - it works. I find git a pain on the
command line, but it's as powerful as it is confusing to use - it's
just
On 4 November 2014 15:30, Milan Horák stran...@tiscali.cz wrote:
Hi,
IMHO the NSIS installer is already available as I am using it to make
Windows packages on http://kicad.nosoftware.cz
Or am I missing something here?
Milan
No not at all. Sounds like Jean-Pierre has been keeping it much
On 4 November 2014 16:57, Milan Horák stran...@tiscali.cz wrote:
Hi,
I am using the NSIS script originating from the sources. Before compiling I
just change date and revision and run it.
How can I find out if it includes Python scripting support?
Milan
I downloaded BZR5228 install and
Hi Wayne,
It was on tonights list (for me that's around 6~7hrs from now). If
you've got time, by all means put it through now, that would be great.
Best Regards,
Brian.
On 31 October 2014 13:59, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/29/2014 8:47 AM, Brian Sidebotham wrote
.
Thanks,
Wayne
On 10/31/2014 10:25 AM, Brian Sidebotham wrote:
Hi Wayne,
It was on tonights list (for me that's around 6~7hrs from now). If
you've got time, by all means put it through now, that would be great.
Best Regards,
Brian.
On 31 October 2014 13:59, Wayne Stambaugh stambau
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
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
On 24 October 2014 16:31, Wayne Stambaugh stambau...@verizon.net wrote:
Brian,
I restored the custom FindPythonLibs.cmake file. I found an issue with
the stock version when configuring on MSYS2. I made some minor changes
to it which should make it more robust when looking for mingw python
On 25 October 2014 17:22, Wayne Stambaugh stambau...@verizon.net wrote:
I've been working on packaging KiCad on MSYS2 with mingw64 and mingw32.
I have everything building including the full Python scripting.
Unfortunately our current install paths when building with mingw don't
match up with
On 25 October 2014 15:52, Wayne Stambaugh stambau...@verizon.net 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. I also could not
On 24 October 2014 21:17, Nick Østergaard oe.n...@gmail.com wrote:
Hello
Some background info:
I was allowed by Ajo to play around on the Jenkins build server [1] to
add automatic building of the doxygen documatation for the purpose of
having it online and always up to date. I have dumped
On 25 October 2014 22:29, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/25/2014 4:59 PM, Brian Sidebotham wrote:
I expect the other two PATH_SUFFIXES supplied to that find_path() are
wrong by the way, I've not removed them in case they are actually
correct, but generally the only
On 23 October 2014 00:28, Wayne Stambaugh stambau...@verizon.net wrote:
Adam,
I just committed the fix with my original patch along with a fix for the
missing files generated by make_lexer() in r5216. Hopefully, this
solves the problem.
Thanks,
Wayne
Excellent work Wayne!
The duplicate
On 21 October 2014 23:25, Wayne Stambaugh stambau...@verizon.net wrote:
3.0.0 sounds good to me.
Wayne
I'm good with the triplet, and any number sounds fine to me! :D
Best Regards,
Brian.
___
Mailing list: https://launchpad.net/~kicad-developers
On 21 October 2014 04:37, Andrew Zonenberg azonenb...@drawersteak.com wrote:
Hi all,
While browsing recent commits I saw some updates to authors.txt which
prompted me to take a look at the file and noticed two minor issues.
1) maintener (line 15) should be spelled maintainer
2) Neither
On 21 October 2014 22:58, Marco Ciampa ciam...@libero.it wrote:
Hello,
talking about the project of switching the KiCad documentation to an
easier to maintain and translate format, after some experiments, (I know,
I am slow ... I am not a real programmer) I have produced something
to check.
On 22 October 2014 11:11, Nick Østergaard oe.n...@gmail.com wrote:
Hi
I also think that Cirilo Bernardo should not be forgotten, he made
great contributions especially in regard to the 3D tools.
Nick
Oh, so sorry - that was mentioned in the original email!!
Will be there in a minute...
On 22 October 2014 11:22, Brian Sidebotham brian.sidebot...@gmail.com wrote:
On 22 October 2014 11:11, Nick Østergaard oe.n...@gmail.com wrote:
Hi
I also think that Cirilo Bernardo should not be forgotten, he made
great contributions especially in regard to the 3D tools.
Nick
Oh, so
On 22 October 2014 14:01, Tim Hutt tdh...@gmail.com wrote:
Hi,
I'm trying to do some kicad development on windows. I initially downloaded
built it with kicad-winbuilder which went without a hitch. Kicad runs fine.
However, if I perform a null-rebuild (i.e. I don't change anything and just
-- Forwarded message --
From: Brian Sidebotham brian.sidebot...@gmail.com
Date: 22 Oct 2014 22:50
Subject: Re: [Kicad-developers] new documentation format
To: Marco Ciampa ciam...@libero.it
Cc:
On 22 Oct 2014 22:02, Marco Ciampa ciam...@libero.it wrote:
On Wed, Oct 22, 2014
Kicad-Winbuilder was broke a few commits ago by removing some custom python
finding cmake module. I've not had the time to replace it with another
working version. I was hoping to replace it before it was removed.
Hopefully it should be fixed soon!
Best Regards,
Brian.
On 22 Oct 2014 21:30, Tim
The re-designed layout us much more appealing. It looks much better than
the previous layout.
On 22 Oct 2014 19:14, Mark Roszko mark.ros...@gmail.com wrote:
Actually I planned to do this:
Rename the netlist dialog to Netlist Options
Add a Generate Netlist menu option which does the immediate
On 22 Oct 2014 23:03, Brian Sidebotham brian.sidebot...@gmail.com wrote:
The re-designed layout us much more appealing. It looks much better than
the previous layout.
On 22 Oct 2014 19:14, Mark Roszko mark.ros...@gmail.com wrote:
Actually I planned to do this:
Rename the netlist dialog
On 22 Oct 2014 23:00, Marco Ciampa ciam...@libero.it wrote:
Sorry I forgot to show directly the .po files. See by yourself:
https://github.com/ciampix/kicad-doc/blob/master/src/asciidoc/cvpcb/po/cvpcb.pot
You will see that there are many big paragraphs
Yeah, that po file looks good.
Thank-you for the update Andrew.
When I updated the file I asked for any missing people to come forward
and I'd add them straight to the list. I'll do it tonight and sync the
list on http://www/kicad-pcb.org too.
Best Regards,
Brian.
On 21 October 2014 04:37, Andrew Zonenberg
On 17 October 2014 14:10, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/17/2014 8:44 AM, jp charras wrote:
Le 17/10/2014 14:22, Mark Roszko a écrit :
Alright, I've played around. It appears there is many CAM/gerber
software that cannot handle G75 arcs that are full 360 degrees. I
tested
On 16 October 2014 17:30, Garth Corral gcor...@abode.com wrote:
Hi, guys.
After the recent eeschema dialog commit, my build of wxFormBuilder won’t
allow me to do anything with dialog_eeschema_options_base.fbp. It will open
it just fine, but after that I can’t use the UI; clicking on
Hi All,
I've just updated the AUTHORS.txt wtih some recent, and some
not-so-recent contributors to the list.
Some notes about the list:
(1) It's not in any order what-so-ever.
(2) It's not complete!
With regard to 2, please do not feel offended if you feel as though
you've made a contribution
a look at the dialog to see if
they're experiencing the same problem.
Best Regards,
Brian Sidebotham.
On 16 October 2014 17:56, Garth Corral gcor...@abode.com wrote:
Thanks for the quick reply.
Yes, already tried a sample of files; 1.11, 1.12 and 1.13 files open and
seemingly work just fine
1 - 100 of 415 matches
Mail list logo