User:Kris Nicholson
(New page: Just me...) |
|||
| Line 1: | Line 1: | ||
| − | + | Hi, I'm Kris. | |
| + | |||
| + | I'm in my 4th year at Canterbury University, working on my BSc(Hons) in Computer Science. | ||
| + | |||
| + | == Ideas for my Design Study == | ||
| + | |||
| + | I'm just putting up some ideas here. Please comment in the discussion page if you have any suggestions, but please don't do my work for me ;) | ||
| + | |||
| + | === COSC460 - Texturing methods for terrain rendering using GPU based methods === | ||
| + | |||
| + | Probably won't be suitable for several reasons. I did not create and probably will have no need to modify the majority of the code as it covers the main terrain rendering algorithm (ROAM) etc. Most of my time is spent in the shader code itself, which exists outside of object orientedness. Of course there will still be design considerations (use of functions, code repetition etc) but it would be difficult to apply most of our OO knowledge. Shaders are also very picky in their implementations so I have had to throw some ideas out the window (functions, arrays, dynamic branching and loops are fairly recent developments in shader land). | ||
| + | |||
| + | On the other hand, I know for a fact I have violated some decent design considerations. I know I have at least one case of inheritance for implementation. Or perhaps there's a bigger problem. I may make up a class diagram at some point to have a closer look. One red flag may be that I have been primarily editing one class, whose primary job is to interface with the shaders. | ||
Revision as of 02:44, 29 July 2008
Hi, I'm Kris.
I'm in my 4th year at Canterbury University, working on my BSc(Hons) in Computer Science.
Ideas for my Design Study
I'm just putting up some ideas here. Please comment in the discussion page if you have any suggestions, but please don't do my work for me ;)
COSC460 - Texturing methods for terrain rendering using GPU based methods
Probably won't be suitable for several reasons. I did not create and probably will have no need to modify the majority of the code as it covers the main terrain rendering algorithm (ROAM) etc. Most of my time is spent in the shader code itself, which exists outside of object orientedness. Of course there will still be design considerations (use of functions, code repetition etc) but it would be difficult to apply most of our OO knowledge. Shaders are also very picky in their implementations so I have had to throw some ideas out the window (functions, arrays, dynamic branching and loops are fairly recent developments in shader land).
On the other hand, I know for a fact I have violated some decent design considerations. I know I have at least one case of inheritance for implementation. Or perhaps there's a bigger problem. I may make up a class diagram at some point to have a closer look. One red flag may be that I have been primarily editing one class, whose primary job is to interface with the shaders.
