flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Martin <windo...@gmail.com>
Subject Re: [DISCUSSION] Squiggly 1.1 release candidate 0
Date Wed, 22 Oct 2014 00:57:31 GMT
> 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 <justin@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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message