 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I want to be able to describe a bunch of objects(walls, windows, doors in
a set of rooms) as a series lines of data. Then I want to do have
features like have each object's name be automatically generated from its
data, use some data form a previous defined new object and use defaults
etc. My question is of implementation, is this something I should try
coding up in POV-RAY, or should I brush up on my Perl or try Python to
write a preprocessor to generate a POV-RAY code file?
Rick
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rick Berger wrote:
> My question is of implementation, is this something I should try
> coding up in POV-RAY, or should I brush up on my Perl or try Python to
> write a preprocessor to generate a POV-RAY code file?
You might want to look at the LOME project on sourceforge. That's just what
it does.
--
Darren New, San Diego CA, USA (PST)
The NFL should go international. I'd pay to
see the Detroit Lions vs the Roman Catholics.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rick Berger" <rbe### [at] rogers com> wrote in message
news:494c0f6e$1@news.povray.org...
>I want to be able to describe a bunch of objects(walls, windows, doors in
> a set of rooms) as a series lines of data. Then I want to do have
> features like have each object's name be automatically generated from its
> data, use some data form a previous defined new object and use defaults
> etc. My question is of implementation, is this something I should try
> coding up in POV-RAY, or should I brush up on my Perl or try Python to
> write a preprocessor to generate a POV-RAY code file?
>
> Rick
You might also want to look at povhouse at
http://www.geocities.com/povstairs/povhouse/ . It takes a floor plan (with
doors windows, columns, floors, ceilings etc) drawn in the free InkScape
vector graphics editor. You name each element in InkScape and export as a
POV-Ray include file. The POV-House macros take the exported prism objects
and renders a 3D building.
It might provide a starting point for what you want to do, or may serve as
an example or inspiration.
Regards,
Chris B.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 19 Dec 2008 13:48:52 -0800, Darren New wrote:
> Rick Berger wrote:
>> My question is of implementation, is this something I should try coding
>> up in POV-RAY, or should I brush up on my Perl or try Python to write a
>> preprocessor to generate a POV-RAY code file?
>
> You might want to look at the LOME project on sourceforge. That's just
> what it does.
Thanks Darren, unfortunately it's implemented in C# and I haven't explore
deploying C# applications in an UNIX/Linux environment. I think I'd be in
for more work than I want in trying to port LOME over, if anybody
comments on this or other approaches it would interesting to hear them.
Rick
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rick Berger wrote:
> Thanks Darren, unfortunately it's implemented in C# and I haven't explore
> deploying C# applications in an UNIX/Linux environment. I think I'd be in
> for more work than I want in trying to port LOME over,
Well, I don't know how much work you're talking about. I just copied the
MacroExpanderExec directory over to my Linux partition, opened a terminal in
the Debug subdirectory, and typed
% mono FCCS.CLI.exe hello
and it processed the (nonexistent) files correctly.
So chances are good you don't even have to recompile it. (This is on
OpenSuSE 11 x64, so I'd expect it would work for you too.)
You might have to grope into the macros, because they generate .bat files
for doing the renders as part of the expansion, since the Windows "job
queue" thing couldn't handle it, due to being too small. But other than
that, if you want to manually render the generated .INI files, go for it.
--
Darren New, San Diego CA, USA (PST)
The NFL should go international. I'd pay to
see the Detroit Lions vs the Roman Catholics.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
