I went through the RC. Checked in a bunch of spelling errors in SWC names, README, RELEASE_NOTES. IMO, it wouldn’t be right to release a Spell Checker with spelling errors in the supporting documentation ;-).
Everything else (LICENSE, NOTICE, build, RAT) all looks fine so I would likely vote to approve the next RC. -Alex On 10/21/14, 5:57 PM, "Chris Martin" <windo...@gmail.com> wrote: >> That incorrect you should only have one of ApacheFlexSpellingUI.swc or >ApacheFlexSpellingUIEx.swc, for spark controls you need >ApacheFlexSpellingUIEx.swc. These swcs define the same classes so you can >only use one at a time. > >Ahh good to know! Then i'd adjust my first suggested change to the README >to make it clear that you can only target either mx or spark, so you can >only use one of the two swcs at a time. > >Chris > >On Tue, Oct 21, 2014 at 5:19 PM, Justin Mclean <jus...@classsoftware.com> >wrote: > >> Hi, >> >> > Per the README I also have ApacheSpellingUI.swc in my src folder. Is >> that right? >> >> That incorrect you should only have one of ApacheFlexSpellingUI.swc or >> ApacheFlexSpellingUIEx.swc, for spark controls you need >> ApacheFlexSpellingUIEx.swc. These swcs define the same classes so you >>can >> only use one at a time. >> >> > I did not find any references to ApacheSpellingFramework.swc or >> ApacheFlexLinguisticUtils.swc in the README file. >> >> I believe ApacheFlexSpellingFramework.swc and >>ApacheFlexSpellingEngine.swc >> exist so that Squiggy can be used with both AS and Flex project, but we >> would have to ask Adobe/original developers what their intent was. You >> require both for Squiggly to work with Flex projects. >> ApacheFlexLinguisticUtils.swc I think is optional and may be required if >> you want to add your own custom dictionaries but again I'm not 100% sure >> what Adobe's intent was. >> >> Thanks, >> Justin
