Just wanted to say I love this and I'm sure it will improve visibility of
the KiCad project and lower the barrier of entry for new developers.
Some questions:
- Are there any plans to use the Gitlab CI system in the future?
- Will the KiCad libraries also be migrated or is the plan to keep
This is a notice to everyone on this mailing list that the bug tracker
on Launchpad is currently frozen. Please do not make any changes to the
Launchpad bug report system until further notice. Unfortunately it
appears that I cannot disable the bug tracker until the migration script
completes
Congratulations guys: KiCon, The Linux Foundation, KiCad Services
Corporation... The project is definitely changing gears, and it's very
exciting to see. Keep rocking!
Javier
On Tue, Dec 3, 2019 at 3:29 PM Wayne Stambaugh wrote:
> I wanted keep everyone up to date with my employment situation
Congrats from the commercial side of things!
Ben
On Tue, Dec 3, 2019 at 8:52 AM Wayne Stambaugh wrote:
> Hi Seth,
>
> On 12/3/19 9:39 AM, Seth Hillbrand wrote:
> > On 2019-12-03 06:28, Wayne Stambaugh wrote:
> >> I wanted keep everyone up to date with my employment situation since my
> >>
Please disregard - I had a URL error. Sorry for the noise.
Steve
On 12/3/19 1:44 PM, Steven A. Falco wrote:
> I am trying to update the Fedora nightly builder for the new gitlab
> repositories.
>
> I'm running into a problem accessing the kicad-doc repo over https.
>
> Here is what
I am trying to update the Fedora nightly builder for the new gitlab
repositories.
I'm running into a problem accessing the kicad-doc repo over https.
Here is what I'm seeing:
saf$ git clone https://gitlab.com/kicad/services/kicad-doc/kicad-doc
Cloning into 'kicad-doc'...
remote: HTTP Basic:
OK, my stuff is pushed
> On 3 Dec 2019, at 17:44, Jeff Young wrote:
>
> He he… I had sort of the same idea, only I’m building it lazily at runtime.
> But I think your idea would be even better.
>
> Since I’ve already made the changes to have STROKE_FONT use const pointers to
> the data
He he… I had sort of the same idea, only I’m building it lazily at runtime.
But I think your idea would be even better.
Since I’ve already made the changes to have STROKE_FONT use const pointers to
the data structures, let me merge in first and then you can move it to
compile-time.
Cheers,
On 12/3/19 7:27 AM, Jeff Young wrote:
Hi Seth,
Trying to keep track of lengths is going to be ugly. I did re-write
the bounding-box calc (which saves a bunch), and re-mapped the
initialisation to use stack storage until all the points had been
allocated (which saves a little).
But it’s
Yeah, the 10.14 build works on 10.15.
It probably makes sense to rename them now, and have the un-suffixed
one be the one that works on 10.14-10.15 and the other one be labeled
and work on 10.12-10.13. Pretty soon, we can limit that just to
10.13, but for now we're supporting both.
What should
Adam/all,
Is the 10.14 installer also to be used for 10.15? Right now there is no
mention on the website about the 10.15 support (and actually says only
10.12-10.14 are supported).
-Ian
___
Mailing list: https://launchpad.net/~kicad-developers
Post to
Hi Simon,
I’m already doing that — it helps a little but less than I thought it would.
Cheers,
Jeff.
PS: I’m trying out another version which pre-flights the number of strokes, but
not the number of points in each stroke.
> On 3 Dec 2019, at 15:42, Simon Richter wrote:
>
> Hi,
>
> On Tue,
Hi,
On Tue, Dec 03, 2019 at 03:27:26PM +, Jeff Young wrote:
> Changing the glyph back to a deque (and leaving the strokes vectors) would
> probably alleviate much of the performance hit — but I’m not sure if it would
> bring back the memory issues or not.
Would it make sense to build it
Hi Seth,
Trying to keep track of lengths is going to be ugly. I did re-write the
bounding-box calc (which saves a bunch), and re-mapped the initialisation to
use stack storage until all the points had been allocated (which saves a
little).
But it’s still too slow (especially when you try to
Excellent news!
> On 3 Dec 2019, at 14:39, Seth Hillbrand wrote:
>
> On 2019-12-03 06:28, Wayne Stambaugh wrote:
>> I wanted keep everyone up to date with my employment situation since my
>> termination from WIT. I am excited to announce that I have joined the
>> KiCad Services Corporation[1]
Hi Seth,
On 12/3/19 9:39 AM, Seth Hillbrand wrote:
> On 2019-12-03 06:28, Wayne Stambaugh wrote:
>> I wanted keep everyone up to date with my employment situation since my
>> termination from WIT. I am excited to announce that I have joined the
>> KiCad Services Corporation[1] which will allow
On 2019-12-03 06:28, Wayne Stambaugh wrote:
I wanted keep everyone up to date with my employment situation since my
termination from WIT. I am excited to announce that I have joined the
KiCad Services Corporation[1] which will allow me to earn income while
still working on KiCad as much as
I wanted keep everyone up to date with my employment situation since my
termination from WIT. I am excited to announce that I have joined the
KiCad Services Corporation[1] which will allow me to earn income while
still working on KiCad as much as possible. You can see my interview
video[2] with
The other multi-word tags in the components are "pcb-calculator" and
"3d-viewer" (and we also have "feature-request"). I was using a hyphen
because using the longer words "symboleditor" didn't look as good as saying
"symbol-editor." I did the hyphen on the fp-editor one for symmetry.
I will use
On 02.12.19 22:25, Tomasz Wlostowski wrote:
> On 02/12/2019 21:51, Kliment (Future Bits) wrote:
>> The video looks very much like to me like the trace is following a
>> voronoi cell boundary with cells coming out from each obstacle outline
>> vertex. But what do I know? Maybe I'm just imagining
On 03/12/2019 02:43, Mark Roszko wrote:
> Just throw in a linear regression somewhere and we can say KiCad has
> AI based routing ;)
>
Our GAL does a lot of matrix multiplications. We could perhaps advertise
KiCad as the first EDA tool with a Deep Learning Techniques-based
rendering engine ;-).
Hi,
Here's the merge request: https://gitlab.com/kicad/code/kicad/merge_requests/5
Cheers
On Mon, Dec 2, 2019 at 4:03 PM Seth Hillbrand wrote:
>
> On 2019-12-02 04:30, Jonatan Liljedahl wrote:
> > ADDED new option to set selection highlight thickness.
> > Also change selection shadow width
22 matches
Mail list logo
