OK, to try this out, I'll be collecting, for a period of one week, 
submissions for office supplies.  Anyone can make a submission, or 
multiple submissions.  There are only a few guidelines I'll stipulate:

1) Email me your submissions, rather than spamming the NG with binaries.

2) Try to use a macro parameter to define the size of your object.  If 
you cannot, then please use a variable named 'meter', and place the 
following at the beginning of your code:

#ifndef(meter)
#declare meter = 1.0;
#end

Then, create all your objects based on this variable.

3) It is assumed that all submissions are given with permission to post 
them in the POV-Ray Library.  It is also assumed that I am being given 
permission to be the one posting them there.  It is also assumed that 
you would like credit for your work, so I will ensure that the final 
upload contains credits for all contributors.

4) Try to make objects that would require more than a few minutes of 
mucking about in SDL to replicate.  The point is to have quality 
objects.  If you can't make a whole set of quality objects, just make 
one or two - that's why we're doing this as a group.

Any other questions or suggestions, post them here.  After next Sunday, 
I'll package all the contributions together and upload them.

-- 
...Ben Chambers
www.pacificwebguy.com

Post a reply to this message

Chambers <ben### [at] pacificwebguycom> wrote:
> OK, to try this out, I'll be collecting, for a period of one week,
> submissions for office supplies.

fine enough.  So it closes next monday?  oh, sunday...

> 1) Email me your submissions, rather than spamming the NG with binaries.

how about a standard title?  "Povray Object Collection:  office supplies"?

> 2) Try to use a macro parameter to define the size of your object.  If
> you cannot, then please use a variable named 'meter', and place the
> following at the beginning of your code:
>
> #ifndef(meter)
> #declare meter = 1.0;
> #end

hmm, how about abbrevs?  m is traditional for meter, cm for centimeter etc.  I'd
very much like to spell <1.2,.86,.2>*m rather than <1.2,.86,.2>*meter or
centimeter...  what about yankees and their weird measure units?

> 4) Try to make objects that would require more than a few minutes of
> mucking about in SDL to replicate.  The point is to have quality
> objects.  If you can't make a whole set of quality objects, just make
> one or two - that's why we're doing this as a group.

that sounds great!  I'm guessing you're expecting pure CSG, no meshes?

Post a reply to this message

Chambers <ben### [at] pacificwebguycom> wrote:
> OK, to try this out, I'll be collecting, for a period of one week, 

  Do you think that's enough?

> 2) Try to use a macro parameter to define the size of your object.  If 
> you cannot, then please use a variable named 'meter', and place the 
> following at the beginning of your code:

> #ifndef(meter)
> #declare meter = 1.0;
> #end

> Then, create all your objects based on this variable.

  I would like to suggest what I suggested in the other post:

  If possible, try to make the different dimensions of the object
configurable. For example, if you are making a table, try to make
it possible to define either the width and depth or the "aspect
ratio" of the tabletop, the length of the table legs, etc. instead
of just creating a fixed model. In some cases it may be feasible to
put some limits on the given measures.

  The most flexible way to do this is to put something like this in
the include file:

#ifndef Someid_Table_Leg_Length
  #declare Someid_Table_Leg_Length = 5;
#end

  Or, alternatively:

#local Table_Leg_Length = 5;
#ifdef Someid_Table_Leg_Length_Factor
  #local Table_Leg_Length = Table_Leg_Length * Someid_Table_Leg_Length_Factor;
#end

  This way people can either use your #include with its default settings,
or they can fine-tune some settings like:

#declare Someid_Table_Leg_Length_Factor = 1.2;
#include "theinclude.inc"

  It would also be nice to be able to configure other things about the
object in a similar way. For example, if you are making a lamp, it should
be possible to tell if the lamp is on or off, and its brightness/color,
for example like:

#declare Someid_Lamp_Light = on;
#declare Someid_Lamp_Light_Color = <1.2, 1, .6>;
#declare Someid_Lamp_Light_Fade_Distance = 4;
#include "thelamp.inc"

  Likewise for other similar things, eg. object which can be open or close,
objects which can have parts which are rotated (ie. it should be possible
to define the rotation angle for that part), etc.

-- 
                                                          - Warp

Post a reply to this message

nemesis wrote:
> Chambers <ben### [at] pacificwebguycom> wrote:
>> OK, to try this out, I'll be collecting, for a period of one week,
>> submissions for office supplies.
> 
> fine enough.  So it closes next monday?  oh, sunday...
> 
>> 1) Email me your submissions, rather than spamming the NG with binaries.
> 
> how about a standard title?  "Povray Object Collection:  office supplies"?

As long as its emailed to me, I'll see it.  I haven't had a problem with 
my spam filters catching legitimate mail.  Then, I'll composite them 
into a single package to be uploaded.

>> 2) Try to use a macro parameter to define the size of your object.  If
>> you cannot, then please use a variable named 'meter', and place the
>> following at the beginning of your code:
>>
>> #ifndef(meter)
>> #declare meter = 1.0;
>> #end
> 
> hmm, how about abbrevs?  m is traditional for meter, cm for centimeter etc.  I'd
> very much like to spell <1.2,.86,.2>*m rather than <1.2,.86,.2>*meter or
> centimeter...  what about yankees and their weird measure units?

Try to use macro parameters.  If you can't, then we should use a 
standard sizing system.  Rather than argue about it here, I'd recommend 
just using the above.

If you use parameters, however, then the above is unnecessary.

>> 4) Try to make objects that would require more than a few minutes of
>> mucking about in SDL to replicate.  The point is to have quality
>> objects.  If you can't make a whole set of quality objects, just make
>> one or two - that's why we're doing this as a group.
> 
> that sounds great!  I'm guessing you're expecting pure CSG, no meshes?

That's the idea, of course.

-- 
...Ben Chambers
www.pacificwebguy.com

Post a reply to this message

Warp wrote:
> Chambers <ben### [at] pacificwebguycom> wrote:
>> OK, to try this out, I'll be collecting, for a period of one week, 
> 
>   Do you think that's enough?

For office supplies?  Sure.  I don't expect everyone to push out a dozen 
objects or so; one per person should be enough, and the given time frame 
is fine for that.

>> 2) Try to use a macro parameter to define the size of your object.  If 

<snip>

>   I would like to suggest what I suggested in the other post:
> 
>   If possible, try to make the different dimensions of the object
> configurable. For example, if you are making a table, try to make

Exactly.  If they can't do that, then using a standard sizing system is 
best.  I didn't want to argue about a sizing system, so I kept it simple.

Of course, macro or defined parameters are best :)

-- 
...Ben Chambers
www.pacificwebguy.com

Post a reply to this message

Chambers wrote:
> 1) Email me your submissions, rather than spamming the NG with binaries.

Although it probably wouldn't hurt to post here if you're working on 
something.

Personally, I've been working on a ball point pen, and I plan on doing a 
handheld (ie small) stapler, as well as a 3 hole punch.

-- 
...Ben Chambers
www.pacificwebguy.com

Post a reply to this message

"Chambers" <ben### [at] pacificwebguycom> wrote in message 
news:4794efd1@news.povray.org...
> nemesis wrote:
>> that sounds great!  I'm guessing you're expecting pure CSG, no meshes?
>
> That's the idea, of course.

     In this day and age, that's a real shame.

       ~Steve~



>
> -- 
> ...Ben Chambers
> www.pacificwebguy.com

Post a reply to this message

St. wrote:
> "Chambers" <ben### [at] pacificwebguycom> wrote in message 
> news:4794efd1@news.povray.org...
> 
>>nemesis wrote:
>>
>>>that sounds great!  I'm guessing you're expecting pure CSG, no meshes?
>>
>>That's the idea, of course.
> 
> 
>      In this day and age, that's a real shame.
> 
>        ~Steve~
> 
> 
Ohhh!  Glad that got said before I put too much time in.  That should be 
made clearer on the web page.

Post a reply to this message

"Jim Charter" <jrc### [at] msncom> wrote in message 
news:479516b0$1@news.povray.org...
> St. wrote:

>>      In this day and age, that's a real shame.


> Ohhh!  Glad that got said before I put too much time in.  That should be 
> made clearer on the web page.

    Heh, well, I can't think of anything better than mixing a good mesh 
modeler with PoV. For me at least, it = perfect.  :)

      ~Steve~

Post a reply to this message

St. wrote:
> "Chambers" <ben### [at] pacificwebguycom> wrote in message 
> news:4794efd1@news.povray.org...
>> nemesis wrote:
>>> that sounds great!  I'm guessing you're expecting pure CSG, no meshes?
>> That's the idea, of course.
> 
>      In this day and age, that's a real shame.
> 
>        ~Steve~

Don't get me wrong - there's no way I'd turn away a good model if one 
got submitted.  I just prefer CSG for its flexibility (through macros 
and / or parameters), compactness, and the fact that it uses real curves.

-- 
...Ben Chambers
www.pacificwebguy.com

Post a reply to this message