# royale-dev mailing list archives

##### Site index · List index
Message view
Top
From Carlos Rovira <carlos.rov...@codeoscopic.com>
Subject Re: Getting An Emulation Component To Run
Date Tue, 16 Oct 2018 12:03:44 GMT
```Hi Alina,
can't.
We can wait a bit more, or try to send me the file in other way

El mar., 16 oct. 2018 a las 12:23, Alina Kazi (<alina.kazi@d-bz.com>)
escribió:

> Thanks Carlos.
>
> I have created a Project with one module to Compile that cover all
> scenario's (problems).
> 3 Errors : https://paste.apache.org/hUJz
>
> Thanks,
> Alina Kazi
>
>
>
> -----Original Message-----
> From: Carlos Rovira [mailto:carlosrovira@apache.org]
> Sent: Tuesday, October 16, 2018 2:49 PM
> To: dev@royale.apache.org
> Subject: Re: Getting An Emulation Component To Run
>
> Hi Alina,
>
> here's the page I did about ROs
>
>
> https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject
>
> I updated right now with this:
>
> Update Oct, 15th, 2018: We have mx:RemoteObject working in develop branch
> you can check the example here:
>
> https://github.com/apache/royale-asjs/tree/develop/examples/mxroyale/RemoteObjectAMFTest
> ,
> The example can be tested as well with
>
> https://github.com/apache/royale-asjs/tree/develop/examples/amf/SampleAmfWebApp
> ,
> just remember that we still doesn't support Small Messages in BlazeDS (and
> this should not make a big difference), so remember to disable it like we
> explain in this document.
>
> Let us now if you find any problem. Just let you know that I'm working
> with mx:RemoteObject without issue at the moment.
>
> Best
>
> Carlos
>
>
>
>
> El mar., 16 oct. 2018 a las 11:17, Alina Kazi (<alina.kazi@d-bz.com>)
> escribió:
>
> > Hi Alex,
> >
> > Created a mxmlc task directly in build.xml still an error is occured :
> > Added to Build.xml : https://paste.apache.org/wBDm Error :
> > https://paste.apache.org/OXFT
> >
> > Thanks,
> > Alina Kazi
> >
> >
> >
> > -----Original Message-----
> > From: Alex Harui [mailto:aharui@adobe.com.INVALID]
> > Sent: Tuesday, October 16, 2018 11:46 AM
> > To: dev@royale.apache.org
> > Subject: Re: Getting An Emulation Component To Run
> >
> > Hi Alina,
> >
> > The example in examples/mxroyale/RemoteObjectAMFTest is working and
> > accesses the server that is in examples/amf/ SampleAmfWebApp.
> > Theoretically, your old mx:RemoteObject code should work untouched.
> > Try it without touching it and tell us what kinds of errors you are
> > getting.  If you are getting runtime errors, see how the
> > RemoteObjectAMFTest uses "casting" to be explicit about the types of the
> RemoteObject expressions.
> > You'll see "as Operation" to indicate that an mx:method in an
> > mx:RemoteObject is an Operation.
> >
> > The compile-mxml macro is in the build.xml file.  It has certain
> > expectations of the structure of the source files.  Your source files
> > are likely have a different folder structure.  You will need to add
> > source-paths and other compiler options to the macro, or stop using
> > the macro and call the mxmlc ant task directly.  That is up to you.
> > This is a good opportunity to get to know Ant and the compiler better.
> >
> > HTH,
> > -Alex
> >
> > ﻿On 10/15/18, 11:07 PM, "Alina Kazi" <alina.kazi@d-bz.com> wrote:
> >
> >     Hi Alex & Carlos,
> >     I haven't tested my ported Application with server side
> > functionality yet.
> >     Can you please share an Example that I can follow to get my
> > mx:RemoteObject working as FLEX.
> >
> >     I have another question
> >
> >     I am working on my Application and it has two different
> > directories like com->shm->modules->AP and
> > com->shm->modules->components and  I want to compile a file inside
> > com->shm->modules->AP->abc.mxml and it uses a file inside
> com->shm->modules->components->xyz.mxml.
> >     I have added        <compile-mxml folder="/com/shm/modules/AP/"
> > example=" abc"/> to build.xml.
> >      unable to access xyz inside abc.
> >
> >     Like
> >
> D:\apache-royale-0.9.3-bin-js-swf\royale-asjs\examples\mxroyale\tourdeflexmodules\src\spark\components\
> > VideoPlayerExample.mxml is using VideoPlayer.mxml    in my case
> > VideoPlayer.mxml  is not is the same directory.
> >
> >     Thanks,
> >     Alina Kazi
> >
> >     -----Original Message-----
> >     From: Carlos Rovira [mailto:carlosrovira@apache.org]
> >     Sent: Tuesday, October 16, 2018 12:26 AM
> >     To: dev@royale.apache.org
> >     Subject: Re: Getting An Emulation Component To Run
> >
> >     Hi Alex,
> >
> >     yes, I added those classes when worked trying to make it work in
> > net RO, but I found a wall at that time. I think DSK objects had a
> > different code when deserialized, and our AMF implementation was not
> > able to handle that.
> >     I was not able to know how to deal with that so I had to abandon.
> > At least I could pass that disabling small messages on BlazeDS.
> >
> >     I don't think Small Messages are very important, don't know how
> "small"
> >     will be, so I think we can go to other things more important. If I
> > found some problem as I start to grow my application that could be
> > related to small messages I'll report. Hope not find any issue
> >
> >     The only drawback could be people coming that must know they need
> > to disable small messages on their BlazeDS.
> >
> >     I think it will be more important later since IExternalizable in
> > itself seems an important addition.
> >
> >     Thanks
> >
> >     Carlos
> >
> >
> >
> >     El lun., 15 oct. 2018 a las 20:21, Alex Harui
> >     escribió:
> >
> >     > The classes that represent DSK, DSA and DSC are in the MXRoyale and
> >     > Network projects, but it looks like they implement IExternalizable.
> > I
> >     > don't see any evidence that the JS AMF support currently handles
> >     > IExternalizable.
> >     >
> >     > I'm not clear on how important SmallMessages and IExternalizable
> > are.
> >     > If it isn't that important, there are plenty of other things to
> work
> >     > on.  If it is important, do we have a test case that uses
> > IExternalizable?
> >     >
> >     > -Alex
> >     >
> >     > On 10/15/18, 10:55 AM, "Carlos Rovira" <carlosrovira@apache.org>
> > wrote:
> >     >
> >     >     Yes,
> >     >
> >     >     I tried today (with code pre-callProperty, that I think does
> not
> > make
> >     >     difference for this).
> >     >     There's small message support in RPC classes, but when I looked
> > at that
> >     >     code when I investigate it, I think must be accompanied from
> > some AMF
> >     >     serialization/deserialization support. I couldn't find any
> > resources on
> >     >     this in the internet about how to handle DSK, DSA or DSC. Maybe
> >     > you can ask
> >     >     internally in Adobe how to deal with that. My guess is that
> this
> >     >     to Flash plugin AMF serialization capabilities.
> >     >
> >     >
> >     >
> >     >
> >     >     El lun., 15 oct. 2018 a las 19:03, Alex Harui
> >     >     escribió:
> >     >
> >     >     > Carlos,
> >     >     >
> >     >     > Have you verified that small messages do not work with the MX
> >     >     > RemoteObject?  I thought I saw Small Message support when I
> > was
> >     > migrating
> >     >     > the code.
> >     >     >
> >     >     > Thanks,
> >     >     > -Alex
> >     >     >
> >     >     > On 10/15/18, 10:01 AM, "Carlos Rovira" <
> > carlosrovira@apache.org>
> >     > wrote:
> >     >     >
> >     >     >     Hi Alina,
> >     >     >
> >     >     >     just for if you don't know. If you use BlazeDS Java
> server,
> >     > remember
> >     >     > to set
> >     >     >     up small messages to false, or you RemoteObjects will not
> > work.
> >     > To get
> >     >     >     small messages we'll need to upgrade AMF
> >     > serialization-deserialization
> >     >     > to
> >     >     >     know how to handle DSK, DSA, and DSC RemoteClass aliases.
> >     >     >
> >     >     >     Best
> >     >     >
> >     >     >     Carlos
> >     >     >
> >     >     >
> >     >     >     El lun., 15 oct. 2018 a las 18:39, Alex Harui
> >     >     >     escribió:
> >     >     >
> >     >     >     > Hi Alina,
> >     >     >     >
> >     >     >     > Good to know.  You (and anybody working with the
> > emulation
> >     >     > components) are
> >     >     >     > expected to keep track of the commits to the
> > royale-compiler
> >     > as well
> >     >     > as the
> >     >     >     > royale-asjs repos and stay updated.  We are still
> > finding bugs
> >     > in the
> >     >     >     > transpiling that may affect you.
> >     >     >     >
> >     >     >     > Thanks,
> >     >     >     > -Alex
> >     >     >     >
> >     >     >     > On 10/15/18, 2:17 AM, "Alina Kazi" <
> alina.kazi@d-bz.com>
> >     > wrote:
> >     >     >     >
> >     >     >     >     Hi Alex,
> >     >     >     >
> >     >     >     >     Thanks a lot it worked for me.
> >     >     >     >
> >     >     >     >     -Alina kazi
> >     >     >     >
> >     >     >     >     -----Original Message-----
> >     >     >     >     From: Alex Harui [mailto:aharui@adobe.com.INVALID]
> >     >     >     >     Sent: Monday, October 15, 2018 2:07 PM
> >     >     >     >     To: dev@royale.apache.org
> >     >     >     >     Subject: Re: Getting An Emulation Component To Run
> >     >     >     >
> >     >     >     >     Hi Alina,
> >     >     >     >
> >     >     >     >     Are you sure you are using the latest compiler?
> Try
> >     > compiling
> >     >     >     > examples/mxroyale/RemoteObjectAMFTest.  It compiles
> > without
> >     > errors
> >     >     > for me.
> >     >     >     >
> >     >     >     >     I have to stop for tonight.  Hopefully others will
> > help
> >     > you.
> >     >     >     >
> >     >     >     >     -Alex
> >     >     >     >
> >     >     >     >     On 10/15/18, 1:37 AM, "Alina Kazi" <
> > alina.kazi@d-bz.com>
> >     > wrote:
> >     >     >     >
> >     >     >     >         Hi Alex,
> >     >     >     >         We are using MX Remote Object in almost our
> every
> >     > Class like
> >     >     > this:
> >     >     >     >         <mx:RemoteObject
> >     >     > channelSet="{parentApplication.amfChannelSet}"
> >     >     >     > id="DataProviderService"  showBusyCursor="true"
> >     >     >     >
> >     >     >     >  destination="shmBasic" fault="handleFault(event);"
> >     >     >     >
> >     >     >     >  result="handleResult(event);" />
> >     >     >     >         We get error ASBlocker subsystem.
> >     >     >     >         When we comment RemoteObject we need to comment
> > methods
> >     >     > those are
> >     >     >     > using it.
> >     >     >     >
> >     >     >     >         I agree with that if I will delete some code
> for
> >     > compilation
> >     >     > I
> >     >     >     > will face other issues at later stage.
> >     >     >     >
> >     >     >     >         Can I replace mx:remoteObject with  :
> >     >     >     >         <s:RemoteObject id="ro" endpoint="
> >     >     >     >
> >     >     >
> >     >
> >
> >     >     > "
> >     >     >     > destination="census"/>
> >     >     >     >
> >     >     >     >         Thanks in Advance,
> >     >     >     >         Alina Kazi
> >     >     >     >
> >     >     >     >         -----Original Message-----
> >     >     >     >         From: Alex Harui [mailto:
> >     >     >     >         Sent: Monday, October 15, 2018 1:16 PM
> >     >     >     >         To: dev@royale.apache.org
> >     >     >     >         Subject: Re: Getting An Emulation Component To
> > Run
> >     >     >     >
> >     >     >     >         Hi Alina,
> >     >     >     >
> >     >     >     >         I recommend just running the compiled
> > application and
> >     > fixing
> >     >     >     > problems as you run into them.
> >     >     >     >
> >     >     >     >         If you start copying code and deleting other
> > code, you
> >     > cannot
> >     >     >     > guarantee that the results will run.  I'm not even sure
> >     > TitleWindow
> >     >     > is a
> >     >     >     > valid child control of an Application.  Usually it is
a
> > popup
> >     > dialog.
> >     >     >     >
> >     >     >     >         When you run the application, you will probably
> > find
> >     >     > exceptions in
> >     >     >     > the console.  Set a breakpoint, see if you can figure
> > out why
> >     > it is
> >     >     >     > generating an exception. Change the code as needed.
> >     >     >     >
> >     >     >     >         If you aren’t getting exceptions, then look
at
> > the
> >     > element
> >     >     > tree.
> >     >     >     > Either all of the expected elements have been created
> or
> > not.
> >     > If
> >     >     > not, then
> >     >     >     > look at the innermost element to see what it is.  In
> the
> >     > properties
> >     >     > for the
> >     >     >     > element is a royale_wrapper property that points to the
> >     > transpiled
> >     >     > AS3
> >     >     >     > class.  That can help you know what class didn't create
> > its
> >     > children.
> >     >     >     > Check the _beads array of that class to see if it
> > created its
> >     >     > or
> >     >     >     > not.  If not, check the CSS for that element, or debug
> > into
> >     > its code.
> >     >     >     >
> >     >     >     >         If the elements have been created, check the
> > sizes.
> >     > Often
> >     >     > some of
> >     >     >     > them will have width or height = 0.  Try to figure why
> > it is
> >     > getting
> >     >     > a bad
> >     >     >     > size.
> >     >     >     >
> >     >     >     >         If you take this approach, then if you get
> stuck
> > you
> >     >     > a
> >     >     >     > much more specific question and we can give you more
> > specific
> >     >     >     >
> >     >     >     >         Unfortunately, our days only overlap by a few
> > hours,
> >     > but I
> >     >     > hope
> >     >     >     > other committers can help as well.  It is in their best
> >     > interest to
> >     >     > improve
> >     >     >     > their help and debugging skills.
> >     >     >     >
> >     >     >     >         -Alex
> >     >     >     >
> >     >     >     >         On 10/15/18, 12:59 AM, "Alina Kazi" <
> >     > alina.kazi@d-bz.com>
> >     >     > wrote:
> >     >     >     >
> >     >     >     >             Hi Alex,
> >     >     >     >             As our whole application is compiled
> > successfully
> >     > without
> >     >     >     > error as a part of SparkRoyale Library.
> >     >     >     >
> >     >     >     >             Now, We have created a project like
> >     > tourdeflexmodules to
> >     >     >     > compile and visually see the application output.
> >     >     >     >             Initially started with the basic(small)
> file
> > of our
> >     >     >     > application that is used by most of the files of our
> >     > Application.
> >     >     >     >
> >     >     >     >             We have a file in our application
> > "Picklist.mxml"
> >     >     >     >             It was actually like :
> >     >     >     >             [1]
> >     >     >     >
> >     >     >
> >     >
> >
> >     >     >     >
> >     >     >     >             we want to see it visually as all our mx
> and
> > spark
> >     >     > controls
> >     >     >     >             Deleted whole code accept visual controls
> > from src
> >     > file :
> >     >     >     >             [2]
> >     >     >     >
> >     >     >
> >     >
> >
> >     >     >     >
> >     >     >     >             Nothing shows inside spark BorderContainer
> &
> >     > TitleWindow.
> >     >     >     >             [3]
> >     >     >     >
> >     >     >
> >     >
> >
> >     >     >     >             How can we see all visual controls as they
> > were in
> >     > Flex
> >     >     > of
> >     >     >     > this particular file.
> >     >     >     >             Even spark BorderContainer default.css is
> > copied
> >     > from
> >     >     > Flex
> >     >     >     > ->Royale.
> >     >     >     >
> >     >     >     >             Thanks,
> >     >     >     >             Alina Kazi
> >     >     >     >
> >     >     >     >             -----Original Message-----
> >     >     >     >             From: Alex Harui [mailto:
> >     >     >     >             Sent: Monday, October 15, 2018 11:15 AM
> >     >     >     >             To: dev@royale.apache.org
> >     >     >     >             Subject: Re: Getting An Emulation Component
> > To Run
> >     >     >     >
> >     >     >     >             Hi Alina,
> >     >     >     >
> >     >     >     >             Different APIs will have different
> solutions.
> >     > Pick an
> >     >     > API you
> >     >     >     > want to have work and let's discuss how to make it
> work.
> >     >     >     >
> >     >     >     >             -Alex
> >     >     >     >
> >     >     >     >             On 10/14/18, 10:48 PM, "Alina Kazi" <
> >     > alina.kazi@d-bz.com
> >     >     > >
> >     >     >     > wrote:
> >     >     >     >
> >     >     >     >                 Hi Alex,
> >     >     >     >
> >     >     >     >                 All mx and spark class methods those
> > were left
> >     > empty
> >     >     > for
> >     >     >     > the compilation of Application.
> >     >     >     >                 Also Module does not show anything on
> > screen.
> >     >     >     >
> >     >     >     >                 Thanks in Advance,
> >     >     >     >                 Alina
> >     >     >     >
> >     >     >     >                 -----Original Message-----
> >     >     >     >                 From: Alex Harui [mailto:
> >     >     >     >                 Sent: Thursday, October 11, 2018 12:32
> PM
> >     >     >     >                 To: dev@royale.apache.org
> >     >     >     >                 Subject: Re: Getting An Emulation
> > Component To
> >     > Run
> >     >     >     >
> >     >     >     >                 Hi Alina,
> >     >     >     >
> >     >     >     >                 Which components or properties are you
> > trying
> >     > to get
> >     >     > to
> >     >     >     > run?
> >     >     >     >
> >     >     >     >                 -Alex
> >     >     >     >
> >     >     >     >                 On 10/10/18, 10:40 PM, "Alina Kazi" <
> >     >     > alina.kazi@d-bz.com>
> >     >     >     > wrote:
> >     >     >     >
> >     >     >     >                     Hi Alex,
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     What if CSS for a component is not
> > written
> >     > in
> >     >     > Basic /
> >     >     >     > Express defaults.css?
> >     >     >     >
> >     >     >     >                     And We need it in MXRoyale /
> > SparkRoyale
> >     >     >     >
> >     >     >     >                     Thanks,
> >     >     >     >
> >     >     >     >                     Alina Kazi
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     From: Alex Harui [mailto:
> >     >     >     >                     Sent: Monday, October 08, 2018 8:40
> > PM
> >     >     >     >                     To: Alina Kazi
> >     >     >     >                     Subject: Re: Getting An Emulation
> >     > Component To
> >     >     > Run
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     Hi Alina,
> >     >     >     >
> >     >     >     >
> >     >     >     >
> > as
> >     > well.
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     CSS with ClassReference is a way
to
> > use
> >     >     > Composition to
> >     >     >     > customize components.   Copying code is usually a bad
> > practice
> >     > as it
> >     >     >     > creates maintenance issues.  So, in general, the
> > preference
> >     > should
> >     >     > be to
> >     >     >     > use CSS.
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     HTH,
> >     >     >     >
> >     >     >     >                     -Alex
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     From: Alina Kazi <
> > alina.kazi@d-bz.com>
> >     >     >     >                     Date: Monday, October 8, 2018 at
> > 2:02 AM
> >     >     >     >                     To: Alex Harui <aharui@adobe.com>
> >     >     >     >                     Subject: Getting An Emulation
> > Component To
> >     > Run
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     Hi Alex,
> >     >     >     >
> >     >     >     >                     We want to know how can we identify
> > which
> >     > is the
> >     >     > right
> >     >     >     > stub?
> >     >     >     >
> >     >     >     >                     For Example: selected property
> > written
> >     >     > differently in
> >     >     >     > CheckBox, RadioButton and
> >     >     >     >
> >     >     >     >                     we want selected property for
> > Button. How
> >     > can we
> >     >     >     > identify and pick the right code for Button?
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     1.       copying the little bits
of
> > code
> >     > from the
> >     >     >     > Basic or Express version into the right stub in the
> > Emulation
> >     >     > Component
> >     >     >     >
> >     >     >     >                     2.       copying the CSS from Basic
> > or
> >     > Express
> >     >     >     > defaults.css into the MXRoyale or SparkRoyale
> > defaults.css
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >                     Thanks in Advance,
> >     >     >     >
> >     >     >     >                     Alina Kazi
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >     >
> >     >     >
> >     >     >     --
> >     >     >     Carlos Rovira
> >     >     >
> >     >     >
> >     >
> >
> >     >     >
> >     >     >
> >     >     >
> >     >
> >     >     --
> >     >     Carlos Rovira
> >     >
> >     >
> > %7C04eb29f37fce
> >     >
> > 40d3df9908d632c77330%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6367
> >     >
> > 52229546474497&amp;sdata=7S2M%2BRlyCsWd2pShdvTsjfyJp9xyZ5bdaAc3zZQrilU
> >     > %3D&amp;reserved=0
> >     >
> >     >
> >     >
> >
> >     --
> >     Carlos Rovira
> >
> > 52668214131201&amp;sdata=xMMzkzX1tt0CmoIMPkTJzmeI4dzHI6NmsYNzodykMQM%3
> > D&amp;reserved=0
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
>
>

--

<http://www.codeoscopic.com>

Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

Conócenos en 1 minuto! <https://avant2.es/#video>

AVISO LEGAL: La información contenida en este correo electrónico, y en su
exclusivo de la persona y/o personas a las que va dirigido. No está
permitido el acceso a este mensaje a cualquier otra persona distinta a los
indicados. Si Usted no es uno de los destinatarios, cualquier duplicación,
reproducción, distribución, así como cualquier uso de la información
contenida en él o cualquiera otra acción u omisión tomada en relación con
el mismo, está prohibida y puede ser ilegal. En dicho caso, por favor,
notifíquelo al remitente y proceda a la eliminación de este correo
electrónico, así como de sus adjuntos si los hubiere. En cumplimiento de la
legislación española vigente en materia de protección de datos de carácter
personal y del RGPD 679/2016 le informamos que sus datos están siendo
objeto de tratamiento por parte de CODEOSCOPIC S.A. con CIFA85677342, con
la finalidad del mantenimiento y gestión de relaciones comerciales y
administrativas. La base jurídica del tratamiento es el interés legítimo de
la empresa. No se prevén cesiones de sus datos, salvo que exista una
obligación legal. Para ejercitar sus derechos puede dirigirse a CODEOSCOPIC