Subject:
|
Re: Change to existing policy on embedding POV-Ray code in Official Files
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Mon, 19 Jan 2004 22:40:00 GMT
|
Viewed:
|
2722 times
|
| |
|
|
In lugnet.cad.dev, Orion Pobursky wrote:
> In lugnet.cad.dev, Larry Pieniazek wrote:
> > In lugnet.cad.dev, Orion Pobursky wrote:
> > > The LDraw.org Standards Committee (LSC) has recently discussed the issue of
> > > embedded POV-Ray code in Official Parts Library files. After careful
> > > consideration and with inputs from leading non-LSC members, most notably Lars
> > > Hassing and Chris Dee, we have agreed that the inclusion of this code is
> > > undesirable.
> > >
> > > Our main reasoning behind this conclusion is outlined below is that the
> > > inclusion of POV-Ray code locks the Official Library into a standard beyond the
> > > control of the LSC. The intermixing of language formats creates backwards
> > > compatiblity issues that are too large to ignore.
> >
> > Could you give a bit more info on the compatability issues (or a pointer to
> > where they're discussed)?
>
> Basically,
>
> The POV team controls the syntax, functionality, and implementation of the
> POV-Ray Scene Description Language (P-R SDL) format. While the POV Team is very
> good at maintaining backwards compatibility, they have in the past change the
> functionality of or depreciated some the commands. Since we, the LSC, have no
> input on how or when changes to this format occur this creates the potential for
> a discongruity between the LDraw Official Parts Library and the P-R SDL. This
> discongruity could effect 1 part or every part in the library leading to a
> massive effort to bring the Official Library back into alignment with the P-R
> SDL. This best solution to prevent this and to allow for POV Code descriptions
> of the Official Library is to disallow the inclusion of P-R SDL code in the
> Official Library and establish a separate library for the P-R SDL code.
OK, but whether or not the P-R SDL code was out of whack would not affect the
usability of parts as parts within LDraw format programs themselves, right?
(0)Only affect the accuracy or completeness or error state of transformation (by
tools such as L3P after enhancement of whatever) to P-R SDL renderable models,
right?
If there is a separate library, would it be a duplication of the base library or
would it include the base library parts (via inclusion) plus addons or ??
This may all be ground that was covered in your internal discussions and
everyone's time might be better spent just doing their homework on the nuances
instead of asking you to recap (although if you don't mind, please go ahead, and
thank you!)...
Per the LSC charter, as I understood it:
"The LSC shall have a mailing list or other communication method where only
members can post to, but the
entire community can read. This allows the community to keep tabs on what is
being discussed, and discuss LSC issues in public forums such as LUGNET's
CAD.* groups. The LSC should encourage this discussion, and should draw
ideas and suggestions from non-LSC members in the community, ensuring
everyone's voice is heard. However, the LSC shall be the only group that
votes to ratify a proposal as a standard."
Orion, would you be kind enough to remind the LUGNET readership of the URL to
the archive view of that mailing list? (or correct my misremembering, that cite
is from the .99 draft... whoever is curator for cad.dev(1) perhaps ought to link
to the final version of the standards committee charter in the forum header
page...)
0 - because the POV stuff would be commented out, and invisible to LDraw format
programs, right?
1 - Steve Bliss is curator of all of /cad/ per
http://news.lugnet.com/admin/curators/curators.cgi as I understand it...
|
|
Message has 2 Replies:
Message is in Reply To:
27 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
|
|
|
|
