home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.graphics:11788 comp.graphics.animation:993 comp.sys.amiga.graphics:7369
- Newsgroups: comp.graphics,comp.graphics.animation,comp.sys.amiga.graphics
- Path: sparky!uunet!think.com!ames!agate!doc.ic.ac.uk!daresbury!gzc
- From: g.coulter@daresbury.ac.uk (Gary.C)
- Subject: RayTrace Script Language Definition
- Message-ID: <1992Nov12.133922.4577@gserv1.dl.ac.uk>
- Reply-To: g.coulter@daresbury.ac.uk
- Organization: Daresbury Laboratory, UK
- Date: Thu, 12 Nov 1992 13:39:22 GMT
- Lines: 40
-
- Hi Everyone .. ( Not to sure if I have sent this to the right place,
- in fact I don't think there is a right place for this)
-
- As you may have read already I am trying to gather some information
- regarding the writing of a GUI for the well Known & used raytracers
- such as POV, Rayshade & Radiance.
-
- What I want to do is implement my own standard script language that I
- can easily generate using the GUI. Once generated I want to convert the
- script into the script language of the target raytracer ie POV. I
- initially want to do this for only one raytracer ie POV, but in the end
- I need a way of selecting which raytracer script format to generate.
-
- Not having done anything like language definition and parsing before I
- was hoping that someone out there could point me in the right direction.
-
- (1)
-
- Is there already any source code out there to convert from one raytracer's
- script to another that I could look at. Just to give me an idea as to how to
- do this.
-
- (2)
-
- Should I write a BNF Formal language specification and then use a technique
- such as recursive decent to evaluate the source script and then generate
- the destination script.
-
- (3)
-
- Anyone elses thoughts and Ideas on this would be very helpfull. There are
- probably lots of ways of doing this, its just a case of finding the best
- one.
-
- Thank You For any help & for sparing the time to write back.
-
- Gary
-
-
-
-