After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 118134 - gok tracker bug for performance issues
gok tracker bug for performance issues
Status: RESOLVED OBSOLETE
Product: gok
Classification: Deprecated
Component: performance
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Access team bug-tracker
GNOME Access team bug-tracker
AP4
Depends on: 108137 108164 109187 112281 117072 133385 136442 136444 160848
Blocks:
 
 
Reported: 2003-07-23 17:51 UTC by David Bolter
Modified: 2005-04-08 15:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Bolter 2003-07-23 17:51:28 UTC
This is a general tracker bug for gok performance issues.
Comment 1 David Bolter 2003-07-23 17:56:03 UTC
I've added gconf keys (in gok head):
apps->gok->spy->gui_search_breadth
apps->gok->spy->gui_search_depth

Note you must do a make install and restart your gconfd, or log out
and back in.  GOK often needs to interrogate the active application or
window for certain gui elements.  These keys describe a maximum
breadth to search (at any node), and the maximum depth to search when
walking the gui tree. We need to find the magic values that work with
all apps.

Also, we need to explore improving the search algorithm pruning.

(added dependancies)
Comment 2 Calum Benson 2003-08-07 16:16:15 UTC
Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME
bug list :)
Comment 3 bill.haneman 2003-08-22 17:17:07 UTC
I don't expect changing the search depth will help much for most
applications.

Comment 4 David Bolter 2004-02-04 14:23:25 UTC
Adding dependacy for bug 133385: "Performance is slow when using GOK
with 'File types and Programs' application"
Comment 5 bill.haneman 2004-05-06 13:03:57 UTC
marking 'AP4' to indicate triage, but as a tracker bug without an urgent
use-case, we don't need this on the global a11y radar.
Comment 6 Calum Benson 2004-10-21 16:45:58 UTC
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 7 bill.haneman 2005-04-08 15:38:54 UTC
David and I decided that this tracker wasn't serving much purpose since we have
a 'performance' category in which these bugs are already logged.  So we're
closing the tracker, leaving the other bugs open.