the Fiddler.'s picture

Planning for OpenTK 0.3.14

To help prioritize tasks, please check the list below and choose the two most important features for you:

  1. Documentation (NDoc function reference, user manual, improved tutorials)
  2. Bug and stability fixes.
  3. Joystick support.
  4. Improved mode setting (fullscreen modes, FSAA, stencil, stereo)
  5. Glu bindings (tesselation, quadrics)
  6. Mac OS X support
  7. OpenAL bindings
  8. Fonts and Text (multiple font sheets, text layout)

This will help focus resources on items that will be more useful for your projects. You don't need to create an account before posting.

Thanks!

Edit: Added item 8


Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Inertia's picture

4. Improved mode setting (fullscreen modes, FSAA, stencil, stereo)

Hard to select the 2nd, I'd vote for either 2. or 6. because those might break other things if added in very late.

Anonymous's picture

5. Glu bindings (tesselation, quadrics)
7. Fonts and Text (multiple font sheets, text layout)

Itai.

Anonymous's picture

1. Documentation
5. Glu bindings (tesselation, quadrics)

nythrix's picture

2. Bug and stability fixes. (i think this is a must)
5. Glu bindings

the Fiddler.'s picture

Thanks everyone, it seems Glu is more important than I thought - I'll bump its priority.

@nythrix: Do you have any specific problems in mind?

@everyone: please keep your suggestions coming.

nythrix's picture

Oh no, nothing I know of right now. Generally speaking any library should aim to be stable and bug free in the first place. And you've been doing a good job in this direction up till now.

lubos's picture

1. Documentation

the Fiddler.'s picture

What would you find more useful: a class/function reference (listing available functionality, along usage with examples/links) or a user manual (detailing how to set up a project, perform common tasks etc)?

lubos's picture

i would like both, but at least function/class reference would be useful, maybe use of doxygen?
1. Also why not to include examples source code to binary package, and leave source package only for openTK sources?
2. Maybe also include a MonoDevelop project in QuickStart project along Visual Studio project?

thx for this nice library ;)

the Fiddler.'s picture

You're welcome :)

1. Also why not to include examples source code to binary package, and leave source package only for openTK sources?
Err, mistake :/. I planned to re-release at first, but due to a) a lack of time and b) the fact that almost everyone downloaded the source release along with the binaries, I decided to leave that for the next release. I'm planning to actually integrate the source into the ExampleLauncher (ideally you would be able to interactively change something and relaunch the example) - we'll see how that goes.

2. Maybe also include a MonoDevelop project in QuickStart project along Visual Studio project?
Well, MonoDevelop can use .sln files directly (File->Import) since at least version 0.12, so it's not that glaring an omission. Will probably do that in 0.3.14 though.

Regarding the function reference, I've spent the past few releases adding xml docs to public members. Not everything is ready, but now it's mostly a matter of adding ndoc into the build process.