WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
Bug 101727
[GTK] Isolate the GTK/Gail/Pango specific code in accessibility/gtk
https://bugs.webkit.org/show_bug.cgi?id=101727
Summary
[GTK] Isolate the GTK/Gail/Pango specific code in accessibility/gtk
Mario Sanchez Prada
Reported
2012-11-09 01:41:38 PST
This is a bug to track work initially started in
bug 99578
, to provide conditional compilation units for isolating the GTK specific code in accessibility/gtk, so most of the code in there can be later reused in other ports, such as EFL
Attachments
Patch proposal
(10.60 KB, patch)
2012-11-09 02:04 PST
,
Mario Sanchez Prada
cfleizach
: review+
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Mario Sanchez Prada
Comment 1
2012-11-09 02:04:27 PST
Created
attachment 173245
[details]
Patch proposal Here comes the patch, properly filling the ChangeLog and addressing the review comments from
bug 99578
.
Mario Sanchez Prada
Comment 2
2012-11-09 11:48:14 PST
Committed
r134094
: <
http://trac.webkit.org/changeset/134094
>
Martin Robinson
Comment 3
2012-11-09 12:04:17 PST
I think we should just replace this code for both platforms with something platform-independent, if possible.
Alejandro Piñeiro
Comment 4
2012-11-12 03:11:18 PST
(In reply to
comment #3
)
> I think we should just replace this code for both platforms with something platform-independent, if possible.
This was discussed at
bug 99578 comment 4
, 5 and 6. The idea is replace the gail/pango code used to implement some methods of AtkText. Mario suggested stuff like TextIterator, that it is already in use. But that task can be long, so first step is isolate that code (this patch) while working on the final and platform-independent solution. In summary: this isolation is a temporary solution.
Martin Robinson
Comment 5
2012-11-12 08:25:45 PST
(In reply to
comment #4
)
> (In reply to
comment #3
) > > I think we should just replace this code for both platforms with something platform-independent, if possible. > > This was discussed at
bug 99578 comment 4
, 5 and 6. The idea is replace the gail/pango code used to implement some methods of AtkText. Mario suggested stuff like TextIterator, that it is already in use. But that task can be long, so first step is isolate that code (this patch) while working on the final and platform-independent solution. In summary: this isolation is a temporary solution.
Hrm. Do you mean that there will be many patches and the work will be incomplete during that time?
Mario Sanchez Prada
Comment 6
2012-11-15 04:05:10 PST
(In reply to
comment #5
)
> (In reply to
comment #4
) > > (In reply to
comment #3
) > > > I think we should just replace this code for both platforms with something platform-independent, if possible. > > > > This was discussed at
bug 99578 comment 4
, 5 and 6. The idea is replace the gail/pango code used to implement some methods of AtkText. Mario suggested stuff like TextIterator, that it is already in use. But that task can be long, so first step is isolate that code (this patch) while working on the final and platform-independent solution. In summary: this isolation is a temporary solution. > > Hrm. Do you mean that there will be many patches and the work will be incomplete during that time?
As for WebKitGTK the work won't ever be incomplete (it will for other ports, though), since it will keep working as it used to do so far. These conditional compilation units were added just to ease the work of other ports (EFL) should they want to reuse the non-GTK dependant ATK code (which is 99% already). However, I'd expect that over time (probably while implementing those notimplemented() bits in the #if !PLATFORM(GTK) regions) most of those conditional bits (e.g. pango / gail) will be implemented in a more generic way so they could be shared by all the ports. Which I think is what you suggested in your first comment.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug