OpenTK gains support for OpenGL ES 1.0, 1.1 and 2.0

ah!
http://mono-project.com/Linker

Inertia has done most of the research necessary for ES 2.0, but unless someone volunteers to translate the necessary enums into XML we probably won't have strong types ready for the 1.0 release. The main issue is that none of the core developers is using OpenGL|ES right now, so other issues tend to take precedence.

The actual XML is very simple:

<enum name="GetIntegerPName">
  <token name="BlendEquation" value="0x8009" />
  <token name="BlendEquationRGB" value="0x8009" />
  <token name="BlendEquationAlpha" value="0x883d" />
  ...
</enum>
 
<function name="GetInteger" extension="Core">
  <param name="pname"><type>GetIntegerPName</type></param>
</function>

Realistically, if everyone that encountered a non-strongly-typed ES function would volunteer a few minutes to post the necessary XML, OpenGL|ES would become strongly-typed by the end of this month.

GetIntegerPName and the rest of the enums are already available:

• #1013: [ES 2.0] Cleanup #1
• #1014: [ES 2.0] Cleanup #2
• #1015: [ES 2.0] Cleanup #3

All that's left is their XML definition.

Thanks for your answer. I'd like to lean more about updating those XML definitions.

In "Bind/Specifications/ES10/signatures.xml" a found (for example):

<function name="DrawArrays" extension="Core" profile="" category="1.0" version="1.0">
    <returns type="void" />
    <param type="GLenum" name="mode" flow="in" />
    <param type="GLint" name="first" flow="in" />
    <param type="GLsizei" name="count" flow="in" />
</function>

Is all it takes to make the first parameter use the strongly-typed enum a change like the following?

<function name="DrawArrays" extension="Core" profile="" category="1.0" version="1.0">
    <returns type="void" />
    <param type="GLenum" name="mode" flow="in"><type>BeginMode</type></param>
    <param type="GLint" name="first" flow="in" />
    <param type="GLsizei" name="count" flow="in" />
</function>

(The "BeginMode"-Enum is already defined in the same file, but the tokens are all upper-case)

If you intend to work on ES 1.1 (and the extension pack?) my recommendation is using the ES 2.0 cleanup as a basis to start with. This will be alot more efficient than starting from scratch (for example the texture, VBO and fragment ops parts are already done and you could simply delete unsupported tokens and the FBO/GLSL related stuff ), so your work would be limited to cleaning up the fixed-func parts of ES 1.1

Novell is offering a commercial solution for Android and iPhone , called MonoTouch, which includes OpenTK bindings. (I am not affiliated with Novell).

There is no support for WinCE at this point. A port is feasible but I lack the necessary hardware.

Support for Windows Phone 7 is impossible, as it does not offer OpenGL ES.