I think it would be a better use of your time if you could make the
BOM exporter already existing have them auto populated.
2017-05-14 21:39 GMT+02:00 Kristoffer Ödmark :
> Well I think these reasons are strange, I think that having a built in way
> of exporting the
It would be useful to have a csv export solution in the component table,
both grouped and ungrouped.
Dan
On 2017-05-14 22:12, Andrey Kuznetsov wrote:
Agree, a csv file option should be available.
Would be nice if there were 2 flavors, grouped and ungrouped.
That's all a general user might
Agree, a csv file option should be available.
Would be nice if there were 2 flavors, grouped and ungrouped.
That's all a general user might want.
Asking a general user to deal with python is unreasonable, and it took me a
while to figure out how the current plug in system works and even longer
Well I think these reasons are strange, I think that having a built in
way of exporting the BoM from the software is reasonable. Since not
everyone are the same.
The component table is what a user expects to see when wanting to
generate a BOM. I can assure you that no EE or student expects to
Stevn,
My position in term of electronic design is 180 degrees from yours.
When many engineering hours are spent design a manufacturable board,
you do not want some bean counter change the BOM in a whim.
So in order to control the proper life of a design, you want the schematic
to contain the
I agree with this decision as well but for different reasons.
The more I get into small scale self manufacturing, the more I am
persuaded by the argument that you want to keep as little BoM
information in the Kicad schematic fields as reasonably possible. It
becomes a maintenance nightmare,
JP,
This seems very sensible :)
Oliver
On 13 May 2017 04:18, "jp charras" wrote:
> Le 12/05/2017 à 13:55, Oliver Walters a écrit :
> > This feature was IN this branch of code but was vetoed. It was WYSIWYG
> BoM with export to:
> >
> > *SV
> > XML
> > HTML
> >
> > Wayne
Le 12/05/2017 à 13:55, Oliver Walters a écrit :
> This feature was IN this branch of code but was vetoed. It was WYSIWYG BoM
> with export to:
>
> *SV
> XML
> HTML
>
> Wayne mentioned that KiCad used to have such a BOM export tool but I haven't
> been using KiCad long
> enough to have
Ofcourse, but then that also has the problem that I dont really know
what kind of output I can expect, with this component table I know
exaclty what to expect. I can see the output before I export it.
For example in the pcbnew bom-exporter I get a field that is called
"supplier and ref", but
This feature was IN this branch of code but was vetoed. It was WYSIWYG BoM
with export to:
*SV
XML
HTML
Wayne mentioned that KiCad used to have such a BOM export tool but I
haven't been using KiCad long enough to have experienced it.
If there is real need for such a feature then I leave that to
Did you ever try pcbnew > file > export > BOM?
Den 12/05/2017 13.17 skrev "Kristoffer Ödmark" :
> Doesnt really matter what delimiter is used.
>
> It would just feel better if kicad had a default BOM-generation built in.
> Then I dont mind if someone prefers the
Doesnt really matter what delimiter is used.
It would just feel better if kicad had a default BOM-generation built
in. Then I dont mind if someone prefers the alternative scritpting way
to go because they can generate html or pdf or pictures or whatever. A
simple delimiter based exporter as
On Fri, May 12, 2017 at 10:25:49AM +0200, Kristoffer Ödmark wrote:
> Just to generate a .csv or a rahter a .tsv as the default.
May I suggest a .?sv
where the ? character is a "user defined character" that defaults to ...
comma (or tab or what you want) Separated Values list?
TIA
--
Marco
Hey!
This might be the one of the best new features with kicad in my opninion!
It would be more intuitive to have a bom-generator inside this tool as
well. A wsiwyg BOM-generator if you will. Just to generate a .csv or a
rahter a .tsv as the default. Leaving the current way to plugin-generate
Thanks JP :)
On Mon, May 8, 2017 at 8:45 PM, jp charras wrote:
> Le 08/05/2017 à 09:19, Oliver Walters a écrit :
> > JP,
> >
> > You are correct, wxID_CANCEL was all that was needed.
> >
> > #004 is attached
> >
> > Thanks for the feedback :)
> >
>
> Thanks.
> I committed
Le 08/05/2017 à 09:19, Oliver Walters a écrit :
> JP,
>
> You are correct, wxID_CANCEL was all that was needed.
>
> #004 is attached
>
> Thanks for the feedback :)
>
Thanks.
I committed your patches.
--
Jean-Pierre CHARRAS
___
Mailing list:
JP,
You are correct, wxID_CANCEL was all that was needed.
#004 is attached
Thanks for the feedback :)
On Mon, May 8, 2017 at 4:40 PM, jp charras wrote:
> Le 08/05/2017 à 05:29, Oliver Walters a écrit :
> > JP,
> >
> > I was expecting this response :)
> >
> > I was
Le 08/05/2017 à 05:29, Oliver Walters a écrit :
> JP,
>
> I was expecting this response :)
>
> I was happy to acquiesce initially on this style change as it was only my
> preference over yours, but
> reading through the responses of a lot of people on the original thread, I
> believe that the
Le 06/05/2017 à 07:35, Oliver Walters a écrit :
> After feedback on the original thread
> (https://lists.launchpad.net/kicad-developers/msg29057.html)
>
> I have made some further improvements to the component table:
>
> a) Add values from template fields where no value exists
> b) Allow users
19 matches
Mail list logo