Re: [Mono-list] Comparison: Windows/WPF vs Mono/Glade/Gtk
I don't think M$ wants to keep WPF for ever, every one is thinking WebAPI with Jquery -- View this message in context: http://mono.1490590.n4.nabble.com/Comparison-Windows-WPF-vs-Mono-Glade-Gtk-tp4662042p4662058.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Comparison: Windows/WPF vs Mono/Glade/Gtk
Hi, there, Has anyone worked with Glade/Gtk on a Mono across platforms? Can you provide a comparison how it stacks up in comparison/contrast with native if you will .NET WPF? Assuming C# in all cases. Gtk# with Glade or MonoDevelop: This solution is great if you don't really care very much about how things are displayed. For example, you want to have a table on the window, and you don't want to care about fonts, background colors, etc. Nearly everything in Gtk# is fixed, you can't touch it. This is probably great to give the impression of stability and consistency between platforms and applications. It is not very good if you want to somehow innovate or just do things differently. WPF is not supported in mono, and I have to confess that I haven't worked with it at all. Just WinForms is provided, and it seems that it has been abandoned: I mean, you can still create applications using WinForms, but it is not adviced to do so. It seems that nobody is taking care of the winforms code. So, embedding avalon does not seem to be possible at all. -- Baltasar (baltas...@gmail.com http://baltasarq.info/) ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Comparison: Windows/WPF vs Mono/Glade/Gtk
Hi, I am working with Gtk# a lot, in a nutshell: WPF works only on windows, so if you want your app cross-platform, don't use it. WinForms are cute on windows, ugly on linux and mac, and some features don't even works there or are glitched GTK is cute on linux, somewhat OK on windows, despite it may look alien to some users (not all controls look identical as in winforms applications), on Mac it's probably similar to windows (I don't have mac I can't test it). Biggest caveat I found in Gtk# is that it has no embedded webbrowser, so if your application needs to render web pages or html, it will be extremely complicated to get it working. Also, there is no decent GUI WYSIWYG editor. There are many of them, including mono itself, but they all are incomparable worse than WYSIWYG for WinForms that is in VisualStudio. On Thu, Feb 27, 2014 at 3:27 PM, Baltasar García Perez-Schofield baltas...@gmail.com wrote: Hi, there, Has anyone worked with Glade/Gtk on a Mono across platforms? Can you provide a comparison how it stacks up in comparison/contrast with native if you will .NET WPF? Assuming C# in all cases. Gtk# with Glade or MonoDevelop: This solution is great if you don't really care very much about how things are displayed. For example, you want to have a table on the window, and you don't want to care about fonts, background colors, etc. Nearly everything in Gtk# is fixed, you can't touch it. This is probably great to give the impression of stability and consistency between platforms and applications. It is not very good if you want to somehow innovate or just do things differently. WPF is not supported in mono, and I have to confess that I haven't worked with it at all. Just WinForms is provided, and it seems that it has been abandoned: I mean, you can still create applications using WinForms, but it is not adviced to do so. It seems that nobody is taking care of the winforms code. So, embedding avalon does not seem to be possible at all. -- Baltasar (baltas...@gmail.com http://baltasarq.info/) ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Comparison: Windows/WPF vs Mono/Glade/Gtk
WideMargin uses an embedded webbrowser with GTK# webkitsharp on linux. Works great. However we also used WPF on windows via a MVC pattern. We started with GTK on windows but found it to be ugly there and just didn't feel right. Xamarin Studio uses GTK on windows but they have heavily skinned it to look like a Mac app. So with Xamarin Studio you have a linux UI (which doesn't support linux) running on a windows operating system which looks like a Mac app. Which I find kind of amusing. Cheers, Daniel Hughes On Fri, Feb 28, 2014 at 4:06 AM, Petr Bena benap...@gmail.com wrote: Hi, I am working with Gtk# a lot, in a nutshell: WPF works only on windows, so if you want your app cross-platform, don't use it. WinForms are cute on windows, ugly on linux and mac, and some features don't even works there or are glitched GTK is cute on linux, somewhat OK on windows, despite it may look alien to some users (not all controls look identical as in winforms applications), on Mac it's probably similar to windows (I don't have mac I can't test it). Biggest caveat I found in Gtk# is that it has no embedded webbrowser, so if your application needs to render web pages or html, it will be extremely complicated to get it working. Also, there is no decent GUI WYSIWYG editor. There are many of them, including mono itself, but they all are incomparable worse than WYSIWYG for WinForms that is in VisualStudio. On Thu, Feb 27, 2014 at 3:27 PM, Baltasar García Perez-Schofield baltas...@gmail.com wrote: Hi, there, Has anyone worked with Glade/Gtk on a Mono across platforms? Can you provide a comparison how it stacks up in comparison/contrast with native if you will .NET WPF? Assuming C# in all cases. Gtk# with Glade or MonoDevelop: This solution is great if you don't really care very much about how things are displayed. For example, you want to have a table on the window, and you don't want to care about fonts, background colors, etc. Nearly everything in Gtk# is fixed, you can't touch it. This is probably great to give the impression of stability and consistency between platforms and applications. It is not very good if you want to somehow innovate or just do things differently. WPF is not supported in mono, and I have to confess that I haven't worked with it at all. Just WinForms is provided, and it seems that it has been abandoned: I mean, you can still create applications using WinForms, but it is not adviced to do so. It seems that nobody is taking care of the winforms code. So, embedding avalon does not seem to be possible at all. -- Baltasar (baltas...@gmail.com http://baltasarq.info/) ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Comparison: Windows/WPF vs Mono/Glade/Gtk
Hello, Has anyone worked with Glade/Gtk on a Mono across platforms? Can you provide a comparison how it stacks up in comparison/contrast with native if you will .NET WPF? Assuming C# in all cases. Areas of interest: * Support for MVVM design patterns; I have some sense that possibly Glade/Gtk data binding is weak-to-none. That's significant, but perhaps not a non-starter. * Support for docking libraries such as Avalon; or just docking in general. Declarative Xml is one thing, and the ability to save and restore layout, content, etc. Any any other caveats, pitfalls, gotchas. Thank ye... Best regards, Michael ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
