Closed Bug 92033 (gtk2) Opened 19 years ago Closed 11 years ago

gtk2 port

Categories

(Core :: XUL, defect)

x86
Linux
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: blizzard, Assigned: blizzard)

References

(Depends on 5 open bugs)

Details

(Keywords: access, meta)

Tracking bug for gtk2 work.
Depends on: 92034
-> blizzard@mozilla.org
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).
Keywords: access
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.
Depends on: 121246
Depends on: 121248
Depends on: 121251
Depends on: 121252
Depends on: 121253
Depends on: 121254
Depends on: 121255
Depends on: 121256
Depends on: 121257
Depends on: 121258
Depends on: 121259
Depends on: 121260
Depends on: 121262
Depends on: 121263
Depends on: 121264
Depends on: 121265
Depends on: 121266
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.
jay.yan@sun.com
Depends on: 121613
Depends on: 121615
Depends on: 122131
Depends on: 122429
Depends on: 123197
Depends on: 131041
Depends on: 131043
Depends on: 137106
Depends on: 136315
Now that 1.1 has branched when is this going in?
Will this be the default build for unix?
Depends on: 139726
Depends on: 140698
Depends on: 140868
Depends on: 140873
Depends on: 140878
Depends on: 140867
Depends on: 140896
Depends on: 140897
Depends on: 140900
Depends on: 140902
Depends on: 140903
Depends on: 140904
QA Contact: jrgm → nobody
Depends on: 141075
Depends on: 141077
Depends on: 141081
Depends on: 141092
Depends on: 141094
Depends on: 141239
Depends on: 141669
Depends on: 144212
Depends on: 144215
Depends on: 143993
Depends on: 143991
Depends on: 144421
Depends on: 145601
Depends on: 148065
Depends on: 148309
Depends on: 145863
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[1], 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 :) 
[1] 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 ;) 
Depends on: 153805
Depends on: 154348
Depends on: 156093
Depends on: 156593
Depends on: 157438
Depends on: 160589
Depends on: 160621
Depends on: 162363
Depends on: 162507
Depends on: 163358
Depends on: 163257
Depends on: 162250
Depends on: 164994
Depends on: 165558
mass CCed gtk2 related bugs to browser-china-gtk2@sun.com, remove browser-china-
atf@sun.com from the CC list.
Depends on: 166138
Depends on: 166202
Depends on: 167782
Depends on: 169094
Depends on: 169096
Depends on: 169108
Depends on: 169340
Depends on: 169635
Alias: gtk2
Depends on: 170919
Depends on: 171461
Depends on: 172203
Depends on: 172103
Depends on: 173225
Depends on: 173640
Depends on: 173849
Depends on: 174471
Depends on: 174058
Depends on: 175947
Depends on: 176299
Depends on: 176514
Depends on: 176518
Depends on: 176341
Depends on: 176708
Depends on: 176713
Depends on: 176716
Depends on: 176842
Depends on: 176556
Depends on: 177405
Depends on: 177665
Depends on: 178045
Depends on: 178067
Depends on: 178145
Depends on: 177905
Depends on: 178404
Depends on: 178501
Depends on: 178732
Depends on: 178764
Depends on: 178805
Depends on: 179078
Depends on: 179181
Depends on: 179512
Depends on: 179657
Depends on: 179667
Depends on: 179740
Depends on: 179832
Depends on: 180052
Depends on: 180123
Depends on: 180147
Depends on: 180319
Depends on: 180309
Depends on: 180700
Depends on: 181053
Depends on: 181233
Depends on: 181404
Depends on: 182130
Depends on: 182162
Depends on: 182575
Depends on: 182726
Depends on: 183303
Depends on: 183370
Depends on: 183389
Depends on: 183518
Depends on: 183841
Depends on: 183912
Depends on: 184599
Depends on: 184670
Depends on: 184941
Depends on: 184956
Depends on: 120034
Depends on: 120035
Depends on: 185160
Depends on: 185299
Depends on: 186510
Depends on: 186567
Depends on: 186616
Depends on: 186621
Depends on: 187029
Depends on: 187280
Depends on: 187335
Blocks: 119081
No longer blocks: 119081
Depends on: 187931
Depends on: 188156
Depends on: 188987
Depends on: 188996
Depends on: 186789
Depends on: 189229
Depends on: 189761
Blocks: majorbugs
Depends on: 187388
Blocks: 191072
No longer depends on: 188987
No longer blocks: 191072
Depends on: 191072
Depends on: 192999
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.
Depends on: 193618
Depends on: 194180
Depends on: 194186
Depends on: 194610
Depends on: 195057
Depends on: 180841
Depends on: 184612
Depends on: 195817
Depends on: 195868
Depends on: 196008
Depends on: 196177
Depends on: 196517
Depends on: 197041
Depends on: 197288
Depends on: 195104
Depends on: 195414
Depends on: 197301
Depends on: 197658
Depends on: 197911
Depends on: 198082
Depends on: 198284
Depends on: 198502
Depends on: gtk2_triage
Depends on: 200060
Depends on: 200917
Depends on: 201158
Depends on: 201209
Depends on: 179138
Depends on: 201501
Depends on: 201944
Depends on: 195708
Depends on: 202388
Depends on: 201220
Depends on: 204090
Depends on: 204248
Depends on: 204310
Depends on: 204664
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.
Depends on: 204870
Depends on: 205226
Depends on: 205425
Blocks: 205594
Depends on: 205492
Depends on: 205752
Depends on: 205981
Depends on: 206361
No longer blocks: 205594
Depends on: 205594
Depends on: 206554
Depends on: 206713
Depends on: 207001
Depends on: 207255
Depends on: 208762
Depends on: 208763
Depends on: 208721
Depends on: 209606
Depends on: 211788
Depends on: 211834
Depends on: 213747
Depends on: 211907
Depends on: 214583
Depends on: 214779
Depends on: 214715
Depends on: CTL2
Depends on: 215822
No longer depends on: 215822
Depends on: 212824
Depends on: 209496
Depends on: 216752
Depends on: 194323
Depends on: 215951
Depends on: 215032
Depends on: 219017
Depends on: 220429
Depends on: 220430
Depends on: 221012
Depends on: 222870
Depends on: 218155
Depends on: 227328
Depends on: 227963
Depends on: 227986
Depends on: 227970
Depends on: 229569
Depends on: 230235
Depends on: 210931
Depends on: 230764
Depends on: 230733
Depends on: 230943
Depends on: 231231
Depends on: 231723
Depends on: 231408
Depends on: 214412
Depends on: 232553
Depends on: 232456
Depends on: 118296
Depends on: 232492
Depends on: 232579
Depends on: 233371
Depends on: 219625
Depends on: 236565
Depends on: 239466
Depends on: 239914
No longer depends on: 239914
Depends on: 240327
Depends on: 209342
Depends on: 240495
Depends on: 241187
Depends on: 203671
Depends on: 29856
Depends on: 255900
Depends on: 198954
Depends on: 270750
No longer blocks: majorbugs
Depends on: flash-badmatch
No longer depends on: 189761
Marking fixed.  This was done a few years ago.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Depends on: 1174378
No longer depends on: 1174378
You need to log in before you can comment on or make changes to this bug.