Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am currently learning openGL myself, but it looks like I was lucky enough to find better resources. <a href="http://duriansoftware.com/joe/An-intro-to-modern-OpenGL.-Chapter-1%3a-The-Graphics-Pipeline.html" rel="nofollow">This</a> tutorial is pretty fast paced, but covers a lot of basics. I would also mention the <a href="http://www.amzn.com/0321498828" rel="nofollow">OpenGL Superbible 5th ed.</a>, but personally it hasn't been helping me much. As far as your problems with matrices, it is probably best you get a basic understanding of linear algebra and basic 3D math before you go learning OpenGL. For that, I recommend <a href="http://www.amzn.com/1556229119" rel="nofollow">this book</a>, or the Durian Software tutorial above. </p> <p>As far as shaders go, I'm probably not the best source, but simple shader construction typically goes like this: </p> <ol> <li>Load shader into memory as a character array. </li> <li>Generate handles for your vertex shader, fragment shader, and program objects with glCreateShader()</li> <li>Bind the source code to your shader objects with glShaderSource() and glCompileShader()</li> <li>Link your vertex and and fragment shaders with glLinkProgram() then enable the final program with glUseProgram()</li> <li>Load your vertex attributes (like coordinates, texture coordinates, and normals) into a buffer with glGenBuffer() (to create handles), glBindBuffer(), and glBufferData().</li> <li>Bind your vertex attribute array buffer (again, just your collection of coordinates, normals, and other data to be processed), and use glVertexAttribPointer() to allow it to be read correctly by your shader.</li> <li>Uniforms and attributes are just a way to make your program on the CPU communicate with the shader on the GPU.</li> <li>Draw </li> </ol> <p>I'm afraid that I'm too under qualified to further explain, and basic code examples of the entire process would take up far too much, but I could offer small bits if necessary. However, the resources I linked to each come with complete examples.</p>
    singulars
    1. This table or related slice is empty.
    1. POCommunication between OpenGL and GLSL
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USLouie
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou led me into a trap mate. The tutorial you linked me to is using a deprecated version of GLSL. :(
      singulars
      1. PO
      1. USPilpel
    2. COWill learning it help me or will it be a waste of time?
      singulars
      1. PO
      1. USPilpel
    3. COWhoops, I forgot it uses older shader code. For those examples specifically, just replace "attribute" with "in" and "varying" with "out" on the vertex shader and "in" on the fragment shader and change the version number and it will compile fine. As for whether or not you should learn the older shader language, that is a hard question to answer. Personally, I would stick with the newer one, but knowing a couple deprecated counterparts can't hurt. After all, not everyone has the latest hardware.
      singulars
      1. PO
      1. USLouie
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload