M abi/src/wp/ap/Makefile
M abi/src/wp/ap/xp/Makefile
M abi/src/wp/ap/xp/ap_Dialog_Id.h
M abi/src/wp/ap/xp/ao_EditMethods.cpp
M abi/src/wp/ap/xp/ap_Menu_Id.h
M abi/src/wp/ap/xp/ap_Menu_LabelSet_EnUS.h
M abi/src/wp/ap/xp/ap_Menu_Layouts_MainMenu.h
M abi/src/wp/ap/xp/ap_String_Id.h
M abi/src/wp/ap/unix/Makefile
A abi/src/wp/ap/xp/ap_Dialog_Spell.cpp
A abi/src/wp/ap/xp/ap_Dialog_Spell.h
A abi/src/wp/ap/unix/ap_UnixDialog_Spell.cpp
A abi/src/wp/ap/unix/ap_UnixDialog_Spell.h
M abi/src/other/spell/Makefile
M abi/src/other/spell/ispell.h
M abi/src/other/spell/lookup.c
M abi/src/other/spell/newMain.c
M abi/src/other/spell/sp_spell.h
A abi/src/other/spell/correct.c
It currently only has a unix front-end, so only the cool people can play
for now ;) To try it out, you'll need to #if some code back in (in place
so nothing breaks on other platforms).
In the dlgSpell function (line 2869) in wp/ap/xp/ap_EditMethods.cpp,
change the "#if 0" to "#if 1" to make it call the dialog.
You'll definitely need to do a full "make clean; make". Also, I've added a
good chunk of code here, so if anyone has compilation issues (on non-unix
platforms, too) or run-time weirdness, please let me know.
Also, do the other language's menu labels auto default to EnUS?
Or should I add a stub line to each of those? If they need stubs, then
this probably is not going to run non-EnUS... Again, if something comes
up, let me know and I'll fix it.
There are some display oddities. The previously mentioned
insertion point garbage is behaving a bit better, but now, I get odd gray
blocks where the dialog was when the page is scrolled.
Other issues:
- the sentence boundary finder is quite limited,
- user dictionaries don't do anything
- the ignore all is not persistent and doesn't affect squiggles
(this will be remedied shortly)
For people wanting to make Windows and BeOS frontends (or anyone curious
to see what it looks like), there are some screenshots of my dialog
available here:
http://toaster.sped.ukans.edu/abisource/screenshots/
Justin