I decided to create a new project on sourceforge: The LD Part Editor - A pure part editor.
Basically it will be a java SWT / JFace / OpenGL offline rich client.
I had to introduce the *.lpc file format for the LD Pattern Creator and I do not plan to use another new file format for the editor (e.g. *.lpe). The im- and export should use the native *.dat file standard.
30367b Brick, Round 2 x 2 Dome Top - Blocked Open Stud with Bottom Axle Holder x Shape + Orientation
30367c Brick, Round 2 x 2 Dome Top - Hollow Stud with Bottom Axle Holder x Shape + Orientation
I don't need c right now, but if someone works on b it should be easy to make c as well.
Also the patternable top face needs to go down until directly over the studs. The new R2 patterns go down that far, and the new ones all use 30367b, so no need to rework the top face of 30367.dat. Also we should rename 30367 to 30367a like we did with the cylinder 2 x 2 x 2.
I want to go live with the new LDraw.org website soon. I can't get rid of the old site since the PT still relies on it but I want to elicit thoughts on what main features should be in place before the switchover.
Since Tim Gould has been working on revising mklist, I'm curious what modern LDraw programs actually rely on mklist. The only one I can think of off the top of my head is MLCad.
I'd like to answer that question with my reasoning here.
The reason behind creating these shortcuts was that when building models,
I again and again found myself in 2 actions:
(a) searching the matching tyre for a wheel (because in MLCad all parts get scaled in the parts library preview, so all wheels and tyres look the same size)
(b) after I had found them, I to each model added a "wheel+tyre" assembly submodel
After having done this some times, I was asking myself why the assembly of (b)
was not part of the library.
Of course, the answer is: avoid clutter. As some wheels can carry different tyres, a combinatoric explosion
might occur. This prevented me some time from creating these shortcuts.
I then discovered that e.g. SR3DBuilder contains a separate database for this purpose: "TireManager.txt" (see attachment).
It is a simple text file which lists wheels plus their matching tyres.
When I saw that, I felt reminded of the discussion about 2 other things:
(i) alias part numbers
(ii) physical color shortcuts
There, the discussion was just the same: should we track this data somewhere?
The discussion about these 2 mainly went like this at those times:
First, an agreement was achieved that this information is quite valuable and needs to be stored somewhere.
The initial idea then was to have a separate database.
It then turned out that that separate database was nothing else than simple redirections
of part number to other part numbers, or of part numbers plus a certain color to other part numbers.
Then the question arose why we would create all the effort to maintain tooling etc. for a separate database,
when the existing mechanisms (i.e., LDRAW lines of type "1", part usage) would do everything we need.
Voila, a prefix was added to easily distinguish these files, and later, even an !LDRAW_ORG header type was added
(which I consider even better), and that was it. I find this solution very elegant, as it is self-contained and does
not add a secondary database.
When I remembered that, I felt that at least for the "usual" wheel+tyre assemblies, i.e., such that occur
in official LEGO models, we should have these shortcuts, basically for the same reasoning:
there is only a limited number of combinations possible, and that number is not too high:
SR3DBuilder's text file for example currently counts 165 such combinations.
Another disadvantage of that file is that it only lists matching part numbers, but it does not carry
information about the offset and orientation, and the color of the tyre. In fact, that text file is a stripped-down
instance of an LDRAW line type "1" (part usage), but without positioning, matrix and coloring element.
I felt that being a loss, and a step backward behind what our library already can do.
And I felt that these combinations should not be a private detail of tool SR3DBuilder, but of the library itself.
I cannot really see the "clutter" argument, as the number of these assemblies will be small, compared
to the plenty of physical color shortcut files we already have.
To make a long story short:
I would very much like to have these shortcuts in our library, at least for the wheel+tyre combinations
that occured in official LEGO models.
The tread list in the old parts request topic was getting way too big. I've created a now Part Request forum while Chris Dee works on a parts requestor system. I moved the old part request thread there and split it based on the top level threads in the tree.
