Oh, sorry. The fault was on my side.
My email provider moved the mail from Jon into the junk folder. I missed
it, because I did not thought about and wondered about Rafals mail.
Thanks for clarifying, sorry for this confusion.
Back to topic:
Even if I worked with another tool and have no experience with KiCAD, I
think I know that KiCAD is not Altium (Eagle, Cadence, PADS, ...). And
even I'm inspired by, I thik I have some more ideas and wishes which are
nowhere implemented yet, so don't worry about my working background. ;)
Where would you normally discuss topics like this? The mailing list
would be fine for me, but I'm afraid of waisting and confusing by
discussing multiple topics in that way here. Maybe you have a better
place already?
greetings
Oliver
Am 26.02.2024 um 20:08 schrieb 'Rafał Pietrak' via KiCad Developers:
Hi Oliver,
You've asked for snippet source - it came from this email by Jon.
-R
W dniu 26.02.2024 o 15:47, Jon Evans pisze:
Hello Oliver,
On Mon, Feb 26, 2024 at 9:34 AM 'White Fox' via KiCad Developers
<[email protected] <mailto:[email protected]>> wrote:
As far I know, KiCAD has no support for multiboard projects. I
looked
out for something like a road map and found something on gitlab, but
maybe outdated. Last edit was 2020.
Personally I have come to the conclusion that long-term roadmaps are
of limited use, especially for KiCad.
At the moment we focus more on planning for the next upcoming
release. Anything that is not being actively worked on for that next
release is considered "unplanned".
So I would like to know, what KiCAD devs think about multiboard
projects. Are they on track for KiCAD development, was this already
discussed? Or will this overload development capacities?
This falls into the category of things that have been talked about,
but there are no immediate plans and nobody is working on it.
I think I could at least contribute some
experience. (Unfortunately, Altium supports multiboard projects,
but in
a poorly way, it could be much more powerfull.)
The first step would be to have some discussion of what problems we
are trying to solve, and then we can brainstorm possible ways of
solving them.
Often, people who are experienced with other tools like to talk about
features in terms of the other tools: "KiCad should do it like X", or
"KiCad should not do it like Y".
What I find more useful is to make sure to discuss what people
actually need to do, independent of what tool they use, and agree on
that first.
It is then easier to discuss the advantages and disadvantages of
various possible ways of doing it.
For "multiboard projects" I think if you ask 5 people, you will
possibly get 5 different answers about what this feature means, and
what they want to do with it.
So, figuring this out (and getting it documented) is a good first step.
The same I wrote for multiboard projects I could repeat for pcb
variation support, but I better do not and just mentioned it.
Variants are planned and being more actively worked on, although
there are a number of things that have to happen first, and I think
schematic variant support will come before PCB variant support.
Best,
Jon
--
You received this message because you are subscribed to the Google
Groups "KiCad Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/a/kicad.org/d/msgid/devlist/CA%2BqGbCCF2av3Efih-fP_ZVcum3Q45tBgpMAQ6nrN5GZ6mOMabg%40mail.gmail.com
<https://groups.google.com/a/kicad.org/d/msgid/devlist/CA%2BqGbCCF2av3Efih-fP_ZVcum3Q45tBgpMAQ6nrN5GZ6mOMabg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
Das Nötige ist einfach und das Komplizierte unnötig
-Michail Kalaschnikow
As a german, please let me tell you: Germans are not rude.
If you invite a german to have lunch with you and he says simply 'No', be
assured that he means:
«I'm so glad that you ask me to spend lunch time with you, I'm sure it would be
a great time,
but unfortunately, I'm deeply sorry for that, I have a meeting with my boss and
a few minutes later,
I promised our most important customer a call.
And moreover, I'm a little embarassed for that, I feel a bit sick today, maybe
I'm not a good lunch companion today.
But I really hope so that we can share this great time another time.»
The reason for this kind of highly efficient conversation, which is typical for
germans, is quite simple:
He knows that you are probably very busy with highly important business,
and it is a special kind of German courtesy not to want to waste your precious
time.
So please, don't misunderstand short and precise communication as rowdyness.
--
You received this message because you are subscribed to the Google Groups "KiCad
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/kicad.org/d/msgid/devlist/5449b0b8-8ed5-408b-8736-b44e0ebefd65%40gmx.de.
