Ron Parker <ron### [at] povrayorg> wrote:
: Of course, the Unix version can be redirected to /dev/null and all copyright
: text gets sent to the bit bucket; I don't know of any way to prevent that
: sort of abuse and still provide a command-line version of POV.

  I think this falls into the category "the user is granted the
privilege to modify and compile the source code for their own personal
use in any fashion they see fit."

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

On 24 Nov 2001 11:29:34 -0500, Warp wrote:
> Ron Parker <ron### [at] povrayorg> wrote:
>: Of course, the Unix version can be redirected to /dev/null and all copyright
>: text gets sent to the bit bucket; I don't know of any way to prevent that
>: sort of abuse and still provide a command-line version of POV.
> 
>   I think this falls into the category "the user is granted the
> privilege to modify and compile the source code for their own personal
> use in any fashion they see fit."

What if someone distributes a script that invokes the official POV in such
a way as to conceal the copyright notice?  I think that's sorta covered under
the clauses about linking, but I wonder whether there's a problem there.

-- 
#macro R(P)z+_(P)_(P)_(P+1)_(P+1)+z#end#macro Q(C,T)bicubic_patch{type 1u_steps
6v_steps 6R(1)R(3)R(5)R(7)pigment{rgb z}}#end#macro _(Y)#local X=asc(substr(C,Y
,1))-65;<T+mod(X,4)div(X,4)9>-2#end#macro O(T)Q("ABEFUQWS",T)Q("WSXTLOJN",T)#
end O(0)O(3)Q("JNKLCGCD",0)light_source{x 1}// ron### [at] povrayorg

Post a reply to this message

In article <slr### [at] fwicom> , Ron Parker 
<ron### [at] povrayorg>  wrote:

> What if someone distributes a script that invokes the official POV in such
> a way as to conceal the copyright notice?  I think that's sorta covered under
> the clauses about linking, but I wonder whether there's a problem there.

All this would be covered by the "Any attempt to obscure the fact that the

sections (the commercial and unofficial sections) in povlegal.doc.  So such
a script being distributed together with POV-Ray in form of an unofficial
version or commercial distribution would not be allowed.  Of course only
distributing the script would be legal as the user can do with POV-Ray what
he wants, even obscure the fact that he is running POV-Ray to himself, which
shouldn't be a problem...

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote in news:3bff7942@news.povray.org:

> Coridon Henshaw <che### [at] sympaticoca> wrote:
>: Your best bet here is probably to wait until the 3.5 sources release
>: and then compile a Win32 command-line version using a cut-down DOS
>: front end.  The DOS front end doesn't throw up a splash screen so you
>: can run background renders--completely within the terms of
>: povlegal--without getting splashed. 

>   Just be sure to not to distribute this version.

The result of following my instructions is to port Pov to the Win32 console 
platform.  Win32 console apps cannot generate splash screens.  The only 
requirements in Povlegal for presenting the credits in text-based ports is 
that the credits screen is left intact.  Unless you are arguing that it is 
illegal to port Povray to any command-line platform, I see no reason that a 
Win32 console port would be illegal.

Post a reply to this message

> The result of following my instructions is to port Pov to the Win32
console
> platform.  Win32 console apps cannot generate splash screens.  The only
> requirements in Povlegal for presenting the credits in text-based ports is
> that the credits screen is left intact.  Unless you are arguing that it is
> illegal to port Povray to any command-line platform, I see no reason that
a
> Win32 console port would be illegal.

just get it to echo a the legally required oompf to the console as soon as
it starts


--

Rick

Kitty5 WebDesign - http://Kitty5.com
POV-Ray News & Resources - http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037

PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA

Post a reply to this message

Coridon Henshaw <che### [at] sympaticoca> wrote:
: Win32 console apps cannot generate splash screens.

  Are you sure?

  I think (I'm not 100% sure) that console apps can open windows in the same
way as any other windows program.

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote in news:3c001b78@news.povray.org:

> Coridon Henshaw <che### [at] sympaticoca> wrote:
>: Win32 console apps cannot generate splash screens.
 
> I think (I'm not 100% sure) that console apps can open windows in the
> same  way as any other windows program.

Pretty much by definition any app which creates windows ceases to be a 
console mode app.

Again, are you asserting that it is illegal to port Povray to a text-based 
platform?  (y/n)

Post a reply to this message

On 24 Nov 2001 18:17:58 -0500, che### [at] sympaticoca (Coridon Henshaw)
wrote:

>Again, are you asserting that it is illegal to port Povray to a text-based 
>platform?  (y/n)

It is not, as long as a) the full copyright message is displayed b) it
is clearly stated that it is an unofficial version and the POV Team is
not responsible for this version and c) you take the burden of
supporting it.


Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG      e-mail : pet### [at] tagpovrayorg

Post a reply to this message

Coridon Henshaw <che### [at] sympaticoca> wrote:
: Pretty much by definition any app which creates windows ceases to be a 
: console mode app.

  Not true.
  For example a program could be used from the console, it could read
commands and execute them, etc, and it could open windows for example for
drawing a graph (matlab works this way in X).

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

> Coridon Henshaw <che### [at] sympaticoca> wrote:
> : Pretty much by definition any app which creates windows ceases to be a
> : console mode app.
>
>   Not true.
>   For example a program could be used from the console, it could read
> commands and execute them, etc, and it could open windows for example for
> drawing a graph (matlab works this way in X).

a console app ceases to be a console app when it cannot be run in a console
only environment


--

Rick

Kitty5 WebDesign - http://Kitty5.com
POV-Ray News & Resources - http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037

PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA

Post a reply to this message