+
We're now ready to handle some input!
@@ -268,4 +263,4 @@ public class Program
}
```
-You can also view this on its own [here](../sources/1.1-final-result.html).
\ No newline at end of file
+You can also view this on its own [here](../sources/1.1-final-result.html).
diff --git a/website/docs/opengl/c1/2-hello-quad.md b/documentation/opengl/c1/2-hello-quad.md
similarity index 93%
rename from website/docs/opengl/c1/2-hello-quad.md
rename to documentation/opengl/c1/2-hello-quad.md
index e227a92c75..46c96ce264 100644
--- a/website/docs/opengl/c1/2-hello-quad.md
+++ b/documentation/opengl/c1/2-hello-quad.md
@@ -1,19 +1,13 @@
---
-{
- "TableOfContents": {
- "Name": "1.2 - Hello Quad",
- "Url": "2-hello-quad.html",
- "Metadata": {
- "AuthorGitHub": "ohtrobinson",
- "DateTimeWritten": "02/11/2022 12:00",
- "PreviewImage": ""
- }
- }
-}
+sidebar_position: 2
+sidebar_label: Hello Quad
+slug: 2-hello-quad
---
# 1.2 - Hello Quad
-
+
+> [!NOTE]
+> You can view the source code for this tutorial [here](https://github.com/dotnet/Silk.NET/tree/main/examples/CSharp/OpenGL%20Tutorials/Tutorial%201.2%20-%20Hello%20Quad).
Let's draw something on-screen! In this tutorial, you'll learn:
@@ -49,7 +43,8 @@ _gl = _window.CreateOpenGL();
What are we doing here? Silk.NET requires you to keep a **reference** to the OpenGL API. If you've used or seen OpenGL in C, you'll notice that this is different to the way that it is done there. This is done so that you can more easily keep track of multiple contexts. If you don't know what that is, don't worry about it for now, we won't be using it in these tutorials.
-
+> [!NOTE]
+> If you take a look at the source in the Silk.NET samples repository, you will notice that it uses `_gl = GL.GetApi(_window)`. This is another way to get the GL API, however when using Silk.NET windowing, it's recommended that you use `_window.CreateOpenGL()` instead.
Now, run your application again. If all is good, you should see no change. Awesome! Let's do our first steps in OpenGL: Clearing the window.
@@ -61,7 +56,8 @@ A window contains at least two **framebuffers**. A framebuffer is a set of textu
* Color texture
* Depth stencil texture
-
+> [!NOTE]
+> The technical name for these textures is **buffers**. For simplicity reasons we will call them textures here, as to not confuse you with the buffers we use later in the tutorial.
On top of this, a window will contain at least two of these framebuffers. This is known as **double-buffering** and is imperative for rendering to work properly. One buffer is displayed, while another is rendered to. They are then swapped between once the GPU is ready.
@@ -93,7 +89,7 @@ _gl.Clear(ClearBufferMask.ColorBufferBit);
Run your application again, and you should see a lovely sky blue window!
-
+
Congrats! You've done your first thing in OpenGL! Didn't work? Check the [source code](../sources/1.2.2-clear-window.html) for this section here.
@@ -172,7 +168,7 @@ In modern graphics programming, you are expected to use triangles, lines, or poi
Therefore, a quad is made of two right-angle triangles. This can best be seen if we view the result in **wireframe** mode.
-
+
In the image, you can also see where the four vertices go in relation to the quad. While you won't *usually* be defining vertices yourself, it's still handy to know how it works.
@@ -206,7 +202,8 @@ Let's fill our buffer with some data! Before we do that though, you need to be a
#### Unsafe C#
Silk.NET heavily uses `unsafe` code. Don't worry, this won't make your computer explode, however it does exit out of the "memory safe" managed environment of C#, and enters a realm where undefined behavior, segmentation faults, and strange results are more likely to occur if you are not careful. Since we're working with low-level APIs, and OpenGL is defined in plain C, some unsafe code will be necessary in order for us to be able to communicate with it from C#.
-
+> [!NOTE]
+> If you wish to use `Span` instead, and remain in `safe` mode, Silk.NET does support these too. However, I will be using `unsafe` in this tutorial instead, as this is both what I personally use, as well as what the samples use.
Unsafe mode is not enabled by default, so we need to enable it. To enable it:
- If you're on Visual Studio 2022, open your project properties and under Build --> General, make sure the box that says "Unsafe code" is checked.
@@ -457,7 +454,8 @@ The last thing we need to do before we can begin drawing our quad to the screen
This is done with the **attribute setup**. This sets various parameters in the VAO, which tells OpenGL how to read the vertex data in the vertex buffer. As vertex buffers can contain more than just position data (it can contain almost anything you want), it is vital that OpenGL knows how to separate out the individual bits of data, so it can pass it to the shader correctly.
-
+> [!WARNING]
+> While fragment shaders (and other shaders) can have `in` attributes, the only ones you can directly set *outside* of a shader are the ones going into the vertex shader. The only way to set attributes in the fragment shader is to pass them through the vertex shader. Therefore, the attribute setup only affects the vertex shader and vertex buffer, not any other shader.
Add the following to your `OnLoad` method:
@@ -479,7 +477,7 @@ The stride tells OpenGL the size (in bytes) of a *single* vertex. The offset tel
This diagram gives a visual explanation of what stride and offset do (credit to LearnOpenGL):
-
+
In our example, the only things we define per vertex is the position of the vertex itself, which is 3 values per vertex. Therefore, our stride is just `3 * sizeof(float)` (remember, stride is in **bytes**, so we must multiply by the size of the float primitive). Since we are only defining one attribute, we don't need to have any offset. Therefore, we can just use `0`. OpenGL expects a `void` pointer, so we must cast it to `void*`.
@@ -496,7 +494,8 @@ _gl.BindBuffer(BufferTargetARB.ElementArrayBuffer, 0);
Doing this means we've "un-bound" everything, so calling something like `BufferData` won't affect the buffers we've just created.
-
+> [!WARNING]
+> You **MUST** unbind the vertex array first, before unbinding the other buffers. If you forget to do it in this order, the buffer will be unbound from the vertex array, meaning you'll see incorrect results when you render the object.
If you want to see the resulting code so far, you can see it [here](../sources/1.2.7-finished-setup.html).
@@ -529,7 +528,7 @@ The last parameter is a pointer to the starting index of the indices. Since we w
And that's it! Run your program and you should see a lovely orange rectangle on a blue background. Exciting, isn't it... Right...?
-
+
While this may have seen like a lot of set up for a boring result, this code can render pretty much anything you want to the screen. It remains pretty much the same, whether you're rendering a basic quad like this, or a complex 3D model. All you need to change are the vertices & indices going in, and some more complex shader code to handle the transformations.
diff --git a/website/docs/opengl/c1/3-hello-texture.md b/documentation/opengl/c1/3-hello-texture.md
similarity index 90%
rename from website/docs/opengl/c1/3-hello-texture.md
rename to documentation/opengl/c1/3-hello-texture.md
index c012cb7438..142016a784 100644
--- a/website/docs/opengl/c1/3-hello-texture.md
+++ b/documentation/opengl/c1/3-hello-texture.md
@@ -1,19 +1,13 @@
---
-{
- "TableOfContents": {
- "Name": "1.3 - Hello Texture",
- "Url": "3-hello-texture.html",
- "Metadata": {
- "AuthorGitHub": "lumi2021",
- "DateTimeWritten": "11/01/2024 16:00",
- "PreviewImage": ""
- }
- }
-}
+sidebar_position: 3
+sidebar_label: Hello Texture
+slug: 3-hello-texture
---
# 1.3 - Hello Texture
-
+
+> [!NOTE]
+> You can view the source code for this tutorial [here](https://github.com/dotnet/Silk.NET/tree/main/examples/CSharp/OpenGL%20Tutorials/Tutorial%201.3%20-%20Hello%20Texture).
In the previous tutorial, we've shown you how to open an OpenGL window and draw a colored quad.
@@ -35,7 +29,8 @@ The most common type of texture is a 2D texture, which stores the 2D grid of pix
as texture objects are a lot more complex than just 2D arrays!
This data is stored in GPU memory, and can be read by a shader.
-
+> [!NOTE]
+> There are multiple different dimensions of texture from 1D through to 3D. For the purposes of this tutorial, we will be focusing on 2D.
Textures are quite finicky to setup, and need quite a bit of information in order to be drawn.
The most important piece of information that we need to send to the texture to see it on the screen are the texture coordinates.
@@ -62,7 +57,7 @@ With how we have structured the data, both the vertex and texture coordinates ca
If we try to run our program now...
-
+
Well, that doesn't look like the quad we were expecting. This is because we have updated the vertex buffer we're passing to the vertex shader,
but haven't updated anything else such as our vertex layout definition. Luckily, it's very easy to modify the the example vertex layout
@@ -71,7 +66,7 @@ shown in the previous tutorial to work with our new texture coordinates.
In our `VertexAttribPointer` calls, we declared an `aPosition` attribute with a size of 3 floats and a stride of 12 bytes (`3 * sizeof(float)` equals 12).
Because of this, our buffer is being read like this:
-
+
As you can see, the vertex buffer is being read as if the first vertex was composed of the first three floats in the buffer, then the second
vertex the next three floats, the third vertex the next three, and so on and so forth. However, this is now wrong! Since each
@@ -88,7 +83,7 @@ _gl.VertexAttribPointer(positionLoc, 3, VertexAttribPointerType.Float, false, 5
This will make the buffer be read like this (including the texture coordinate pointer, which we'll add into our code later):
-
+
Now the positions of each vertex are being read correctly! Each position is still three floats, but by skipping the two floats after each position,
we skip over the U and V floats in between each XYZ floats, thus reading them correctly.
@@ -155,7 +150,7 @@ should be incremented before reading the vertex attribute data. This means that
If you do everything right, you will see this result!
-
+
This gives us a nice visualisation of the texture coordinates, but it's not a textured quad. What exactly are we looking at?
What you are seeing is the texture coordinates we passed displayed as a color!
@@ -163,7 +158,7 @@ What you are seeing is the texture coordinates we passed displayed as a color!
The Red, Green and mix between these two colors you see are, respectively, the X and Y texture coordinate values of that pixel.
In the shader, the values are being read like this:
-
+
As you can see, as the X/U coordinate increases so does the amount of red in the output pixel, and likewise as the Y/V coordinate increases so does the amount of green.
Even though we only specified UV values for each vertex, all pixels in the quad have UV values. That's because, as you read before,
@@ -206,8 +201,10 @@ _texture = _gl.GenTexture();
_gl.ActiveTexture(TextureUnit.Texture0);
_gl.BindTexture(TextureTarget.Texture2D, _texture);
```
-
+
+> [!NOTE]
+> Texture units are locations in the OpenGL state where textures can be bound. Instead of textures being specified directly to shader samplers,
+textures are bound to a texture unit, and the texture unit is then specified to the shader sampler.
After that, we need to load the image. You can do it with the following line:
```cs
@@ -280,7 +277,8 @@ But pay attention! Notice that our texture coordinates are between the ranges of
with normalized values! To better understand this, think about a 250x500 pixels image. If you want to get the pixel at the position
(250, 250), we need to send (250 / width, 250 / height), or (1, 0.5), as the texture coordinate. This way the size of the texture doesn't matter to the shader.
-
+> [!NOTE]
+> You can use the equation ` 1/size * pixel_position ` to get the normalized coordinate for a particlar axis!
After having configured our uniform `uTexture`, we need to bind our texture unit to it. To do so, we do it using the following lines:
```cs
@@ -309,7 +307,7 @@ With that, the texture in the texture unit 0 should be set for our sampler2D.
And now when you run it (drumroll...), you can see the image being drawn inside the quad!
-
+
## Transparency in OpenGL
Well, you must have noticed the black corners around the texture. If you use another program to check the texture, it's completely transparent! So why isn't it rendering like so?
@@ -337,7 +335,7 @@ If this isn't sufficient, there are a large amount of other blending function co
And when you run the program now, the transparent pixels of the image will not be visible anymore:
-
+
you can see the code final result [clicking here](../sources/1.3-final-result.html).
@@ -362,15 +360,15 @@ Let's see the most common values for these parameters:
#### `TextureWrapMode.Repeat`:
Just repeats the image without any change, turning any coordinates outside the [0, 1) range by taking the fractional part of said number.
-
+
#### `TextureWrapMode.MirroredRepeat`:
Mirror the texture for each 1 texture coordinate unit.
-
+
#### `TextureWrapMode.ClampToEdge`:
Returns the pixel on the respective edge of the image.
-
+
### `TextureMinFilter` & `TextureMagFilter`:
When we draw a texture, the area on the screen in which we're drawing the texture typically doesn't have the same size or shape as the texture. This means that during rendering we
@@ -386,15 +384,16 @@ pixels to the texture coordinates and will return a linear interpolation of them
This is an example from [Learn OpenGL](https://learnopengl.com/Getting-started/Textures). See how the neighbor colors are interpolated to return a different
color:
-
+
#### `Texture(Min/Mag)Filter.Nearest`:
The nearest filter returns the color of the center of the nearest pixel, no interpolation is done.
-
+
-
+> [!NOTE]
+> As `TexParameter` functions don't accepts enuns, you will have to do a explicit convertion using `(int)` in a `TexParameterI`, for integer parameters.
## Mipmaps
Now for the last part of this tutorial. Mipmaps are an essential resource for making good renders.
@@ -402,7 +401,7 @@ Now for the last part of this tutorial. Mipmaps are an essential resource for ma
But first, what are Mipmaps?
Mipmaps are a map of tiny versions of the texture. The following is an example of mipmap texture:
-
+
But what is this used for?
@@ -416,7 +415,7 @@ eliminating the moiré effect.
An example from [Wikipedia](https://en.wikipedia.org/wiki/File:Mipmap_Aliasing_Comparison.png). It's possible to notice weird patterns
generated far away in the render without mipmaps:
-
+
But if you think that generating mipmaps by hand for all your textures is really hard work, don't worry! OpenGL provides a special method to
do this for you.
@@ -457,7 +456,7 @@ And now the mipmaps will be used.
## Wrapping up
You've just completed another Silk.NET tutorial! Here are some next steps you can take:
-* Move on to the [next tutorial](../../coming-soon.html), where we'll be abstracting away some of our code to make it easier to read.
+* Move on to the next tutorial, where we'll be abstracting away some of our code to make it easier to read.
* View the full tutorial source code on the [Silk.NET git repository](https://github.com/dotnet/Silk.NET/tree/main/examples/CSharp/OpenGL%20Tutorials/Tutorial%201.3%20-%20Textures).
* Join the [Discord server](https://discord.gg/DTHHXRt), where you can ask questions, show your stuff, and chat with everyone there.
diff --git a/documentation/opengl/index.md b/documentation/opengl/index.md
new file mode 100644
index 0000000000..ed4c6067f6
--- /dev/null
+++ b/documentation/opengl/index.md
@@ -0,0 +1,5 @@
+# OpenGL Tutorials
+
+We're still working on the web, text-based walkthroughs of our example projects. However, the code is already written!
+
+You can check out some examples of using Silk.NET for OpenGL [here](https://github.com/dotnet/Silk.NET/tree/main/examples).
diff --git a/documentation/proposals/Proposal - Generation of Library Sources and PInvoke Mechanisms.md b/documentation/proposals/Proposal - Generation of Library Sources and PInvoke Mechanisms.md
index d084a74271..ff9479d8f1 100644
--- a/documentation/proposals/Proposal - Generation of Library Sources and PInvoke Mechanisms.md
+++ b/documentation/proposals/Proposal - Generation of Library Sources and PInvoke Mechanisms.md
@@ -294,7 +294,7 @@ The binding class **shall** implement the static subinterface (i.e. to proxy cal
- Will explode the repo a lot, but will also improve compile times because everything's already there and no need to generate at compile time
- ClangSharp is used by win32metadata (official c#, rust bindings) and generally accurate for parsing header files
- very correct, battle tested, more reliable than BuildTools 2.0
-- Just use ReadOnlySpan\n{x.Value}\n
"))); - } -} diff --git a/src/Website/Silk.NET.Statiq/FancyImageShortCode.cs b/src/Website/Silk.NET.Statiq/FancyImageShortCode.cs deleted file mode 100644 index 11ab0ff4da..0000000000 --- a/src/Website/Silk.NET.Statiq/FancyImageShortCode.cs +++ /dev/null @@ -1,97 +0,0 @@ -// Licensed to the .NET Foundation under one or more agreements. -// The .NET Foundation licenses this file to you under the MIT license. - -using System; -using System.Collections.Generic; -using System.Text; -using System.Threading.Tasks; -using Statiq.Common; - -namespace Silk.NET.Statiq -{ - public class FancyImageShortCode : IShortcode - { - public Task");
- sb.Append($" ");
- if (!string.IsNullOrWhiteSpace(caption))
- {
- sb.AppendLine("
");
- sb.AppendLine(caption);
- }
-
- sb.AppendLine("
Info
{Markdown.ToHtml(x.Value)}Warning
{Markdown.ToHtml(x.Value)}'
- });
- });
-
- var squares1 = document.getElementById("square1");
- var squares2 = document.getElementById("square2");
- var squares3 = document.getElementById("square3");
- var squares4 = document.getElementById("square4");
- var squares5 = document.getElementById("square5");
- var squares6 = document.getElementById("square6");
- var squares9 = document.getElementById("square7");
- var squares10 = document.getElementById("square8");
-
- if ($('.square').length != 0) {
-
- $(document).mousemove(function(e) {
- posX = event.clientX - window.innerWidth / 2;
- posY = event.clientY - window.innerWidth / 6;
-
- squares1.style.transform = "perspective(500px) rotateY(" + posX * 0.05 + "deg) rotateX(" + posY * (-0.05) + "deg)";
- squares2.style.transform = "perspective(500px) rotateY(" + posX * 0.05 + "deg) rotateX(" + posY * (-0.05) + "deg)";
- squares3.style.transform = "perspective(500px) rotateY(" + posX * 0.05 + "deg) rotateX(" + posY * (-0.05) + "deg)";
- squares4.style.transform = "perspective(500px) rotateY(" + posX * 0.05 + "deg) rotateX(" + posY * (-0.05) + "deg)";
- squares5.style.transform = "perspective(500px) rotateY(" + posX * 0.05 + "deg) rotateX(" + posY * (-0.05) + "deg)";
- squares6.style.transform = "perspective(500px) rotateY(" + posX * 0.05 + "deg) rotateX(" + posY * (-0.05) + "deg)";
- squares9.style.transform = "perspective(500px) rotateY(" + posX * 0.02 + "deg) rotateX(" + posY * (-0.02) + "deg)";
- squares10.style.transform = "perspective(500px) rotateY(" + posX * 0.02 + "deg) rotateX(" + posY * (-0.02) + "deg)";
-
- });
- }
-
- // Activate the image for the navbar-collapse
- ArgonKit.initNavbarImage();
-
- $navbar = $('.navbar[color-on-scroll]');
- scroll_distance = $navbar.attr('color-on-scroll') || 500;
-
- // Check if we have the class "navbar-color-on-scroll" then add the function to remove the class "navbar-transparent" so it will transform to a plain color.
-
- if ($('.navbar[color-on-scroll]').length != 0) {
- ArgonKit.checkScrollForTransparentNavbar();
- $(window).on('scroll', ArgonKit.checkScrollForTransparentNavbar)
- }
-
- $('.form-control').on("focus", function() {
- $(this).parent('.input-group').addClass("input-group-focus");
- }).on("blur", function() {
- $(this).parent(".input-group").removeClass("input-group-focus");
- });
-
- // Activate bootstrapSwitch
- $('.bootstrap-switch').each(function() {
- $this = $(this);
- data_on_label = $this.data('on-label') || '';
- data_off_label = $this.data('off-label') || '';
-
- $this.bootstrapSwitch({
- onText: data_on_label,
- offText: data_off_label
- });
- });
-
- // Activate Carousel
- $('.carousel').carousel({
- interval: false
- });
-
- // Datepicker
- $('.datepicker')[0] && $('.datepicker').each(function() {
- $('.datepicker').datepicker({
- disableTouchKeyboard: true,
- autoclose: false
- });
- });
-
-
- // Datepicker
- flatpickr('.flatpickr', {});
-
- // Datepicker - range
- flatpickr('.range', {
- mode: "range"
- });
-
- // DateTimePicker
- flatpickr('.datetimepicker', {
- enableTime: true,
- dateFormat: "Y-m-d H:i",
- });
-
- // Activate Sliders
- ArgonKit.initSliders();
-
- });
-
- // Methods
-
- function hideNavbarCollapse($this) {
- $this.addClass('collapsing-out');
- }
-
- function hiddenNavbarCollapse($this) {
- $this.removeClass('collapsing-out');
- }
-
-
- // Events
-
- if ($collapse.length) {
- $collapse.on({
- 'hide.bs.collapse': function() {
- hideNavbarCollapse($collapse);
- }
- })
-
- $collapse.on({
- 'hidden.bs.collapse': function() {
- hiddenNavbarCollapse($collapse);
- }
- })
- }
-
-
- // Returns a function, that, as long as it continues to be invoked, will not
- // be triggered. The function will be called after it stops being called for
- // N milliseconds. If `immediate` is passed, trigger the function on the
- // leading edge, instead of the trailing.
-
- function debounce(func, wait, immediate) {
- var timeout;
- return function() {
- var context = this,
- args = arguments;
- clearTimeout(timeout);
- timeout = setTimeout(function() {
- timeout = null;
- if (!immediate) func.apply(context, args);
- }, wait);
- if (immediate && !timeout) func.apply(context, args);
- };
- };
-
-
- ArgonKit = {
- misc: {
- navbar_menu_visible: 0
- },
-
- checkScrollForTransparentNavbar: debounce(function() {
- if ($(document).scrollTop() > scroll_distance) {
- if (transparent) {
- transparent = false;
- $('.navbar[color-on-scroll]').removeClass('navbar-transparent');
- }
- } else {
- if (!transparent) {
- transparent = true;
- $('.navbar[color-on-scroll]').addClass('navbar-transparent');
- }
- }
- }, 17),
-
- initNavbarImage: function() {
- var $navbar = $('.navbar').find('.navbar-translate').siblings('.navbar-collapse');
- var background_image = $navbar.data('nav-image');
-
- if ($(window).width() < 991 || $('body').hasClass('burger-menu')) {
- if (background_image != undefined) {
- $navbar.css('background', "url('" + background_image + "')")
- .removeAttr('data-nav-image')
- .css('background-size', "cover")
- .addClass('has-image');
- }
- } else if (background_image != undefined) {
- $navbar.css('background', "")
- .attr('data-nav-image', '' + background_image + '')
- .css('background-size', "")
- .removeClass('has-image');
- }
- },
-
- initDatePicker: function() {
- if ($datepicker.length != 0) {
- $datepicker.datetimepicker({
- icons: {
- time: "tim-icons icon-watch-time",
- date: "tim-icons icon-calendar-60",
- up: "fa fa-chevron-up",
- down: "fa fa-chevron-down",
- previous: 'tim-icons icon-minimal-left',
- next: 'tim-icons icon-minimal-right',
- today: 'fa fa-screenshot',
- clear: 'fa fa-trash',
- close: 'fa fa-remove'
- }
- });
- }
- },
-
- initSliders: function() {
- // Sliders for demo purpose in refine cards section
- var slider = document.getElementById('sliderRegular');
- if ($('#sliderRegular').length != 0) {
-
- noUiSlider.create(slider, {
- start: 40,
- connect: [true, false],
- range: {
- min: 0,
- max: 100
- }
- });
- }
-
- var slider2 = document.getElementById('sliderDouble');
-
- if ($('#sliderDouble').length != 0) {
-
- noUiSlider.create(slider2, {
- start: [20, 60],
- connect: true,
- range: {
- min: 0,
- max: 100
- }
- });
- }
- }
- }
-
-
-
- // Returns a function, that, as long as it continues to be invoked, will not
- // be triggered. The function will be called after it stops being called for
- // N milliseconds. If `immediate` is passed, trigger the function on the
- // leading edge, instead of the trailing.
-
- function debounce(func, wait, immediate) {
- var timeout;
- return function() {
- var context = this,
- args = arguments;
- clearTimeout(timeout);
- timeout = setTimeout(function() {
- timeout = null;
- if (!immediate) func.apply(context, args);
- }, wait);
- if (immediate && !timeout) func.apply(context, args);
- };
- };
\ No newline at end of file
diff --git a/website/_theme/lib/bootstrap.min.js b/website/_theme/lib/bootstrap.min.js
deleted file mode 100644
index 2b24323815..0000000000
--- a/website/_theme/lib/bootstrap.min.js
+++ /dev/null
@@ -1,6 +0,0 @@
-/*!
- * Bootstrap v4.3.1 (https://getbootstrap.com/)
- * Copyright 2011-2019 The Bootstrap Authors (https://github.com/twbs/bootstrap/graphs/contributors)
- * Licensed under MIT (https://github.com/twbs/bootstrap/blob/master/LICENSE)
- */
-!function(t,e){"object"==typeof exports&&"undefined"!=typeof module?e(exports,require("jquery"),require("popper.js")):"function"==typeof define&&define.amd?define(["exports","jquery","popper.js"],e):e((t=t||self).bootstrap={},t.jQuery,t.Popper)}(this,function(t,g,u){"use strict";function i(t,e){for(var n=0;n
'}),Ze=l({},Be.DefaultType,{content:"(string|element|function)"}),tn="fade",en="show",nn=".popover-header",on=".popover-body",rn={HIDE:"hide"+ze,HIDDEN:"hidden"+ze,SHOW:"show"+ze,SHOWN:"shown"+ze,INSERTED:"inserted"+ze,CLICK:"click"+ze,FOCUSIN:"focusin"+ze,FOCUSOUT:"focusout"+ze,MOUSEENTER:"mouseenter"+ze,MOUSELEAVE:"mouseleave"+ze},sn=function(t){var e,n;function i(){return t.apply(this,arguments)||this}n=t,(e=i).prototype=Object.create(n.prototype),(e.prototype.constructor=e).__proto__=n;var o=i.prototype;return o.isWithContent=function(){return this.getTitle()||this._getContent()},o.addAttachmentClass=function(t){g(this.getTipElement()).addClass($e+"-"+t)},o.getTipElement=function(){return this.tip=this.tip||g(this.config.template)[0],this.tip},o.setContent=function(){var t=g(this.getTipElement());this.setElementContent(t.find(nn),this.getTitle());var e=this._getContent();"function"==typeof e&&(e=e.call(this.element)),this.setElementContent(t.find(on),e),t.removeClass(tn+" "+en)},o._getContent=function(){return this.element.getAttribute("data-content")||this.config.content},o._cleanTipClass=function(){var t=g(this.getTipElement()),e=t.attr("class").match(Ge);null!==e&&0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Your one-stop-shop for high performance .NET graphics & compute. -
-Spruce up your games and applications with cross-platform 3D graphics, audio, compute and haptics. Fast. Free. Cross platform.
- --
- Supported by
-
- 
- 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Up-to-date
-With an efficient bindings regeneration mechanism, we are committed to ensuring our bindings reflect the latest specifications with monthly updates generated straight from the upstream sources.
-
- consistent
- reliable
- predictable
-
- Learn more
-
-
-
-
-
-
-
-
-
- High-level utilities
-In addition to providing high-speed, direct, and transparent bindings, we provide high-level utilities and wrappers to maximise productivity in common workloads such as platform-agnostic abstractions around Windowing and Input, bringing your apps to a vast number of platforms without changing a single line!
-
- simple
- portable
- everywhere
-
- Learn more
-
-
-
-
-
-
-
-
-
- Good-to-go
-Silk.NET caters for anything you could need in swift development of multimedia, graphics, compute applications. Silk.NET is an all-in-one solution, complete with Graphics, Compute, Audio, Input, and Windowing.
-
- swift
- smooth
- success
-
- Learn more
-
-
-
-
-
- 
-
-
-
-
-
-
-
-
-
- An all-in-one solution.
--
-
-
- ----- ----
First-party bindings for over 17 individual APIs
-
- -
- ----- ----
Official support for all major desktop & mobile platforms
-
- -
- ----- ----
Friendly & active community & developers
-
-
-
-
-
-
-
-
- Reliable & dependable.
-
-
-
-
-
-
-
- Strong backing.
-We're proud to be an official project under the benevolent .NET Foundation umbrella - an independent, non-profit organization established to support an innovative, commercially friendly, open-source ecosystem around the .NET platform with corporate sponsorship from Microsoft, Amazon AWS, and many others.
-
-
-
-
- This means you can count on us not disappearing tomorrow, and continuing to remain under steady development; a guarantee that similar libraries just can't provide.
-
-
-
-
- Continuously improving.
-We're quick to develop and release new major versions for keeping up with changes and new trends in the ecosystem. In addition, we're keen to create infrastructure to make minor incremental improvements easy to implement.
We're happy to look at any idea the community has for us, large or small, so feel free to chat to us if you think there's a way we can improve!
-
-
-
-
- Free & open.
-Silk.NET is licensed under the very permissive MIT/X11 license, which means that you can use Silk.NET in your commercial, non-commercial, hobby, or just about any other kind of project.
We offer no commercial support, which means that everyone has equal access to the best support the Silk.NET team can provide. And last but not least, we have a thriving, friendly, and approachable community who, if we're unable to for whatever reason, are happy to guide you in using our library.
-
-
-
-
-
-
-
-
-
- Ready for anything.
-Silk.NET provides a plethora of bindings to accomodate just about any multimedia, graphics, and compute workload you could possibly throw at it.
- -
- 
- 
- 
- 
- 
- 
- 
- 
- 
-
-
-
-
-
-
-
-
-
-
-
- Not your cup of tea? Try Stride.
-Silk.NET is low-level and empowers the developer with complete control over rendering. Because of this, we understand Silk.NET isn't for everyone. If you fancy something more high-level, give Stride a shot! Stride is a 2D & 3D game engine supported by the .NET Foundation.
-
-