[Mono-list] Newbie question: GUI choice
Hey guys, I'm considering Mono as the environment for a cross-platform GUI application I'm designing. The app would ideally run with just one code base on Linux, OS X, and Windows. Is Windows.Forms the best choice for cross-platform GUI programming in Mono? I assume that Gtk# is Linux-specific, and Qt# looks like its going nowhere. Thanks, Christian ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
Windows.Forms is a solution yes but Gtk# works today on Linux, Unixes and Windows. See the GTK+/GTK# installer for Windows on forge.novell.com Erik Christian Convey wrote: Hey guys, I'm considering Mono as the environment for a cross-platform GUI application I'm designing. The app would ideally run with just one code base on Linux, OS X, and Windows. Is Windows.Forms the best choice for cross-platform GUI programming in Mono? I assume that Gtk# is Linux-specific, and Qt# looks like its going nowhere. Thanks, Christian ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
Hello, I'm considering Mono as the environment for a cross-platform GUI application I'm designing. The app would ideally run with just one code base on Linux, OS X, and Windows. Is Windows.Forms the best choice for cross-platform GUI programming in Mono? I assume that Gtk# is Linux-specific, and Qt# looks like its going nowhere. You may also want to consider wx.NET. It uses /native/ widgets on each platform that you mentioned. Gtk# does work on OSX, but requires the X11 server to be installed, which may or may not be a deployment issue. You can see wx.NET screenshots at: http://wxnet.sourceforge.net/screenshots/ (Disclaimer: I am a wx.NET developer :-) ) Cheers. -- Bryan Bulten http://www.bulten.ca/ http://wxnet.sourceforge.net/ ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
I'm considering Mono as the environment for a cross-platform GUI application I'm designing. The app would ideally run with just one code base on Linux, OS X, and Windows. Is Windows.Forms the best choice for cross-platform GUI programming in Mono? I assume that Gtk# is Linux-specific, and Qt# looks like its going nowhere. GTK# is cross-platform, but has lots of DLLs etc. you have to deploy with it I think mono does implement WinForms more or less so you'd better use that - George Birbilis ([EMAIL PROTECTED]) http://www.kagi.com/birbilis -- ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
I'm considering Mono as the environment for a cross-platform GUI application I'm designing. The app would ideally run with just one code base on Linux, OS X, and Windows. Is Windows.Forms the best choice for cross-platform GUI programming in Mono? I assume that Gtk# is Linux-specific, and Qt# looks like its going nowhere. GTK# is cross-platform, but has lots of DLLs etc. you have to deploy with it I think mono does implement WinForms more or less so you'd better use that I don't think using Windows.Forms will work. Unless I am wrong, mono is the only (or the only major) .NET-compatible CLI for the PowerPC platform. However, mono implements Windows.Forms through winelib, which is entirely dependent upon the x86 platform. Thus, Windows.Forms code is not portable to PowerPC through mono. However, there may be another PowerPC CLI out there that can handle Windows.Forms. If not, Gtk# will be your best bet, since it is cross-platform compatible as long as the GTK library is installed. However, be careful to avoid Gnome#, since that library is entirely dependent upon the GNOME desktop environment. -- Stephen Touset [EMAIL PROTECTED] ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
Qt# is not going very quickly, but it is not dead. On Tuesday 09 November 2004 11:00 am, Christian Convey wrote: Qt# looks like its going nowhere. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
Hello Stephen, On Tue, 2004-11-09 at 17:24 -0500, Stephen Touset wrote: I don't think using Windows.Forms will work. Unless I am wrong, mono is the only (or the only major) .NET-compatible CLI for the PowerPC platform. However, mono implements Windows.Forms through winelib, which is entirely dependent upon the x86 platform. Thus, Windows.Forms code is not portable to PowerPC through mono. This is no longer true. The current, ongoing implementation of System.Windows.Forms is built directly on top of libgdiplus, which is our implementation of GDIPLUS.DLL using Cairo (http://www.cairographics.org). We have stopped developing the Wine-based Windows Form implementation for more than 6 months. When completed, you will be able to run WinForms app on top of an X11 server on Mac OS X. There is also ongoing work in the Cairo team to natively support the OSX Core Graphics system. When that is completed, you will be able to run WinForms apps directly on OS X without an X server. -- Duncan Mak [EMAIL PROTECTED] ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
Qt# is not going very quickly, but it is not dead. That would be perfect if in the future Windows.Form would use Qt# under kde and Gtk# under Gnome. That would bring consistency to mono applications under unixes and GUI consistency is what unixes need. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
The current, ongoing implementation of System.Windows.Forms is built directly on top of libgdiplus, which is our implementation of GDIPLUS.DLL using Cairo (http://www.cairographics.org). We have stopped developing the Wine-based Windows Form implementation for more than 6 months. I had not heard of this, but it is useful information. Nonetheless, I believe my point still has some merit. From what I understand through some quick skimming of recent Mono developments is that this libgdiplus implementation is far from complete, and missing implementations for crucial windowing elements. As it stands, I still think it would be better to build cross-platform applications using Gtk# at this time, since Gtk# is fully (or almost-fully) implemented in mono. No offense is meant towards Ximian's excellent development efforts, but I feel that if the OP is intending to develop a product for commercial release, they can't rely on the new Windows.Forms implementation until it has been released, or is at least nearing completion. -- Stephen Touset [EMAIL PROTECTED] ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
That would be perfect if in the future Windows.Form would use Qt# under kde and Gtk# under Gnome. As I understand it, this is probably not likely to happen any time in the near future. The Qt and Gtk APIs not only differ by their function calls, but their basic architecture, too. It would be an extremely difficult endeavor to create an API that fully-exposed the features in different windowing system architectures. -- Stephen Touset [EMAIL PROTECTED] ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
Hello Fabien, On Tue, 2004-11-09 at 23:45 +0100, Fabien Meghazi wrote: That would be perfect if in the future Windows.Form would use Qt# under kde and Gtk# under Gnome. That would bring consistency to mono applications under unixes and GUI consistency is what unixes need. The current implementation of Windows Forms is already the 3rd design of how to implement such an API. In the initial implementation, we tried to abstract the API into an intermediate layer with interfaces, believing that it is possible to have multiple pluggable rendering back-ends as you've suggested above. Very quickly, the complexity of the managing the various layers of abstractions got completely out of control. Other than very simple demos (one form, one button), we were not able to get anything to work. The current implementation, based on libgdiplus/GDIPLUS.DLL, is the simplest design yet. Hopefully this design will stick. -- Duncan Mak [EMAIL PROTECTED] ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question: GUI choice
Il giorno 09/nov/04, alle 23:30, [EMAIL PROTECTED] ha scritto: I don't think using Windows.Forms will work. Unless I am wrong, mono is the only (or the only major) .NET-compatible CLI for the PowerPC platform. However, mono implements Windows.Forms through winelib, which is entirely dependent upon the x86 platform. Thus, Windows.Forms code is not portable to PowerPC through mono. Ahem. Don't forget DotGNU, whose Portable.NET works on Mac/PPC and has a working, non-depending-on-winelib Windows.Forms implementation (that has its fair share of problems: requires X11 and is incomplete AFAIK, implementing only part of .NET 1.0's WinForms behaviour). I'd be intriguing (if I manage to find some time) to try something with Managed WinForms+Cocoa#... - e. l0ne v. -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Software per PC e non solo...scopri tutto quello che c'รจ da sapere! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2969d=10-11 ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
