date:20180219

Re: rs model / tag

2018-02-19 Thread Piotr Zarzycki

Mandeep,

You have to just open them. Most of them were configured to work with
Moonshine. Once you open there is possibility that something went wrong, so
you need to check Project Settings.

Are you pointing to the good Royale SDK folder. ?

Did you try open Hello World?

Try also reseting all settings and setup again, than open Hello World. You
can reset in File - General. I'm not in front of my PC, so may be wrong.

Thanks, Piotr



On Tue, Feb 20, 2018, 06:14 Mandeep Sarma  wrote:

> I believe my settings are similar to yours (as per my screenshot).
>
> What is the proper way to import an example project into moon shine? I
> have tried to do it manually and I've tried importing a flex project.
>
> Thanks,
> Mandeep
>
> [image: Inline image 1]
>
> On Sun, Feb 18, 2018 at 6:41 AM, piotrz  wrote:
>
>> Mandeep,
>>
>> I just look into that and didn't have any problem with configuration and
>> build using Moonshine 1.9.0 and released version of Royale 0.9.1 JS only.
>> Royale website didn't have also Moonshine IDE files in the repository I
>> just
>> committed it.
>>
>> My project configuration looks like that:
>>
>> <
>> http://apache-royale-users.20374.n8.nabble.com/file/t1/configuration_royalewebsite.png
>> >
>>
>> I setup Royale 0.9.1 JS only SDK in File -> Settings:
>> > >
>>
>> If you want you can copy Moonshine configuration file for this project
>> which
>> I just committed [1] to see if it helps.
>>
>> [1] https://goo.gl/tFjbpD
>>
>> Thanks,
>> Piotr
>>
>>
>>
>> --
>> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>>
>
>

Re: Substitutes in Apache Royale

2018-02-19 Thread Alex Harui

Sorry, just realized I referenced the JS compiler.  Please try using bin/compc 
and bin/mxmlc.  You won't need the –targets parameter, just the load-config 
option.

HTH,
-Alex

From: Alex Harui >
Reply-To: "users@royale.apache.org" 
>
Date: Monday, February 19, 2018 at 11:14 PM
To: "users@royale.apache.org" 
>
Subject: Re: Substitutes in Apache Royale

Hi Alina,

Piotr might be better at helping you use Moonshine.  The IDEs sort of expect 
that the libraries/SWCs that your code needs is in the same folder as the 
compiler.  That's why it might be easier to work from the command line.

I remembered this morning that the Royale SWF Compiler doesn't have embedded 
font support.  However the goal isn't so much to make a runnable SWF but to 
have the compilation and linking complete so we can determine the full set of 
Flex APIs used in your app.

If your code has two projects, then we will want you to compile both projects 
with the Royale compiler and get two API reports.  The Library project would be 
compiled with js/bin/compc and the main app would be compiled with js/bin/mxmlc.

I think you will want to use the compiler option:
   -load-config="path to a Flex SDK flex-config.xml"
and also use
  –compiler.targets=SWF

HTH,
-Alex


From: Alina Kazi >
Reply-To: "users@royale.apache.org" 
>
Date: Monday, February 19, 2018 at 10:10 PM
To: "users@royale.apache.org" 
>
Subject: RE: Substitutes in Apache Royale

Hi Alex,
Our Flex Application(Main Project) is dependent on Flex Library Project , I 
tookoriginal code (Library Project) without porting it, Compiling it using 
Royale Compiler's SWF compiler (apache-royale-0.9.1-bin-js-swf or 
apache-royale-0.9.0-bin-js-swf)
[cid:image001.png@01D3AA3A.7CAB69F0]

Moonshine IDE (1.9.0) Console :
Loading configuration: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml
:
: C:\Users\aleena\Documents\SHMALIB\defaults Error: unable to open 
'C:\Users\aleena\AppData\Roaming\npm\node_modules\apache-royale\royale-js\frameworks\royale-config.xml'.
: defaults (line: -1)
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(35): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\mx-manifest.xml'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 35)
:
:   
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\player\11.0\playerglobal.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\rpc.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\osmf.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\spark.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\apache.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\flatspark.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\framework.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\spark_dmv.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\sparkskins.swc'.
:

Re: Substitutes in Apache Royale

2018-02-19 Thread Alex Harui

Hi Alina,

Piotr might be better at helping you use Moonshine.  The IDEs sort of expect 
that the libraries/SWCs that your code needs is in the same folder as the 
compiler.  That's why it might be easier to work from the command line.

I remembered this morning that the Royale SWF Compiler doesn't have embedded 
font support.  However the goal isn't so much to make a runnable SWF but to 
have the compilation and linking complete so we can determine the full set of 
Flex APIs used in your app.

If your code has two projects, then we will want you to compile both projects 
with the Royale compiler and get two API reports.  The Library project would be 
compiled with js/bin/compc and the main app would be compiled with js/bin/mxmlc.

I think you will want to use the compiler option:
   -load-config="path to a Flex SDK flex-config.xml"
and also use
  –compiler.targets=SWF

HTH,
-Alex


From: Alina Kazi >
Reply-To: "users@royale.apache.org" 
>
Date: Monday, February 19, 2018 at 10:10 PM
To: "users@royale.apache.org" 
>
Subject: RE: Substitutes in Apache Royale

Hi Alex,
Our Flex Application(Main Project) is dependent on Flex Library Project , I 
tookoriginal code (Library Project) without porting it, Compiling it using 
Royale Compiler's SWF compiler (apache-royale-0.9.1-bin-js-swf or 
apache-royale-0.9.0-bin-js-swf)
[cid:image001.png@01D3AA3A.7CAB69F0]

Moonshine IDE (1.9.0) Console :
Loading configuration: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml
:
: C:\Users\aleena\Documents\SHMALIB\defaults Error: unable to open 
'C:\Users\aleena\AppData\Roaming\npm\node_modules\apache-royale\royale-js\frameworks\royale-config.xml'.
: defaults (line: -1)
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(35): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\mx-manifest.xml'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 35)
:
:   
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\player\11.0\playerglobal.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\rpc.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\osmf.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\spark.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\apache.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\flatspark.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\framework.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\spark_dmv.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\sparkskins.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\textLayout.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\experimental.swc'.
: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)
:
: 
:
:
:

RE: Substitutes in Apache Royale

2018-02-19 Thread Alina Kazi

Hi Alex,

Our Flex Application(Main Project) is dependent on Flex Library Project , I 
took original code (Library Project) without porting it, Compiling it using 
Royale Compiler's SWF compiler (apache-royale-0.9.1-bin-js-swf or 
apache-royale-0.9.0-bin-js-swf)



 

Moonshine IDE (1.9.0) Console :

Loading configuration: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml

: 

: C:\Users\aleena\Documents\SHMALIB\defaults Error: unable to open 
'C:\Users\aleena\AppData\Roaming\npm\node_modules\apache-royale\royale-js\frameworks\royale-config.xml'.

: defaults (line: -1)

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(35): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\mx-manifest.xml'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 35)

: 

:   

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\player\11.0\playerglobal.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\rpc.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\osmf.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\spark.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\apache.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\flatspark.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\framework.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\spark_dmv.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\sparkskins.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\textLayout.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\experimental.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\advancedgrids.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\authoringsupport.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\flash-integration.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(61): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\libs\mx\mx.swc'.

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml (line: 61)

: 

: 

: 

: 

: C:\Users\aleena\Documents\SHMALIB\obj\SHMALIBConfig.xml(64): col: 0 Error: 
unable to open 
'D:\apache-royale-0.9.1-bin-js-swf\royale-asjs\frameworks\locale\en_US'.

Re: rs model / tag

2018-02-19 Thread Mandeep Sarma

I believe my settings are similar to yours (as per my screenshot).

What is the proper way to import an example project into moon shine? I have
tried to do it manually and I've tried importing a flex project.

Thanks,
Mandeep

[image: Inline image 1]

On Sun, Feb 18, 2018 at 6:41 AM, piotrz  wrote:

> Mandeep,
>
> I just look into that and didn't have any problem with configuration and
> build using Moonshine 1.9.0 and released version of Royale 0.9.1 JS only.
> Royale website didn't have also Moonshine IDE files in the repository I
> just
> committed it.
>
> My project configuration looks like that:
>
>  configuration_royalewebsite.png>
>
> I setup Royale 0.9.1 JS only SDK in File -> Settings:
> 
>
> If you want you can copy Moonshine configuration file for this project
> which
> I just committed [1] to see if it helps.
>
> [1] https://goo.gl/tFjbpD
>
> Thanks,
> Piotr
>
>
>
> --
> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>

Re: Substitutes in Apache Royale

2018-02-19 Thread Alex Harui

I'm sure many people would be happier if there were fewer lines of code to be 
touched.  IMO, this debate is about where it is reasonable to ask folks to 
change their code.  I am not afraid to ask someone to tweak their code because, 
if you have 100,000 lines of business logic, having to change 1000 lines should 
be much lower risk than porting all 100,000 lines to another JS framework.

Also, there are layers to backwards compatibility.  If we create an 
mx.collections.ArrayCollection for Royale, that might save you from touching 
some lines of code, but what if some other part of your code assumed that 
ArrayCollection subclasses ListCollectionView, and so on?  The number of class 
dependencies that we'd have to mimic could easily extend into reproducing about 
90% of the APIs in Flex.  Flex did not have good separation of concerns.  We 
are not staffed to produce classes for 90% of Flex, and I personally do not 
wish to work on something like that.

Also, there is a really good chance you will have to change some of your code 
around ArrayCollection.  There are no weak references for event listeners in 
Royale, so if your code tosses out an ArrayCollection and expects it to be 
garbage collected, the Royale version will not get GC'd.  If Royale creates an 
ArrayCollection class that wraps an IList and you want to get rid of it, you 
will probably have to call a release() API or something like that.

So, I do not think it is practical to have zero changes to logic that accessed 
Flex classes.  The business logic that I think can be left untouched really 
should not take Flex classes as inputs.  IMO, there is a network layer that 
should abstract how the data is retrieved.  Your business logic should try to 
work with Arrays.  You would probably find it works much faster against Array 
instead of ArrayCollection.  The ResultEvent and FaultEvent should be part of 
the network layer.  And the ResultEvent handler should call some entry point in 
the business logic.

This network layer would be replaced by Royale classes.  The output that gets 
passed into the business logic would be the same arrays and function entry 
points.  If it is impossible or impractical to write business logic without 
Flex classes, I'm interested in knowing that classes are a "must have" and then 
we can consider mimicking those classes.  I would hope that ArrayCollection 
isn't one of them, or if it is, then nobody cares whether it is a 
ListCollectionView or not.  I could imaging mimicking Sort/SortField, but 
really, you should pass in a sorted Array to the business logic.  And then the 
use of ArrayCollection is in the Network layer and you can make calls to an 
ArrayCollecition.release() if you need to.

I wish it could be easier, but I don't know of a practical way to make it so, 
at least without more folks writing framework code.  But it still should be 
much easier and safer than porting every line of code to a new framework.

My 2 cents,
-Alex

From: Piotr Zarzycki 
>
Reply-To: "users@royale.apache.org" 
>
Date: Monday, February 19, 2018 at 2:10 PM
To: "users@royale.apache.org" 
>
Subject: Re: Substitutes in Apache Royale

So you basically would like to in your code avoid changes FaultEvent to Event 
everywhere ?  Yes ? That's the point in your case of having typed events for 
AMF handlers ?

2018-02-19 23:06 GMT+01:00 Carlos Rovira 
>:
All AMF/RemoteObject API worked with that. And our AMF/RemoteObject 
implementation in Royale does the same. In fact we already have FaultEvent and 
Result Event... why don't use it? seems to me more complicated to change it to 
no use that...
Our code relies heavily in AMF so all that classes are in lots of code to 
manage the use of the incoming data for the server and that data is what gives 
the result object from the backend to the client to manage it,

2018-02-19 23:00 GMT+01:00 Gabe Harbs 
>:
I don’t use AMF, but I have no idea why you need specially typed events for 
that.

Maybe I’m missing something…

On Feb 19, 2018, at 11:38 PM, Carlos Rovira 
> wrote:

Hi Harbs

2018-02-15 10:53 GMT+01:00 Gabe Harbs 
>:
None of the cases where I had ResultEvent and FaultEvent really made a lot of 
sense to keep that logic in Royale (events should generally be of type Event), 
so keeping those events would just mask places where code should probably be 
rewritten.

I think you was not using AMF. With RemoteObjects, I think Fault and Result 
events are a must or at least I can't imagine a way to handle the async 
behavior in other way. Maybe your

Re: Substitutes in Apache Royale

2018-02-19 Thread Piotr Zarzycki

So you basically would like to in your code avoid changes FaultEvent to
Event everywhere ?  Yes ? That's the point in your case of having typed
events for AMF handlers ?

2018-02-19 23:06 GMT+01:00 Carlos Rovira :

> All AMF/RemoteObject API worked with that. And our AMF/RemoteObject
> implementation in Royale does the same. In fact we already have FaultEvent
> and Result Event... why don't use it? seems to me more complicated to
> change it to no use that...
> Our code relies heavily in AMF so all that classes are in lots of code to
> manage the use of the incoming data for the server and that data is what
> gives the result object from the backend to the client to manage it,
>
> 2018-02-19 23:00 GMT+01:00 Gabe Harbs :
>
>> I don’t use AMF, but I have no idea why you need specially typed events
>> for that.
>>
>> Maybe I’m missing something…
>>
>> On Feb 19, 2018, at 11:38 PM, Carlos Rovira 
>> wrote:
>>
>> Hi Harbs
>>
>> 2018-02-15 10:53 GMT+01:00 Gabe Harbs :
>>>
>>> None of the cases where I had ResultEvent and FaultEvent really made a
>>> lot of sense to keep that logic in Royale (events should generally be of
>>> type Event), so keeping those events would just mask places where code
>>> should probably be rewritten.
>>>
>>>
>> I think you was not using AMF. With RemoteObjects, I think Fault and
>> Result events are a must or at least I can't imagine a way to handle the
>> async behavior in other way. Maybe your scenario was different right?
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: Substitutes in Apache Royale

2018-02-19 Thread Gabe Harbs

I don’t use AMF, but I have no idea why you need specially typed events for 
that.

Maybe I’m missing something…

> On Feb 19, 2018, at 11:38 PM, Carlos Rovira  wrote:
> 
> Hi Harbs
> 
> 2018-02-15 10:53 GMT+01:00 Gabe Harbs  >:
> None of the cases where I had ResultEvent and FaultEvent really made a lot of 
> sense to keep that logic in Royale (events should generally be of type 
> Event), so keeping those events would just mask places where code should 
> probably be rewritten.
> 
> 
> I think you was not using AMF. With RemoteObjects, I think Fault and Result 
> events are a must or at least I can't imagine a way to handle the async 
> behavior in other way. Maybe your scenario was different right?
> 
> 
> -- 
> Carlos Rovira
> http://about.me/carlosrovira 
>

Re: Substitutes in Apache Royale

2018-02-19 Thread Piotr Zarzycki

Wish I could have from .NET async, await <3 :)

2018-02-19 22:38 GMT+01:00 Carlos Rovira :

> Hi Harbs
>
> 2018-02-15 10:53 GMT+01:00 Gabe Harbs :
>>
>> None of the cases where I had ResultEvent and FaultEvent really made a
>> lot of sense to keep that logic in Royale (events should generally be of
>> type Event), so keeping those events would just mask places where code
>> should probably be rewritten.
>>
>>
> I think you was not using AMF. With RemoteObjects, I think Fault and
> Result events are a must or at least I can't imagine a way to handle the
> async behavior in other way. Maybe your scenario was different right?
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: rs model / tag

Re: Substitutes in Apache Royale

Re: Substitutes in Apache Royale

RE: Substitutes in Apache Royale

Re: rs model / tag

Re: Substitutes in Apache Royale

Re: Substitutes in Apache Royale

Re: Substitutes in Apache Royale

Re: Substitutes in Apache Royale

9 matches

Site Navigation

Mail list logo

Footer information