[Gtk-sharp-list] Gtk libraries
Adam Tauno Williams
awilliam at whitemice.org
Thu Oct 18 21:26:12 UTC 2012
On Fri, 2012-10-12 at 08:12 -0400, Andrew York wrote:
> Please correct me if I'm wrong but I don't think that the Gtk interface
> is a focus of Mono/Monodevelop anymore.
I don't know if it ever was a focus of 'Mono'.,
> They make most if not all of
> their money from iPad and Android based development so there is not a
> lot of motivation to make these changes even if they are helpful.
You are confusing the Xamarin people with the Mono community. No I
wouldn't expect anything useful to come from Xamarin. You can't even
use Xamarin stuff on Linux.
> Also are not the Mono dev leaders planning on switching to XWT in
>the next year or so. I'm not sure how much focus will be on Gtk in
>the future, but again I may be wrong.
Gtk is ultimately bound to GNOME. And there are top-notch GNOME
applications that use Gtk#. The work on the bindings I'd expect to come
from that angle.
"Xwt is a new .NET framework for creating desktop applications that run
on multiple platforms from the same codebase. Xwt works by exposing one
unified API across all environments that is mapped to a set of native
controls on each platform."
I wish them the best of luck, but I've heard this song before, and it
doesn't usually work out well. The underlying controls don't correspond
to each other 1:1 and you get left with least-common-denominator and
lots of edge conditions. Even if that works out there is the question
of how hard they will work on the Gtk backend [xwt sits on top of a
'native' toolkit, one backend is Gtk]. So you could end up with xwt as
a cross-toolkit abstraction layer that works on Windows and Mac and
others are red-headed step-children. I doubt Xamarin has any real
interest in anything outside of Windows and Mac.
As for Gtk versions an Monodevelop - in the previous thread I don't see
any reference to opening a MD bug about the supporting later versions.
That would be step #1 I think.
> On 10/12/2012 7:12 AM, Doug Blank wrote:
> > On Thu, Oct 11, 2012 at 3:34 AM, Elmar Haneke <elmar at haneke.de> wrote:
> >>> This is useful information! Where did you get your binaries? What
> >>> versions are you using? Are they pre-built somewhere? I really just
> >>> need the Mac and Windows fixes for the above issues.
> >> I'm using the binaries from www.gtk.org.
> >>> The only binaries available on the site mentioned above are 2.24.
> >> There are several binaries available once you have a look at the
> >> FTP-Server linked from the summary page:
> >> http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/
> >> Perhaps the 2.22 binary does help.
> > Thank you, thank you! Mono/MonoDevelop should come with these, but if
> > not, *every* system that deploys Gtk on Windows should use these
> > binaries. It is a shame that hard work has gone into fixing these
> > bugs, but they haven't made their way into all of the places that they
> > should.
> > I copied the binaries from:
> > http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.22/gtk+_2.22.1-1_win32.zip
> > into my deployed mono\bin directory, and that appears to work with all
> > testing so far. (If anyone knows of a potential incompatibility please
> > let us know.
> > The most important fix for us was that we can now use the clipboard to
> > copy text out of our application.
More information about the Gtk-sharp-list