[Mono-list] Porting Microsoft.Reporting.WinForms to Mono?

[Michael Hutchinson]

Yes, GTK# is a thin C# wrapper over the C library, the API is pretty
much exactly the same except with "C#-ified" names.

The only gotcha is that the GTK# 2 API is frozen at GTK+ 2.12 - though
of course you can P/Invoke into newer API pretty easily, like we do
for MonoDevelop. There's a GTK# 3, which is a wrapper over GTK+ 3.x,
but it hasn't yet had a stable release AFAIK.

- M

On 5 March 2014 18:48, Michael McGlothlin <mike.mcglothlin at gmail.com> wrote:
> I've used Gtk under Linux so I'd guess Gtk# might be similar? I'm already
> trying to figure out how to mesh together the C# way of doing things with
> the iOS, Android, etc way while maximizing code reuse. Keep finding myself
> cycling through different methods or rolling my own but not sure what the
> best way is. Lots to process.
>
> Thanks,
> Michael McGlothlin
> Sent from my iPhone
>
> On Mar 5, 2014, at 10:56 AM, "Andy York" <andy at brdstudio.net> wrote:
>
> I would like to warn you that learning some of the Gtk# API was a challenge
> for me at first because I was stuck in the Microsoft way of doing things.
> Once I learned how to use Gtk# effectively I loved it but not at first.
>
> For example the Gtk.TreeView does not work anything like WinForms.GridView
> and everyone I know who tried to make the Gtk.TreeView work like a
> WinForms.GridView didn't succeed but preferred the Gtk.TreeView +
> Gtk.TreeStore methods in the end.
>
> In the long run it feels to me like Gtk# is easier to use MVC techniques on
> than WinForms so if you have the time to learn the Gtk# API I recommend it
> very highly for cross platform development.
>
> This is just the opinion of a humble developer nothing more.
>
>
> ________________________________
> From: "Miguel de Icaza" <miguel at xamarin.com>
> Sent: Wednesday, March 05, 2014 11:47 AM
> To: "Michael McGlothlin" <mike.mcglothlin at gmail.com>
> Subject: Re: [Mono-list] Porting Microsoft.Reporting.WinForms to Mono?
>
> Hey,
>
> Mono has an implementaiton of Windows.Forms, but it is both old,
> unmaintainted and known to have some bugs.
>
> Some people have been able to use it effectively, but we do not currently
> have an active maintainer, so we encourage developers to pick something like
> Gtk# instead.
>
>
> On Thu, Feb 27, 2014 at 3:21 PM, Michael McGlothlin
> <mike.mcglothlin at gmail.com> wrote:
>>
>> [Intro: I'm somewhat new to C# and am much more familiar with Linux and
>> MacOS than Windows. In the past few months I've been learning C# to develop
>> Xamarin.iOS apps and simply trying to wrap my mind around this combination
>> of C# and iOS stuff that doesn't always make sense to someone that's been
>> doing command-line and server-side Unix, Python, and JavaScript stuff
>> mostly.]
>>
>> I've been asked to fix, update and make portable an app build around
>> Microsoft.Reporting.WinForms. From searching I see a bunch of old posts
>> saying that Mono doesn't support WinForms but nothing very recent. I don't
>> really know much about it so my basic question is if there is an easy fix
>> (add the needed assembly somewhere) and if not what is the recommended way
>> to handle porting?
>>
>> I had nothing to do with writing this app and it's fairly large, complex,
>> and seems poorly written but as much as I'd like to do a total remit it's
>> probably not the best strategy at the moment.
>>
>>
>> Sent from my iPad
>> Michael McGlothlin
>> _______________________________________________
>> Mono-list maillist  -  Mono-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-list
>
>
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>
>
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>



-- 
Michael Hutchinson
http://mjhutchinson.com