To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 9419
9418  |  9420
Subject: 
Change to existing policy on embedding POV-Ray code in Official Files
Newsgroups: 
lugnet.cad.dev, lugnet.cad
Followup-To: 
lugnet.cad.dev
Date: 
Mon, 19 Jan 2004 21:46:58 GMT
Viewed: 
2173 times
  
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.

Note that this restriction would only apply to Official Parts Library Files and
not to the LDraw File Format as a whole.  We are discussing the official
recognition of seperate libraries that define LDraw parts in various 3D formats.
These libraries would not be distributed with the LDraw base package but would
be offered as a downloadable add-on.

Before we make a final decision regarding this matter, we would like to open
this discussion up to the LDraw community as a whole.  Please be constructive
with your comments.

- The LSC



Message has 6 Replies:
  Re: Change to existing policy on embedding POV-Ray code in Official Files
 
(...) Could you give a bit more info on the compatability issues (or a pointer to where they're discussed)? (20 years ago, 19-Jan-04, to lugnet.cad.dev)
  Re: Change to existing policy on embedding POV-Ray code in Official Files
 
(...) Yay! The right place for POV code is in external libraries. Does this mean (URL) is going to be developed? Is a new L3P release in the works? It's been over a year and a half since this tantalizing message was posted. :^) (URL) Don (20 years ago, 19-Jan-04, to lugnet.cad.dev)
  Re: Change to existing policy on embedding POV-Ray code in Official Files
 
(...) Too sad. If I got that complicated language correcly, this means that the problem presented at (URL) and was solved by embedded POV-code has now regressed to be un-solved again. /Tore (20 years ago, 20-Jan-04, to lugnet.cad.dev)
  Re: Change to existing policy on embedding POV-Ray code in Official Files
 
(...) this is exactly what I was hoping for. w. (20 years ago, 27-Jan-04, to lugnet.cad.dev)
  Re: Change to existing policy on embedding POV-Ray code in Official Files
 
(...) Since I've contributed exactly two official parts to the LDraw library (neither of them with inlined POV-Ray code), I'm sure that my opinion carries more weight than anyone's on the subject... :) For some time it has been argued that the use (...) (17 years ago, 2-Jul-07, to lugnet.cad.dev)
  Re: Change to existing policy on embedding POV-Ray code in Official Files
 
(...) Hello All, First I am no part designer but reading through this discussion I got an idea that might be interesting to share. First I think Orion is right with his stand to not allow povcode because of the 'why only pov-ray' argument. So I was (...) (17 years ago, 2-Jul-07, to lugnet.cad.dev)

27 Messages in This Thread:












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

Custom Search

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