> copper
> silk
> soldermask relief
> solderpaste
> outline - as in the outline of the finished board
> route - as in cutting slots with a routing bit
> assembly - like an assembly drawing, fab drawing, etc
> other - not sure what else goes here but this would be a catch all
> plated drill
> unplated drill
>
I think these categories sound great....the only other one I can think
of off-hand might be other fab-related processes like "score" or
"mouse-bite", etc.
> Once this is set, there are some additional attributes that some of
> these may have. For copper layers, we need the stackup order. Do we
> want to associate this with a particular layer and keep it when you move
> them up and down in the visual display? i.e. allow someone to display
> layer 1, layer4, layer 3, layer2 in that order? Or do we automatically
> assign the stackup based on how they are visually? If the stackup is
> not constrained by layer ordering then I think we probably want to
> display the stackup order or it may get too out of sync.
My gut feeling is that the layer number should be independent of the
visualization order. It'll cause too much headache if the layer number
is changing each time the user moves a layer in the sidepane. Hopefully
we can patch PCB to output a gerbv project file during export...that way
we could pre-populate the layer fields and visualization order (from top
to bottom, probably) with PCB, and gerbv will open it up seamlessly.
>
> For drill layers, we need a top and bottom layer that the drill goes to.
> For example on a 16 layer board, you might have a 9-12 drill file and
> a 1-16 drill file, etc. Here I don't really see any other option than
> to have two fields that must be user edited. One is for top layer where
> the values can be symbolic "top" or numeric 1,2,3,4, etc and the other
> for bottom layer where the choices are "bot" or numeric, 4,3,2, etc.
> The defaults would be "top" and "bot" respectively since the majority of
> designs probably do not make use of multiple drill files like this.
I think this sounds great. "top" and "bottom" will make parsing a tiny
bit harder, but it probably makes the most sense. I guess we could
populate with "1" and "1000" as well, but this may be clunkier in the
long run.
Cheers--
Julian
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gerbv-devel mailing list
Gerbv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gerbv-devel
