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 139379 - gok keyboard editor needs updating
gok keyboard editor needs updating
Status: RESOLVED WONTFIX
Product: gok
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: David Bolter
David Bolter
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2004-04-07 15:19 UTC by bill.haneman
Modified: 2011-10-14 10:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch of work in progress (204.83 KB, patch)
2005-07-06 14:38 UTC, David Bolter
none Details | Review
new file required with patch (75.20 KB, application/octet-stream)
2005-07-06 14:39 UTC, David Bolter
  Details

Description bill.haneman 2004-04-07 15:19:07 UTC
the GOK keyboard editor reportedly doesn't work anymore.  We haven't been
testing, etc. so this is not really news... and it's nonessential functionality.
 However it's a very nice feature that would add much value if it were at least
minimally functional.
Comment 1 bill.haneman 2004-08-27 13:08:40 UTC
Not an enhancement, the fact that it doesn't work anymore is a regression.
Comment 2 Calum Benson 2004-10-21 16:41:51 UTC
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 3 David Bolter 2005-06-15 15:21:48 UTC
Bill,

I've delved into revamping the gok keyboard editor. I am currently working on
the changes necessary for it to handle .kbd.in files... this will likely mean
adding a section of the key struct to hang on to existing localized strings
etc... only to be used when in gok editor mode.

If you feel it unecessary for the editor to handle .kbd.in files let's chat soon.
Comment 4 bill.haneman 2005-06-15 15:31:55 UTC
I don't quite understand why the above step would be necessary.

I think that it would be acceptable for the keyboard editor to operate only on
untranslated strings.  This would mean that someone using the editor to replace
a string value would in effect be substituting their own strings for the 'C'
value.  It should be sufficient for the keyboard editor to expose both the
untranslated string and the translated value to the user.  That could be done by
using gettext() inside the keyboard editor, to present the translated string
values for informational purposes while editing - but the edits themselves would
always be to the untranslated string.

Bill
Comment 5 David Bolter 2005-06-15 15:40:10 UTC
My previous comment was based on revamping the editor with the least amount of
work and the smallest delta. I certainly think we can come up with something
better.  Probably keeping the dom around will do the trick... currently we
convert the dom to a keyboard when we read in a file and keyboard to dom when we
write IIRC. I'll get back to you.
Comment 6 David Bolter 2005-06-15 17:42:21 UTC
I'm going to persist the DOM while the keyboard and DOM are edited together.
(Then for saving just do an xmlSaveFile (we currently do keyboard straight to
file using fputs))
Comment 7 David Bolter 2005-07-06 14:38:17 UTC
Created attachment 48722 [details] [review]
patch of work in progress

Currently my patch only outputs .kbd files and not kbd.in files (IIRC). Minimal
testing has been done, but seems to work. I will post an additional req'd
glade2 file shortly.
Comment 8 David Bolter 2005-07-06 14:39:14 UTC
Created attachment 48723 [details]
new file required with patch

new file (not in cvs yet)
Comment 9 Calum Benson 2006-04-26 17:10:31 UTC
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
Comment 10 Akhil Laddha 2011-10-14 10:58:46 UTC
gok (GNOME on-screen keyboard) development has been stalled and it has been replaced by caribou [1]. Maintainers don't have future development plan so i am closing all the bugs as WONTFIX.

[1] https://mail.gnome.org/archives/gnome-bugsquad/2011-October/msg00001.html