Talk:GTK+
From Wikipedia, the free encyclopedia
[edit] GTK on non-X Window System-based environments
Request that someone add a section about GTK on Windows and OSX (expand on "GTK+ can also run under Microsoft Windows") --Wootery 19:32, 5 November 2006 (UTC)
- That would be "GTK on non-X Window System-based environments", not "GTK on non-Linux environments" - GTK+ on Solaris+X11 is just like GTK+ on Linux+X11 is just like GTK+ on FreeBSD+X11 is just like GTK+ on NetBSD+X11 is just like GTK+ on HP-UX+X11 is.... In addition, there are non-X-based Linux environments using GTK+ - see the GTK on DirectFB page. Guy Harris 00:51, 27 November 2006 (UTC)
[edit] Moving Article
i moved this article to GIMP Toolkit since i think this is a clearer solution than just using a wrong/incomplete name for technical reasons. --Pythagoras1 22:35, 5 May 2005 (UTC)
- i propose we move it back. according to Wikipedia:Announcements for January, plus signs are now allowed in article names. --Unforgettableid | talk to me 17:09, 13 January 2006 (UTC)
[edit] GIMP Toolkit/Ruby Bindings
(this discussion was copied from my talk page) - Motor (talk) 09:54:20, 2005-08-12 (UTC)
Why did you reverse my edit to GIMP Toolkit ? The information that it's architecturally unfit for garbage-collected language is true, important and relevant to in the section about support for programming languages. Taw 02:17, 11 August 2005 (UTC)
- Because with the edit (and edit summary) you were trying to make a case, and not writing a encyclopedia article (and yes, I read the link you included). As I said in my edit summary, wikipedia isn't for grinding axes, nor is it a surrogate for mailing list technical disputes. Also, considering the link you provided, I'm pretty sure it counts as original research - Motor (talk) 04:46:00, 2005-08-11 (UTC)
-
- I'm not trying to make any case, I'm merely documenting the facts, and they're not disputed by anyone.
-
-
- According to your own link, they do seem to be disputed -- if not the fact that you can provoke a memory leak (which is hardly unique), then certainly the severity of the problem. Not to mention, this isn't a highly technical article (nor is it developer documentation, or a language bindings howto).
-
-
- I and Ruby/GNOME2 developers found a problem that requires a change to Gtk architecture to fix correctly.
-
-
- I'm not disputing that you have a technical issue with GTK while writing Ruby bindings (who doesn't), nor am I interested in defending GTK developers, merely stating that Wikipedia is not the place to complain about specific "bugs". Does the official GTK documentation acknowledge the problem, if so, perhaps you could quote that?
-
-
- One of the Gtk developers that answered agreed that the problem exists, but he's clear they're not going to fix it. So nobody's disputing the facts. The problem (cooperation across GC boundaries) is not unusual, it should be documented in general in any decent reference on GC,
-
-
- Your edit was not documenting the issue. It was complaing about it. Your post to the mailing list documents the issue, and that's where it belongs. If you think it hasn't had due attention, then repost it. In fact, you might find it useful to include a link to your edited version of the article. You can find a link to it via the page history (sorry if you already know this, I'm just covering bases).
-
-
- and in the Gtk case it seems it has been already discussed, even as early as 1998, wrt Guile bindings. If you cared to read No original research, you'd see quite clearly that this has nothing to do with my edit. Taw 08:29, 12 August 2005 (UTC)
-
-
- I've read it... it is original research. You think you've found a big technical problem with GTK. Reading the link it's clear that he does not agree with you about the severity of the problem, in fact he says quite clearly that "they" designed around it. None of this is relevant -- you are quoting your own research on a mailing list as a source. As I said, the mailing list is the place for this. - Motor (talk) 09:03:52, 2005-08-12 (UTC)
-
[edit] Peer review of a related article
I submitted X Window core protocol for peer review, as I intend to candidate it for featured status. I would appreciate comments (Peer review page). - Liberatore(T) 18:07, 21 February 2006 (UTC)
[edit] "Some software that use GTK+"
It would be nice if somebody creates list of software that uses GTK+
[edit] How to port a Windows app to GTK
Is there a toolkit or developer's guide that summarises how to port a Windows or OS/2 App. to GTK. (For example, what are the equivalent functions for drawing on bitmaps, etc.?) If so, this would be a good addition to the article. 83.104.133.97 11:22, 7 July 2007 (UTC)
[edit] GTK1 and GTK2+ differences
There need to some links where the differences are documented accurately.
[edit] move to The GIMP Toolkit
I suggest to move the article to the name The GIMP Toolkit because that's the official name they give on the projects homepage (While they give you "GTK+" and "The GIMP Toolkit" below the logo in the "origins" box they tell you that "...it is named 'The GIMP Toolkit'...", so that tells me that "GTK+" is just the short form and not the full name.)
I actually already moved it without even giving a edit summary because things just seemed so clear to me, but User:Thumperward saw it differently and just moved it back because "GTK+" is used much more often.
So now I make my suggestion here cause I think we should have it under its official name and a redirect from the frequently used short form - and from the homepage I'm convinced that "The GIMP Toolkit" is the official full name.--Speck-Made 12:10, 6 September 2007 (UTC)
- And as I said on this user's talk, WP:NAME does not mandate that articles are given their full, official names if those are uncommonly used. In this case, "The Gimp Toolkit" is so rarely used that it makes little sense to keep the page there when there's no potential for ambiguity in the abbreviated version. Chris Cunningham 12:35, 6 September 2007 (UTC)
[edit] GTK 1.x
I removed the section regarding "applications still using faster GTK+ 1.x" because itis completely out of date: GTK 1.x applications that still exists to this day are generally unmaintained. Also, embedded environments don't use GTK+ 1.x anymore: they either use 2.6 (i.e. pre-cairo) or 2.10/2.12 with a recent (i.e. 1.4) release of cairo. EmmanueleBassi 13:51, 14 November 2007 (UTC)
[edit] New logo
The new look website has a much simpler logo now, I wonder if this is now the official logo and should replace the one here. bruce89 (talk) 02:31, 6 February 2008 (UTC)
- Yes, it's the new official logo as the author says on his blog. EmmanueleBassi (talk) 13:06, 12 February 2008 (UTC)
- I have uploaded the new one to Wikimedia Commons as Image:New Gtk+.svg, but I need to know its copyright status. bruce89 (talk) 23:19, 23 February 2008 (UTC)
- I asked the author (Andreas Nilsson) and he's not sure about the specific licensing. I've changed the current license to match the old logo ([GFDL]) as a temporary stop-gap, while the GNOME Foundation sorts it out. EmmanueleBassi (talk) 14:18, 25 February 2008 (UTC)
- Thanks 02:40, 5 March 2008 (UTC)
- I asked the author (Andreas Nilsson) and he's not sure about the specific licensing. I've changed the current license to match the old logo ([GFDL]) as a temporary stop-gap, while the GNOME Foundation sorts it out. EmmanueleBassi (talk) 14:18, 25 February 2008 (UTC)
- I have uploaded the new one to Wikimedia Commons as Image:New Gtk+.svg, but I need to know its copyright status. bruce89 (talk) 23:19, 23 February 2008 (UTC)
[edit] Release History
Why should there be a release history table, there must have been 100s of individual versions (2.12.0, 2.12.1 etc.). Perhaps just a table of major versions such as 2.8, 2.10 and 2.12 would be more suitable? bruce89 (talk) 02:40, 5 March 2008 (UTC)
[edit] GTK+ 3.0
What about talks on the next GTK+?
Imendio wants the next generation of GTK to enable development of better user interfaces with sophisticated visual effects, animations, physics, and stacking. Other desired improvements include stronger OS integration, improved back-end support, increased portability, easier custom widget creation, architecture that makes language bindings easier to maintain, and support for a data abstraction layer.
http://arstechnica.com/articles/culture/reinventing-gtk.ars
http://developer.imendio.com/sites/developer.imendio.com/files/gtk-hackfest-berlin2008.pdf
http://developer.imendio.com/sites/developer.imendio.com/files/imendio-gtk-vision.pdf
http://aruiz.typepad.com/siliconisland/2008/03/gtk-hackfest-20.html
http://mail.gnome.org/archives/gtk-devel-list/2008-March/msg00017.html
http://www.clutter-project.org/