Just a heads up for all of our documentation developers. I've deleted
the kicad-doc branch from KiCad project on github and sent an invitation
to Marco so he can transfer the master copy of kicad-doc to the KiCad
project. Please do not send any pull requests to Marco's kicad-doc repo
until after
Everyday things get a little bit better. Good work team!
On Aug 21, 2015 8:02 AM, Wayne Stambaugh stambau...@gmail.com wrote:
Just a heads up for all of our documentation developers. I've deleted
the kicad-doc branch from KiCad project on github and sent an invitation
to Marco so he can
Well this gives me some hope. :) We'll table this issue until after the
stable release. Maybe wxFormBuilder development will start up again.
If not we will have to make a decision. Thanks everyone for the input.
Cheers,
Wayne
On 8/17/2015 5:02 PM, Chris Pavlina wrote:
Here, have another
Looks good. Just one minor issue, as I was looking through it and
noticed a lot of spelling and grammar errors. Please run a spell
checker to fix the spelling errors. Would some of our native English
speaking developers please check the grammar. How is the static site
code maintained? Is
On 8/19/2015 4:03 PM, jp charras wrote:
Le 19/08/2015 21:12, Wayne Stambaugh a écrit :
On 8/19/2015 12:10 PM, Lorenzo Marcantonio wrote:
On Wed, 19 Aug 2015 17:47:56 +0200,
Wayne Stambaugh wrote:
This may be window manager related. I get no assertion on windows.
I've seen this before and
We're sneaking up on it. I prefer the slow steady progression. Yes,
most folks would love to everything done right now. All that does is
burn people out so you have these big changes in a short period of time
and then nothing for long periods of time.
On 8/21/2015 9:03 AM, Adam Wolf wrote:
There has been a good bit of grumbling recently about the MRU path
situation in KiCad. The previous behavior was broken during the Kiway
development. There have been some patches but none of them solve the
underlying problem that is there is MRU path code scattered all over the
place which makes
Currently everything is on github
https://github.com/nickoe/kicad-website
Yea there are spelling errors. Anyone can feel free to do the
corrections and submit a pull request. Github lets anyone do text file
changes via the web interface where it automates it all (branching,
editing and pull
Just some suggestions:
- Why do you put a blog section? I believe the news section should be the
main part of the site. Just look the sites of projects such as OpenWRT,
LibreOffice and others. I think the news section should have the most
visibility and get updated often, so viewers could see the
On 21.08.2015 23:15, Mário Luzeiro wrote:
Hi Tomasz, all,
after remove boost, I also noted that you remove ExportTo functions.
Are there any way (already implemented) that I can export to a
ClipperLib::Paths ?
Hi Mario,
SHAPE_POLY_SET internally uses ClipperLib::Paths. Please don't use
I think the news section should have the most visibility and get updated often
Because someone would have to update it often. If someone wants to
step up and commit to update it like every 2 weeks, then fine. Most
of LibreOffice news are just events and the fact they have hundreds of
devs working
I would opt for a config file. I can't decide between a single
MRU for each EDA_BASE_FRAME or one for each frame
in PGM_BASE; no doubt with the different ways people work
some would prefer one or the other.
While on the topic of paths and config files, a handful of users
have complained in the
On 8/21/2015 6:12 PM, Cirilo Bernardo wrote:
I would opt for a config file. I can't decide between a single
MRU for each EDA_BASE_FRAME or one for each frame
in PGM_BASE; no doubt with the different ways people work
some would prefer one or the other.
Thanks for the input. I'll probably
In response to a message written on 03.03.2015, 01:08, from nats:
Thanks a lot for this information.
I managed to get it working, after some discussion on IRC I copied the
LSET code
inside the plugin.
It'll be removed when kicad python new api will be ready.
Here is the link for reference:
The KiCad documentation has been transferred to the KiCad project on
github so we should be able to resume normal doc development activities.
I created a Documentation team on github and made Marco the maintainer
so either he or I should be able to help you if you previously had push
privileges
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
16 matches
Mail list logo
