Re: [Mono-list] Why doesn't Mono do cross platform GUI development like Java?
> From: mono-list-boun...@lists.ximian.com [mailto:mono-list- > boun...@lists.ximian.com] On Behalf Of Jonathan Mitchell > > It seems there is also an offering from nevron > > https://www.nevron.com There are lots of products and projects out there offering widgets and visualizations - Syncfusion, Telerik, Steema, ComponentOne, DevExpress, Infragistics... These are just the ones listed at the bottom of the page on http://xamarin.com/forms A true alternative GUI toolkit that allows you to design forms & applications and run them natively cross-platform, I believe, is what Xvm and Eto.Forms are about. Like what Windows Forms and WPF would be, if you could count on them being reliable and available cross-platform. And like what GTK would be, if given the same conditions - but unfortunately generally not safe to assume it's present or even conveniently installable. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Why doesn't Mono do cross platform GUI development like Java?
It seems there is also an offering from nevron https://www.nevron.com > On 30 Nov 2014, at 15:30, Edward Ned Harvey (mono) > wrote: > >> From: Terry Reese [mailto:ree...@gmail.com] >> >> Thanks -- I'd looked at the Xamarin forms, but I'm only interested in client >> development -- no iOS or Android, so that seems non-optimal at this point. >> The XWT sounds interesting, but I couldn't tell if it was actually an active >> project. Most of the discussion about it has been around 2012, though I see >> there have been some recent check-in on Git, so maybe. I had the same >> question with the ETO project. These seem like one off efforts, and I was >> something that was actually being baked into mono and actually maintained >> (not like Windows.Forms has been). > > I'm not sure how "active" a project needs to be - I am a maintainer on > rdiff-backup, and nobody's committed anything in like 3 years because there's > so little demand for any changes. Basically, it's stable and very little > need to continue working on it. > > Xwt and Eto, however, are a little bit different. It's understandable that > OS interfaces will change over time, some development effort will always be > needed to maintain, but there's no sign of falling below THAT threshold right > now. > > Xwt is currently used by Xamarin.Studio / Monodevelop, which suggests quite a > bit of feature capability and stability and compatibility. However, they're > moving away from it because they need more control, available by using the > native toolkits directly. In my opinion, that's not condemning to Xwt - It's > an indicator that they have sufficient development effort available as to > maintain the separate projects for each platform, but for those who can't or > don't want to afford the extra effort, Xwt could still be useful as long as > it does what you want & need it to do. > > I don't know what projects out there use Eto, but it seems to be bigger, more > robust and more actively maintained than Xwt. > > FWIW, I have not yet used either one personally. It's on the to-do list, to > evaluate them. > ___ > 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] Why doesn't Mono do cross platform GUI development like Java?
> From: Terry Reese [mailto:ree...@gmail.com] > > Thanks -- I'd looked at the Xamarin forms, but I'm only interested in client > development -- no iOS or Android, so that seems non-optimal at this point. > The XWT sounds interesting, but I couldn't tell if it was actually an active > project. Most of the discussion about it has been around 2012, though I see > there have been some recent check-in on Git, so maybe. I had the same > question with the ETO project. These seem like one off efforts, and I was > something that was actually being baked into mono and actually maintained > (not like Windows.Forms has been). I'm not sure how "active" a project needs to be - I am a maintainer on rdiff-backup, and nobody's committed anything in like 3 years because there's so little demand for any changes. Basically, it's stable and very little need to continue working on it. Xwt and Eto, however, are a little bit different. It's understandable that OS interfaces will change over time, some development effort will always be needed to maintain, but there's no sign of falling below THAT threshold right now. Xwt is currently used by Xamarin.Studio / Monodevelop, which suggests quite a bit of feature capability and stability and compatibility. However, they're moving away from it because they need more control, available by using the native toolkits directly. In my opinion, that's not condemning to Xwt - It's an indicator that they have sufficient development effort available as to maintain the separate projects for each platform, but for those who can't or don't want to afford the extra effort, Xwt could still be useful as long as it does what you want & need it to do. I don't know what projects out there use Eto, but it seems to be bigger, more robust and more actively maintained than Xwt. FWIW, I have not yet used either one personally. It's on the to-do list, to evaluate them. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mono-list Digest, Vol 115, Issue 32
> Most of the discussion about it has been around 2012, though I see there have been some recent check-in on Git, so maybe. I had the same question with the ETO project. I've been recently playing with the Eto project recently, and I'd give it about 8 pts over 10. > These seem like one off efforts, and I was something that was actually being baked into mono and actually maintained. That would be definitely great. For example, Qt has some bindings, but... nothing official, an effort (laudable effort) of a single person, I think. > (not like Windows.Forms has been). Oh, yes. I actually wonder why it is so difficult. I mean, WinForms is drawn over System.Drawing. Even if System.Drawing is based on X11... ¿would it be so difficult to change it to whatever else? I don't know. Sometimes I think about suggesting C# bindings for Fltk. It would be ugly, but I guess at least it would exist (it is a very simple toolkit). Or maybe Fltk has something like System.Drawing to draw over it. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
