Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
101–110 of 138 posts
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#102Earlier quoted context omitted.
The trouble is not in finding a solution that works on desktops for Linux, macOS and Windows -- we have that already 10 times over. What is needed is a protocol which can be targeted by the average JS UI framework creator. It needs to be fairly light weight, and exist mostly as a layer below any sort of framework. If that's X11, so be it, but I haven't seen it running in a browser before. One such use case would be a…
> native UI driven by React + JS. https://github.com/Microsoft/react-native-windows Watching how Microsoft manages this project may give an additional insight into how ideas you are suggesting would fare. (It doesn't seem to be a tire fire or anything from initial impressions.)
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#103Earlier quoted context omitted.
> Can't we just make a proper, easy to use portable desktop application framework please? We should just go back to Delphi, it was/is one of the best ways of doing GUIs.
Isn't delphi procedural just like e.g. Swing/AWT or Windows Forms? (Been a long time since I worked with Delphi). I think XAML/XUL and similar declarative GUIs are better.
Delphi forms are in one of two formats.
1) Binary serialization of the form data (this is the older versions, pre 4/5)
2) A textual representation.
The code for a Delphi form was pre-XML, but it looked like a set of standard markup. There were resources (Form, Button, Edit, Label - these types of control) and they were laid out in a hierarchical developer readable form in blocks. The form code was streamed to/from the file (the files were embedded as resources in the Eve, and the form was read and re-constituted at runtime as well as design time.) Borland made a massive deal about the "two way editing" one could do to the forms. The developer was able to cut and paste controls, and the controls were cut/copied as straight text, which could be pasted to notepad (for example) IIRC.
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#104Earlier quoted context omitted.
Does the binary size matter? Memory footprint is more important. There's always PyQt which works cross platform
I have used PyQt. I wouldn't suggest that it's a suitable cross-platform toolkit for anything more than the most basic applications.
Calibre (https://ic.tweakimg.net/ext/i/1324631500.jpeg)
Spyder (https://github.com/spyder-ide/spyder)
Orange (https://orange.biolab.si/screenshots/)
QGIS (https://live.osgeo.org/_images/qgis_style.png)
OpenShot (http://www.openshot.org/static/img/gallery/clip-overview.jpg)...
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#105Can't we just make a proper, easy to use portable desktop application framework please? I really don't care what language is used so log as JS is avoidable (It can still be a compilation target so it could even be JS), and I can make a snappy desktop app that takes 10 not 100mb. I'm not even sure which one I'm hoping for at the moment. Xamarin seems to have bet fully on mobile. Avalonia looks nice but feels like it w…
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#106Can't we just make a proper, easy to use portable desktop application framework please? I really don't care what language is used so log as JS is avoidable (It can still be a compilation target so it could even be JS), and I can make a snappy desktop app that takes 10 not 100mb. I'm not even sure which one I'm hoping for at the moment. Xamarin seems to have bet fully on mobile. Avalonia looks nice but feels like it w…
try Qt
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#107Earlier quoted context omitted.
Regarding native cross-platform UI frameworks, isn't this what Xwt is supposed to be ( https://github.com/mono/xwt )? There's no XAML non-sense and it's an object-oriented approach to building your UI, similar to Windows.Forms. The primary benefit to it over something browser-based is start-up time. Since it's ultimately using native assemblies and there's no web server that needs to be spun up causing start-time lag…
Maybe non-Xamarin-employee interest has declined sine the announcement of Xamarin Forms coming to the desktop? https://blog.xamarin.com/glimpse-future-xamarin-forms-3-0/ (2017May)
But one big difference between Xwt and Xamarin Forms is that Xwt supports Linux via GTK (GTK1, GTK2 & GTK3) whereas Xamarin Forms does not.
Xamarin Forms also requires different code for different targets, such as:
// Android
Forms.Init(this, null);
var androidFragment = new MyFormsPage().CreateFragment(this);
// iOS
Forms.Init()
var iosViewController = new MyFormsPage().CreateViewController();
// UWP
Forms.Init(e);
var uwpElement = new MyFormsPage().CreateFrameworkElement();Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#108Python is huge in numerical libraries (numpy/scipy) and deep learning. But it is lacking in UIs. Yes, there's PyQt, but Qt is GPL'ed, making it impossible to use at our shop. And wxPython feels really archaic to use.
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#109Earlier quoted context omitted.
try Qt
It's GPL'ed. That means it is a no-go for a lot of people. E.g., my boss would be against it.
Re: Electron.Net: Build cross platform desktop apps using .NET core and ASP.NET core
#110Can't we just make a proper, easy to use portable desktop application framework please? I really don't care what language is used so log as JS is avoidable (It can still be a compilation target so it could even be JS), and I can make a snappy desktop app that takes 10 not 100mb. I'm not even sure which one I'm hoping for at the moment. Xamarin seems to have bet fully on mobile. Avalonia looks nice but feels like it w…
Original announcement is here, and macOS support was recently added. Language development seems pretty slow, though. http://www.red-lang.org/2016/03/060-red-gui-system.html?m=1