|
 |
I've been thinking that some form of Pov Manager utility would be a fun
programming project. This would be a multipurpose utility for viewing and
changing multiple Pov-Ray files. It would be sort of a mish mash of useful
things. Examples of things it might include could be a settings viewer and
changer, this would allow you to view and change global settings in your pov
files at a glance, various colour utilities, other miscellaneous things I
can't think of right now. This might be a little beyond me now so don't
expect anything soon, but if your interested please offer feature
suggestions and comments. Think of it as a kind of TweakUI/Batch
Processor/Windows Explorer for Pov files. Anyone interested?
--
----------------------------------------------------------------------------
-----------
Home Page: http://www.geocities.com/~thomaslake/
----------------------------------------------------------------------------
-----------
Post a reply to this message
|
|
|
|
"Thomas Lake" <tla### [at] REMOVE-THISshaw ca> wrote in message
news:3cd667e0@news.povray.org...
> I've been thinking that some form of Pov Manager utility would be a fun
> programming project.
Hmmm... you would need to parse the whole file and I can't see how it
would support animation, but otherwise a cool idea. I'm thinking you would
have a kind of forms layout that had camera positions, light values and
object lists with color wheels or sliders. Difficult.
I usually readjust my variables declarations to accomodate whatever it
is I am trying to tweak at the time, but sometimes it would be nice to have
it all on one page...
Post a reply to this message
|
|
|
|
> Hmmm... you would need to parse the whole file and I can't see how it
> would support animation, but otherwise a cool idea. I'm thinking you would
> have a kind of forms layout that had camera positions, light values and
> object lists with color wheels or sliders. Difficult.
Difficult, definetly. But as for parsing the whole file I don't think I
would have to All I would need to do is parse the file for the specific
features I impliment. No need to parse for julia fractals if I have no
support for them.
> I usually readjust my variables declarations to accomodate whatever it
> is I am trying to tweak at the time, but sometimes it would be nice to
have
> it all on one page...
The problem I see with it is that a lot, if not most, people make use of the
great flexibility of the Pov-Ray scripting language, so instead of finding a
simple floating point number for any given feature I'm just as likely to
find a variable name or a complex function.
Post a reply to this message
|
|
