On 2019-11-23 05:46, Jonatan Liljedahl wrote:
Thanks Seth,
I'm on Mac only (my linux box hasn't been powered on since 5 years or
so). The code I touched should not look different depending on
platform. I guess any difference would rather be in how colors are
presented (considering the #ifdef
On 2019-11-26 13:54, Franck Jullien wrote:
Hi,
Here attached you'll find a patch to correct issue 1849376 on
launchpad.
When a component is placed, action addNeededJunctions is now triggered.
If some of you have some spare time, I also have two branches with
patches you can review and/or test
On 2019-11-26 14:40, Eeli Kaikkonen wrote:
ti 26. marrask. 2019 klo 22.23 Seth Hillbrand (s...@kipro-pcb.com)
kirjoitti:
We need to start with the API definition and file format changes. The
API definition should include end points and returns. The file format
changes should include the fil
On 26/11/2019 20:46, Wayne Stambaugh wrote:
>
>>
>
> It was a joke in the same way that "Never trust the autorouter" is a
> joke. And like most good jokes, there is an uncomfortable truth about
> it.
Indeed ;-) (says the author of the aforementioned joke...)
It's a pun on a quote on the desig
ti 26. marrask. 2019 klo 22.23 Seth Hillbrand (s...@kipro-pcb.com)
kirjoitti:
>
> We need to start with the API definition and file format changes. The
> API definition should include end points and returns. The file format
> changes should include the files and specific configuration lines
> ne
Hi,
Here attached you'll find a patch to correct issue 1849376 on launchpad.
When a component is placed, action addNeededJunctions is now triggered.
If some of you have some spare time, I also have two branches with
patches you can review and/or test. The first allows the hierarchy
navigator to s
I do like fp-editor and sym-editor better. Note that for consistency with
the other multiword tags for GitLab, I will use a hyphen.
-Ian
On Tue, 26 Nov 2019, 8:07 p.m. Jeff Young, wrote:
> I would go with either historic (modedit and libedit) or current
> (fp_editor and symbol_editor).
>
> Mixi
On 2019-11-26 12:41, Jeff Young wrote:
OK, I’ve enabled 2FA. Do I need to do something to get added back to
the project? (When I go to members, all I see are the bot, Seth and
Wayne.)
Cheers,
Jeff.
Hi Jeff-
Wayne and the bot have permissions for the entire project. I'm there
while sorting
FWIW, in the code footprint is often abbreviated as fp, but symbol is rarely
abbreviated.
> On 26 Nov 2019, at 20:45, Ian McInerney wrote:
>
> I do like fp-editor and sym-editor better. Note that for consistency with the
> other multiword tags for GitLab, I will use a hyphen.
>
> -Ian
>
> On
OK, I’ve enabled 2FA. Do I need to do something to get added back to the
project? (When I go to members, all I see are the bot, Seth and Wayne.)
Cheers,
Jeff.
> On 26 Nov 2019, at 19:36, Wayne Stambaugh wrote:
>
> While wearing my official project leader hat, I'm not going to force
> anyone
I would go with either historic (modedit and libedit) or current (fp_editor and
symbol_editor).
Mixing the two would be particularly obscure.
Cheers,
Jeff.
> On 26 Nov 2019, at 19:40, Wayne Stambaugh wrote:
>
>
>
> On 11/26/19 2:20 PM, Ian McInerney wrote:
>> I would like to introduce two n
On 11/26/19 1:31 PM, jp charras wrote:
> Le 26/11/2019 à 18:45, Seth Hillbrand a écrit :
>> On 2019-11-26 09:43, Andy Peters wrote:
>>
>>> On Nov 26, 2019, at 10:41 AM, Seth Hillbrand wrote:
>>>
>>> On 2019-11-26 09:05, Tomasz Wlostowski wrote:
>>> On 22/11/2019 17:42, Rene Pöschl wrote:
>>> I w
On 11/26/19 2:20 PM, Ian McInerney wrote:
> I would like to introduce two new official tags on the bug tracker to
> track issues relating to the symbol and footprint editors. Currently we
> are tracking these under the eeschema and pcbnew tags respectively, but
> those are growing quite large (p
Perfect. Thanks Adam!
On 11/26/19 2:30 PM, Adam Wolf wrote:
> Not that I see. The macOS builds are uploading to S3 right now, should
> be finished within a few minutes.
>
> Adam
>
> On Tue, Nov 26, 2019 at 1:15 PM Wayne Stambaugh wrote:
>>
>> Is there any reason for me to postpone the release
While wearing my official project leader hat, I'm not going to force
anyone to use 2FA but I suggest you do. If you are unwilling to use
2FA, pleasing enable commit notifications for the main repo master and
5.1 branches. I'm figuring if you get a commit notification in your
name that you did not
Not that I see. The macOS builds are uploading to S3 right now, should
be finished within a few minutes.
Adam
On Tue, Nov 26, 2019 at 1:15 PM Wayne Stambaugh wrote:
>
> Is there any reason for me to postpone the release announcement I was
> planning for tomorrow? It doesn't sound like it.
>
> O
I would like to introduce two new official tags on the bug tracker to track
issues relating to the symbol and footprint editors. Currently we are
tracking these under the eeschema and pcbnew tags respectively, but those
are growing quite large (pcbnew has over 500). I think tracking these two
tools
On 11/25/19 10:33 PM, Seth Hillbrand wrote:
> On 2019-11-25 13:28, Seth Hillbrand wrote:
>
>> On 11/25/19 1:01 PM, Michael Geselbracht wrote:
>>> That's me. Someone from Gitlab just contacted me. I totally missed
>>> this mailing.
>>> I have replied that I was not aware that my private group name
Is there any reason for me to postpone the release announcement I was
planning for tomorrow? It doesn't sound like it.
On 11/25/19 9:02 PM, Adam Wolf wrote:
> Andy, thank you so much for this. I normally run through the releases
> but I am quite behind on some work and you definitely prevented t
Le 26/11/2019 à 18:45, Seth Hillbrand a écrit :
> On 2019-11-26 09:43, Andy Peters wrote:
>
>> On Nov 26, 2019, at 10:41 AM, Seth Hillbrand wrote:
>>
>> On 2019-11-26 09:05, Tomasz Wlostowski wrote:
>> On 22/11/2019 17:42, Rene Pöschl wrote:
>> I would assume this is referencing version 6 of eagl
> On Nov 26, 2019, at 10:43 AM, Seth Hillbrand wrote:
>
> On 2019-11-26 08:47, Andy Peters wrote:
>
>>> On Nov 25, 2019, at 7:02 PM, Adam Wolf
>>> wrote:
>>> Andy, thank you so much for this. I normally run through the releases but
>>> I am quite behind on some work and you definitely prev
On 2019-11-26 09:43, Andy Peters wrote:
On Nov 26, 2019, at 10:41 AM, Seth Hillbrand
wrote:
On 2019-11-26 09:05, Tomasz Wlostowski wrote:
On 22/11/2019 17:42, Rene Pöschl wrote:
I would assume this is referencing version 6 of eagle. The current
versions of eagle are actually something that ca
On 2019-11-26 08:47, Andy Peters wrote:
On Nov 25, 2019, at 7:02 PM, Adam Wolf
wrote:
Andy, thank you so much for this. I normally run through the releases
but I am quite behind on some work and you definitely prevented the
macOS release from holding everything up :)
I'll trigger builds
> On Nov 26, 2019, at 10:41 AM, Seth Hillbrand wrote:
>
> On 2019-11-26 09:05, Tomasz Wlostowski wrote:
>> On 22/11/2019 17:42, Rene Pöschl wrote:
>>> I would assume this is referencing version 6 of eagle. The current
>>> versions of eagle are actually something that can (in some aspects) be
>>
On 2019-11-26 09:05, Tomasz Wlostowski wrote:
On 22/11/2019 17:42, Rene Pöschl wrote:
I would assume this is referencing version 6 of eagle. The current
versions of eagle are actually something that can (in some aspects) be
used as a good example. I would therefore assume that this sentence is
On 22/11/2019 17:42, Rene Pöschl wrote:
>
> I would assume this is referencing version 6 of eagle. The current
> versions of eagle are actually something that can (in some aspects) be
> used as a good example. I would therefore assume that this sentence is
> simply out of date and could be removed
I think the differences expressed are about problems in communication, not
differences in actual opinions. I agree with myself (obviously), with what
Andrew said and with Ian. We are just talking past each other, about
different things.
Me said (meant): the content manager should be generic enough
We should not limit the end points available to users to be only the KiCad
systems we decide, and also should not constrain plugins to be open source.
Doing this would constrain independent companies from developing plugins to
interface KiCad with their systems if they so choose (for instance, if a
API definition and file formats are second step. We need to agree on
supported use cases, high level data flows, systems pieces involved.
Thing with public infra is that it's easy to move it to private infra but
not the other way around. So it's best to design as much of the system as
possible to
On 2019-11-25 17:46, Andrew Lutsenko wrote:
Hi Seth,
Yes, I planned to write up my design in google doc and open it to
comments. I think that works best for public discussion, even though it
requires having a google account.
Design I'm thinking about requires 0 custom backend work. It will
> I assume git merges will still go through SSH and not require 2FA either
way?
Yes, this just protects the account from third party remote compromise.
On Tue, Nov 26, 2019 at 8:13 AM Jeff Young wrote:
> Was there a resolution on the 2FA question? (I used to have to use it for
> Adobe’s VPN an
Was there a resolution on the 2FA question? (I used to have to use it for
Adobe’s VPN and hated it, but it is what it is.)
I assume git merges will still go through SSH and not require 2FA either way?
Cheers,
Jeff.
___
Mailing list: https://launchpad.
Hi,
How should I proceed with this patch? I think that regardless of
future features, it would make sense to either just apply this patch
so at least the traces for the second y-scale have a different visual
style, or to add a section in the preferences for setting default
solid/dashed and line wi
HI Eeli,
I've seen that thread earlier and reread it again.
Some of your ideas have merit but I think built-in content manager should:
1. Be at least somewhat coupled to KiCad needs and not be super generic. We
are not building apt-get repository here that has to handle arbitrarily
complex packag
Ok, thanks for the update.
Le mar. 26 nov. 2019 à 13:26, Maciej Suminski
a écrit :
>
> We have not migrated to Gitlab yet, so the issues in
> orsonmmz/kicad-bug-tracker is just a test of the bug tracker migration
> script.
> For the moment, please continue to use Launchpad. We will announce the
>
We have not migrated to Gitlab yet, so the issues in
orsonmmz/kicad-bug-tracker is just a test of the bug tracker migration
script.
For the moment, please continue to use Launchpad. We will announce the
migration date (hopefully soon). The official group will be available
under https://gitlab.com/k
Thanks. I did search here: https://gitlab.com/groups/kicad/-/issues
Not the same GitLab account.
Which one should we use ?
Franck.
Le mar. 26 nov. 2019 à 12:57, Maciej Suminski
a écrit :
>
> Hi Franck,
>
> It is here: https://gitlab.com/orsonmmz/kicad-bug-tracker/issues/11175
> The easiest way t
Hi Franck,
It is here: https://gitlab.com/orsonmmz/kicad-bug-tracker/issues/11175
The easiest way to find a Launchpad bug report in Gitlab is to type the
Launchpad bug id in the search box.
Cheers,
Orson
On 11/26/19 9:14 AM, Franck Jullien wrote:
> Hi,
>
> I can't find this issue on GitLab:
>
ti 26. marrask. 2019 klo 11.27 Nick Østergaard (oe.n...@gmail.com)
kirjoitti:
> I don't know if you use freecad, if you do you probably used the addon
> manager. It is quite helpful in installing python plugins.
>
> It is probably worth reviewing how it works conceptually.
>
Yes, I know about it.
OK, I refreshed my memory. I have a group in github (not gitlab):
https://github.com/kc-plugin-publishers. You can check out there what I
have written. There are three things: the manager script (plugin), example
dummy plugins to be installed, and the description files (.plugininfo
files). Now when
I know, but I thought all issues have been moved.
Sorry for the noise.
Franck.
Le mar. 26 nov. 2019 à 10:40, Ian McInerney a écrit :
>
> We have not officially migrated to GitLab yet, until we announce otherwise
> the current platforms (Launchpad for bug reports/code, GitHub for
> libraries/d
We have not officially migrated to GitLab yet, until we announce otherwise
the current platforms (Launchpad for bug reports/code, GitHub for
libraries/docs/translations) should be used. An announcement about the
transition will be made before it happens.
-Ian
On Tue, Nov 26, 2019 at 8:14 AM Franc
I don't know if you use freecad, if you do you probably used the addon
manager. It is quite helpful in installing python plugins.
It is probably worth reviewing how it works conceptually.
tir. 26. nov. 2019 09.24 skrev Eeli Kaikkonen :
> I'm in a hurry right now, so I just give few points. You c
I'm in a hurry right now, so I just give few points. You can find some
discussions in the forum (I'll find them later). What I learned when I did
some coding is this:
- Ideal content manager is a separate backend and frontend and reusable for
other projects, too.
- It's really general purpose and
That's good to know.
For minimal implementation it will not be required but it can be used for
telemetry, user ratings and things like that.
I'll talk about it more in the doc.
I'm assuming it's easy to expose some service wrapped in a container via
endpoint like kicad-pcb.org/api/v1/ratings or so
Hi,
I can't find this issue on GitLab: https://bugs.launchpad.net/kicad/+bug/1849376
Can you help me ?
Franck.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad
46 matches
Mail list logo
