Mail Archives: geda-user/2016/01/19/10:08:50
On 19/01/16 14:11, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via
geda-user AT delorie DOT com] wrote:
>
>>>> But I do think the output should not have its case changed.
>>> Then we could not join "Resistor 10k" and "resistor 10k" and count
>>> them together in some cases.
>> I think the best thing is to push that problem down to the user.
> Agreed
It would be really nice to do this, but you quickly find that the
program is second-guessing you, and more often than not, the wrong way.
Best to flag it to the user in some way, let them decide. I hate the
Office apps when they decide they think they know better and auto
something, only for you to have to undo it!!
>
>>>> If you want to change anything, wouldn't it be better to have a
>>>> separate
>>>> sch/sym beautifier script ?
>>> Why not? However, at least basic things have to be done well.
>> 1, In 2010 I did one to remove numslots=0 attribute which gsymcheck
>> complains about:
>>
>> $ find . -type f -name \*.sym | xargs perl -i -ne 'if (m/^numslots\=0/) {
>> undef($old); } else { print $old if $old; undef($old); if (m/^T /) { $old =
>> $_; } else { print; }}'
> gsymcheck is broken. I have rewritten it in scheme (see the
> gsymcheck branch in the above repository on github) and used as a
> module for gschem to check symbols interactively. However, I won't
> work on it further yet since I have some other thoughts :)
I'd really like to see an interactive gsymcheck .. must check this out.
Also, are your "thoughts" published anywhere .. like on the github, like
peterbrett .. always nice to read where other people's ideas are at.
>> 2, upcase 1st char of device attribute.
> It's easy to do using Scheme, if you want, isn't it ;)
I feel strongly that you keep to All Caps or All Lower, no mixing or it
makes a pain to read/check. Again, perhaps a means of flagging up to the
user for correction would be really handy.
>> Any more, do you have a list ?
> No
>
> ...
>> Great, I'd like to test that.
> You haven't even recompile gnetlist for that. Just use something
> like:
>
> gnetlist -m ./gnetlist/scheme/*partslist*.scm -g partslist3 -o - test.sch
>
> ...
>>>> And it would be nice if columns lined up as in first example above.
>>> The same. I believe this is a business for some post-processing
>>> program, since we just output a TSV lists.
>> Hmm, maybe we could provide a postprocessor.
> gnetlist is our postprocessor. You can load your custom/preferred
> functions either before or after loading backends and thus change
> its behaviour (e.g., using the -m option mentioned before).
>
> Cheers,
> Vladimir
I have to admit, I really like gnetlist and use the bom2 processor
regularly to generate spreadsheets for parts lists. I can do any further
sorting/processing in the spreadsheet, and filter different parts, add
order codes and supplier all easily from there. It also allows me to
perform some basic checking IN the spreadsheet, as resistors that are
10k and 10K soon show up together. The only grind is you have to go back
to the schematic editor and correct, but once it's right, it's right.
I'm about to do a board design, so I'll have to make some notes as I go
along of the usual 'gotchas' that I come across... !!
MJE
- Raw text -