On 11/25/14, 11:02 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>On Nov 25, 2014 10:56 AM, "Alex Harui" <aha...@adobe.com> wrote: >> >> >> >> On 11/25/14, 10:45 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> >>wrote: >> >> >The mx.states package in FlexJSUI is causing a collision with the Flex >> >SDK's mx.states package. Is there a reason why they have the same >package >> >names. >> >> I was previously unable to get FB to recognize a FlexJS SDK as a Flex >>SDK >> (needed to get MXML handling in the editor). I plan to try again >>someday, >> although others are welcome to take a shot at it sooner. > >How would I go about doing that? Any pointers? You’d have to set up the SDK without any mx classes and debug the errors. I think even Falcon has some assumptions right now, and FB code may have more. One thing that has changed since I last tried it is that FB no longer uses MXMLC to compile the project so that could make the problem easier to solve. > >> >> > >> >Is there a way to tell FB to use FlexJSUI's mx.states.* instead of the >> >Flex >> >SDK's? >> >> I haven’t tried FlexJSJX as an FB project. I did have FlexJSUI as an FB >> project, but haven’t tried that in a while. Did you get that far? > >Yes, I have been using FB all this while with no issues. But it looks >like FlexJSUI's mx.states has started deviating from the Flex SDK version. >Which is manifesting as a problem now. In theory it should be ok to deviate from the API surface of the current Flex SDK. I’m not sure if the hooks from FB are that low level. I can try it myself if you want. Did you make sure that FlexJS and not regular Flex is compiling the code? Is it using a FlexJS flex-config? Also, did you restart FB? It can cache SWCs in memory and further complicate things. -Alex
