kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

I think this discussion is more relevant on the kicad-lib-committers
list, see [1] and [2]

[1] https://lists.launchpad.net/kicad-lib-committers/
[2] https://launchpad.net/~kicad-lib-committers

2015-09-07 16:01 GMT+02:00 nnn4000 <nnn4000@xxxxx>:
> Hi
> I'd like to ask again if the way how the Fab and Silks layers are used in
> kicad libraries will stay as is because after stable release it probably
> won't be possible to change the rules. So I'm asking for more discussion
> about it.
> - For me the main issue is that while Fab is occpied by values there is no
> layer for ipc assembly layer so it can't be introduced until next stable
> release
> - I can't agree that finding components on a board with list of coordinates
> is efficient
> - it's ignored that some of users wants easily print values on silkscreen
> - moving single value to silks (useful at least with some of virtual
> components) removes it from fab (so it's no longer functional), so if user
> don't know about %V (who knows about it?) the task it more complicated than
> unhiding value
> - it's unclear if values on fab should be of size allowing to print on a
> board or scaled down to footprints size (maybe should be clarified what's
> its purpose?)
> - it's it's unclear for me why values have separate layer and reference
> designators have not, aren't refdes more useful?
> - name Fab isn't suggesting it's layer for values
> I simply can't believe it's all ok with the layers. I'm looking forward for
> more opinions.
> Regards
> Michal Stec
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>