Part versioning


RE: Part versioning
#5
(2025-09-06, 23:30)Chris Böhnke Wrote: Do you intend the versioning for the actual file or merely for it's library entry?
The library entry, i.e. "Name".

Being relatively new to LDraw, I'm astonished that the 'same' suffices are used for so many purposes. My only concern is to remove bdc replacement files from the abc swamp. If we manage to do it, then every abc suffix will have a real meaning. Obsoletes are already uniquely identified by a "~" in the start of the description.

One of the key arguments for not to correct orientation or point of origin is the abc suffix. Thus, there are many parts in the library where these could be adjusted to follow the rules.

As a second example, I give 31213bp01.dat. Here, the "b" in the name is meaningless and frankly speaking unnecessary. The "b" originates from rotation of the base part, while the "p01" comes from the pattern. Such a "b" would be needed in the name only if the pattern existed for the previous orientation. Now, consider 31213p01b or 31213p01. The latter could be used if it was the first version of its kind (v1 being suppressed). If a previous version had existed, then it would be 31213p01v2.

Quote:2) What would be the actual naming convention?
Henceforth, whenever a "b replacement file" is created, it is to be named with v2, v3, v4, etc. Previous letters denoting "b replacement files" should be counted in the numbering. For example, if 12345 is replaced, the new Name would be 12345v2 (comparable to 12345b earlier) and if 12345b is replaced, its new Name would be 12345v3 (comparable to 12345c earlier). If the "b" originated from other sources than replacement, then it needs to be kept; 12345bv2.

I don't even know what would happen currently if an abc item other than b-replacement needs to have its origin fixed - would just a random letter be chosen or would it become two letters.

If we wanted to, we could have a script convert all b-files with a history comment containing "created b replacement file" to follow the new convention, but that would add a lot of obsoleted files to the library for no good reason. Therefore, I'd just follow the new convention for new files, knowing that some day, sooner than with earlier conventions, all of the library will follow the rules.
Reply
« Next Oldest | Next Newest »



Messages In This Thread
Part versioning - by Peter Blomberg - 2025-09-06, 2:37
RE: Part versioning - by Philippe Hurbain - 2025-09-06, 7:25
RE: Part versioning - by Orion Pobursky - 2025-09-06, 17:02
RE: Part versioning - by Chris Böhnke - 2025-09-06, 23:30
RE: Part versioning - by Peter Blomberg - 2025-09-07, 4:56

Forum Jump:


Users browsing this thread: 2 Guest(s)