 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
We are getting close to being ready to accept images for the 10best
proposed perhaps too stringent a list earlier, here is a revised one:
supporting JPG's and/or TXT's (or infrequent ZIP's. )
crowded disk.
21% of us povers!)
by the CD designer to allow navigation buttons, etc., to go to next tut,
back to main page, etc.
dumped into the same directory.
say p.b.t., we aim to make it more easy to use.
switch from Arial to Courier??
10best update:
survey
http://10best.ratrace.com/10best.html
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Greg M. Johnson" wrote:
> [...]
> 6) Please make all your file names long and cryptic. For example, make
> it gmj1905b.html and gmj1905ef.jpg. Please no media.html, fog1.jpg,
> julia.html, etc. The files will eventually be unzipped and may end up
> dumped into the same directory.
I'm not sure if that's a good idea - if someone wants to copy a single
tutorial somewhere, it would be a horrible work to collect all the files.
I would suggest either one directory for every tutorial or the same
starting letters for the filenames belonging to one tutorial (like you
already implied with your example).
> 8) Let's adopt a common standard for differentiation between
> explanatory text and pov code. What should this be? <CODE>, <PRE><TT>,
> switch from Arial to Courier??
IMO '<PRE>' and maybe a standardized syntax highlighting scheme for POV
code would be good.
Christoph
--
Christoph Hormann <chr### [at] gmx de>
Homepage: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Greg M. Johnson <"gregj;-"@aol.c;-om> wrote in message
<3a115b01@news.povray.org>...
>6) Please make all your file names long and cryptic. For example, make
>it gmj1905b.html and gmj1905ef.jpg. Please no media.html, fog1.jpg,
>julia.html, etc. The files will eventually be unzipped and may end up
>dumped into the same directory.
and some platforms have problems with directories with a lot of entries
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
<code> is mosy widely used for code examples...
Zilvah
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Like how many is a problem?
Wlodzimierz ABX Skiba wrote:
> Greg M. Johnson <"gregj;-"@aol.c;-om> wrote in message
> <3a115b01@news.povray.org>...
> >6) Please make all your file names long and cryptic. For example, make
> >it gmj1905b.html and gmj1905ef.jpg. Please no media.html, fog1.jpg,
> >julia.html, etc. The files will eventually be unzipped and may end up
> >dumped into the same directory.
>
> and some platforms have problems with directories with a lot of entries
>
> ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3a11695c@news.povray.org> , "Zilvah" <zil### [at] onlineno> wrote:
> <code> is mosy widely used for code examples...
<pre> is used in the POV-Ray User Manual.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Greg M. Johnson <"gregj;-()"@aol.c;-()om> wrote:
: dumped into the same directory.
This idea sounds completely crazy to me.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3a12658e@news.povray.org>, Warp <war### [at] tagpovrayorg>
wrote:
> This idea sounds completely crazy to me.
I agree...purposely make it impossible to tell what files belong to what
tutorials and what their purpose is? Each tutorial should live in it's
own folder, all of these folders could be put in the same place. Then
you don't have to worry about file names, just folder names.
--
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/
<><
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Huff wrote:
> In article <3a12658e@news.povray.org>, Warp <war### [at] tagpovrayorg>
> wrote:
>
> > This idea sounds completely crazy to me.
>
> I agree...purposely make it impossible to tell what files belong to what
> tutorials and what their purpose is? Each tutorial should live in it's
> own folder, all of these folders could be put in the same place. Then
> you don't have to worry about file names, just folder names.
Let's back up one question.
I'd like the collection to look something much more like the povray webring
than say povray.binaries.tutorials. I'd like it to be linked HTML pages
rather than a collection of ZIP files.
Q1: Is the opposition to this proposal based on an assumption of a pile of
ZIP's? IMO, if we go with a pile of ZIP's (even in own subdirectories),
let's just stick with p.b.t., as the CD will offer no value-add to anyone.
I'm just thinking suppose we end up with 100 separate tuts. It is going to
be difficult for the person who wants to "get at" the information by a means
other than the official HTML paths, regardless of 100 subdirectories or
100*(2 to 10) files in one big directory. I'm thinking that it will be a
much bigger pain to write the CD if there are 100 subdirectories, with
little value add to the user.
Q2: Isn't this similar to the IRTC rewriting your carefully chosen file
names to suit its purposes, as it dumps everything into one folder, no?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Greg M. Johnson <"gregj;-"@aol.c;-om> wrote in message
<3a117063$1@news.povray.org>...
>Teach me. You're saying a problem with too many items in one directory?
>Like how many is a problem?
I don't know how many exactly but I remember from DOS and Windows 3.1
that about 2000 entries in directory slow system down dramatically
perhaps this is not limitation but reading method but
what I want to say that povray philosophy is to be platform independent
and as long there is dos version of povray
you shouldn't use long filenames in your cdrom project
(I know 10Best isn't IRTC but look at
http://www.irtc.org/stills/rules.html at 4.f
they point to ISO restrictions)
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
