To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.dat.parts.primitivesOpen lugnet.cad.dat.parts.primitives in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / LDraw Files / Parts / Primitives / 478
477  |  479
Subject: 
Re: 11-16 primitives?
Newsgroups: 
lugnet.cad.dat.parts.primitives
Date: 
Fri, 25 Sep 2009 18:28:52 GMT
Viewed: 
13447 times
  
In lugnet.cad.dat.parts.primitives, Michael Heidemann wrote:
So my question would be: where is the bottleneck that this is still not solved?

Parts Tracker-wise (if I remember right, and if nothing's been changed), there's
only one script which needs to be modified to accept 21.3 files instead of 8.3
files.

Organizationally, I dunno if there is actually a hold-up.  The specifications
state that the parts library allows file names up to 25 characters long.

One real problem is PARTS.LST.  This file is defined in a fixed-width form,
where the part numbers are only allowed 8 characters.  I believe some programs
(such as MLCAD?) depend on PARTS.LST.  So some backwards-compatible solution
would be needed to shoe-horn 21.3 filenames into the existing PARTS.LST format.

So maybe one of the following:

1) Allow longer filenames for primitives and subparts, but keep parts on the 8.3
standard.  This allows longer filenames where they are more needed, and keeps
the PARTS.LST format working.  An awkward solution, but the easiest to
implement.

2) Forget backwards compatibility, change the format of PARTS.LST.

3) Create another parts list file in an expanded format (maybe tab-delimited?).
For the existing PARTS.LST, leave out parts with long files names.  Truncating
their name to 8 characters is a possibility, but that seems somewhat useless.

Steve



Message has 1 Reply:
  Re: 11-16 primitives?
 
(...) When the LSC updated the spec to allow 21.3 filenames, I don't think any of us were aware that this would create a problem for PARTS.LST. However, looking at the file, there's a chance that MLCAD will work perfectly well with longer filenames (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)

Message is in Reply To:
  Re: 11-16 primitives?
 
(...) This is the status quo now for many months. What action has been taken to solve that problem? To me it seems only to be a little adjustment to some lines of code (but maybe I am wrong). So my question would be: where is the bottleneck that (...) (15 years ago, 25-Sep-09, to lugnet.cad.dat.parts.primitives)

22 Messages in This Thread:




Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR