Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Balnian

Pages: [1]
DotNet / What should be the criteria for .Net Core Merge? (Community Input)
« on: November 22, 2017, 10:19:48 pm »
Since the PR has been open for a couple of month, i would like to know what should be the criteria to merge the PR?
Exemples :
  • Works on Windows, Mac, Linux
  • Works/tested on Windows ONLY (same as current repo?)
  • Works on Windows, Linux (because we cannot test Mac?)
  • ...

Please feel free to express your opinion!!!

  • Make SFML.Net work with .Net Core 2.0
  • Native Windows, Linux, Mac support (.Net Core 2.0)
  • Exemples in the repo using OpenTK (OpenGL in C#) are broken because OpenTK hasn't been ported to .Net Core (we might leave 1 OpenGL exemple "broken" until the OpenTK team port to .Net Core and clean up other exemples using it)
  • The PR has been tested on Windows and Ubuntu 16.04 (please feel free to test other OS, distro and architecture like ARM...)

DotNet / .Net Core Real Talk
« on: June 22, 2017, 05:21:14 pm »
Hi, there's now 2 PR for a .Net Core conversion to SFML.Net, but one thing people don't seem to understand, is that changing the project to .Net Core has impact on the minimum version of of .Net Framework that will be needed to use SFML.Net (the minimum version will become 4.5+) https://docs.microsoft.com/en-us/dotnet/standard/net-standard#net-platforms-support

Also some things are not yet in for .Net Core like VB support coming in 2.0 https://blogs.msdn.microsoft.com/dotnet/2017/05/10/announcing-net-core-2-0-preview-1/, missing CriticalFinalizerObject (also coming in 2.0) and OpenTK has not been updated to .Net Core yet.

But, on the other side, we would be able to build SFML.Net project that would work on Linux, Mac, Windows, ... all natively, there's also the fact that .Net Core is faster then .Net Framework https://blogs.msdn.microsoft.com/dotnet/2017/06/07/performance-improvements-in-net-core/

Finally... should we change SFML.Net to.Net Core or create a new binding called SFML.Net Core (or something else...because this one might confuse some people)

Please use this post to discuss the matter, it's not an official/sanctioned post but i think it's an healthy discussion to have together.

Feature requests / Websocket
« on: March 16, 2017, 07:02:17 pm »
I think it would be nice that we add websocket to the nework module, because normaly to use a websocket in c++ you either have to include a whole network library on the side of sfml network module just for the websocket or you can do your own wrapper out of libwebsocket which doesn't look fun to do/use.

Also since websocket are based on HTTP it could be a good thing to update sfml HTTP at the same time :P ... Or we can just wrappe libwebsocket and forget about HTTP  ;D

DotNet / SFML.Net Core???
« on: December 16, 2016, 10:44:53 pm »
Is there a reason that the last release of the binding wasn't made to support Dotnet Core?
With dotnet Core support it would allow cross platform support of the binding.

I was able to convert the current code of the repo to a working Dotnet Core lib in about 20 minutes, i had to change 2 things ( CriticalFinalizerObject of Window/context.cs to a IDisposable and the [Serializable] of Window/LoadingFailedException.cs was removed) and some other small changes like to the basic project file to allow unsafe code...
I would have like to make it available by nuggets but i don't have much experience with doing that and i didn't test the cross platform aspect (but it should work... just swap the CSFML libs for windows for the platform specific ones in the project root)

^ first post hope i don't have to many spelling mistakes   ;D

Pages: [1]