| |
Hi,
I'm the author of SR 3D Builder and I was thinking that the update were
including part corrections and fixes at least for the official parts, but I
understand that is a huge work.
Since my appl loads the whole part library to build images for all parts, it's
easy for me to find bad lines.
Here are some other personal consideration about part library:
- as I have already told in a previous post in this subject I don't think it's a
good idea to include optional parts in the installation of the update since this
can cause people not installing them cannot load some model.
- Personally I dislike pre-colored parts because they are not useful since you
can change the color of any base part and can generate confusion in newbie.
- "official parts" should be removed from "unofficial parts" library. This is
currently making a lot of confusion in choosing parts
- last and most IMPORTANT: If anyone has the time to translate part description
and put them in a separate file (in the format "PartFileName (TAB)
"PartDescription") for each language, I can make my application load this
translation without having to change part definition. This is a great step
forward for everybody
Please let me know your opinion
In lugnet.cad, Chris Dee wrote:
> In lugnet.cad, Philippe Hurbain wrote:
> > In lugnet.cad, Sergio Reano wrote:
> > > Attention please:
> > > Part 32172.dat has incomplete last line. Fix it
> >
> > You are right, the file is truncated. But this mistake is not recent, it already
> > appeared in LDraw.org Parts Update 2003-02
> > (http://www.ldraw.org/library/updates/lcad0302.zip). A corrected version is now
> > on PT (http://www.ldraw.org/cgi-bin/ptdetail.cgi?s=32172)
> > >
> > > Also part 4220.dat has TAB char separator instead of spaces...
> >
> > This is not a problem, "The whitespace characters allowed for keyword and
> > parameter separation include spaces and tabs." (see
> > http://www.ldraw.org/Article218.html#files)
>
> No changes were made to the content of the part files in 2008-01. This was
> purely a header standardisation exercise, although minor changes were made to
> part descriptions as part of this.
>
> Chris
|
|
| |
In lugnet.cad, Sergio Reano wrote:
> - "official parts" should be removed from "unofficial parts" library. This is
> currently making a lot of confusion in choosing parts
That has always happened in the past, and will presumably happen with the next
update. The parts tracker "unofficial parts library" only contains new
(unreleased) files and that have been modified since the last update. This
update was different, since it was just a header change and cleanup of the
previous one, so no parts were removed from the parts tracker. ("Just" in the
previous sentence wasn't meant to indicate the amount of effort involved, but to
show that no new or update files from the tracker were included.) When the
certified files on the tracker are put into the next update, they will be
removed from the tracker.
--Travis
|
|
| |
> When the
> certified files on the tracker are put into the next update, they will be
> removed from the tracker.
And they may come back on Tracker as a new version when an author improves an
already certified part. So often you have to deal with two version of the same
part, one official and one (improved) on PT.
Philo
|
|
| |
In lugnet.cad, Philippe Hurbain wrote:
> > When the
> > certified files on the tracker are put into the next update, they will be
> > removed from the tracker.
>
> And they may come back on Tracker as a new version when an author improves an
> already certified part. So often you have to deal with two version of the same
> part, one official and one (improved) on PT.
>
> Philo
The suggestion that fixes to already released official parts should not be in
the unofficial library download
(<http://www.ldraw.org/library/unofficial/ldrawunf.zip>) seems reasonable at
first reading, but we need to consider the wider implications.
For example, consider the following scenario: An officially released subpart is
changed (for example to move the stud definitions back up into the parent part
to prevent reflected logos) and all the impacted official parts files are fixed
and uploaded to the Parts Tracker. The revised subfile is then found to be
useful for a new part, which is posted to the Parts Tracker. If the unofficial
download does not include the revised subfile, then the new part will be
incorrectly rendered. If it does include the revised subfile, then it should
also include all the revised parent parts.
These kinds of dependencies get straightened out as part of the update release
process, so we would only issue the updated subfile if it and all its parents
were certified, but it highlights the folly of trying to use only part of the
unofficial libray.
I am concerned if there is widespread use of parts from the unofficial library,
and I would recommend that applications do not automatically perform a wholesale
download of the unofficial library.
The most obvious answer to this is clearly faster turnaround of fixes in more
frequent parts updates. We are working on that and thank you for your continued
patience.
Chris
|
|
| |
In lugnet.cad, Willy Tschager wrote:
> In lugnet.cad, Sergio Reano wrote:
>
> Hi Sergio,
>
> > - last and most IMPORTANT: If anyone has the time to translate part description
> > and put them in a separate file (in the format "PartFileName (TAB)
> > "PartDescription") for each language, I can make my application load this
> > translation without having to change part definition. This is a great step
> > forward for everybody
>
> This has been on the LSCs laundry list for a very long time:
>
> http://news.lugnet.com/cad/dev/org/ldraw/?n=3470&t=i&v=a
> http://news.lugnet.com/cad/dev/?n=10294&t=i&v=a
>
> and they even have a draft written by Jacob:
>
> http://five.pairlist.net/pipermail/lsc/2005-March/000335.html
>
> but if I remember correctly all the 1.0.0 and header stuff got into the way.
>
> w.
Hi Willy,
I don't want to make my approach too simplistic, but if you try using my
program, it automatically creates a file called Parts00.lst in lDraw folder.
If anyone can translate it in any language and we choose a SIMPLE naming
Convention with no strange metacommand or anything else (For example
Part-IT.lst, Part-EN.lst, Part-XX.lst) then my application can open this
translated file for parts description and use them.
Note that it is not necessary to translate ALL part names (even if it is Highly
recommended): if the application finds the translations it uses them, otherwise
use native english ones.
IMPO, translating part name only it would be a great help anyway, even if
associated keywords are still not.
Byes
Sergio
|
|
|
