World: r3wp

hey, they are just plain text books

just take a book well writed

what is your language ?

take a classic

Queen's English ;)

use books.google.com to find a good one

I'm wondering whether, for RebGUI, this approach is actually "better" 
than the current soundex approach? If it means having to pick arbitrary 
literary works for each language then what's the point? I was hoping 
that someone had pre-generated some "standardized" dicts somewhere 
I could grab.

i dunno

soundex is faster

but more complicated

? It's less than a dozen lines of code!

oh really ?

right

http://trac.geekisp.com/rebgui/browser/rebgui-edit.r?format=raw

steeve: don't forget, that the 1s difference in TRAIN speed does 
not actually matter, since it is just a dictionary preparation. What 
matters is the speed of the CORRECT function

how fast is the correct function?

the version I just sent to the ML is now almost 4 times faster than 
Cyphre's

on his example it is about 9 words/s

Graham - Ashley is right - all I did wat I added 'table name to the 
behavior tabbing category ....

Soundex is a language-specific algorithm, unfortunately

So soundex is specific to English ?

Seems so: http://en.wikipedia.org/wiki/Soundex

Looking at the new algorithm again, a lot of effort goes into weighting 
word use (the values block) which in turn is only used in one place 
... to determine the "best" candidate replacement. Given that a spell-checker 
just needs to return a sorted candidate list and the remainder of 
the algorithm handles this quite well, I'd be quite happy with a 
cut-down version that excludes the whole dict/values logic. That 
way I could use the existing dictionary files I have sourced (sans 
soundex codes).

it is easy to cut down - just remove the WORDS and TRAIN functions 
and replace their use by reading the DICT data

So, to create a specialized dictionary, you can train it on eg. a 
medical text ?

yes, sure, you can use any text you want

I suppose medical text can contain a lot of latin words e.g.

alea jacta est

not really ...

might have 100 years ago

Wonder how easy it would be to do real time spell checking?

as Firefox does ...

Isn't that just look up and highlight...quite a bit easier/faster 
than offering corrections?

how easy it would be to do real time spell checking

 ... with a cut-down version of Ladislav's code (mainly limiting edits 
 to one char distance) speed is no longer an issue. I'm looking at 
 using draw to red underline all spelling errors in a text face and 
 then only popping up the spellcheck box on right-clicking a misspelled 
 word.


Problem is synchronizing red underlines with scrolling. R3's rich 
text support would make this trivia [by comparison] to implement.

R3 will support rich text format ? where is this claimed ?

http://www.rebol.com/article/0123.htmland follow-up references in 
some of Carl's blogs.

old speech from Carl

Yea of little faith! ;) We'll know after the Devcon one way or the 
other.

it's no so difficult to synchronize draw effects with scrolling

i've done it many times

The source code for area is here:

	http://trac.geekisp.com/rebgui/browser/widgets/area.r?format=raw

feel free to propose a solution.

ah ah

you got me

there are several ways

we should first define an api

an interface

how to add, remove  drawable items

or define a dialect for this purpose

the issue is not to create synchronisation but to have a good interface

the syncronisation part is trivial, i''ve done it in "easy drawer" 
script