POV-Ray : Newsgroups : povray.beta-test : Povray Beta34 Server Time
23 Dec 2024 08:52:05 EST (-0500)
  Povray Beta34 (Message 1 to 4 of 4)  
From: mMike
Subject: Povray Beta34
Date: 30 Sep 2009 07:30:00
Message: <web.4ac34108e47c3d5cdc6570b40@news.povray.org>
Now, this beta expires tomorrow! Could it be possible to 'extend' the validity
period of the beta?

I know one could just change the source file, but still, why is the period of
beta-validity so short?

Mike


Post a reply to this message

From: clipka
Subject: Re: Povray Beta34
Date: 30 Sep 2009 08:07:58
Message: <4ac34a1e$1@news.povray.org>
mMike schrieb:
> Now, this beta expires tomorrow! Could it be possible to 'extend' the validity
> period of the beta?
> 
> I know one could just change the source file,

You can even do it without touching the source file. On Windows, that's 
just one lazy mouse click a week. On Linux, it's not much more than 
editing a shell script each week.

 > but still, why is the period of beta-validity so short?

To encourage people to switch over to the next one as soon as it's released.

But it also helps encourage the dev team to release new betas every once 
in a while, so I wouldn't shout too loud for what you're asking for :-P


Post a reply to this message

From: nemesis
Subject: Re: Povray Beta34
Date: 3 Oct 2009 05:36:05
Message: <4ac71b05$1@news.povray.org>
clipka wrote:
> mMike schrieb:
>> Now, this beta expires tomorrow! Could it be possible to 'extend' the 
>> validity
>> period of the beta?
>>
>> I know one could just change the source file,
> 
> You can even do it without touching the source file. On Windows, that's 
> just one lazy mouse click a week. On Linux, it's not much more than 
> editing a shell script each week.

I very much prefer it showing me negative expiration day counts... ;)


Post a reply to this message

From: scott
Subject: Re: Povray Beta34
Date: 5 Oct 2009 07:26:09
Message: <4ac9d7d1$1@news.povray.org>
> You can even do it without touching the source file. On Windows, that's 
> just one lazy mouse click a week.

A couple of suggestions that I think would make this solution more 
user-friendly and shouldn't be too hard to add:

1) Make the link to the POV beta page clickable in the expiration extension 
dialog box
2) Put the current version number in the expiration extension box somewhere 
(useful when cross-referencing the beta web page with what you have 
currently installed)

One that might require a bit more coding:

3) Automatically check if a newer version is available or not.  A simple 
text file on the POV server could store the latest version number and the 
link (one line for each OS/version maybe?) and POV could attempt to read 
this file when the expiration date is reached.  Of course if no later 
version is available there is no need to say that one might be there.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.