I've long felt that NeHe was operated as a site unto itself, which it isn't, and which is an inefficient use of GDNet resources. As ||v||atrix later clarified, his intention is to supply such material (non-OpenGL-specific) to GameDev as a whole, and link to them from within NeHe, which is exactly what I think should be the case.

[Edited by - Andrew Russell on March 27, 2006 9:50:18 AM]

We may want to introduce logging functionality into all of the tutorials. This should make it easier for people on the forums to help anyone with a question.

Quote: Original post by Andrew Russell
NeHe is about OpenGL game development

And on that note, maybe focus the tutorials (or even create a series just for this) on developing a modular graphics engine. Have basic tutorials designed to show off specific effects and explain what is going on and how it works.

Then later, add said effects to the graphics engine (or explain a way of adding them).

Just a thought. With all the great minds we have around here, the biggest challenge would be the time to do it.

Richard

Quote: Original post by Andrew Russell

Quote: Original post by nefthy
I think we should invest some time into devising a tutorial-framework. Consistent file naming and such would be usefull too. It would be nice if the tutorials would add up to a simple library, which could be use for experimenting. What I mean is for example the particle engine tutorial could have functions to create, manage and render particle effects with a sepparated demo function, instead of mixing the initialazation of the particle engine with the OpenGL init and rendering with the managment. So that using it outside the tutorial would be much easier. Maybe I should rewrite a tutorial or two to demonstrate what I mean.

Don't worry, this is almost exactly what I had in mind [wink].

This is, if I remember rightly, exactly what my NeHe SDK actually did.

Please keep it to OpenGL stuff!

That is all :).

Quote: Original post by gregs
This is, if I remember rightly, exactly what my NeHe SDK actually did.

Yes, I was not aware of it. I think it might be a good starting point. I will take a deeper look later today.

What I'd essentially like to do is to set up the Tutorials so that the code from them can be used directly in the creation of an SDK of some kind.

I may be a little weird, but I like to print out NeHe's tutorials, and, as we all know, those tutorials have way more black than white. So I created my own solution: I save the pages to disk, and then modify the rgb.css file to make the page printer-friendly.

However, it would be a lot less cumbersome and much easier if you simply added a "printer friendly version" button on each tutorial. Please consider this.

Thanks

That's a good suggestion. I think that the site's in need of a visual overhaul anyway.

I agree. NeHe really needs to be better integrated with the whole GameDev.Net site.

That way the CMS that is used for GameDev could be used with NeHe and the look and feel would be consistent across the whole site.

That and content could be added quicker too.

My 2 cents.