 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
http://abx.art.pl/pov/patches/
Any comments ? Suggestions ?
I wonder if I should store there available compilations adjusted for some
special machines (different compiler settings over standard package).
I'm crosposting but follow-up to povray.unofficial.patches.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX wrote:
> http://abx.art.pl/pov/patches/
>
> Any comments ? Suggestions ?
The link color (silver?) is kind of hard to make out against the white
background. Other than that it looks clean and organized :)
> I wonder if I should store there available compilations adjusted for some
> special machines (different compiler settings over standard package).
It might be helpful to have a central repository for patches and custom
compilations. Some place we can refer people to who are having problems
compiling from source themselves.
-Roz
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Roz wrote:
> ABX wrote:
>
>> http://abx.art.pl/pov/patches/
>>
>> Any comments ? Suggestions ?
Yes, where is the "bounding for inside testing" patch ?
I can get the news message, but that's no code.
Also, It may be worth to make patches availables as downloadable files
(either full file or just a file for the patch command (diff is
usually helpful to generate such file).
I think there might be a need for a styleguide, if you intend to make
a repository. (describing what is provided to clients and what is
requested from submitters; I believe the minimal requirement should be
a patch file and an example pov-scene. Syntax's update should also come
with full documentation as text file or html (if picture are needed,
they should be done with pov-script (provided), so that any
resize/adjustement can be done without loss).
A styleguide extension for picture might be welcome too, in order to
specify some default/classical colour for some items.
(so that there is a kind of homogeneity between the documentations, such
that all X-axis have the same colour (which should avoid nevertheless
the shadeless red/green/blue, a more complex colour is better IMNSHO).
Also, as long as patches do not interact, the repository should be easy,
but you may want to nevertheless organise the patches in a tree, the
root being of course the official 3.5 code.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 08 Aug 2002 09:16:00 +0200, Le Forgeron <jgr### [at] free fr> wrote:
> Yes, where is the "bounding for inside testing" patch ?
> I can get the news message, but that's no code.
There is difference text file with necessary changes attached to this message.
I see it with my newsreader and newswebgate as well.
> Also, It may be worth to make patches availables as downloadable files
> (either full file or just a file for the patch command (diff is
> usually helpful to generate such file).
In my own case I prefer description how, what and why is changed becouse it
can help next MegaPOV coordinator and can be some kind of tutorial for
beginners.
> I think there might be a need for a styleguide, if you intend to make
> a repository. (describing what is provided to clients and what is
> requested from submitters; I believe the minimal requirement should be
> a patch file and an example pov-scene. Syntax's update should also come
> with full documentation as text file or html (if picture are needed,
> they should be done with pov-script (provided), so that any
> resize/adjustement can be done without loss).
> A styleguide extension for picture might be welcome too, in order to
> specify some default/classical colour for some items.
> (so that there is a kind of homogeneity between the documentations, such
> that all X-axis have the same colour (which should avoid nevertheless
> the shadeless red/green/blue, a more complex colour is better IMNSHO).
Am I wrong or my own patches fits in your styleguide ?
I think I made rather patch directory instead of repository.
> Also, as long as patches do not interact, the repository should be easy,
> but you may want to nevertheless organise the patches in a tree, the
> root being of course the official 3.5 code.
I agree. It will be difficoult but since I'm mostly involved in translation
project I have no time for any better organization at this moment. It would be
graet if patch repository could be holded somehow on www.povray.org but than
it could be mistaken that it is official. Also the Team should be twice as big
as is then.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX wrote:
> On Thu, 08 Aug 2002 09:16:00 +0200, Le Forgeron <jgr### [at] freefr> wrote:
>
>>Yes, where is the "bounding for inside testing" patch ?
>>I can get the news message, but that's no code.
>>
>
> There is difference text file with necessary changes attached to this message.
> I see it with my newsreader and newswebgate as well.
>
Oh, I now see it, as a small link to an attached file.
I was expecting full inline code, just as for the other patch.
>
>>Also, It may be worth to make patches availables as downloadable files
>> (either full file or just a file for the patch command (diff is
>>usually helpful to generate such file).
>>
>
> In my own case I prefer description how, what and why is changed becouse it
> can help next MegaPOV coordinator and can be some kind of tutorial for
> beginners.
>
I was just thinking about having something "easy" for
"Joe the Crazy-Patcher" (a newbie). Something like the set of
consecutive (and ordered) patches that Joe blindly apply to its Linux
kernel.
It may also help the nanoPov coordinators/maker, otherwise the
understanding of the code become mandatory (Ok, it just take a few years
of patching pov before understanding the subtilities...)
>
>>I think there might be a need for a styleguide, if you intend to make
>>a repository. (describing what is provided to clients and what is
>>requested from submitters; I believe the minimal requirement should be
>>a patch file and an example pov-scene. Syntax's update should also come
>>with full documentation as text file or html (if picture are needed,
>>they should be done with pov-script (provided), so that any
>>resize/adjustement can be done without loss).
>>A styleguide extension for picture might be welcome too, in order to
>>specify some default/classical colour for some items.
>>(so that there is a kind of homogeneity between the documentations, such
>>that all X-axis have the same colour (which should avoid nevertheless
>>the shadeless red/green/blue, a more complex colour is better IMNSHO).
>>
>
> Am I wrong or my own patches fits in your styleguide ?
You're ok, but if you open the repository to others, it would help to
have the same kind of presentation for all the patches.
> I think I made rather patch directory instead of repository.
>
I wish you will be successul, because otherwise, a lot of patches are
going to wander on the internet. A one-stop site is a real good thing.
>
>>Also, as long as patches do not interact, the repository should be easy,
>>but you may want to nevertheless organise the patches in a tree, the
>>root being of course the official 3.5 code.
>>
>
> I agree. It will be difficoult but since I'm mostly involved in translation
> project I have no time for any better organization at this moment.
So far, the patches do not impact each others, so no problem. Even the
image of the tree is bogus when a new patch will require more than one
previous independent patches.
> It would be
> graet if patch repository could be holded somehow on www.povray.org but than
> it could be mistaken that it is official. Also the Team should be twice as big
> as is then.
Well, Do it now on your pages, if successful it could always been
transfered later.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3D5### [at] freefr>, Le Forgeron <jgr### [at] freefr>
wrote:
> > I agree. It will be difficoult but since I'm mostly involved in translation
> > project I have no time for any better organization at this moment.
>
> So far, the patches do not impact each others, so no problem. Even the
> image of the tree is bogus when a new patch will require more than one
> previous independent patches.
As you said, a tree is insufficient to represent the information, it is
more of a network, but it could get difficult to read. Just give a list
of patches each patch requires.
--
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: chr### [at] tagpovrayorg
TAG web site: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <h7o2lugibs91jsi2a5vrlot6e1ntt9ah42@4ax.com>,
ABX <abx### [at] babilonorg> wrote:
> Any comments ? Suggestions ?
Light gray on white is not easy to read.
--
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: chr### [at] tagpovrayorg
TAG web site: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 08 Aug 2002 13:46:44 -0500, Christopher James Huff <chr### [at] maccom>
wrote:
> > Any comments ? Suggestions ?
>
> Light gray on white is not easy to read.
I'm happy there is any different suggestion. Seems can be something
interesting. I'm not happy becouse I though I have it already changed to
black. Since I plan some next patch for today I will change it again.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX wrote:
> On Thu, 08 Aug 2002 13:46:44 -0500, Christopher James Huff <chr### [at] maccom>
> wrote:
>
>>>Any comments ? Suggestions ?
>>
>>Light gray on white is not easy to read.
>
>
> I'm happy there is any different suggestion. Seems can be something
> interesting. I'm not happy becouse I though I have it already changed to
> black. Since I plan some next patch for today I will change it again.
>
> ABX
Looks like you went from silver to gray to black. Black is easier to spot
on the white background than the grayer shades. How about trying a dark
blue color? The darker shade should be in keeping with the clean theme
but with a little coloring, make the links stand out. But this is just
picking nits and one of those totally subjective things ;)
-Roz
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ABX wrote:
> http://abx.art.pl/pov/patches/
>
> Any comments ? Suggestions ?
>
> I wonder if I should store there available compilations adjusted for
> some special machines (different compiler settings over standard
> package).
>
> I'm crosposting but follow-up to povray.unofficial.patches.
will post this on povray.co.uk just as soon as its back up....
--
Rick
Kitty5 NewMedia http://Kitty5.co.uk
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
---
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/2002
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
