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 / 9092
9091  |  9093
Subject: 
Re: Repository of .dat files with inline POV-Ray code... any interest?
Newsgroups: 
lugnet.cad.dev
Date: 
Tue, 29 Jul 2003 20:35:16 GMT
Viewed: 
4087 times
  
In lugnet.cad.dev, Tony Hafner wrote:
> In lugnet.cad.dev, Steve Bliss wrote:
> > In lugnet.cad.dev, Tony Hafner wrote:
> > 
> > > What's the current plan for POV-Ray code in official parts?  I have
> > > been out of the loop for a while, but my last understanding was that
> > > parts with inline POV-Ray code don't have any chance of getting
> > > certified on the parts tracker.  Is this still the case?
> > 
> > Yes, it's pretty much still the case.  I would really prefer to not
> > have any POV code in the parts library at all.  But if there must be
> > some, I think it should stay in the primitive files.
> > 
> > > I am specifically referring to cases where primitive substitution
> > > causes gaps around curved surfaces.  The ldraw code looks fine in
> > > the usual tools (ldraw, MLCAD, L3Lab), and the extra code makes the
> > > parts render without gaps in POV-Ray.
> > 
> > I think a better solution is to work on POV versions of part files.
> > Generally, writing POV code is easier than LDraw code.  So if you
> > can make an LDraw version of a file, you can make a POV version.
> 
> Okay... then I'd like to open this up to a question for the community:
> 
> Is anyone interested in working on a single shared repository of
> ldraw-compatible parts with inlined POV-Ray code?  How many authors out there
> are comfortable with both POV-Ray and ldraw code and interested in this?
> 
> I'm picturing files that are essentially official parts with some added inline
> code.  And when ldraw releases updates, we'd attempt to POV-Ray fix all parts
> that need it and we'd update all of the POV-Ray parts with the new ldraw code
> when parts are officially re-released.  The deliverables would be parts
> downloads similar to the official releases, and a user would just install this
> over the official release.
> 
> Note that a good number of parts could be fixed with just a line or two of code
> and some new primitives.  Imagine a primitive that is a true disc minus a
> 16-segment disc- how many parts would that fix?  20?  More?
> 
> And if we did this, could ldraw.org host the downloads?  I doubt that I could
> afford the bandwidth to host them on my site for very long.
> 
> --
> Tony Hafner
> www.hafhead.com

Why not just a library of POV code only parts, ala LGEO/Raves, only compatible
with the LDraw.org library?  We could host this project on Sourceforge so anyone
who was interested could develop.  I think if we do it Pov only, LDraw.org is
more likely to offically recognize our efforts

-Orion



Message has 1 Reply:
  Re: Repository of .dat files with inline POV-Ray code... any interest?
 
(...) Because parts with inline POV code work with the version of L3P that we have now. Why not start by building a library of modified official parts, but with the explicit goal of eventually converting them into POV only parts when L3P or some (...) (23 years ago, 29-Jul-03, to lugnet.cad.dev)

Message is in Reply To:
  Repository of .dat files with inline POV-Ray code... any interest?
 
(...) Okay... then I'd like to open this up to a question for the community: Is anyone interested in working on a single shared repository of ldraw-compatible parts with inlined POV-Ray code? How many authors out there are comfortable with both (...) (23 years ago, 29-Jul-03, to lugnet.cad.dev)

18 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
    

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