I think Michael Kirby has made the best categorization so far. There is a use for spell check, but it's cost of development appears to outweigh it's immediate benefit. I also agree with the others who think that the open api is the place for this kind of functionality to reside. So, for all of the spell check fanatics: you're all developers yourselves, what are you prepared to do to get it? Come up with the spell check api and explore the bridging software on your own. Do the research, figure out what kind of functionality several 3rd party checkers would require then submit your api proposals. Look into what it would take on IntelliJ's part to provide a view of JavaDoc comments that a spell checker could make sense of. Until someone can prove that the return on investment for this feature is not as high as it seems, the guys at IntelliJ should do no work on that portion of their open api (if it's there at all). It's up to you to hash out some of the gory details.
-- Shane _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
