Am 22.09.2016 um 17:29 schrieb LanuHum:

> We will need the sample files from all types of objects that can be created on
> Bishop export. All modifiers, media{}, photons{}, interior{} and so on.
> We need to learn how to Bishop writes the text: where to put spaces and line
> transfers.

Uh... no, actually you need to generally learn the intricate details of
POV-Ray's scene description language. Because you certainly don't want
to limit your importer to POV files created by Bishop3D.

Oh, the fun you'll have! ;)

Post a reply to this message

Stephen <mca### [at] aolcom> wrote:
>
> I think we should start an new thread and not hijack this one any more.
>
>
> --
>
> Regards
>      Stephen

We are with you, it does not help. :)
You did not understand anything. I help Mr, but I need .pov files with different
styles of writing. I do not need your importer-exporter.
:)(:

Post a reply to this message

On 9/22/2016 6:17 PM, LanuHum wrote:
> Stephen <mca### [at] aolcom> wrote:
>>
>> I think we should start an new thread and not hijack this one any more.
>>
>>
>> --
>>
>> Regards
>>       Stephen
>
> We are with you, it does not help. :)
> You did not understand anything.

But who but the enlightened, understand anything?

> I help Mr, but I need .pov files with different
> styles of writing. I do not need your importer-exporter.
> :)(:
>
>

I know.
It will be done.

-- 

Regards
     Stephen

Post a reply to this message

On 9/22/2016 6:05 PM, clipka wrote:
> Am 22.09.2016 um 17:29 schrieb LanuHum:
>
>> We will need the sample files from all types of objects that can be created on
>> Bishop export. All modifiers, media{}, photons{}, interior{} and so on.
>> We need to learn how to Bishop writes the text: where to put spaces and line
>> transfers.
>
> Uh... no, actually you need to generally learn the intricate details of
> POV-Ray's scene description language. Because you certainly don't want
> to limit your importer to POV files created by Bishop3D.
>

It is a start.

> Oh, the fun you'll have! ;)
>

With me helping. It is guaranteed. ;-)


-- 

Regards
     Stephen

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 22.09.2016 um 17:29 schrieb LanuHum:
>
> > We will need the sample files from all types of objects that can be created on
> > Bishop export. All modifiers, media{}, photons{}, interior{} and so on.
> > We need to learn how to Bishop writes the text: where to put spaces and line
> > transfers.
>
> Uh... no, actually you need to generally learn the intricate details of
> POV-Ray's scene description language. Because you certainly don't want
> to limit your importer to POV files created by Bishop3D.
>
> Oh, the fun you'll have! ;)

I see.
The problem of parsing the scene that you allow the user to wear underpants on
his head. :))))))))))))
Your SDL encourages mess.
But nor is it terrible. There is no desire to write when no one needs.
..pov file can be easily read using python, but it will take a lot of work

Post a reply to this message

On 9/22/2016 6:54 PM, LanuHum wrote:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 22.09.2016 um 17:29 schrieb LanuHum:
>>
>>> We will need the sample files from all types of objects that can be created on
>>> Bishop export. All modifiers, media{}, photons{}, interior{} and so on.
>>> We need to learn how to Bishop writes the text: where to put spaces and line
>>> transfers.
>>
>> Uh... no, actually you need to generally learn the intricate details of
>> POV-Ray's scene description language. Because you certainly don't want
>> to limit your importer to POV files created by Bishop3D.
>>
>> Oh, the fun you'll have! ;)
>
> I see.
> The problem of parsing the scene that you allow the user to wear underpants on
> his head. :))))))))))))

Some users do not have underpants to wear. ;)
Some only want to point and click.

That is who mostly use modellers.


> Your SDL encourages mess.
> But nor is it terrible. There is no desire to write when no one needs.
> ...pov file can be easily read using python, but it will take a lot of work
>

It is a template, yes?
It is not for me to criticise what I cannot do myself.



-- 

Regards
     Stephen

Post a reply to this message

Stephen <mca### [at] aolcom> wrote:
> On 9/22/2016 6:05 PM, clipka wrote:
> > Am 22.09.2016 um 17:29 schrieb LanuHum:
> >
> >> We will need the sample files from all types of objects that can be created on
> >> Bishop export. All modifiers, media{}, photons{}, interior{} and so on.
> >> We need to learn how to Bishop writes the text: where to put spaces and line
> >> transfers.
> >
> > Uh... no, actually you need to generally learn the intricate details of
> > POV-Ray's scene description language. Because you certainly don't want
> > to limit your importer to POV files created by Bishop3D.
> >
>
> It is a start.
>
> > Oh, the fun you'll have! ;)
> >
>
> With me helping. It is guaranteed. ;-)
>
>
> --
>
> Regards
>      Stephen

:)))))

Post a reply to this message

Stephen <mca### [at] aolcom> wrote:
> On 9/22/2016 6:54 PM, LanuHum wrote:
> > clipka <ano### [at] anonymousorg> wrote:
> >> Am 22.09.2016 um 17:29 schrieb LanuHum:
> >>
> >>> We will need the sample files from all types of objects that can be created on
> >>> Bishop export. All modifiers, media{}, photons{}, interior{} and so on.
> >>> We need to learn how to Bishop writes the text: where to put spaces and line
> >>> transfers.
> >>
> >> Uh... no, actually you need to generally learn the intricate details of
> >> POV-Ray's scene description language. Because you certainly don't want
> >> to limit your importer to POV files created by Bishop3D.
> >>
> >> Oh, the fun you'll have! ;)
> >
> > I see.
> > The problem of parsing the scene that you allow the user to wear underpants on
> > his head. :))))))))))))
>
> Some users do not have underpants to wear. ;)
> Some only want to point and click.
>
> That is who mostly use modellers.
>

If you are working only with the mouse, the program creates the standard file in
a style that is easy to handle.

#declare CoPigment = pigment{granite color_map{...}}
#declare CoNormal = normal{granite 1 normal_map{...}}
#declare CoFinish = finish{brilliance 2 ...}
#declare Concrete = texture{pigment{CoPigment}normal{CoNormal}finish{CoFinish}}
#declare Spheroid = sphere{0,1 texture{Concrete}}
object {Spheroid}

This order and the well-read


>
> > Your SDL encourages mess.
> > But nor is it terrible. There is no desire to write when no one needs.
> > ...pov file can be easily read using python, but it will take a lot of work
> >
>
> It is a template, yes?
> It is not for me to criticise what I cannot do myself.
>

If the user writes himself, he does so:

sphere {0,
    1 texture{pigment{granite

color_map{...}}normal{granite 1
                      normal_map{...}}finish{

brilliance 2
......}
   }
}

Then the user writes here:
Lanuhum!Your importer does not work!
Povray does not find an error!!!
:)))))))

To read such a mess with no errors in the Povray written source code parser
almost the size of one megabyte!!!!!!!

Post a reply to this message

On 9/22/2016 8:00 PM, LanuHum wrote:
> Stephen <mca### [at] aolcom> wrote:
>> On 9/22/2016 6:54 PM, LanuHum wrote:
>>> clipka <ano### [at] anonymousorg> wrote:
>>>> Am 22.09.2016 um 17:29 schrieb LanuHum:

I am not comfortable hijacking this thread. It is bad manners to the 
original poster and it deserves a thread of its own.
I am not comfortable discussing it in this detail when I am not part of 
your group. No one wants an outside busybody telling them what to do.

And as they say in the SAP world. If there is only one way to do it. 
Then you are doing it wrong.


-- 

Regards
     Stephen

Post a reply to this message

On 9/20/2016 10:13 PM, lelama wrote:
> Hi,
> I am looking for an interactive viewer "a la Blender".
>
> Something very simple...

24 posts later. I wish I had just said. No I don't think there is.
Because I have not heard of any and I am looking for one too, Windoze 
though.



-- 

Regards
     Stephen

Post a reply to this message