Hi Allen,
Allen Bierbaum wrote:
>
> That makes sense. But I would also say that demos may try to pack more
> capabilities into a single application and in many cases provide an
> interface for trying out different things.
Agreed. Like the ATI demos.
> For example, the nvidia demos like nalu and vulcan are not examples. We
> are a long way from making something like that though so lets worry
> about that when we get to it.
Those are much more about models than code. They do some cool code too,
but it's rather subtle. I think something more obvious would be better
for us.
> At this point I would suggest we just create a directory for "examples"
> and create subdirectories for each example. Put the code in there for
> the applications and build them as part of the common build (to make
> sure they don't break and get them into the nightly build). Once we get
> to many application examples in there and some of them are too large or
> too well documented, then we can start debating which ones should be
> demos and which ones should be tutorials. I would rather have people
> spend time writing examples then debating "what is an example". :)
I added a ticket for that. The main part would be to define what's
necessary to build the examples as part of the dailybuild and how to
include them in the dists.
Basic question: Do we want to spend the effort of doing that for 1.8? Or
just for 2.0 and up? I guess the framework would take me a number of
hours (including testing, which takes a long time for dists and stuff),
so I'm more inclined to let Andreas' enhanced sceneviewer cover the demo
part for 1.8 and concentrate on 2. The cluster can be covered by a
slightly extended version of the cluster tutorial, that should be much
faster than trying to come up with a full example framework. Just my $.02...
> I was just trying to think of a way to get "working" code snipets of
> 5-10 lines into the documentation. ie. little pieces of code that show
> how to use the interface of a class but not how to use it in an entire
> application. This type of thing may not be needed right now though. I
> would rather have people spend time writing examples then trying to
> figure out how to extract code snipets and put them in the documentation.
Doxygen let's you dissect examples programs, not sure if you can use
that for this purpose.
> Summary: Let's stop talking about this and just start making it happen.
> Dirk, tell us how you want it to be and then let's make it so. :)
I would like to see more effort spend on 2 than 1. I would like to push
1.8 out the door as soon as we have the NURBS in it (including
demo/tutorial).
Dirk
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
