 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Morpheus Dreamlord <mor### [at] mailexcite com> wrote:
: Ok, so who cares about 1 person not using a program....but I won't be
: changing my mind about this....
There are 2 persons not using the program. My reason is that the original
author is going to make it a win95-only program.
--
- Warp. -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If you write the program in c/c++ it is fairly easy to port to other
machines. If you really want portability then write the program in java.
If you write it in java (which is a language similar to c++) then just the
one copy of the prog will run on any java capable machine or os.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
HeHe, I noticed that soon afterwards.. Seems by battries are going on the blink..
Thomas Charron
Alain CULOS wrote:
> This message is really intended for Thomas Charron :
>
> Could you please set up your computer date to be near reality (1998, not 1997) as
> my automatic newsgroup reader will not download 'old' messages (20 days) and I do
> not really want to be searching for each such message manually or set the date span
> to more than 20 days.
>
> Regards,
> Al.
>
> --
> ANTI SPAM / ANTI ARROSAGE COMMERCIAL :
> To answer me, please take out the Z from my address.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
the feature that i'd most like in a texture editor for povray is one that
can import textures from povray code. From any pov source file or include
file. Another feature i'd like to see is the ability to save a library of
thumbnails associated with textures. it would just save any render of a
texture in the library as a seperate image file. this would make it easy
to browse through textures you've already made without having to wait for
each one to render to see what it looks like.
Tim Burton wrote:
> I have been humoring the possibility of creating a texture editor for
> Pov and am wondering if it would be worthwhile and what features people
> would like. I have been using TextureMagic 0.95 and find it to be sadly
> out of date.
>
> Is there a demand for this type of utility, and if so what would people
> like it to have?
>
> Tim Burton
> TBu### [at] ThrtCom
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
On Tue, 21 Jul 1998 19:06:49 -0700, in povray.binaries.utilities you
wrote:
>the feature that i'd most like in a texture editor for povray is one that
>can import textures from povray code. From any pov source file or include
>file. Another feature i'd like to see is the ability to save a library of
>thumbnails associated with textures. it would just save any render of a
>texture in the library as a seperate image file. this would make it easy
>to browse through textures you've already made without having to wait for
>each one to render to see what it looks like.
if you only want to get thumbnails of all POV-Ray textures located on
your harddisk, perhaps my program TextureView (freeware for Windows
95) could help you... take a look at
http://www.rz.fhtw-berlin.de/~s0049669/software.html
Bye,
Friedemann
Friedemann Schmidt
Fri### [at] Stonescom
Raytracing-Gallery: http://www.rz.fhtw-berlin.de/~s0049669
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bret Slivka wrote:
>
> the feature that i'd most like in a texture editor for povray is one that
> can import textures from povray code. From any pov source file or include
> file.
I don't think this is at all easy to implement. With the possibility of
includes, file i/o, macros, and texture assignments to variables and
arrays, it would be extremely difficult to extract textures without basically
parsing the entire source.
Dan
--
http://www.flash.net/~djconnel/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dan Connelly wrote:
> Bret Slivka wrote:
> >
> > the feature that i'd most like in a texture editor for povray is one that
> > can import textures from povray code. From any pov source file or include
> > file.
>
> I don't think this is at all easy to implement. With the possibility of
> includes, file i/o, macros, and texture assignments to variables and
> arrays, it would be extremely difficult to extract textures without basically
> parsing the entire source.
>
> Dan
TextureView by Friedemann Schmidt does an excellent job on any
#declared texture in any standard pov file. Although it doesn't preview
textures inside of the body of an object statement it does a great job of
allowing you to search entire directories for #decalred textures and gives
you a choice to render each texture into a thumbnail view with pov as the
rendering engine. This ensures that what you see is what you get. As far as
the difficulty of texture extraction when it does it's directory search for
textures
it searches only for declarations of textures and ignores the rest of the pov
code.
After doing a search of my main include directory which is very extinsive by the
way it came back in about 4 min. with 1200 textures. Pretty impressive if you ask
me.
K.Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I can see the problem though, I often use calculated values in colour_maps
for example to animate textures. This would be a bit of a trick to parse.
Also which texture do you render, the one at clock=0.0 or clock=0.5 or....
Gordon
<gbe### [at] birdcameroncomau>
K. Tyler wrote in message <35C2E5BD.3551F37A@pacbell.net>...
>Dan Connelly wrote:
>
>> Bret Slivka wrote:
>> >
>> > the feature that i'd most like in a texture editor for povray is one
that
>> > can import textures from povray code. From any pov source file or
include
>> > file.
>>
>> I don't think this is at all easy to implement. With the possibility of
>> includes, file i/o, macros, and texture assignments to variables and
>> arrays, it would be extremely difficult to extract textures without
basically
>> parsing the entire source.
>>
>> Dan
>
>TextureView by Friedemann Schmidt does an excellent job on any
>#declared texture in any standard pov file. Although it doesn't preview
>textures inside of the body of an object statement it does a great job of
>allowing you to search entire directories for #decalred textures and gives
>you a choice to render each texture into a thumbnail view with pov as the
>rendering engine. This ensures that what you see is what you get. As far as
>the difficulty of texture extraction when it does it's directory search for
>textures
>it searches only for declarations of textures and ignores the rest of the
pov
>code.
>After doing a search of my main include directory which is very extinsive
by the
>way it came back in about 4 min. with 1200 textures. Pretty impressive if
you ask
>me.
>
>K.Tyler
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
