 | | Re: In dev: new ldconfig.ldr file
|
|
(...) 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 (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) How about combining, steve's, andrew's, and your earlier idea with something like: [Configurations] # FILE Config Name LOCALE 0=ldconfig.ldr default EN 1=ldcfgalt.ldr ldlite EN 2=ldconfig_DE.ldr default DE 3=ldcfgalt_DE.ldr ldlite DE (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) 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 (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) Err, I missed that point in the search path discussion - or I would have recommended putting them in a different section. If [configurations] is too generic, then how about [LDraw.configurations]? Steve (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
| |
| | Re: In dev: new ldconfig.ldr file
|
|
(...) To be honest, I don't remember for sure, but I doubt it. My general standpoint on these kinds of things is that LDraw is a 3D-library, not a database. And language issues are (mostly) outside the scope of the library. However, I think Don had (...) (20 years ago, 9-Aug-04, to lugnet.cad.dev)
|
