| |
Steve Bliss wrote:
> In lugnet.cad.dev, Kyle McDonald wrote:
>
> > How about a ldcfgblk.ldr? For those of us who prefer to edit on a
> > black background instead of a paper white one?
> >
> > I suppose the software could just swap edge=0 for edge=8 and vice
> > versa, but what about the non-black and white edges?
>
>
> I'd say we're getting to the point where -- if there are going to be more than a
> handful of color configurations -- we'd want to think about some alternate
> distribution/management methods for 'color configurations'. Similar to what
> other softwares do with downloading 'skins'.
That sounds sensible.
Also it's occurred to me since my last post on the
internationization topic, that the Color names, and color
definitions might be better off split up.
1. If the skins or theme's catch on, there's no sense having a
'localized' version of every theme.
2. When a new color is added or an old one updated, who wants to
have to go and edit every copy with the same data.
Seems easier to have the numeric vales in one file and the names
in multiple other files. Maybe the default (or 'C' Locale ;) )
names are in with the numeric definitons, and you only need an
colornames file if you want different names?
-Kyle
--
_
-------------------------ooO( )Ooo--------------------------------
Kyle J. McDonald (o o) Systems Support Engineer
Sun Microsystems Inc. ||||| Kyle.McDonald@Sun.COM
1 Network Drive \\\// voice: (781) 442-2184
Burlington, MA 01803 (o o) fax: (781) 442-1542
--------------------------------ooO(_)Ooo-------------------------
|
|
| |
In lugnet.cad.dev, Kyle McDonald wrote:
> Also it's occurred to me since my last post on the
> internationization topic, that the Color names, and color
> definitions might be better off split up.
Yes ... and no.
If we did produce a fully internationalized, multi-namable color definition set,
we'd almost certainly include a 'default name' property for the colors.
So think of the data in ldconfig.ldr as the color definitions + the default
names.
If anyone wants to work on a definition of a language file, with info like...
ldlang-en.ldr:
0 COLOURNAME 0 Black
(I'm mono-lingual, so this is as far as the example is going to go)
... that would be cool.
But I feel fairly strongly that international color-name-lists really belong in
the upcoming color database, not in the LDraw distribution.
Steve
|
|
|
