silk.net.maths could very easily be used in an opentk application
silk.net.maths could very easily be used in an opentk application
Pso it's the same difference really
Sspeaking of opentk,may i ask some questions related to opentk?
Ptheir server is the best place to get help using opentk
Snot help really tbh
Sthey are infact more related to silk
Sso
Slet me get an essay started/s
S-why is the GL not static like opentk?
-why is window an interface instead of an abstract class?
-why does silk use unsafe code?
-why isn't there documation?
-why isn't the silk website updated?
-why is window an interface instead of an abstract class?
-why does silk use unsafe code?
-why isn't there documation?
-why isn't the silk website updated?
P- Because the function pointers are tied to the OpenGL context being use. The way OpenTK handled this was maintained some secret static state (mutable static state is evil!) that you needed to explicitly switch out if you were using multiple contexts, whereas we just tie the functions to the context themselves by virtue of having an instance. In addition, it means that all of the memory consumed by the function pointer table can be freed when you're done with the object, rather than have it always linger in static state.
- Because it doesn't need to be an abstract class? The windowing interfaces just define a "contract" for what APIs windowing implementations need to implement, which is the very definition of an interface. We have an abstract class internally for helping us write our own first-party applications. Unless you mean why isn't it an abstract class _you_ can inherit from? The answer to that is we're not going to force all of our users to use our APIs in a specific way, especially if that's not how our APIs are represented internally. We're not going to use a design pattern just for the sake of using it, our users can do that.
- Two answers to this:
- If a function uses an unsafe function (i.e. literally any function that leaves C#'s managed land and/or uses raw memory management), the caller function is only as safe as the additional checks it provides prior to accessing the callee. Given Silk.NET provides no checks, philosophically **all of Silk.NET is unsafe, even functions that don't use pointers**. What I'm trying to say is: **don't be afraid of unsafe**.
- Most of our OpenGL bindings have fully "safe" overloads (in/out/ref/Span) for functions that deal in single-dimension pointers. Pointers of two dimensions or more do not get overloaded into anything meaningful today. And for the other bindings, structs don't get overloaded and are always unsafe.
P- Because noone has made the time to add some. We welcome community contributions in this area, it is very hard for a maintainer to maintain the entirety of Silk.NET in their free time _and_ still have time left over to write documentation at the end of it.
- Because noone has made the time to update it. We welcome community contributions in this area, it is very hard for a maintainer to maintain the entirety of Silk.NET in their free time _and_ still have time left over to update the website at the end of it.
AHaving the window system the way it is is literally 100x nicer than the OpenTK way
I switched to GLFW for the sole reason that I hated OpenTK windowing, it was in my experience laggy and the fact that you had to inherit off it meant yeah I couldn't design it in the way I wanted it to be
The silk windowing makes it tempting just to write a minimal abstract around it so it can fit in with the current windowing system I already have
I switched to GLFW for the sole reason that I hated OpenTK windowing, it was in my experience laggy and the fact that you had to inherit off it meant yeah I couldn't design it in the way I wanted it to be
The silk windowing makes it tempting just to write a minimal abstract around it so it can fit in with the current windowing system I already have
ABut I'm insane so I'll probably continue to write my own windowing system even if it provides literally the same functions lmao
Li have also written a very light wrapper around windowing to fit with the style of my code
Lits a really really nice interface
Pimagine if you couldn't trivially make it fit with the style of your code though
Lthat would be very slightly annoying but id probably figure it out after awhile
Lwoudlnt be as clean tho
Pexactly
PSilk.NET 1.0 was very strategically designed
PFor 2.0 we sorta forgot who we were a bit and rushed ahead to get loads more bindings and mobile support
Land it shows with the state of buildtools
PAnd in 3.0 we've returned to that strategic design (even better than last time as well)
L(still doesnt run under linux no matter how much fiddling ive done)
Simagine using......(i have been adivised to not continue this sentance to avoid a controverisy)
Li mean i think eventually being able to have a linux ci run the bindings regeneration on request then open a PR would be sick
AAt that point you could buy a dedicated server or two and have it run bindings generation
Lalso me being able to work on BuildTools at all would also be cool
Ldw DNF pays for our CI
AWould probably do it at twice the speed
Anice
AIdk what ci is but nice
Pftr the .NET Foundation has still given us diddly squat on the server front after nearly 9 months
Lcontinuous integration
Pgod 3.0 is CI is soooo goooooooood
Sis the .net foundation related to microsoft or is it just sort of something unrelated?
Lo i should try running 3.0 build tools under linux
Lat least what we have so far
PMicrosoft founded it and is the largest corporate sponsor
Lat least some of the tests
AI need to look up what CI is
Pall of the intellectual property Microsoft produces for .NET is owned by the .NET Foundation
Swait,does linux support C#?,i think it only supports it using certain stuff
Scould be wrong trho
Stho*
P....where have you been for the last 8 years haha
Llinux runs c# just fine lol
Sso you technically own C#?
Leven dotnet framework apps run p well under linux
Lwhat?
