wait, so silk doesn't have the pure-android implementation yet?
wait, so silk doesn't have the pure-android implementation yet?
Li wish
Twas that a 3.0 thing that i just thought was real
RThey don't have a pure anything implementation. They use SDL and GLFW for their windowing systems
Pno we will do
Pbut 3.0 has effectively zero (0) lines of code
RBut yes, the plan is to go full native
Pwell that’s also false information
Pwe will use GLFW on desktop at least initially
Lnot 100% full, we will have GLFW
Lye
RFair enough
Tguess i'll just go huff copium
LGLFW will be the "sane fallback"
RI suppose that makes sense.
Lwhen there's no platform code
Pwe need a fallback that’s all
RI thought it was just a temporary thing
Pwe will build up full native over time
Lonly platforms on desktop we will need is X11, Wayland, Win32, and Cocoa i think?
PWe don’t even have maintenance effort to make a GLFW 3.0 let alone a full native 3.0
PMac doesn’t deserve our dev time tbh, but everything else yeah
Fsad Mac noises
RI'm still confused just to how the windowing implementation is supposed to work. The proposal does not help me in the slightest
Lmaybe i'll toy around with a DRM impl
Falthough apple computers arent supposed to make noise
Pfeel free to amend the proposal. It is open source after all.
PRight now all I’ve been told is “there are problems”
Pthe idea is you have an ISurface. If the backend can support it you’ll be able to cast it to a specialised surface. If the backend does support it, the TryEnabke methods return true
RThat helps explain it, I think, but I probably won't be back to work on it for a while, I think the PR and branch are still up if anyone wants to have a go. I have kinda started moving my personal project away from C#, so it means I am working elsewhere, I also have full time non programming work now, that has me up at 2 in the morning
RSo I have very little energy to do anything outside of work, and the energy I do have I end up putting into my own projects.
Pk
FIn Silk.Net tutorials (from repo) code is structured in classes like Shader, Texture etc. Is it how the real project should be organized or its just for demonstaration purposes for easy learning?
Lyou can structure it however you like
Labstractions over GL range a lot
ZThat's the best part tbh
Lits good to note you dont always have to abstract over every part of GL
Llike if you only ever need 1 shader you dont need a shader abstraction
ZI mean it's probably still good to have a basic abstraction in case you might need it later
ZBut depends
Lyeah it really depends
Zarchitecture can really get wild sometimes
Lmy engine has a shader abstraction that i really havent needed in months (i have cut my engine down to only need a single shader for everything) but i havent deleted them since they are helpful incase i do ever need it in the unlikely scenario
ZIs your engine GL-based?
Lit was originally built for GL, but has expanded much further
Zoh wow
ZThat sure is a lot
Lthis is after i culled veldrid too lol
LD3D9 is on another branch
Land GL is technically 2 separate backends, one for FFP and one for modern
ZWas there something wrong with it?
