Re: Newest little Harbs (was Re: Null pointer errors)

[Carlos Rovira]

hehe, not geek but very related! Beautiful name! :)

2018-05-03 22:14 GMT+02:00 Harbs :

> Funny, but you weren’t very far off… ;-)
>
> We named our daughter Malka which is Hebrew for queen. (No, it was not
> because of Royale. I might be a geek but my wife definitely is not. ;-p She
> was named after a grandmother.) So she does in fact have a “Royale” name…
>
> :-)
>
> Harbs
>
> > On May 2, 2018, at 6:50 PM, Alex Harui  wrote:
> >
> > Whatever you do, do not name her "Royale"
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Jewel is no longer dependent of Basic

[Carlos Rovira]

Hi,

I think I was too optimistic here. I was looking at JewelExample code and I
have more Basic dependencies, like "View"
But I'm very confused that after remove all "Basic" pom dependencies all is
compiling correctly.
I check parent poms, searching for "Basic" and I didn't find it...so how is
this magic going on? :?
I'm missing something? thoughts?

thanks

Carlos


2018-05-03 19:33 GMT+02:00 Carlos Rovira :

> Hi,
>
> I'm really amazed that I can get rid of Basic so easily.
> Just moved UIBase and HTMLElementWrapper to Core and that's it, I removed
> Basic dependency from Jewel projects, and I though I would have to deal
> with more dependencies not found...but that not happen :?...
>
> That proves that Royale is really well architected. Huge congrats to all
> of you that make it possible! Specially Alex and Peter!
>
> Best,
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: There's some example of MXRoyale to look at?

[Carlos Rovira]

So you mean that ControlsExample are looking wrong and components should
appear? Strange...

Ok, hope someone could take a look, since I think it could be another good
point to make noise in social networks...a good one :)

thanks

2018-05-03 20:24 GMT+02:00 Alex Harui :

> Hi Carlos,
>
> I haven't looked at those examples in a long time.  My main focus is on
> getting the Flex SDK Mustella tests to run.  I've got plenty on my plate
> right now so it would be good for others to figure out why things are going
> wrong and get to know the emulation components better.
>
> My 2 cents,
> -Alex
>
> On 5/3/18, 9:29 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> Hi Alex,
>
> I finaly could build MXRoyale with maven and:
>
> 1.- HelloWorld; I can see the label "Hello World" but only on
> js-release,
> not in js-debug. So I think that's weird, did you saw that issue?
>
> 2.- ControlsExample: compile but I see the same as in 1) nothing in
> debug
> and HelloWorld label in release. I suppose that's normal since I
> remember
> you want to make all compile, but still don't have visuals. That's
> right?
>
> thanks
>
> 2018-04-26 19:21 GMT+02:00 Carlos Rovira :
>
> > Hi Alex,
> >
> > you're right, our case (Codeoscopic Application to migrate) uses
> modules
> > extensively too, so Modules is for me very needed, and will be for
> any
> > serious royale application out there.
> > I want to have SWF side as well, and I'll try it as I get some time.
> As
> > you say, we should:
> >
> > 1.- get at least bounding boxes and event handlers working so we
> could see
> > a "ugly" interface that layouts correctly and work correctly, but
> doesn't
> > look pretty at that time
> >
> > 2.- make it match HTML look and feel
> >
> > For me 1 is important, and we can delay 2 for now, since we need to
> get
> > more a more needed components on Jewel.
> >
> > In the other hand, I can at some time, help on making MXRoyale look
> like
> > MX and Spark...but I think there's much to do now to think on that,
> and I
> > don't mind if that components doesn't look good right now. I think
> MX and
> > Spark need work flawlessly for now and have at least bounding boxes
> on
> > screen and events working.
> >
> > Thanks
> >
> > Carlos
> >
> >
> >
> > 2018-04-25 18:36 GMT+02:00 Alex Harui :
> >
> >> Hi Carlos,
> >>
> >> I think these components are going to look ugly for a little while
> >> longer.  Also, I have been trying to get them to work for SWF
> output as
> >> well because Alina's app uses modules extensively and having the
> Flash
> >> version verify interfaces could be a huge time savings.
> Eventually, I hope
> >> that we can replace the views in the emulation components with Jewel
> >> views.  The SWF version of the Jewel views don't have to look
> great, it
> >> just has to take up the same space on the screen.  We just want to
> make
> >> sure we can run most of the code paths through the verifier.
> >>
> >> If you have time to try mocking the visuals for SWF that would be
> >> interesting to see.
> >>
> >> I'm mainly saying that I don't think blog posts about these
> components is
> >> going to look nearly as attractive as the Jewel blog posts
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 4/25/18, 1:32 AM, "carlos.rov...@gmail.com on behalf of Carlos
> >> Rovira"  carlosrov...@apache.org>
> >> wrote:
> >>
> >> Hi Alex,
> >>
> >> 2018-04-25 9:39 GMT+02:00 Alex Harui  >:
> >>
> >> > 120 MX classes compile. Only six MX UI components work at all.
> >> There are
> >> > examples in examples/mxroyale.  We have not started on Spark.
> >> >
> >>
> >> That sounds very good. Congrats!
> >>
> >>
> >> >
> >> > In mustella/mxtests is a copy of the flex-sdk checkintest.
> The
> >> first six
> >> > tests run without modification (actually a few tests that
> tested
> >> internals
> >> > were disabled).  That's actually a fair amount of work
> because to
> >> get that
> >> > much to run we had to emulate Application and states and some
> >> containers as
> >> > well.
> >> >
> >> > But like I said in another thread.  This is a new effort and
> I have
> >> been
> >> > distracted by other things and haven't spent nearly as much
> time on
> >> this as
> >> > I had hoped, and wished more existing committers would help.
> >> Getting all
> >> > of this to compile is a fair amount of work.  Getting it 

Jenkins build is back to normal : royale-asjs_jsonly #739

[apacheroyaleci]

See 

Jenkins build is back to normal : Royale_ASDoc_Example #711

[apacheroyaleci]

See 

Re: Newest little Harbs (was Re: Null pointer errors)

[Harbs]

Funny, but you weren’t very far off… ;-)

We named our daughter Malka which is Hebrew for queen. (No, it was not because 
of Royale. I might be a geek but my wife definitely is not. ;-p She was named 
after a grandmother.) So she does in fact have a “Royale” name…

:-)

Harbs

> On May 2, 2018, at 6:50 PM, Alex Harui  wrote:
> 
> Whatever you do, do not name her "Royale"

Jenkins build is back to normal : royale-asjs #731

[apacheroyaleci]

See 

Build failed in Jenkins: royale-asjs #730

[apacheroyaleci]

s/js/libs>

package-clean:
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/out>

clean-temp:
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/temp/royale-asjs>

checkintests-clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/mustella/tests/basicTests/BasicTestsApp.swf>

mxtests-clean:

clean:
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/royale-sdk-description.xml>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/js/libs>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/temp>
 [echo] ROYALE_HOME = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/>
 [echo] royalelib = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>
 [echo] doc_output = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/asdoc-output>
 [echo] compiler.source-path = 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/projects/*/src/main/royale>

clean:

super-clean:
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/mustella/tests/basicTests/bin>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/locale>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/mx>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/rsls>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Halo>
   [delete] Deleting directory 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Spark>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/airmobile-config.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/macfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/winfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/localfonts.ser>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/mxml-manifest.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/spark-manifest.xml>
   [delete] Deleting: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/ide/flashbuilder/flashbuilder-config.xml>

create-description:
 [echo] build.number is 20180503

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks>

tweak-for-jsonly:
[mkdir] Created dir: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/themes/Spark>

stage-source:

clean-temp:
[mkdir] Created dir: 
<http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/roy

Build failed in Jenkins: Royale_ASDoc_Example #710

[apacheroyaleci]

See 


Changes:

[aharui] try moving initialView to be last property to set up so fx:Declarations

--
Started by upstream project "royale-asjs" build number 729
originally caused by:
 Started by upstream project "royale-asjs_jsonly" build number 737
 originally caused by:
  Started by upstream project "royale-typedefs" build number 373
  originally caused by:
   Started by upstream project "royale-compiler" build number 230
   originally caused by:
Started by an SCM change
Building in workspace 

 > git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git.exe config remote.origin.url https://github.com/apache/royale-asjs.git # 
 > timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs.git
 > git.exe --version # timeout=10
 > git.exe fetch --tags --progress https://github.com/apache/royale-asjs.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git.exe rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10
 > git.exe rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 40d0e1ca8ca44cc5272e9c69c86d4cf009f6c1a7 
(refs/remotes/origin/develop)
 > git.exe config core.sparsecheckout # timeout=10
 > git.exe checkout -f 40d0e1ca8ca44cc5272e9c69c86d4cf009f6c1a7
Commit message: "try moving initialView to be last property to set up so 
fx:Declarations and most other properties get initialized first.  This should 
be more like the order of execution in Flex"
 > git.exe rev-list --no-walk ace886accf956d0ecc7b393cf5e7e31bfea9a922 # 
 > timeout=10
[ASDoc] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat -file build.xml 
-Denv.FLASHPLAYER_DEBUGGER=C:\adobe\flash\11.7\flashplayerdebugger.exe 
-Denv.PLAYERGLOBAL_HOME=C:\adobe\flash 
-Denv.AIR_HOME=C:\adobe\air\4.0\AdobeAIRSDK '"-DROYALE_HOME=C:\Program Files 
(x86)\Jenkins\workspace\royale-asjs"' -Dbuild.noprompt=true 
-Dplayerglobal.version=11.7 clean main && exit %%ERRORLEVEL%%"
Buildfile: 


clean:
   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting directory 


build_example.compile:
 [echo] Compiling ASDoc.swf
 [echo] ROYALE_HOME: C:\Program Files (x86)\Jenkins\workspace\royale-asjs
 [echo] ROYALE_COMPILER_HOME: C:\Program Files 
(x86)\Jenkins\workspace\royale-asjs/../royale-compiler/compiler-jx
 [echo] GOOG_HOME: ${GOOG_HOME}
  [taskdef] Could not load definitions from resource flexTasks.tasks. It could 
not be found.

BUILD FAILED
:157:
 Problem: failed to create task or type mxmlc
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken place.


Total time: 1 second
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #738

[apacheroyaleci]

See 


Changes:

[aharui] try moving initialView to be last property to set up so fx:Declarations

--
[...truncated 464.74 KB...]
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.141 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLPropertySpecifierNodeNumberTests
[junit] Tests run: 27, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 
0.781 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLPropertySpecifierNodeStringTests
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.141 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLPropertySpecifierNodeTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 
sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLPropertySpecifierNodeUintTests
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.11 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLRegExpNodeTests
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.094 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLResourceNodeTests
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.156 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLScriptNodeTests
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.141 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLSpecifierNodeBaseTests
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0 
sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLStringNodeTests
[junit] Tests run: 10, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.407 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLStyleNodeTests
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.172 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLUintNodeTests
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.359 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLXMLListNodeTests
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.156 sec
[junit] Running 
org.apache.royale.compiler.internal.tree.mxml.MXMLXMLNodeTests
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
0.25 sec
[junit] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8

main:

swf:

compiler.jx:

prebuild:
[mkdir] Created dir: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\target\classes
[mkdir] Created dir: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\target\classes\META-INF
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

prepare:
 [echo] Making lib directory C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx/lib

all:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-dependency:

download-dependency:
  [get] Getting: 
https://raw.githubusercontent.com/kohsuke/args4j/master/LICENSE
  [get] To: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\lib\args4j-LICENSE.txt
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-dependency-closure:

download-dependency-closure:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx

check-dependency:

download-dependency:
 [echo] basedir is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\compiler-jx
 [echo] ROYALE_COMPILER_HOME is C:\Program Files 

Re: There's some example of MXRoyale to look at?

[Alex Harui]

Hi Carlos,

I haven't looked at those examples in a long time.  My main focus is on getting 
the Flex SDK Mustella tests to run.  I've got plenty on my plate right now so 
it would be good for others to figure out why things are going wrong and get to 
know the emulation components better.

My 2 cents,
-Alex

On 5/3/18, 9:29 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" 
 wrote:

Hi Alex,

I finaly could build MXRoyale with maven and:

1.- HelloWorld; I can see the label "Hello World" but only on js-release,
not in js-debug. So I think that's weird, did you saw that issue?

2.- ControlsExample: compile but I see the same as in 1) nothing in debug
and HelloWorld label in release. I suppose that's normal since I remember
you want to make all compile, but still don't have visuals. That's right?

thanks

2018-04-26 19:21 GMT+02:00 Carlos Rovira :

> Hi Alex,
>
> you're right, our case (Codeoscopic Application to migrate) uses modules
> extensively too, so Modules is for me very needed, and will be for any
> serious royale application out there.
> I want to have SWF side as well, and I'll try it as I get some time. As
> you say, we should:
>
> 1.- get at least bounding boxes and event handlers working so we could see
> a "ugly" interface that layouts correctly and work correctly, but doesn't
> look pretty at that time
>
> 2.- make it match HTML look and feel
>
> For me 1 is important, and we can delay 2 for now, since we need to get
> more a more needed components on Jewel.
>
> In the other hand, I can at some time, help on making MXRoyale look like
> MX and Spark...but I think there's much to do now to think on that, and I
> don't mind if that components doesn't look good right now. I think MX and
> Spark need work flawlessly for now and have at least bounding boxes on
> screen and events working.
>
> Thanks
>
> Carlos
>
>
>
> 2018-04-25 18:36 GMT+02:00 Alex Harui :
>
>> Hi Carlos,
>>
>> I think these components are going to look ugly for a little while
>> longer.  Also, I have been trying to get them to work for SWF output as
>> well because Alina's app uses modules extensively and having the Flash
>> version verify interfaces could be a huge time savings.  Eventually, I 
hope
>> that we can replace the views in the emulation components with Jewel
>> views.  The SWF version of the Jewel views don't have to look great, it
>> just has to take up the same space on the screen.  We just want to make
>> sure we can run most of the code paths through the verifier.
>>
>> If you have time to try mocking the visuals for SWF that would be
>> interesting to see.
>>
>> I'm mainly saying that I don't think blog posts about these components is
>> going to look nearly as attractive as the Jewel blog posts
>>
>> My 2 cents,
>> -Alex
>>
>> On 4/25/18, 1:32 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira" 
>> wrote:
>>
>> Hi Alex,
>>
>> 2018-04-25 9:39 GMT+02:00 Alex Harui :
>>
>> > 120 MX classes compile. Only six MX UI components work at all.
>> There are
>> > examples in examples/mxroyale.  We have not started on Spark.
>> >
>>
>> That sounds very good. Congrats!
>>
>>
>> >
>> > In mustella/mxtests is a copy of the flex-sdk checkintest.  The
>> first six
>> > tests run without modification (actually a few tests that tested
>> internals
>> > were disabled).  That's actually a fair amount of work because to
>> get that
>> > much to run we had to emulate Application and states and some
>> containers as
>> > well.
>> >
>> > But like I said in another thread.  This is a new effort and I have
>> been
>> > distracted by other things and haven't spent nearly as much time on
>> this as
>> > I had hoped, and wished more existing committers would help.
>> Getting all
>> > of this to compile is a fair amount of work.  Getting it to run is
>> going to
>> > be a serious effort.  Expecting that we'd get MX and Spark working
>> in this
>> > short amount of time is not realistic.
>> >
>>
>> Alex, I think is not realistic to think we can get people on board
>> showing
>> Basic examples, or thinks that "doesn't look good". For me, I had a
>> long
>> journey to start producing things that looks in a way we can blog,
>> twit and
>> so on..., so what you see wasn't worth it, for me is the 

Jewel is no longer dependent of Basic

[Carlos Rovira]

Hi,

I'm really amazed that I can get rid of Basic so easily.
Just moved UIBase and HTMLElementWrapper to Core and that's it, I removed
Basic dependency from Jewel projects, and I though I would have to deal
with more dependencies not found...but that not happen :?...

That proves that Royale is really well architected. Huge congrats to all of
you that make it possible! Specially Alex and Peter!

Best,

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: There's some example of MXRoyale to look at?

[Carlos Rovira]

Hi Alex,

I finaly could build MXRoyale with maven and:

1.- HelloWorld; I can see the label "Hello World" but only on js-release,
not in js-debug. So I think that's weird, did you saw that issue?

2.- ControlsExample: compile but I see the same as in 1) nothing in debug
and HelloWorld label in release. I suppose that's normal since I remember
you want to make all compile, but still don't have visuals. That's right?

thanks

2018-04-26 19:21 GMT+02:00 Carlos Rovira :

> Hi Alex,
>
> you're right, our case (Codeoscopic Application to migrate) uses modules
> extensively too, so Modules is for me very needed, and will be for any
> serious royale application out there.
> I want to have SWF side as well, and I'll try it as I get some time. As
> you say, we should:
>
> 1.- get at least bounding boxes and event handlers working so we could see
> a "ugly" interface that layouts correctly and work correctly, but doesn't
> look pretty at that time
>
> 2.- make it match HTML look and feel
>
> For me 1 is important, and we can delay 2 for now, since we need to get
> more a more needed components on Jewel.
>
> In the other hand, I can at some time, help on making MXRoyale look like
> MX and Spark...but I think there's much to do now to think on that, and I
> don't mind if that components doesn't look good right now. I think MX and
> Spark need work flawlessly for now and have at least bounding boxes on
> screen and events working.
>
> Thanks
>
> Carlos
>
>
>
> 2018-04-25 18:36 GMT+02:00 Alex Harui :
>
>> Hi Carlos,
>>
>> I think these components are going to look ugly for a little while
>> longer.  Also, I have been trying to get them to work for SWF output as
>> well because Alina's app uses modules extensively and having the Flash
>> version verify interfaces could be a huge time savings.  Eventually, I hope
>> that we can replace the views in the emulation components with Jewel
>> views.  The SWF version of the Jewel views don't have to look great, it
>> just has to take up the same space on the screen.  We just want to make
>> sure we can run most of the code paths through the verifier.
>>
>> If you have time to try mocking the visuals for SWF that would be
>> interesting to see.
>>
>> I'm mainly saying that I don't think blog posts about these components is
>> going to look nearly as attractive as the Jewel blog posts
>>
>> My 2 cents,
>> -Alex
>>
>> On 4/25/18, 1:32 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira" 
>> wrote:
>>
>> Hi Alex,
>>
>> 2018-04-25 9:39 GMT+02:00 Alex Harui :
>>
>> > 120 MX classes compile. Only six MX UI components work at all.
>> There are
>> > examples in examples/mxroyale.  We have not started on Spark.
>> >
>>
>> That sounds very good. Congrats!
>>
>>
>> >
>> > In mustella/mxtests is a copy of the flex-sdk checkintest.  The
>> first six
>> > tests run without modification (actually a few tests that tested
>> internals
>> > were disabled).  That's actually a fair amount of work because to
>> get that
>> > much to run we had to emulate Application and states and some
>> containers as
>> > well.
>> >
>> > But like I said in another thread.  This is a new effort and I have
>> been
>> > distracted by other things and haven't spent nearly as much time on
>> this as
>> > I had hoped, and wished more existing committers would help.
>> Getting all
>> > of this to compile is a fair amount of work.  Getting it to run is
>> going to
>> > be a serious effort.  Expecting that we'd get MX and Spark working
>> in this
>> > short amount of time is not realistic.
>> >
>>
>> Alex, I think is not realistic to think we can get people on board
>> showing
>> Basic examples, or thinks that "doesn't look good". For me, I had a
>> long
>> journey to start producing things that looks in a way we can blog,
>> twit and
>> so on..., so what you see wasn't worth it, for me is the key factor.
>>
>> Now I can start to spread the word about this effort in social
>> networks. I
>> tried the examples, but need to fix poms to build with maven. I'll do
>> it
>> today in order to see it working.
>>
>> If we can show that work, and make people out there know about it,
>> maybe we
>> can bring you more people to help in that effort.
>>
>> Thanks
>>
>> Carlos
>>
>>
>> >
>> > My 2 cents,
>> > -Alex
>> >
>> > On 4/24/18, 3:40 PM, "carlos.rov...@gmail.com on behalf of Carlos
>> > Rovira" > carlosrov...@apache.org>
>> > wrote:
>> >
>> > I was wondering if there's some example of the emulation
>> components to
>> > show
>> > the work done
>> > Something that aggregates all mx and spark components that we
>> have now
>> > emulated?
>> > I'm 

RE: Apache Royale on LinkedIn! Join us!

[Alina Kazi]

Awesome!!

-Original Message-
From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of 
Carlos Rovira
Sent: Thursday, May 03, 2018 3:53 PM
To: us...@royale.apache.org; dev@royale.apache.org
Subject: Re: Apache Royale on LinkedIn! Join us!

Hey! it's amazing that we are growing very quickly on LinkedIn and we are right 
now 43 members in only few hours!.

Keep on and make it huge! :)

2018-05-03 7:42 GMT+02:00 Carlos Rovira :

> Hi all
>
> just want to announce that we're now on LinkedIn!!
>
> The new Apache Royale group is a very cool site to post conversations 
> and as well something very important for the health of this community: 
> Jobs! :)
>
> So come on and join us!
>
> Here's the link to the group:
>
> https://www.linkedin.com/groups/12118437
>
> (Note: seems LinkedIn groups are in an on going redesign, so we can't 
> still change the group logo to our Apache Royale logo, but seems 
> things will be improving as they update the service)
>
> Thanks
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>


--
Carlos Rovira
http://about.me/carlosrovira

Re: Bug iterating ArrayList

[Alex Harui]

Ah yes, that's true.  When we get around to emulating ArrayCollection it will 
be iterable.

-Alex

On 5/3/18, 12:39 AM, "Yishay Weiss"  wrote:

From memory, it wasn’t possible to iterate through ArrayList with for each 
in Flex either.




From: Σπύρος Αγγελόπουλος 
Sent: Thursday, May 3, 2018 10:13:11 AM
To: dev@royale.apache.org
Subject: RE: Bug iterating ArrayList

Hi ,
Issue #220

Spiros



-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID]
Sent: Wednesday, May 2, 2018 6:53 PM
To: dev@royale.apache.org
Subject: Re: Bug iterating ArrayList

Hi,

Thanks for reporting.  Can you file a GitHub issue?


https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Froyale-asjs%2Fissues=02%7C01%7Caharui%40adobe.com%7C990895fc93c64621be7708d5b0c8fac4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636609299610677792=r3AdzckDnL44R2KMCL6iv2jIYw5OhuSHJj7jb5cXnUM%3D=0

Thanks,
-Alex

On 5/2/18, 7:37 AM, "Σπύρος Αγγελόπουλος"  wrote:

The code below produce a strange results

var ar:ArrayList = new ArrayList;
ar.addItem(new String("some value"));
var index:int=0;
for each (var obj:Object in ar)
{
   index++;
}
trace ( "for each iteration ="+ index);
index =0;
for (var i:int=0;i < ar.length ;i++)
{
   index++;
}
trace ("for iterations =" +index);

the console output :

16:26:13.431 Language.js:237 for each iteration =52
16:26:13.432 Language.js:237 for iterations =1



The version of SDK is Apache Royale 0.9.3 FP11.7 AIR14.0 en_US 
(nightBuild)


Spiros

Re: New blog example to review

[Dany Dhondt]

Hi Carlos,

I mean a widget like putting a vimeo video on your site or a google map

-Dany

Op 3 mei 2018 om 09:43 uur uur schreef Carlos Rovira :

Hi Dany,

thanks! I'm creating the examples in "examples/blog" folder and uploading
the "js-release" html/js/css output to the website. Then showing it in an
iFrame so people could look at the code and the final result. Don't know
what you mean exactly with "widget", can you elaborate more about this?
since a widget can be many things and depends to the context (wordpress,
mobile, desktop OS,...)

thanks!



2018-05-03 8:08 GMT+02:00 Dany Dhondt :

Hi Carlos,

thanks for these great examples.


To show the component, is it as easy as linking the compiled js file in an
iFrame?

So would this be the way to create a widget?


thx

Dany



Op 3 mei 2018 om 06:41 uur uur schreef Olaf Krueger 

Re: States doesn't work properly anymore

[Piotr Zarzycki]

Alex,

I had some session yesterday with that and I think I have found the reason.
It is connected with how MDL is working. Let's start from the initial code

This is how code looks like:
 -> After translation -> 
  -> after
translation -> 


In above case the parent of NavigationLayout should be, a View, but it
isn't. Each MDL component is going through some kind of invalidation
mechanism - it's called upgrading. Sometime in the results of upgrading MDL
library is adding additional containers. In above case our translated code
should looks like:


   


BUT it looks like that:


- This ELEMENT is not a Royale
creation. It doesn't have  royale_wrapper.




Initial state is setting up correctly along with initial class "
examplesBackground"
- However changes are not possible because we are checking whether parent
exists and it exists but it's not a Royale component.

I'm not sure how to fix that yet.

Thanks, Piotr


2018-05-01 22:26 GMT+02:00 Alex Harui :

> An element without a royale_wrapper breaks the fundamental contract in
> UIBase.  I recommend that you figure that part out.
>
> Good luck,
> -Alex
>
> On 5/1/18, 12:33 PM, "Piotr Zarzycki"  wrote:
>
> In the other words - My website is loaded and component have initial
> state.
>
> Than I'm clicking on the button I'm changing state for that component.
>
> Piotr
>
> On Tue, May 1, 2018, 7:27 PM Piotr Zarzycki  >
> wrote:
>
> > This component is already on the display list. I'm changing States
> of that
> > component. That's the weirdest thing.
> >
> > Piotr
> >
> > On Tue, May 1, 2018, 7:06 PM Alex Harui 
> wrote:
> >
> >> Hi Piotr,
> >>
> >> What is the call stack at that point?  Should the component be on
> the
> >> display list or is it still having its properties set up per the
> >> lifecycle?  If it is just having its properties set up, there
> should be
> >> another call to setClassName in addedToParent and parent should not
> be
> >> undefined.
> >>
> >> -Alex
> >>
> >> On 5/1/18, 9:58 AM, "piotrz"  wrote:
> >>
> >> Alex,
> >>
> >> I just checked getter for parent and royale_wrapper on element
> is
> >> undefined.
> >>
> >> <
> >> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
> com%2Ffile%2Ft1%2Froyale_wrapper_undefined.png=02%
> 7C01%7Caharui%40adobe.com%7C4df3cf45055440294eb908d5af84cc3e%
> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636607907300284114=%
> 2BWvX%2B84oVUsWZO4Q3rO4QwPRnR1TcZJKseXYJB1ni8U%3D=0>
> >>
> >>
> >> Piotr
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Sent from:
> >> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fapache-royale-development.20373.n8.nabble.
> com%2F=02%7C01%7Caharui%40adobe.com%7C4df3cf45055440294eb908d5af84
> cc3e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636607907300284114=W4AV3qDPNfO1VlCywDh5bd5u9Oa7Fh
> 0JXDhzrFIp%2FMM%3D=0
> >>
> >>
> >>
>
>
>


-- 

Piotr Zarzycki

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

Re: New blog example to review

[Carlos Rovira]

Hi Dany,

thanks! I'm creating the examples in "examples/blog" folder and uploading
the "js-release" html/js/css output to the website. Then showing it in an
iFrame so people could look at the code and the final result. Don't know
what you mean exactly with "widget", can you elaborate more about this?
since a widget can be many things and depends to the context (wordpress,
mobile, desktop OS,...)

thanks!



2018-05-03 8:08 GMT+02:00 Dany Dhondt :

> Hi Carlos,
>
> thanks for these great examples.
>
>
> To show the component, is it as easy as linking the compiled js file in an
> iFrame?
>
> So would this be the way to create a widget?
>
>
> thx
>
> Dany
>
>
>
> Op 3 mei 2018 om 06:41 uur uur schreef Olaf Krueger  >:
>
> Hi Carlos,
> thanks for another nice Blog example!!!
>
> I would just like to mention that your example doesn't work properly in
> IE11
> (styles/layout issues) [1].
> This is no issue for myself (No need to support IE11) but if I remember it
> correctly you would like
> to support IE11 also someday...
>
> Thanks,
> Olaf
>
> [1]
> https://snag.gy/Jw8nTB.jpg
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

RE: Bug iterating ArrayList

[Yishay Weiss]

From memory, it wasn’t possible to iterate through ArrayList with for each in 
Flex either.




From: Σπύρος Αγγελόπουλος 
Sent: Thursday, May 3, 2018 10:13:11 AM
To: dev@royale.apache.org
Subject: RE: Bug iterating ArrayList

Hi ,
Issue #220

Spiros



-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID]
Sent: Wednesday, May 2, 2018 6:53 PM
To: dev@royale.apache.org
Subject: Re: Bug iterating ArrayList

Hi,

Thanks for reporting.  Can you file a GitHub issue?

https://github.com/apache/royale-asjs/issues

Thanks,
-Alex

On 5/2/18, 7:37 AM, "Σπύρος Αγγελόπουλος"  wrote:

The code below produce a strange results

var ar:ArrayList = new ArrayList;
ar.addItem(new String("some value"));
var index:int=0;
for each (var obj:Object in ar)
{
   index++;
}
trace ( "for each iteration ="+ index);
index =0;
for (var i:int=0;i < ar.length ;i++)
{
   index++;
}
trace ("for iterations =" +index);

the console output :

16:26:13.431 Language.js:237 for each iteration =52
16:26:13.432 Language.js:237 for iterations =1



The version of SDK is Apache Royale 0.9.3 FP11.7 AIR14.0 en_US (nightBuild)


Spiros

RE: Bug iterating ArrayList

[Σπύρος Αγγελόπουλος]

Hi , 
Issue #220  

Spiros 



-Original Message-
From: Alex Harui [mailto:aha...@adobe.com.INVALID] 
Sent: Wednesday, May 2, 2018 6:53 PM
To: dev@royale.apache.org
Subject: Re: Bug iterating ArrayList

Hi,

Thanks for reporting.  Can you file a GitHub issue?

https://github.com/apache/royale-asjs/issues

Thanks,
-Alex

On 5/2/18, 7:37 AM, "Σπύρος Αγγελόπουλος"  wrote:

The code below produce a strange results

var ar:ArrayList = new ArrayList;
ar.addItem(new String("some value"));
var index:int=0;
for each (var obj:Object in ar)
{
   index++;
}
trace ( "for each iteration ="+ index);
index =0;
for (var i:int=0;i < ar.length ;i++)
{
   index++;
}
trace ("for iterations =" +index);
   
the console output : 

16:26:13.431 Language.js:237 for each iteration =52
16:26:13.432 Language.js:237 for iterations =1



The version of SDK is Apache Royale 0.9.3 FP11.7 AIR14.0 en_US (nightBuild)


Spiros 

Re: New blog example to review

[Dany Dhondt]

Hi Carlos,

thanks for these great examples.

To show the component, is it as easy as linking the compiled js file in an 
iFrame?
So would this be the way to create a widget?

thx
Dany


Op 3 mei 2018 om 06:41 uur uur schreef Olaf Krueger :

Hi Carlos,
thanks for another nice Blog example!!!

I would just like to mention that your example doesn't work properly in IE11
(styles/layout issues) [1].
This is no issue for myself (No need to support IE11) but if I remember it
correctly you would like
to support IE11 also someday...

Thanks,
Olaf

[1]
https://snag.gy/Jw8nTB.jpg



--
Sent from: http://apache-royale-development.20373.n8.nabble.com/