Thanks Piotr, I see where I am going wrong, I was using an example of the web which uses mx:tags, but the one in the examples folder of the SDK uses js:tags. I assumed (wrongly I guess) that the two SDKs where the same except that the JS version only compiled to JS. I see this is not the case.
As I am working with Flex 3 code and a BlazeDS backend is there any advantage/disadvantage with working with the different SDK versions? Which one would you suggest for me (I only want to output JS HTML apps). On Fri, 5 Feb 2021 at 17:24, Piotr Zarzycki <[email protected]> wrote: > And example which you are running is inside downloaded folder of 0.9.7 ? > > Can you try Nightly build ? You can easly download it trough the Moonshine > SDK Installer and try example which comes with that ? > > pt., 5 lut 2021 o 17:22 David Slotemaker de Bruine < > [email protected]> napisał(a): > >> 9.7 (js only) >> >> On Fri., 5 Feb. 2021, 17:17 Piotr Zarzycki, <[email protected]> >> wrote: >> >>> Hi David, >>> >>> What version of SDK are you using ? >>> >>> pt., 5 lut 2021 o 17:14 David Slotemaker de Bruine < >>> [email protected]> napisał(a): >>> >>>> Hi All, >>>> >>>> I am trying the RemoteObject example. I only have the JS version of the >>>> SDK installed, and I am getting: >>>> >>>> <mx:RemoteObject "Tag is unexpected" >>>> >>>> and "Definition not found" for: >>>> >>>> import mx.rpc.AsyncToken; >>>> import mx.rpc.Responder; >>>> import mx.rpc.events.FaultEvent; >>>> import mx.rpc.events.ResultEvent; >>>> >>>> I have "xmlns:mx="library://ns.apache.org/royale/mx" declared in the >>>> Application tag. >>>> >>>> Is the reason it wont compile because I need the Flex version of the >>>> SDK?? I am trying to connect to a BlazeDS backend, >>>> >>>> Cheers, >>>> >>>> David >>>> >>>> >>>> >>> >>> -- >>> >>> Piotr Zarzycki >>> >> > > -- > > Piotr Zarzycki > -- *David Slotemaker de Bruïne* *Head of Educational Robotics* Av. Sarriá, 130 - 08017 Barcelona <https://maps.google.com/?q=Av.+Sarri%C3%A1,+130+-+08017+Barcelona&entry=gmail&source=g> T. +34 932 523 729 ext. 135 [email protected]
