Re: [Kicad-developers] Group selection idea

[Rohan Agrawal]

Just adding my 2 cents, as a user of Kicad.

I think that PCB groups and schematic groups should be linked. They should
also be reusable between different boards and projects.

For example I have a 5V switching design I use on a lot of boards, and
would like to be able to have it in a library of such designs that I can
pull from.

Rohan

On Thu, Jan 12, 2017 at 12:38 PM Kristoffer Ödmark <
kristofferodmar...@gmail.com> wrote:

> I think Physical design reuse (PDR) is far out of scope of the group
> selection idea. However it Might be used. I actually put some thinking
> on howto implement some kind of PDR into Kicad without having to
> redesign everything existing already. Its in a google doc with comments
> enabled.
>
> [Google docs link]
>
> https://docs.google.com/document/d/1ivRRu7F2g6_WU9bgHlaUTaXZw02oluMh4NA41BqEM-8/edit?usp=sharing
>
> PDR discussions I think should be in a separate thread, since the amount
> of work to get there is quite a bit more, involves both eeschema and
> pcbnew, new file formatting, specifying workflows etc etc.
>
> Its called snippets in Am, PDR in PADS.
>
> - Kristoffer
>
> On 2017-01-12 18:47, Clemens Koller wrote:
> > Hello!
> >
> > This feature looks really useful in production if it's implemented
> properly.
> > Some comments from my side how things could be extended in the future:
> >
> > Group selection (also read: table-based/parametric-based selection!)
> seems like a great feature and the step towards physical design reuse (PDR).
> > With some intelligent grouping of routed components and
> automatic/assisted selection of components based on netlist-topology (or
> manual or table based selection) it is possible to create a physical design
> reuse (or channels) by duplicating groups with the same layout but
> different component references + different net names / instances of net
> names.
> > An additional approach is intelligent "group editing" (table based - a
> must have for complex designs!) where there is an automatic / assisted
> rename of components and netnames to create reuses. This also applies to
> the schematic entry, obviously.
> >
> > The word "intelligent" above means obviously, that there is some
> infrastructure and coding work to consider.
> >
> > An example screenshot of one of my designs using a buggy commercial
> product is attached. There are 60 similar channels.
> > Layouting these manually would be a hell of work, obviously.
> >
> > Regards,
> >
> > Clemens
> >
> >
> > On 2017-01-12 17:37, Wayne Stambaugh wrote:
> >> I think this feature would be useful but we should proceed with caution
> >> if we are going to include persistence.  I'm guessing making groups
> >> persistent will require a change to the pcb file format.  We should
> >> think this through thoroughly before moving forward.  Is it possible
> >> that this grouping could be used for an am like room feature?  If
> >> so, than we need to plan this out accordingly rather than just commit a
> >> new feature for the sake of convenience.
> >>
> >> On 1/12/2017 6:55 AM, Tomasz Wlostowski wrote:
> >>> I like it. Give me a few days to review it and I hope it will get
> >>> merged. You'll also have to make the groups persistent (save to file).
> >>> Recursive grouping (group of groups) would be also an advantage.
> >>>
> >>>
> >>> Cheers,
> >>> Tom
> >>>
> >>> Sent from my Samsung Galaxy smartphone.
> >>>
> >>>
> >>>  Original message 
> >>> From: Kristoffer Ödmark 
> >>> Date: 12/01/2017 12:41 (GMT+01:00)
> >>> To: kicad-developers@lists.launchpad.net
> >>> Subject: Re: [Kicad-developers] Group selection idea
> >>>
> >>> Hey again, What would be the chances of seing this getting into the
> >>> master branches on launchpad, what would I have to add/change to get it
> >>> there?
> >>>
> >>> - Kristoffer
> >>>
> >>> On 2017-01-11 21:59, Kristoffer Ödmark wrote:
>  Attaching Patch!
> 
>  ( Thanks Chris! )
> 
>  On 2017-01-11 20:51, Kristoffer Ödmark wrote:
> > Hello!
> >
> > I hacked together a group selection concept looking like this:
> > https://youtu.be/eJp-aJ8i0H4
> >
> > It can assign BOARD_ITEM to a specific group for easier selection and
> > group manipulation. I am open to suggestions on changes, this is
> surely
> > not an optimal implementation.
> >
> > Useful when you may want to keep the relative position of something
> on
> > the board like maybe a RF layout etc.
> >
> > It cannot currently save the group assignments between sessions,
> since
> > that would require some changes to the file format. That would need
> some
> > agreement that this is indeed wanted.
> >
> > it also doesnt work on zones right now.
> >
> > ps: I do not now the best way to attach a patch file.
> > I added my feature
> > commit
> > git pull
> > fix conflict
> > commit
> >
> > Anyone have any steps on how to get one patch file 

Re: [Kicad-developers] Group selection idea

[Kristoffer Ödmark]

I think Physical design reuse (PDR) is far out of scope of the group 
selection idea. However it Might be used. I actually put some thinking 
on howto implement some kind of PDR into Kicad without having to 
redesign everything existing already. Its in a google doc with comments 
enabled.


[Google docs link]
https://docs.google.com/document/d/1ivRRu7F2g6_WU9bgHlaUTaXZw02oluMh4NA41BqEM-8/edit?usp=sharing

PDR discussions I think should be in a separate thread, since the amount 
of work to get there is quite a bit more, involves both eeschema and 
pcbnew, new file formatting, specifying workflows etc etc.


Its called snippets in Am, PDR in PADS.

- Kristoffer

On 2017-01-12 18:47, Clemens Koller wrote:

Hello!

This feature looks really useful in production if it's implemented properly.
Some comments from my side how things could be extended in the future:

Group selection (also read: table-based/parametric-based selection!) seems like 
a great feature and the step towards physical design reuse (PDR).
With some intelligent grouping of routed components and automatic/assisted 
selection of components based on netlist-topology (or manual or table based 
selection) it is possible to create a physical design reuse (or channels) by 
duplicating groups with the same layout but different component references + 
different net names / instances of net names.
An additional approach is intelligent "group editing" (table based - a must 
have for complex designs!) where there is an automatic / assisted rename of components 
and netnames to create reuses. This also applies to the schematic entry, obviously.

The word "intelligent" above means obviously, that there is some infrastructure 
and coding work to consider.

An example screenshot of one of my designs using a buggy commercial product is 
attached. There are 60 similar channels.
Layouting these manually would be a hell of work, obviously.

Regards,

Clemens


On 2017-01-12 17:37, Wayne Stambaugh wrote:

I think this feature would be useful but we should proceed with caution
if we are going to include persistence.  I'm guessing making groups
persistent will require a change to the pcb file format.  We should
think this through thoroughly before moving forward.  Is it possible
that this grouping could be used for an am like room feature?  If
so, than we need to plan this out accordingly rather than just commit a
new feature for the sake of convenience.

On 1/12/2017 6:55 AM, Tomasz Wlostowski wrote:

I like it. Give me a few days to review it and I hope it will get
merged. You'll also have to make the groups persistent (save to file).
Recursive grouping (group of groups) would be also an advantage.


Cheers,
Tom

Sent from my Samsung Galaxy smartphone.


 Original message 
From: Kristoffer Ödmark 
Date: 12/01/2017 12:41 (GMT+01:00)
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] Group selection idea

Hey again, What would be the chances of seing this getting into the
master branches on launchpad, what would I have to add/change to get it
there?

- Kristoffer

On 2017-01-11 21:59, Kristoffer Ödmark wrote:

Attaching Patch!

( Thanks Chris! )

On 2017-01-11 20:51, Kristoffer Ödmark wrote:

Hello!

I hacked together a group selection concept looking like this:
https://youtu.be/eJp-aJ8i0H4

It can assign BOARD_ITEM to a specific group for easier selection and
group manipulation. I am open to suggestions on changes, this is surely
not an optimal implementation.

Useful when you may want to keep the relative position of something on
the board like maybe a RF layout etc.

It cannot currently save the group assignments between sessions, since
that would require some changes to the file format. That would need some
agreement that this is indeed wanted.

it also doesnt work on zones right now.

ps: I do not now the best way to attach a patch file.
I added my feature
commit
git pull
fix conflict
commit

Anyone have any steps on how to get one patch file for this, now I got
one patch file, and a merge.

- Kristoffer


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : 

Re: [Kicad-developers] [RFC] Standard field for manufacturer part number in schematic symbols

[Kaspar Emanuel]

I have put up a proposal for a "community standard" on the forum:
https://forum.kicad.info/t/standard-symbol-field-names-initiative/4870/1

On 12 January 2017 at 18:33, Kaspar Emanuel 
wrote:

>
> On 12 January 2017 at 16:44, Kaspar Emanuel 
> wrote:
>
>>
>> Is there actually any issue, internally to KiCAD, with creating multiple
>> fields with the same name? It seems to let me create two fields called MPN
>> and save and re-open without a problem.
>>
>
>
> Actually, just tested again and it doesn't like fields with the same name,
> it simply overwrites them once you press ok, not sure what I was doing
> before. That's a shame.
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Standard field for manufacturer part number in schematic symbols

[Kaspar Emanuel]

On 12 January 2017 at 16:44, Kaspar Emanuel 
wrote:

>
> Is there actually any issue, internally to KiCAD, with creating multiple
> fields with the same name? It seems to let me create two fields called MPN
> and save and re-open without a problem.
>


Actually, just tested again and it doesn't like fields with the same name,
it simply overwrites them once you press ok, not sure what I was doing
before. That's a shame.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Group selection idea

[Kristoffer Ödmark]

Yes, my patch was just an idea in its current implementation though it 
is very useful. But in the future I could see things as:


- Hierarchial groups
	- Connection between eeschema so that symbols could belong to a group 
by default and that nets that are only connected between symbols sharing 
the same group could be considered part of the group upon creation in pcb

- And of course persistance, that is very nice to have I have noticed


On 01/12/2017 06:00 PM, Wayne Stambaugh wrote:

On 1/12/2017 11:53 AM, Kaspar Emanuel wrote:

It does look really neat and I agree with Wayne it bears some thought
and could be a really powerful feature.

Wayne, I think what you mean by "a***m like room feature" are reusable
"snippets" of placed and routed components. Is that right?


I'm not sure what it's called in am.  I seem to remember a
discussion about "rooms" regarding one of the commercial EDA products
but could not say for sure which one.  Basically the feature is reusable
blocks of board objects.  I think this feature could be really powerful
if we think about the bigger picture rather than just the patch we have
in front of us.



On 12 January 2017 at 16:37, Wayne Stambaugh > wrote:

I think this feature would be useful but we should proceed with caution
if we are going to include persistence.  I'm guessing making groups
persistent will require a change to the pcb file format.  We should
think this through thoroughly before moving forward.  Is it possible
that this grouping could be used for an am like room feature?  If
so, than we need to plan this out accordingly rather than just commit a
new feature for the sake of convenience.

On 1/12/2017 6:55 AM, Tomasz Wlostowski wrote:
> I like it. Give me a few days to review it and I hope it will get
> merged. You'll also have to make the groups persistent (save to file).
> Recursive grouping (group of groups) would be also an advantage.
>
>
> Cheers,
> Tom
>
> Sent from my Samsung Galaxy smartphone.
>
>
>  Original message 
> From: Kristoffer Ödmark >
> Date: 12/01/2017 12:41 (GMT+01:00)
> To: kicad-developers@lists.launchpad.net

> Subject: Re: [Kicad-developers] Group selection idea
>
> Hey again, What would be the chances of seing this getting into the
> master branches on launchpad, what would I have to add/change to
get it
> there?
>
> - Kristoffer
>
> On 2017-01-11 21:59, Kristoffer Ödmark wrote:
>> Attaching Patch!
>>
>> ( Thanks Chris! )
>>
>> On 2017-01-11 20:51, Kristoffer Ödmark wrote:
>>> Hello!
>>>
>>> I hacked together a group selection concept looking like this:
>>> https://youtu.be/eJp-aJ8i0H4
>>>
>>> It can assign BOARD_ITEM to a specific group for easier
selection and
>>> group manipulation. I am open to suggestions on changes, this is
surely
>>> not an optimal implementation.
>>>
>>> Useful when you may want to keep the relative position of
something on
>>> the board like maybe a RF layout etc.
>>>
>>> It cannot currently save the group assignments between sessions,
since
>>> that would require some changes to the file format. That would
need some
>>> agreement that this is indeed wanted.
>>>
>>> it also doesnt work on zones right now.
>>>
>>> ps: I do not now the best way to attach a patch file.
>>> I added my feature
>>> commit
>>> git pull
>>> fix conflict
>>> commit
>>>
>>> Anyone have any steps on how to get one patch file for this, now
I got
>>> one patch file, and a merge.
>>>
>>> - Kristoffer
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers

> Post to : kicad-developers@lists.launchpad.net

> Unsubscribe : https://launchpad.net/~kicad-developers

> More help   : https://help.launchpad.net/ListHelp

>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers

> Post to : kicad-developers@lists.launchpad.net

> Unsubscribe : https://launchpad.net/~kicad-developers

> More help   : https://help.launchpad.net/ListHelp

>

___
Mailing list: 

Re: [Kicad-developers] Group selection idea

[Wayne Stambaugh]

On 1/12/2017 11:53 AM, Kaspar Emanuel wrote:
> It does look really neat and I agree with Wayne it bears some thought
> and could be a really powerful feature.
> 
> Wayne, I think what you mean by "a***m like room feature" are reusable
> "snippets" of placed and routed components. Is that right?

I'm not sure what it's called in am.  I seem to remember a
discussion about "rooms" regarding one of the commercial EDA products
but could not say for sure which one.  Basically the feature is reusable
blocks of board objects.  I think this feature could be really powerful
if we think about the bigger picture rather than just the patch we have
in front of us.

> 
> On 12 January 2017 at 16:37, Wayne Stambaugh  > wrote:
> 
> I think this feature would be useful but we should proceed with caution
> if we are going to include persistence.  I'm guessing making groups
> persistent will require a change to the pcb file format.  We should
> think this through thoroughly before moving forward.  Is it possible
> that this grouping could be used for an am like room feature?  If
> so, than we need to plan this out accordingly rather than just commit a
> new feature for the sake of convenience.
> 
> On 1/12/2017 6:55 AM, Tomasz Wlostowski wrote:
> > I like it. Give me a few days to review it and I hope it will get
> > merged. You'll also have to make the groups persistent (save to file).
> > Recursive grouping (group of groups) would be also an advantage.
> >
> >
> > Cheers,
> > Tom
> >
> > Sent from my Samsung Galaxy smartphone.
> >
> >
> >  Original message 
> > From: Kristoffer Ödmark  >
> > Date: 12/01/2017 12:41 (GMT+01:00)
> > To: kicad-developers@lists.launchpad.net
> 
> > Subject: Re: [Kicad-developers] Group selection idea
> >
> > Hey again, What would be the chances of seing this getting into the
> > master branches on launchpad, what would I have to add/change to
> get it
> > there?
> >
> > - Kristoffer
> >
> > On 2017-01-11 21:59, Kristoffer Ödmark wrote:
> >> Attaching Patch!
> >>
> >> ( Thanks Chris! )
> >>
> >> On 2017-01-11 20:51, Kristoffer Ödmark wrote:
> >>> Hello!
> >>>
> >>> I hacked together a group selection concept looking like this:
> >>> https://youtu.be/eJp-aJ8i0H4
> >>>
> >>> It can assign BOARD_ITEM to a specific group for easier
> selection and
> >>> group manipulation. I am open to suggestions on changes, this is
> surely
> >>> not an optimal implementation.
> >>>
> >>> Useful when you may want to keep the relative position of
> something on
> >>> the board like maybe a RF layout etc.
> >>>
> >>> It cannot currently save the group assignments between sessions,
> since
> >>> that would require some changes to the file format. That would
> need some
> >>> agreement that this is indeed wanted.
> >>>
> >>> it also doesnt work on zones right now.
> >>>
> >>> ps: I do not now the best way to attach a patch file.
> >>> I added my feature
> >>> commit
> >>> git pull
> >>> fix conflict
> >>> commit
> >>>
> >>> Anyone have any steps on how to get one patch file for this, now
> I got
> >>> one patch file, and a merge.
> >>>
> >>> - Kristoffer
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> 
> > Post to : kicad-developers@lists.launchpad.net
> 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> > More help   : https://help.launchpad.net/ListHelp
> 
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> 
> > Post to : kicad-developers@lists.launchpad.net
> 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> 
> > More help   : https://help.launchpad.net/ListHelp
> 
> >
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> 
> Post to : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> 
> More help   : 

Re: [Kicad-developers] Group selection idea

[Kaspar Emanuel]

It does look really neat and I agree with Wayne it bears some thought and
could be a really powerful feature.

Wayne, I think what you mean by "a***m like room feature" are reusable
"snippets" of placed and routed components. Is that right?

On 12 January 2017 at 16:37, Wayne Stambaugh  wrote:

> I think this feature would be useful but we should proceed with caution
> if we are going to include persistence.  I'm guessing making groups
> persistent will require a change to the pcb file format.  We should
> think this through thoroughly before moving forward.  Is it possible
> that this grouping could be used for an am like room feature?  If
> so, than we need to plan this out accordingly rather than just commit a
> new feature for the sake of convenience.
>
> On 1/12/2017 6:55 AM, Tomasz Wlostowski wrote:
> > I like it. Give me a few days to review it and I hope it will get
> > merged. You'll also have to make the groups persistent (save to file).
> > Recursive grouping (group of groups) would be also an advantage.
> >
> >
> > Cheers,
> > Tom
> >
> > Sent from my Samsung Galaxy smartphone.
> >
> >
> >  Original message 
> > From: Kristoffer Ödmark 
> > Date: 12/01/2017 12:41 (GMT+01:00)
> > To: kicad-developers@lists.launchpad.net
> > Subject: Re: [Kicad-developers] Group selection idea
> >
> > Hey again, What would be the chances of seing this getting into the
> > master branches on launchpad, what would I have to add/change to get it
> > there?
> >
> > - Kristoffer
> >
> > On 2017-01-11 21:59, Kristoffer Ödmark wrote:
> >> Attaching Patch!
> >>
> >> ( Thanks Chris! )
> >>
> >> On 2017-01-11 20:51, Kristoffer Ödmark wrote:
> >>> Hello!
> >>>
> >>> I hacked together a group selection concept looking like this:
> >>> https://youtu.be/eJp-aJ8i0H4
> >>>
> >>> It can assign BOARD_ITEM to a specific group for easier selection and
> >>> group manipulation. I am open to suggestions on changes, this is surely
> >>> not an optimal implementation.
> >>>
> >>> Useful when you may want to keep the relative position of something on
> >>> the board like maybe a RF layout etc.
> >>>
> >>> It cannot currently save the group assignments between sessions, since
> >>> that would require some changes to the file format. That would need
> some
> >>> agreement that this is indeed wanted.
> >>>
> >>> it also doesnt work on zones right now.
> >>>
> >>> ps: I do not now the best way to attach a patch file.
> >>> I added my feature
> >>> commit
> >>> git pull
> >>> fix conflict
> >>> commit
> >>>
> >>> Anyone have any steps on how to get one patch file for this, now I got
> >>> one patch file, and a merge.
> >>>
> >>> - Kristoffer
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Standard field for manufacturer part number in schematic symbols

[Kaspar Emanuel]

On 9 January 2017 at 14:29, Brian Sidebotham 
wrote:

> 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 fields that are common to all symbols that you
> create. If the value is anything other than blank, the field is saved with
> the symbol.
>

Yes, at this point I was suggesting adding standard template field names.
But following further thought I have decided to try to organize the
community of external tooling creators to agree on some standard fieldnames
and a schema for them. I will post here with updates on that.



> The easiest way to specify multiples is probable to suffix with a number,
> like Manufacturer-1, PartNumber-1, Manufacturer-2, PartNumber-2, etc.
>

Is there actually any issue, internally to KiCAD, with creating multiple
fields with the same name? It seems to let me create two fields called MPN
and save and re-open without a problem.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Group selection idea

[Wayne Stambaugh]

I think this feature would be useful but we should proceed with caution
if we are going to include persistence.  I'm guessing making groups
persistent will require a change to the pcb file format.  We should
think this through thoroughly before moving forward.  Is it possible
that this grouping could be used for an am like room feature?  If
so, than we need to plan this out accordingly rather than just commit a
new feature for the sake of convenience.

On 1/12/2017 6:55 AM, Tomasz Wlostowski wrote:
> I like it. Give me a few days to review it and I hope it will get
> merged. You'll also have to make the groups persistent (save to file).
> Recursive grouping (group of groups) would be also an advantage.
> 
> 
> Cheers,
> Tom
> 
> Sent from my Samsung Galaxy smartphone.
> 
> 
>  Original message 
> From: Kristoffer Ödmark 
> Date: 12/01/2017 12:41 (GMT+01:00)
> To: kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] Group selection idea
> 
> Hey again, What would be the chances of seing this getting into the
> master branches on launchpad, what would I have to add/change to get it
> there?
> 
> - Kristoffer
> 
> On 2017-01-11 21:59, Kristoffer Ödmark wrote:
>> Attaching Patch!
>>
>> ( Thanks Chris! )
>>
>> On 2017-01-11 20:51, Kristoffer Ödmark wrote:
>>> Hello!
>>>
>>> I hacked together a group selection concept looking like this:
>>> https://youtu.be/eJp-aJ8i0H4
>>>
>>> It can assign BOARD_ITEM to a specific group for easier selection and
>>> group manipulation. I am open to suggestions on changes, this is surely
>>> not an optimal implementation.
>>>
>>> Useful when you may want to keep the relative position of something on
>>> the board like maybe a RF layout etc.
>>>
>>> It cannot currently save the group assignments between sessions, since
>>> that would require some changes to the file format. That would need some
>>> agreement that this is indeed wanted.
>>>
>>> it also doesnt work on zones right now.
>>>
>>> ps: I do not now the best way to attach a patch file.
>>> I added my feature
>>> commit
>>> git pull
>>> fix conflict
>>> commit
>>>
>>> Anyone have any steps on how to get one patch file for this, now I got
>>> one patch file, and a merge.
>>>
>>> - Kristoffer
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python LAYER_PAIR parameter for EXCELLON_WRITER().BuildHolesList()

[Martin Schreiber]

On Thursday 12 January 2017 12:37:37 jp charras wrote:
>
> It could be worth to explain us what exactly are you trying to do.

MSEkicadBOM is a tool in order to combine KiCad with a component database and 
to automate document and production file generation. MSEkicadBOM scans the 
KiCad schematic files and matches the found components with the Firebird 
component database and looks up the associated footprint in the database, see
http://mseide-msegui.sourceforge.net/pics/msekicadbom.png
http://mseide-msegui.sourceforge.net/pics/kicad_component.png

'Reporting'-'Component-Footprintlist' creates a *.cmp list which can be 
imported into schematic.

Document and production file generation uses infos defined in setup dialogs 
which can use macros, the data is stored in project files and project 
templates. See for example
http://mseide-msegui.sourceforge.net/pics/kicad_globalsettings.png
http://mseide-msegui.sourceforge.net/pics/kicad_globalsettings1.png
http://mseide-msegui.sourceforge.net/pics/kicad_projectsettings.png

All is under construction!

> FILE is a basic C struct.
> These methods are helper methods to create files, but are called by a
> higher lever method.
>
That means that not all functions in pcbnew.py can be used because of missing 
proxy classes?

> If you are trying to create a EXCELLON drill file (exactly a set of files),
> have a look into the demo: gen_gerber_and_drill_files_board.py

Maybe it is possible to abuse the higher level functions in order to produce 
the needed low level results, I prefer to use low level functions directly. 
At the end it means less hassle.
It seems it already has been talked about:
https://lists.launchpad.net/kicad-developers/msg10233.html

Thanks, Martin

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Group selection idea

[Tomasz Wlostowski]

I like it. Give me a few days to review it and I hope it will get merged. 
You'll also have to make the groups persistent (save to file). Recursive 
grouping (group of groups) would be also an advantage.


Cheers,
Tom

Sent from my Samsung Galaxy smartphone.


 Original message 
From: Kristoffer Ödmark 
Date: 12/01/2017 12:41 (GMT+01:00)
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] Group selection idea

Hey again, What would be the chances of seing this getting into the
master branches on launchpad, what would I have to add/change to get it
there?

- Kristoffer

On 2017-01-11 21:59, Kristoffer Ödmark wrote:
> Attaching Patch!
>
> ( Thanks Chris! )
>
> On 2017-01-11 20:51, Kristoffer Ödmark wrote:
>> Hello!
>>
>> I hacked together a group selection concept looking like this:
>> https://youtu.be/eJp-aJ8i0H4
>>
>> It can assign BOARD_ITEM to a specific group for easier selection and
>> group manipulation. I am open to suggestions on changes, this is surely
>> not an optimal implementation.
>>
>> Useful when you may want to keep the relative position of something on
>> the board like maybe a RF layout etc.
>>
>> It cannot currently save the group assignments between sessions, since
>> that would require some changes to the file format. That would need some
>> agreement that this is indeed wanted.
>>
>> it also doesnt work on zones right now.
>>
>> ps: I do not now the best way to attach a patch file.
>> I added my feature
>> commit
>> git pull
>> fix conflict
>> commit
>>
>> Anyone have any steps on how to get one patch file for this, now I got
>> one patch file, and a merge.
>>
>> - Kristoffer

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Group selection idea

[Kristoffer Ödmark]

Hey again, What would be the chances of seing this getting into the 
master branches on launchpad, what would I have to add/change to get it 
there?


- Kristoffer

On 2017-01-11 21:59, Kristoffer Ödmark wrote:

Attaching Patch!

( Thanks Chris! )

On 2017-01-11 20:51, Kristoffer Ödmark wrote:

Hello!

I hacked together a group selection concept looking like this:
https://youtu.be/eJp-aJ8i0H4

It can assign BOARD_ITEM to a specific group for easier selection and
group manipulation. I am open to suggestions on changes, this is surely
not an optimal implementation.

Useful when you may want to keep the relative position of something on
the board like maybe a RF layout etc.

It cannot currently save the group assignments between sessions, since
that would require some changes to the file format. That would need some
agreement that this is indeed wanted.

it also doesnt work on zones right now.

ps: I do not now the best way to attach a patch file.
I added my feature
commit
git pull
fix conflict
commit

Anyone have any steps on how to get one patch file for this, now I got
one patch file, and a merge.

- Kristoffer


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python LAYER_PAIR parameter for EXCELLON_WRITER().BuildHolesList()

[jp charras]

Le 12/01/2017 à 12:05, Martin Schreiber a écrit :
> On Wednesday 11 January 2017 08:52:37 Martin Schreiber wrote:
>>
>> How must the LAYER_PAIR type parameter be defined in Python?
>>
> Similar problem with 
> "CreateDrillFile(EXCELLON_WRITER self, FILE * aFile) -> int".
> How to define "FILE * aFile"?
> "
> [...]
>   f1 = file(aoutputfile,'w')
>   drlwriter.CreateDrillFile(f1)
>   f1.close()
> [...]
> "
> returns:
> "
> Traceback (most recent call last):
>   File "", line 4, in 
>   File "drillfile.py", line 33, in drillfile
> drlwriter.CreateDrillFile(f1)
>   File "/usr/lib/python2.7/site-packages/pcbnew.py", line 10059, in 
> CreateDrillFile
> return _pcbnew.EXCELLON_WRITER_CreateDrillFile(self, *args)
> TypeError: in method 'EXCELLON_WRITER_CreateDrillFile', argument 2 of 
> type 'FILE *'
> ".
> 
> Martin

It could be worth to explain us what exactly are you trying to do.
FILE is a basic C struct.
These methods are helper methods to create files, but are called by a higher 
lever method.

If you are trying to create a EXCELLON drill file (exactly a set of files), 
have a look into the demo:
gen_gerber_and_drill_files_board.py

-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python LAYER_PAIR parameter for EXCELLON_WRITER().BuildHolesList()

[Martin Schreiber]

On Wednesday 11 January 2017 08:52:37 Martin Schreiber wrote:
>
> How must the LAYER_PAIR type parameter be defined in Python?
>
Similar problem with 
"CreateDrillFile(EXCELLON_WRITER self, FILE * aFile) -> int".
How to define "FILE * aFile"?
"
[...]
  f1 = file(aoutputfile,'w')
  drlwriter.CreateDrillFile(f1)
  f1.close()
[...]
"
returns:
"
Traceback (most recent call last):
  File "", line 4, in 
  File "drillfile.py", line 33, in drillfile
drlwriter.CreateDrillFile(f1)
  File "/usr/lib/python2.7/site-packages/pcbnew.py", line 10059, in 
CreateDrillFile
return _pcbnew.EXCELLON_WRITER_CreateDrillFile(self, *args)
TypeError: in method 'EXCELLON_WRITER_CreateDrillFile', argument 2 of 
type 'FILE *'
".

Martin

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp