Skip to content

Conversation

@ccawley2011
Copy link
Contributor

The differences between the OpenGL 3 and OpenGL ES 2 demos are:

  • Vertex Array Objects were introduced in OpenGL 3.0 or OpenGL ES 3.0 - older versions require extensions.
  • Memory mapped buffers require extensions - glMapBufferRange is in OpenGL 3.0 or OpenGL ES 3.0 and could be used as an alternative, but glMapBuffer is only available in OpenGL ES with extensions.
  • The GLSL shader code is different.
  • Different link libraries are required depending on which API should be used (see discussion in Use GLAD for all OpenGL demos #777).

Copy link
Contributor

@RobLoach RobLoach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to have some consistancy.

Copy link
Contributor

@sleeptightAnsiC sleeptightAnsiC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find some of those changes a bit confusing, but I suspect you wanted to keep the code the same, in all files, at all costs. Sadly, because we have to deal with so many demos, the review process is really hard, so apologies if I missed something obvious.

Overall, I think that merging this without feature detection implemented doesn't seem very useful. Right now, most of those additions is just a dead code.

However, just like I mentioned in #777 (comment) , I do agree that we need this.

glGetProgramiv(dev->prog, GL_LINK_STATUS, &status);
assert(status == GL_TRUE);

/* TODO: Detect at runtime */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this unfinished? Are you planning to implement this in the force push?

(same for other files)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the current consensus regarding PR #777? Should I wait for that to be merged, or should this one be merged first and that one rebased on top? Or should the existing loader code from x11_opengl3 be adapted for the other demos instead of using GLAD?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the current consensus regarding PR #777? Should I wait for that to be merged

I don't believe you will get #777 merged any time soon. I would ignore it for now.

Or should the existing loader code from x11_opengl3 be adapted for the other demos instead of using GLAD?

I think this will be a way to go in the future. Right now, we have way too many duplicate code in the demos, so we need to deal with this problem before doing anything else.

@RobLoach (tactical ping)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants