 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have aleady posted something like this in p.general :
Would not it be possible just to download the executable of the *nix
version of POV instead of the whole file (6.5 Mb).
The windows users can do this.
Fabien HENON
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I personally don't like the idea of people using non-updated include
files and perhaps making bug reports about them.
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
wrote:
> The windows users can do this.
There is different reason for windows users and downloading this is only
workaround for first run after expiration. IMO it would be reasonable to
download whole package as next step.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> I personally don't like the idea of people using non-updated include
> files and perhaps making bug reports about them.
>
it should not be a problem to include the include-files and instll-scripts
either? the manual and the testscenes etc. do not change a lot.
IMO the reason is: the programmar has not so much time to find out which
files have changed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 27 Jun 2002 11:37:03 +0200, marabou <not### [at] available net> wrote:
> the manual and the testscenes etc. do not change a lot.
Have you noticed that more than half of reports in beta-test group is
connected with documentation or wrong rendering sample scenes? Do You think
beta testing has sense only for exacutables ?
> the programmar has not so much time to find out which files have changed
Perhaps but do you really think programmers should put attention on preparing
additional simplified exacutable and lost betatesting of rest of the package ?
The windows case is not to favour. It is betatesting of different compiler
settings. This compilations is AFAIK slower than the one included in full set.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> the manual and the testscenes etc. do not change a lot.
>
> Have you noticed that more than half of reports in beta-test group is
> connected with documentation or wrong rendering sample scenes? Do You
> think beta testing has sense only for exacutables ?
i did not notice.
beta testing for sample scenes makes sense, too. maybe someone does not
want to test those scenes, he wants to find out bugs on his self created
scenes. but i do not want to start another beta-diskussion.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Why would not people who download the executable on its own, engage themselves
not to report bugs ?
I am not an expert at POV3.5 language ( too many changes have occured since POV
3.1), > thus I am not likely to run
into a bug by trying new 'exotic' features.
The thing is that I am also working on making Pyvon ready-for-3.5.
Just having the executable to work with the keywords is well enough.
Fabien
> I personally don't like the idea of people using non-updated include
> files and perhaps making bug reports about them.
>
> --
> #macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
> N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
> N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
