4 ms·

This is great. It would be almost perfect if it didn't rely on WinForms (1) and was built on .NET core from the ground up. Anyway, great project I will keep che

This is great. It would be almost perfect if it didn't rely on WinForms (1) and was built on .NET core from the ground up. Anyway, great project I will keep checking out. (1) instead it could be a runtime that just gives you an interface to the frame buffer somehow and it's up to the integrator to use WinForms/WPF/Qt etc.

MrGilbert 7y ago
I think SDL2-CS[0] would be an awesome candidate for a platform-independent implmentation. Gives you a ton of low-level control. [0] https://github.com/flibitijibibo/SDL2-CS https://github.com/flibitijibibo/SDL2-CS
- ygra 7y ago
  It would conflict with this, though: > ProjectPSX dosn't use any external dependency and uses rather simplistic C# code. And for a learning project I think the ability to download the code and get it to run immediately without hunting for dependencies, is a very important property. More important I'd say than complicating the code to make it run everywhere.
  - ocdtrekkie 7y ago
    A platform independent desktop UI framework really is the biggest gap in the .NET platform right now, and I think Microsoft knows it. We'll probably see something new on that front soon, I'd wager.
    - ygra 7y ago
      I hope. But I don't hold my breath before .NET 5. 3.0 is all about getting Windows Desktop scenarios to .NET Core. Not many of the people who require those would benefit from a cross-platform framework, as neither Windows Forms nor WPF would be portable. Avalonia might have the chance of becoming a decent option, but even working for an employer that provides GUI controls for various platforms it's too early to decide to try supporting it. And then there's the problem that Desktop apps are kinda dying out ...
      - pjmlp 7y ago
        Except 2-1 laptops are also desktops, which many seem to keep forgetting.
      - pknopf 7y ago
        Don't forget Qml.Net. https://github.com/qmlnet/qmlnet https://github.com/qmlnet/qmlnet
    - mandeepj 7y ago
      > We'll probably see something new on that front soon MS has no interest in this space [0]. Your best bet at this moment is Electron or other open source alternates like eto forms. [0] - Scott hunter's .net rocks podcast. The related commentary is past 30 mins from beginning of the show - https://www.dotnetrocks.com/?show=1634 https://www.dotnetrocks.com/?show=1634
      - pjmlp 7y ago
        That is outdated. They were running a developer survey about that I bet our outcries are getting too loud in Redmond. Similar to those of us not bothering with Core until key frameworks got ported. https://devblogs.microsoft.com/dotnet/calling-all-net-desktop-and-mobile-developers/ https://devblogs.microsoft.com/dotnet/calling-all-net-deskto...
        tasogare 7y ago
        They made a survey but that doesn’t mean they will listen to the feedback.
        pjmlp 7y ago
        Windows Forms, WPF, C++/CLI, EF 6, .NET Native, WinUI kind of prove that they do, even if it takes a while to actually pay attention. Even in regards to WCF, I am not sure if they won't be forced to provide some gRPC migration path, when some Fortune 500 start to complain rather loudly.
        Const-me 7y ago
        > when some Fortune 500 start to complain rather loudly Not sure it’s such a huge deal, .NET core already has the most complex parts of the WCF. It has fast async TCP and named pipe streams. It has .NET binary XML support, DataContractSerializer, XmlDictionaryReader, XmlDictionaryWriter classes, technically IMO better than protocol buffers: no foreign languages, similar level of performance, convertable to/from text XML if you want a human readable format for easier debugging. When I needed RPC server in a Linux app written in .NET core, I wrote my own WCF-like thing. I’ve made a T4 template which generates requests/response & envelope classes, and channel factories, using compile-time reflection (EnvDTE stuff) of my service contracts. Took me a few hours. These Fortune 500 companies can probably afford doing the same when they need RPC in .NET.
    - WorldMaker 7y ago
      Microsoft for two BUILD conferences now has stated putting more weight into Xamarin tooling for desktop as well as mobile (WPF, Cocoa, and Gtk renderers for Xamarin) is an end goal. They exist as community projects already (find them all on GitHub), and it continues to sound like Microsoft only expects to invest in them so much as they find community interests, and maybe a reason we don't hear a lot of people talking about those projects is there sadly isn't enough non-Microsoft community interest in such tools.
BluestormDNA 7y ago
That's a very nice idea. I went with WinForms as it was the "stupid easy way" infact on the first i just updated a PictureBox. There was a time when i had a SDL multiplatform branch but it was noticeably slower so i didn't put much effort on it and it ended deleted. I mainly focused on the core PSX things and not much on the program itself like the emulator window itself...
- lostgame 7y ago
  >> I mainly focused on the core PSX things and not much on the program itself like the emulator window itself... As you should. Core functionality always comes first. UI can always be messed about with after, when it 'just works'. Also, fantastic work, here! :)

MrGilbert 7y ago

I think SDL2-CS[0] would be an awesome candidate for a platform-independent implmentation. Gives you a ton of low-level control. [0] https://github.com/flibitijibibo/SDL2-CS https://github.com/flibitijibibo/SDL2-CS

ygra 7y ago
It would conflict with this, though: > ProjectPSX dosn't use any external dependency and uses rather simplistic C# code. And for a learning project I think the ability to download the code and get it to run immediately without hunting for dependencies, is a very important property. More important I'd say than complicating the code to make it run everywhere.
- ocdtrekkie 7y ago
  A platform independent desktop UI framework really is the biggest gap in the .NET platform right now, and I think Microsoft knows it. We'll probably see something new on that front soon, I'd wager.
  - ygra 7y ago
    I hope. But I don't hold my breath before .NET 5. 3.0 is all about getting Windows Desktop scenarios to .NET Core. Not many of the people who require those would benefit from a cross-platform framework, as neither Windows Forms nor WPF would be portable. Avalonia might have the chance of becoming a decent option, but even working for an employer that provides GUI controls for various platforms it's too early to decide to try supporting it. And then there's the problem that Desktop apps are kinda dying out ...
    - pjmlp 7y ago
      Except 2-1 laptops are also desktops, which many seem to keep forgetting.
    - pknopf 7y ago
      Don't forget Qml.Net. https://github.com/qmlnet/qmlnet https://github.com/qmlnet/qmlnet
  - mandeepj 7y ago
    > We'll probably see something new on that front soon MS has no interest in this space [0]. Your best bet at this moment is Electron or other open source alternates like eto forms. [0] - Scott hunter's .net rocks podcast. The related commentary is past 30 mins from beginning of the show - https://www.dotnetrocks.com/?show=1634 https://www.dotnetrocks.com/?show=1634
    - pjmlp 7y ago
      That is outdated. They were running a developer survey about that I bet our outcries are getting too loud in Redmond. Similar to those of us not bothering with Core until key frameworks got ported. https://devblogs.microsoft.com/dotnet/calling-all-net-desktop-and-mobile-developers/ https://devblogs.microsoft.com/dotnet/calling-all-net-deskto...
      - tasogare 7y ago
        They made a survey but that doesn’t mean they will listen to the feedback.
        pjmlp 7y ago
        Windows Forms, WPF, C++/CLI, EF 6, .NET Native, WinUI kind of prove that they do, even if it takes a while to actually pay attention. Even in regards to WCF, I am not sure if they won't be forced to provide some gRPC migration path, when some Fortune 500 start to complain rather loudly.
        Const-me 7y ago
        > when some Fortune 500 start to complain rather loudly Not sure it’s such a huge deal, .NET core already has the most complex parts of the WCF. It has fast async TCP and named pipe streams. It has .NET binary XML support, DataContractSerializer, XmlDictionaryReader, XmlDictionaryWriter classes, technically IMO better than protocol buffers: no foreign languages, similar level of performance, convertable to/from text XML if you want a human readable format for easier debugging. When I needed RPC server in a Linux app written in .NET core, I wrote my own WCF-like thing. I’ve made a T4 template which generates requests/response & envelope classes, and channel factories, using compile-time reflection (EnvDTE stuff) of my service contracts. Took me a few hours. These Fortune 500 companies can probably afford doing the same when they need RPC in .NET.
  - WorldMaker 7y ago
    Microsoft for two BUILD conferences now has stated putting more weight into Xamarin tooling for desktop as well as mobile (WPF, Cocoa, and Gtk renderers for Xamarin) is an end goal. They exist as community projects already (find them all on GitHub), and it continues to sound like Microsoft only expects to invest in them so much as they find community interests, and maybe a reason we don't hear a lot of people talking about those projects is there sadly isn't enough non-Microsoft community interest in such tools.

BluestormDNA 7y ago

That's a very nice idea. I went with WinForms as it was the "stupid easy way" infact on the first i just updated a PictureBox. There was a time when i had a SDL multiplatform branch but it was noticeably slower so i didn't put much effort on it and it ended deleted. I mainly focused on the core PSX things and not much on the program itself like the emulator window itself...

lostgame 7y ago
>> I mainly focused on the core PSX things and not much on the program itself like the emulator window itself... As you should. Core functionality always comes first. UI can always be messed about with after, when it 'just works'. Also, fantastic work, here! :)