avc81's picture

Opentk 1.1

when is scheduled the next opentk release?


Comments

Comment viewing options

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

I'm actually curious as to the state of OpenTK development as well.

Is there a 1.1 planned any time soon?

v1.0 was released just under a year ago I believe.

Thanks!

mark.r.walker@intel.com's picture

Also - is the OpenTK code that is under development in the various blogs also covered by the MIT/X11 license terms - or do the license terms only kick-in when the code is formally released???

Robmaister's picture

Don't quote me on this, but I believe that the code you find around the internet relating to OpenTK doesn't necessarily have to be MIT/X11, and it doesn't default to it. If they include the MIT/X11 license with their code then it is. The reasoning behind this is that MIT/X11 doesn't include a copy-left clause. Things like the GPL force you to release your project open source and license your project GPL (copy left). If you want to be completely legal about things, go do your own research, but generally bugfixes get patched into the main trunk, where the notice is, so it's no big deal.

If you're talking about an engine based off OpenTK or something, they'll almost certainly have their own license terms.

longjoel's picture

I would also like to know when the next formal release is.

Inertia's picture

I believe Fiddler will be able to make a more precise statement, but the slowdown of releases is due to

  • The 1.0 API lockdown.
  • Real Life.
  • A release today would be more like 1.0.1, because it's just minor bugfixes.
  • Most users preferring SVN over installers anyway.

OpenTK is nowhere near dead, but fact is we built it to build other software ontop of it and for that it works fine. Also OpenTK's goals have been achieved: platform neutral low level bindings for OpenGL (& ES), AL and CL with extensions, inline docs and enum sugar ontop. We realized the initial plans for OpenTK 2.0 (namely GLOO, ALOO and the more prominent CLOO) are worth their own svn and projects pages, which is already happening to CLOO and also GLOO has it's own git repo. Isolation is a good thing for things that don't need to be mixed.

I apologize for being slow about OpenGL 4.2, but to my defense I neither have the hardware to verify that it works nor are there (to my knowledge) any tools available yet which allow content creation for use with the tesselation extension. Looking at user feedback it's not a huge priority to others either (likely for the same reasons as mine).

longjoel's picture

I agree, I am very happy with the way 1.0 is, I think a 1.0.1 release with all the bug-fixes would be fantastic though. I am very glad you guys added a link to the nightly build on the front page though.

Keep up the great work!

thorrablot's picture

A 1.0.1 release would be great news - I have seen an occasional OpenTK crash in CreateContextAttribsARB disappear from automated testing when I use the latest instead of 1.0 on a Quadro 4000 card.

The latest SVN did have a couple minor changes that broke the existing 1.0 API that I'm not sure were intentional:

1. DisplayDevice.AvailableDisplays removed - the indexed accessor exists, but I'm not sure how to enumerate (short of handling an exception)

2. TextureEnvMode enum is missing the Replace (7681) token - I just hard-coded around that.

Having a 1.0.1 official release would be preferable to picking up a nightly build for my app.

avc81's picture

i agree with thorrablot. a 1.01 release would be great news. i am developing a commercial product used by thousands of people and i can't rely on nightly builds.

muhkuh's picture

I don't want to rain on your parade but from my point of view there is not much difference between OpenTK and a dead project. There are things that simply do not work anymore.

1. The main page here says "easy integration into GTK#" but GLWidget is just completely broken and from looking at the code never worked right in the first place.
2. MAC OS code has issues. Not even the examples work on OSX. They just hang.

It's normal that things break. It just happens. For an active project this is not so much of an issue. This is how it should be
submit a bug report

  1. have a quick conversation with the developers
  2. if they don't have time they just tell you so and kindly ask if you could investigate
  3. the bug gets tracked down and a patch is submitted
  4. the patch is integrated and a after some time a bugfixing release is done

For OpenTK I never got past the 2nd point. Conversation simply runs dry. It's completely understandable that OpenTK developers don't have that much time anymore. But this should be the time to make use of the community. When people put time into tracking down bugs and even offer to fix them there should at least be someone to talk to who replies within a month. Otherwise the project is simply not actively maintained anymore. Don't get me wrong. I like OpenTK, it helped me a lot and I'm really thankful for getting it for free. But I think there is a problem.

avc81's picture

Yes, muhku is right. something weird is happening with the patch submission. several months ago i posted two patches (matrix from quaternion conversion and matrix shear) and they have not been integrated yet in the svn repository.