Re: [Raypp-general] Source code folder structure

[Ayal P. <ap...@xs...>]

Hi,
First off, sorry I am still lurking on the mailing list, and not 
actively participating.

I think allowing for fast previews is a really great feature. GL/GLUT 
should be supported
on all platforms. However, indeed, you might want to keep dependencies 
down.
So I would make it optional. It could be a separate library?

Would it be possible to offer some form of hook, callback function or 
callback class?
That way the user of Ray++ can make a separate compilation to quickly 
see the rendering.
Objects would have to offer the option of rendering themselves quickly 
I presume, not just
polygons, but blobs, star fields etcetera too.

How do you plan to support it? Will it be rendering in the background 
as a separate thread, displayed
through OpenGL? Or through an idle function that incidentally updates 
the screen while rendering in
time slices?

This could also be an excellent tool for tweaking things like positions 
of objects and camera position,
if you keep the render at coarse level. A poor-mans 3d scene authoring 
tool that would suffice for a programmer.

At any length a very important addition I think!





Andreas Kahler heeft op dinsdag, 9 nov 2004 om 16:45 (Europe/Amsterdam) 
het volgende geschreven:

> Hi!
>
> I'm currently working on a GLUT based output class for ray++
> which does progressive refinement for the rendered image.
> Saves a lot of time when setting up new scenes as you can see
> the coarse scene appearance very quickly.
>
> Question about this: As this has a dependency to the GL/GLUT
> headers and libs I don't want this to be part of the standard
> ray++ static library, as it is quite possible that you do not have
> the GLUT stuff but you still want to use ray++ as you do not
> need the GLUT output. How should we handle this?
> My suggestion to but it into the same source folder structure
> (and therefore put it into the main raypp CVS project and
> distribute with standard builds), but put it into an extra folder
> (maybe called "extras"). The files in there are NOT compiled
> into the raypp lib. You have to compile them separately.
>
> Another thing: Should we include test programs into the CVS
> project? I think about e.g. a small program showing the
> distribution of various sampling strategies or maybe later some
> visualization for the photon map. What about if we put them
> into a programs/tests folder?
>
> Comments?
>
> Andreas
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Raypp-general mailing list
> Ray...@li...
> https://lists.sourceforge.net/lists/listinfo/raypp-general
>