![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Jeremy M. Praay wrote:
>Many of us use Poser now, for including Poser models in our POV-Ray scenes,
>so I'm wondering if anyone else here is interested in having a new forum.
>If you think it would be a good idea, or if not, please voice your opinion.
As Poser is the ONLY app of its kind out there I think this is an excellent
idea. Love it or hate it, if you need people in your images, & don't have
either the skill or time to create from scratch in another app, then you
use Poser.
While there are many Poser sites out there already, I find the er...
proprietary... atmosphere of most of them keeps me from ever participating.
Most of them are not about exchanging information, but trying to sell you
someone's mediocre props.
A forum here, with the usual POV atmosphere would be great!
RG
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Gilles Tran" <tra### [at] inapg inra fr> wrote in message
news:4007e6c5@news.povray.org...
>but there is little
> information about the use of Poser within POV-Ray.
A Poseray forum, and a Wings3d forum too, to boot! :)
~Steve~
> G.
>
> --
>
> **********************
> http://www.oyonale.com
> **********************
> - Graphic experiments
> - POV-Ray and Poser computer images
> - Posters
>
>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Christoph Hormann" <chr### [at] gmx de> wrote in message
news:5pp### [at] triton imagico de...
> A rule to add a prefix like [poser] to the subject of new threads
would
> make it possible to set preferences in the newsreader.
Bingo!
~Steve~
>
> Christoph
>
> --
> POV-Ray tutorials, include files, Sim-POV,
> HCR-Edit and more: http://www.tu-bs.de/~y0013390/
> Last updated 11 Jan. 2004 _____./\/^>_*_<^\/\.______
>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
news:40087ada@news.povray.org...
>
> A Poseray forum, and a Wings3d forum too, to boot! :)
Of course, the risk is that a few years from now, we may start asking for
povray.politics, povray.used-cars and povray.relationships ;)
G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Gilles Tran wrote:
>
> news:5pp### [at] triton imagico de...
>
> > I think a common group for all 3rd party tools would be a good idea
> > (povray.tools or povray.utilities). This way it would be easier to
> > adapt to tools becoming more popular and others less.
>
> povray.tools + the prefix gets my vote.
>
> There's a lot of intersection between these tools (Poser + Poseray for
> instance) so keeping them all at the same place is a good idea.
From a consistent hierarchy point of view I would think that povray.text.utilities
would be a better fit. I have often thought it inconsistent that we had the
povray.utilities.binaries group without the .text group for related discussions.
--
Ken Tyler
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Ken wrote:
>
> Gilles Tran wrote:
>
>>news:5pp### [at] triton imagico de...
>>
>>
>>>I think a common group for all 3rd party tools would be a good idea
>>>(povray.tools or povray.utilities). This way it would be easier to
>>>adapt to tools becoming more popular and others less.
>>
>>povray.tools + the prefix gets my vote.
>>
>>There's a lot of intersection between these tools (Poser + Poseray for
>>instance) so keeping them all at the same place is a good idea.
>
>
> From a consistent hierarchy point of view I would think that povray.text.utilities
> would be a better fit. I have often thought it inconsistent that we had the
> povray.utilities.binaries group without the .text group for related discussions.
>
Is that what it's supposed to mean? I never did understand the
text/binaries designation.
And what are p.b.tutorials and p.t.tutorials intended to be used for?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Wasn't it gonzo who wrote:
>As Poser is the ONLY app of its kind out there I think this is an excellent
>idea.
But it may not be the only app of its kind for long. DAZ Studio is
currently in pre-beta testing. I believe that DAZ decided to write their
own application because they can't use Poser-5 due to the restrictive
nature of its user licence.
DAZ Studio may possibly find greater acceptance within the POV community
because the full-beta version will be free to everyone. The current
version is free to people who've paid to become members of the DAZ
Platinum Club.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Gilles Tran" <gitran_nospam_@wanadoo.fr> wrote in message
news:40088872@news.povray.org...
> news:40087ada@news.povray.org...
> >
> > A Poseray forum, and a Wings3d forum too, to boot! :)
>
> Of course, the risk is that a few years from now, we may start
asking for
> povray.politics, povray.used-cars and povray.relationships ;)
Heh, yes indeed, true. ;) I think Tim's idea is the right way to
go.
~Steve~
>
> G.
>
>
> --
> **********************
> http://www.oyonale.com
> **********************
> - Graphic experiments
> - POV-Ray and Poser computer images
> - Posters
>
>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Great idea.
Mick
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Ken" <tyl### [at] pacbell net> wrote in message
news:4008A67A.C2FFEF8C@pacbell.net...
>
>
> Gilles Tran wrote:
> >
> > news:5pp### [at] triton imagico de...
> >
> > > I think a common group for all 3rd party tools would be a good idea
> > > (povray.tools or povray.utilities). This way it would be easier to
> > > adapt to tools becoming more popular and others less.
> >
> > povray.tools + the prefix gets my vote.
> >
> > There's a lot of intersection between these tools (Poser + Poseray for
> > instance) so keeping them all at the same place is a good idea.
>
> From a consistent hierarchy point of view I would think that
povray.text.utilities
> would be a better fit. I have often thought it inconsistent that we had
the
> povray.utilities.binaries group without the .text group for related
discussions.
>
traditionally, that would be
povray.binaries.utilities.d
or
povray.binaries.utilities.discuss
not povrray.text as the 'text' refers to the type of content posted
further clarified by the last name section (i.e., scene-files)
text content in re third party utilities (reviews, manual explications,
howtos)
would probably belong in
povray.text.utilities.reviews
povray.text.utilities.howtos
although there is some sense of redundancy here
the second level name section has always been meant to be used so
that readers could quickly determine whether the group could comprise
binaries or not
(absent 'binaries' the assumption is that content would be
textual (( ! html) ) )
see usent history, etc.
except for binaries groups (which relates to transit and storage
issues) the general content rule has always turned out to be that user
custom and usage rules except when the server owner decides otherwise
Pan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |