Closed Bug 92033 (gtk2) Opened 19 years ago Closed 11 years ago
Tracking bug for gtk2 work.
Assignee: trudelle → blizzard
May God have mercy on us all. The 212 bug spam-o-rama is Now!
QA Contact: aegis → jrgm
This will help us support the ATK! (Gnome Accessibility Toolit).
Chris, what's the status on this?
Looks like the original gtk port is in mozilla/widget/src/gtk And the gtk2 implementation has been started in mozilla/widget/src/gtk2 Don't know how much progress was made.
It's trundling along. I'm making good progress.
If you pull the GTK2_BRANCH branch in gfx/ you should be able to build.
Hi Blizzard and Aaron, browser China accessibility task force joined in working on this bug. Hope to get some help at the beginning. firstname.lastname@example.org
Now that 1.1 has branched when is this going in? Will this be the default build for unix?
In regards to the last question, GTK2 isn't released yet AFAIK let alone percolated through to the average builder's system so it'll probably be a while before GTK2 becomes the default FE (even once the GTK2FE work is more or less 'finished', which I believe it is not).
gtk2.0 is already at 2.0.3, FWIW, and I don't think 'the average builder' who builds /mozilla/ should be at all afraid of building/installing gtk, so that shouldn't at all be a consideration. That said... gtk2 moz still needs a lot of love *cough*copyandpaste*cough* before it is even seriously dogfoodable, which I think is really where the line has to be drawn for making it the default in unstable branches. Hopefully that won't take /too/ long :)  And in fact nearly ready for 2.2.0
Yikes. I stand corrected. I was basing my data on a spin of GTK2's trunk a month or two ago and thinking that it was still a long long way from release quality. Sorry.
The gtk2 code has had copy/paste for a couple of weeks now. See bug 121248 which is closed. http://lxr.mozilla.org/seamonkey/source/widget/src/gtk2/nsClipboard.cpp
Oh, great. Thanks, Chris. Adam: it is in pretty good shape; of course, we're always taking bug reports at bugzilla.gnome.org ;)
mass CCed gtk2 related bugs to email@example.com, remove browser-china- firstname.lastname@example.org from the CC list.
17 years ago
Depends on: 180500
What is going on with these bugs, there are many many bugs with patches waiting to be applied. I don't mean to cause a fuss, but blizzard obviously doesn't have the time to maintain the gtk2 port of mozilla. Could someone please look at the bugs with patches and get them applied? Nothing has gone in since the 1.3a. A perfect example of this is #183370 there has been a patch with no complaints for almost 2 months. So Can someone please start applying patches?
I've just been busy with other things, that's all. I sent robin private email saying that I was going to start going through some patches by tomorrow. I still indend to do that.
Just a polite request that folks dump latest moz-gtk2 progress into bugzilla. Those of us attempting to document mozilla's surface and insides are in planning mode on gtk2 next week. Can we see the latest? Yes, it sounds insane to think about docs before the code is finished, but that's the way it is.
I don't think we really have any docs.
Thanks Chris. Not looking for docs; just want to be sure that remaining bugs are up to date when planning for future docs occurs. Recent comments here indicate that gtk2 status changes are sometimes batched up and only hit bugzilla much later. This is just a request that any outstanding status changes and resolved issues be pushed into bugzilla. Updates to any tree or from-the-coalface docs would be celebrated at a separate party.
This bug indicates the state of the port. I don't think there's any batching up going on here.
17 years ago
Depends on: 204621
Marking fixed. This was done a few years ago.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.