Colin D Bennett wrote: >> ^__ Properties of the view, not the underlying data - I'd prefer to >> abstract this to the renderer. > > I agree that color does not belong in the layout file. I may keep > changing my preferences on my pcb color theme, but I don't want to > update all my layout files to take advantage of an updated color theme > -- UI preferences like color theme should definitely not be included in > the .pcb layout file itself.
I partly disagree. Some information on color should be in the layout. Real world use cases: 1) Footprints only use the first two copper layers. Convert buffer to element converts tracks on the first layer to pads on top. Tracks on the second layer get pads on bottom layer. Consequently, a pcb meant as a work sheet for footprint creation needs different colors than a regular layout. 2) Four layer layouts have different demands on colors than two layers. If I switch between projects with four layers and two layers, it is a hassle to manually load the fitting color scheme. 3) If I add some layers in the middle of the layer stack, colors of layers below shift to other layers. So this new layer stack clearly needs a special color treatment. The layout may not contain the whole explicit color information. Just a name of a color scheme may be enough. If no matching color scheme can be found in $HOME/.pcb/.color, or in the project dir, some default scheme would be used. That way you can have both. Central color config files and layout chosen color schemes. As a bonus, my color blind colleague can keep a palette adjusted to his needs and we can still both work with the same layout files. ---<)kaimartin(>--- -- Kai-Martin Knaak Email: [email protected] Öffentlicher PGP-Schlüssel: http://pool.sks-keyservers.net:11371/pks/lookup?search=0x6C0B9F53 _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
