Re: MXRoyale build problem

[Carlos Rovira]

ok Alex,

if that makes a problem I'll not use it.
Regarding the problem you have, my work is mostly Jewel projects that are
separate from other things you're doing.
I think there was few files that I must to fix due to when I added
classList methods and Harbs added it to develop, and made me to solve
conflicts at that time.




2018-04-10 17:28 GMT+02:00 Alex Harui :

> Carlos,
>
> I was unable to know how to work on the Jewel branch back when you were
> still working on it because I got concerned about the status showing some
> number of commits ahead and behind against my working copy.  If this is
> somehow related to your use of force push, I would strongly recommend that
> you not use it, especially on the develop branch.   Whatever workflow you
> think is right for remote branches is clearly not right.
>
> Thanks,
> -Alex
>
> From:  on behalf of Carlos Rovira <
> carlosrov...@apache.org>
> Reply-To: "users@royale.apache.org" 
> Date: Tuesday, April 10, 2018 at 4:03 AM
>
> To: "users@royale.apache.org" 
> Subject: Re: MXRoyale build problem
>
> jewel branch was already merged, so since some days I'm not using it. I
> didn't remove it totally, but I'll do in some days (maybe after 0.9.3
> release)
> Maybe for this reason you are a bit confused with that branch, since is
> now deprecated and not synced.
>
> I think my use of rebase is totally ok, so don't worry since I'm using it
> since the beginning with MDL and now with Jewel, and branches are ok.
>
> 2018-04-10 9:21 GMT+02:00 Harbs :
>
>> I suspect that Carlos is doing something different because the
>> jewel-ui-set branch currently shows 22 commits ahead and 127 behind on my
>> machine.
>>
>> Considering I made no local changes, I should not be *any* commits
>> ahead. That would seem like origin has had its history modified which is
>> not good. The only way I would be able to pull in the jewel branch would be
>> to rebase locally...
>>
>> My $0.02,
>> Harbs
>>
>> On Apr 10, 2018, at 7:52 AM, Alex Harui  wrote:
>>
>> Hi Carlos,
>>
>> Does that mean you are using "force push" when rebasing?  I don't use it
>> when rebasing and lots of internet articles advise against using it.  If it
>> is working for you, fine, but I wouldn't want any "forcing" to be a
>> recommended practice for others given the advice I see out there.
>>
>> The key thing for any of us is to understand the differences between
>> merging and rebasing and using them appropriately.  I don't want to take
>> the time to go through it now, but the recommended practice AIUI, is to use
>> merge for public branches and rebase when possible for non-public
>> branches.  MXRoyale is a public branch.
>>
>> Thanks,
>> -Alex
>>
>> From:  on behalf of Carlos Rovira <
>> carlosrov...@apache.org>
>> Reply-To: "users@royale.apache.org" 
>> Date: Monday, April 9, 2018 at 3:01 PM
>> To: "users@royale.apache.org" 
>> Subject: Re: MXRoyale build problem
>>
>> Hi Alex,
>>
>> my problem as I started to use again was that I forgot to check "force
>> push" completely. Without that you are not able to do a rebase, instead you
>> end with a corrupt branch. That was my problem, and I finaly remember that
>> I need to set up that. The way I use to rebase was teach to me by a
>> recognized expert in Git use, and sometimes I use to ask him when I have
>> doubts about how to do something. Rebase is completely a best practice in
>> some scenarios, like the one I use, work in separate branch and rebase over
>> develop, then merge to develop, since you end with a set of consecutive
>> clean commits as if all that commits will be done in that point. No
>> intricate tree object graphs and if some external person comes to see the
>> graph will understand far better that something that is intrincated. Jewel
>> branch was done in this way, and you can see that is very clean.
>>
>> said that (as well I understand now what Piotr said), I only want to
>> express a way that is working for me, but if you all think is not good for
>> you, it's ok, as I said is all subjective, and each one should use what he
>> want (always that doesn't break anything , of course)
>>
>> Thanks
>>
>>
>> 2018-04-09 19:05 GMT+02:00 Alex Harui :
>>
>>> Hi Carlos,
>>>
>>> Using "force push" sounds scary/wrong to me.  Note also that I had
>>> trouble working with your branches and you reported similar problems.  The
>>> general advice on the internet is to not rebase public branches, and I
>>> think I've hit scenarios around that often enough to want to give up on
>>> rebase when merging public branches.
>>>
>>> I always use rebase when pulling changes in from the branch I'm working
>>> from.  That's where it makes sense to me.
>>>
>>> My 2 cents,
>>> -Alex
>>>
>>> From:  on behalf of Carlos Rovira <

Re: MXRoyale build problem

[Alex Harui]

Carlos,

I was unable to know how to work on the Jewel branch back when you were still 
working on it because I got concerned about the status showing some number of 
commits ahead and behind against my working copy.  If this is somehow related 
to your use of force push, I would strongly recommend that you not use it, 
especially on the develop branch.   Whatever workflow you think is right for 
remote branches is clearly not right.

Thanks,
-Alex

From: > on behalf of 
Carlos Rovira >
Reply-To: "users@royale.apache.org" 
>
Date: Tuesday, April 10, 2018 at 4:03 AM
To: "users@royale.apache.org" 
>
Subject: Re: MXRoyale build problem

jewel branch was already merged, so since some days I'm not using it. I didn't 
remove it totally, but I'll do in some days (maybe after 0.9.3 release)
Maybe for this reason you are a bit confused with that branch, since is now 
deprecated and not synced.

I think my use of rebase is totally ok, so don't worry since I'm using it since 
the beginning with MDL and now with Jewel, and branches are ok.

2018-04-10 9:21 GMT+02:00 Harbs 
>:
I suspect that Carlos is doing something different because the jewel-ui-set 
branch currently shows 22 commits ahead and 127 behind on my machine.

Considering I made no local changes, I should not be any commits ahead. That 
would seem like origin has had its history modified which is not good. The only 
way I would be able to pull in the jewel branch would be to rebase locally...

My $0.02,
Harbs

On Apr 10, 2018, at 7:52 AM, Alex Harui 
> wrote:

Hi Carlos,

Does that mean you are using "force push" when rebasing?  I don't use it when 
rebasing and lots of internet articles advise against using it.  If it is 
working for you, fine, but I wouldn't want any "forcing" to be a recommended 
practice for others given the advice I see out there.

The key thing for any of us is to understand the differences between merging 
and rebasing and using them appropriately.  I don't want to take the time to go 
through it now, but the recommended practice AIUI, is to use merge for public 
branches and rebase when possible for non-public branches.  MXRoyale is a 
public branch.

Thanks,
-Alex

From: > on behalf of 
Carlos Rovira >
Reply-To: "users@royale.apache.org" 
>
Date: Monday, April 9, 2018 at 3:01 PM
To: "users@royale.apache.org" 
>
Subject: Re: MXRoyale build problem

Hi Alex,

my problem as I started to use again was that I forgot to check "force push" 
completely. Without that you are not able to do a rebase, instead you end with 
a corrupt branch. That was my problem, and I finaly remember that I need to set 
up that. The way I use to rebase was teach to me by a recognized expert in Git 
use, and sometimes I use to ask him when I have doubts about how to do 
something. Rebase is completely a best practice in some scenarios, like the one 
I use, work in separate branch and rebase over develop, then merge to develop, 
since you end with a set of consecutive clean commits as if all that commits 
will be done in that point. No intricate tree object graphs and if some 
external person comes to see the graph will understand far better that 
something that is intrincated. Jewel branch was done in this way, and you can 
see that is very clean.

said that (as well I understand now what Piotr said), I only want to express a 
way that is working for me, but if you all think is not good for you, it's ok, 
as I said is all subjective, and each one should use what he want (always that 
doesn't break anything , of course)

Thanks


2018-04-09 19:05 GMT+02:00 Alex Harui 
>:
Hi Carlos,

Using "force push" sounds scary/wrong to me.  Note also that I had trouble 
working with your branches and you reported similar problems.  The general 
advice on the internet is to not rebase public branches, and I think I've hit 
scenarios around that often enough to want to give up on rebase when merging 
public branches.

I always use rebase when pulling changes in from the branch I'm working from.  
That's where it makes sense to me.

My 2 cents,
-Alex

From: > on behalf of 
Carlos Rovira >
Reply-To: "users@royale.apache.org" 

Re: Work on Emulation

[Carlos Rovira]

Hi Alina,

as you create the PR (or later in the same PR) you have a right sidebar
with:

-Reviewers

-Assignees (that should be filled with your user)

-Labels (this could be "bug", "enhancement",...whatever you, Alex, and
Peter agree to idetificate better a set of PRs)

-Projects (here is where you add to "Emulation Components", since there's
automatic rules, Github will add it to TO DO directly)

-Milestone (this should be better filled by Alex, or if he wants you can
fill it with his consideration. If he wants to merge all this work for
v0.9.3, Milestone should be v0.9.3

I that's all

Thanks!

Carlos




2018-04-10 8:14 GMT+02:00 Alina Kazi :

> Hi Carlos,
>
> How can I add my Pull Request to Emulation Components ?
>
> and How can i change the status
>
> https://github.com/apache/royale-asjs/projects/4
>
> To do -> In progress ->Done
>
>
>
> Thanks,
>
> Alina Kazi
>
> *From:* carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] *On
> Behalf Of *Carlos Rovira
> *Sent:* Monday, April 09, 2018 7:06 PM
> *To:* users@royale.apache.org
>
> *Subject:* Re: Work on Emulation
>
>
>
> Hi Alina,
>
>
>
> I added some of your PRs to new project "Emulation Components", please if
> you create new add to this project so the tickets can be handler
> automatically.
>
> As well if you can configure for new (and old issues) the info in the
> right sidebar of GitHub, that would be of much help to better organize the
> effort
>
>
>
> thanks :)
>
>
>
>
>
>
>
> 2018-04-09 14:17 GMT+02:00 Alina Kazi :
>
>
>
> https://github.com/apache/royale-asjs/pull/157
>
>
>
> for mx.core.EventPriority
>
>
>
> -Alina Kazi
>
>
>
> *From:* Alina Kazi [mailto:alina.k...@d-bz.com]
> *Sent:* Monday, April 09, 2018 4:45 PM
> *To:* users@royale.apache.org
> *Subject:* RE: Work on Emulation
>
>
>
> https://github.com/apache/royale-asjs/pull/156
>
> for IViewCursor and ICollectionView
>
>
>
> -Alina Kazi
>
> *From:* Alina Kazi [mailto:alina.k...@d-bz.com]
> *Sent:* Monday, April 09, 2018 3:55 PM
> *To:* users@royale.apache.org
> *Subject:* RE: Work on Emulation
>
>
>
> Please review and/or comment on the changes in pull request For
> SandboxMouseEvent and ResizeEvent
>
> https://github.com/apache/royale-asjs/pull/155
>
>
>
> Thanks in Advance J
>
> Alina Kazi
>
>
>
>
>
> *From:* Alina Kazi [mailto:alina.k...@d-bz.com]
> *Sent:* Monday, April 09, 2018 2:57 PM
> *To:* users@royale.apache.org
> *Subject:* RE: Work on Emulation
>
>
>
> Also review Pull Request for mx.effects.IEffectInstance and
> mx.events.EffectEvent
>
> https://github.com/apache/royale-asjs/pull/153
>
>
>
> Thanks in Advance J
>
> Alina Kazi
>
>
>
> *From:* Alina Kazi [mailto:alina.k...@d-bz.com]
> *Sent:* Monday, April 09, 2018 12:04 PM
> *To:* users@royale.apache.org
> *Subject:* RE: Work on Emulation
>
>
>
>
>
> Could Someone Please Review these Pull Requests
>
> https://github.com/apache/royale-asjs/pull/150
>
> https://github.com/apache/royale-asjs/pull/151
>
> https://github.com/apache/royale-asjs/pull/152
>
>
>
> Thanks in Advance J
>
> Alina Kazi
>
>
>
>
>
> *From:* Alina Kazi [mailto:alina.k...@d-bz.com]
> *Sent:* Monday, April 09, 2018 10:25 AM
> *To:* users@royale.apache.org
> *Subject:* RE: Work on Emulation
>
>
>
> Thanks Peter.
>
>
>
> *From:* Peter Ent [mailto:p...@adobe.com]
> *Sent:* Friday, April 06, 2018 7:59 PM
> *To:* users@royale.apache.org
> *Subject:* Re: Work on Emulation
>
>
>
> I merged these changes into the MXRoyale branch. They compiled cleanly.
>
>
>
> Great job!
>
> —peter
>
>
>
> *From: *Alina Kazi 
> *Reply-To: *"users@royale.apache.org" 
> *Date: *Friday, April 6, 2018 at 6:56 AM
> *To: *"users@royale.apache.org" , "
> d...@royale.apache.org" 
> *Subject: *RE: Work on Emulation
>
>
>
>
>
> Please Review :
>
> https://github.com/apache/royale-asjs/pull/145
> 
>
> https://github.com/apache/royale-asjs/pull/149
> 
>
>
>
> Thanks,
>
> Alina Kazi
>
>
>
> *From:* Alina Kazi [mailto:alina.k...@d-bz.com ]
> *Sent:* Friday, April 06, 2018 2:33 PM
> *To:* users@royale.apache.org
> *Subject:* RE: Work on Emulation
>
>
>
> Thanks Piotr.
>
>
>
> *From:* Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com
> ]
> *Sent:* Friday, April 06, 2018 12:32 PM
> *To:* users@royale.apache.org
> *Subject:* Re: Work on 

Re: MXRoyale build problem

[Carlos Rovira]

jewel branch was already merged, so since some days I'm not using it. I
didn't remove it totally, but I'll do in some days (maybe after 0.9.3
release)
Maybe for this reason you are a bit confused with that branch, since is now
deprecated and not synced.

I think my use of rebase is totally ok, so don't worry since I'm using it
since the beginning with MDL and now with Jewel, and branches are ok.

2018-04-10 9:21 GMT+02:00 Harbs :

> I suspect that Carlos is doing something different because the
> jewel-ui-set branch currently shows 22 commits ahead and 127 behind on my
> machine.
>
> Considering I made no local changes, I should not be *any* commits ahead.
> That would seem like origin has had its history modified which is not good.
> The only way I would be able to pull in the jewel branch would be to rebase
> locally...
>
> My $0.02,
> Harbs
>
> On Apr 10, 2018, at 7:52 AM, Alex Harui  wrote:
>
> Hi Carlos,
>
> Does that mean you are using "force push" when rebasing?  I don't use it
> when rebasing and lots of internet articles advise against using it.  If it
> is working for you, fine, but I wouldn't want any "forcing" to be a
> recommended practice for others given the advice I see out there.
>
> The key thing for any of us is to understand the differences between
> merging and rebasing and using them appropriately.  I don't want to take
> the time to go through it now, but the recommended practice AIUI, is to use
> merge for public branches and rebase when possible for non-public
> branches.  MXRoyale is a public branch.
>
> Thanks,
> -Alex
>
> From:  on behalf of Carlos Rovira <
> carlosrov...@apache.org>
> Reply-To: "users@royale.apache.org" 
> Date: Monday, April 9, 2018 at 3:01 PM
> To: "users@royale.apache.org" 
> Subject: Re: MXRoyale build problem
>
> Hi Alex,
>
> my problem as I started to use again was that I forgot to check "force
> push" completely. Without that you are not able to do a rebase, instead you
> end with a corrupt branch. That was my problem, and I finaly remember that
> I need to set up that. The way I use to rebase was teach to me by a
> recognized expert in Git use, and sometimes I use to ask him when I have
> doubts about how to do something. Rebase is completely a best practice in
> some scenarios, like the one I use, work in separate branch and rebase over
> develop, then merge to develop, since you end with a set of consecutive
> clean commits as if all that commits will be done in that point. No
> intricate tree object graphs and if some external person comes to see the
> graph will understand far better that something that is intrincated. Jewel
> branch was done in this way, and you can see that is very clean.
>
> said that (as well I understand now what Piotr said), I only want to
> express a way that is working for me, but if you all think is not good for
> you, it's ok, as I said is all subjective, and each one should use what he
> want (always that doesn't break anything , of course)
>
> Thanks
>
>
> 2018-04-09 19:05 GMT+02:00 Alex Harui :
>
>> Hi Carlos,
>>
>> Using "force push" sounds scary/wrong to me.  Note also that I had
>> trouble working with your branches and you reported similar problems.  The
>> general advice on the internet is to not rebase public branches, and I
>> think I've hit scenarios around that often enough to want to give up on
>> rebase when merging public branches.
>>
>> I always use rebase when pulling changes in from the branch I'm working
>> from.  That's where it makes sense to me.
>>
>> My 2 cents,
>> -Alex
>>
>> From:  on behalf of Carlos Rovira <
>> carlosrov...@apache.org>
>> Reply-To: "users@royale.apache.org" 
>> Date: Monday, April 9, 2018 at 9:46 AM
>>
>> To: "users@royale.apache.org" 
>> Subject: Re: MXRoyale build problem
>>
>> Hi,
>>
>> @Alex, the trick with rebase at least for me is that I must to have very
>> clear the steps to do or I can fail. For example, as I come again this
>> month to work on  Royale, I forget how to do that, and have to re-learn
>> all. For example in Sourcetree you must to set in preferences and option to
>> enable the "force push" or if you find conflicts, you must to solve and
>> recall do a "continue rebase" instead of commit the resolution of
>> conflicts. But in the end, for me always is worth it, since you ensure are
>> working against the latest develop changes and that's always good.
>>
>> @Piotr, sorry but I don't get the relationship between rebase and having
>> lots of branches, since for me is always about the relation between
>> "develop" and ", but maybe as I said is just something
>> subjective of how your brain deal with this kind of task, is the same as
>> when people choose and IDE, or a way of building (ant vs maven)
>>
>> In the end, for me Rebase makes the branches more 

Re: MXRoyale build problem

[Alex Harui]

Hah, you are correct about the version.  I just pushed changes for that
and a few other things.

Look in /royale/royale-asjs/target/rat.txt and see what is listed there.
Sometimes when a build fails, some files are left ound.  Those files
listed in rat.txt should not be under version control d thus can be
deleted.

HTH,
-Alex

On 4/9/18, 11:09 PM, "serkan@likyateknoloji.com"
 wrote:

>
>Hi Alex,
>
>When i chekck the pom.xml of MXRoyale on github, i see that the
>version is 0.9.2 is it normal ?
>
>And here is the output of mvn clean install of royale-asjs
>
>**
>
>
>hostname:~/royale/royale-asjs$ mvn clean install
>[WARNING] The POM for
>org.apache.flex.utilities.converter:flex-sdk-converter-maven-extension:jar
>:1.0.0-SNAPSHOT is missing, no dependency information
>available
>[WARNING] Failed to read extensions descriptor
>/royale/royale-asjs/.mvn/extensions.xml: Plugin
>org.apache.flex.utilities.converter:flex-sdk-converter-maven-extension:1.0
>.0-SNAPSHOT or one of its dependencies could not be resolved: Could not
>find artifact  
>org.apache.flex.utilities.converter:flex-sdk-converter-maven-extension:jar
>:1.0.0-SNAPSHOT
>[INFO] Scanning for projects...
>[INFO]  
>
>[INFO] Reactor Build Order:
>[INFO]
>[INFO] Apache Royale: Framework: Parent
>[pom]
>[INFO] Apache Royale: Framework
>[pom]
>[INFO] Apache Royale: Framework: Fonts
>[war]
>[INFO] Apache Royale: Framework: Libs
>[pom]
>[INFO] Apache Royale: Framework: Libs: Core
>[swc]
>[INFO] Apache Royale: Framework: Libs: Binding
>[swc]
>[INFO] Apache Royale: Framework: Libs: Collections
>[swc]
>[INFO] Apache Royale: Framework: Libs: Graphics
>[swc]
>[INFO] Apache Royale: Framework: Libs: Basic
>[swc]
>[INFO] Apache Royale: Framework: Libs: Charts
>[swc]
>[INFO] Apache Royale: Framework: Libs: Effects
>[swc]
>[INFO] Apache Royale: Framework: Libs: CreateJS
>[swc]
>[INFO] Apache Royale: Framework: Libs: DragDrop
>[swc]
>[INFO] Apache Royale: Framework: Libs: Express
>[swc]
>[INFO] Apache Royale: Framework: Libs: Flat
>[swc]
>[INFO] Apache Royale: Framework: Libs: Formatters
>[swc]
>[INFO] Apache Royale: Framework: Libs: FontAwesome
>[swc]
>[INFO] Apache Royale: Framework: Libs: GoogleMaps
>[swc]
>[INFO] Apache Royale: Framework: Libs: HTML
>[swc]
>[INFO] Apache Royale: Framework: Libs: HTML5
>[swc]
>[INFO] Apache Royale: Framework: Libs: JQuery
>[swc]
>[INFO] Apache Royale: Framework: Libs: Language
>[swc]
>[INFO] Apache Royale: Framework: Libs: Material Design Lite
>[swc]
>[INFO] Apache Royale: Framework: Libs: Mobile
>[swc]
>[INFO] Apache Royale: Framework: Libs: Reflection
>[swc]
>[INFO] Apache Royale: Framework: Libs: Network
>[swc]
>[INFO] Apache Royale: Framework: Libs: Storage
>[swc]
>[INFO] Apache Royale: Framework: Libs: XML
>[swc]
>[INFO] Apache Royale: Framework: Libs: Text
>[swc]
>[INFO] Apache Royale: Framework: Libs: TLF
>[swc]
>[INFO] Apache Royale: Framework: Libs: RoyaleSite
>[swc]
>[INFO] Apache Royale: Framework: Libs: MXRoyale
>[swc]
>[INFO] Apache Royale: Framework: Libs: Jewel
>[swc]
>[INFO] Apache Royale: Framework: Themes
>[pom]
>[INFO] Apache Royale: Framework: Themes: Basic
>[swc]
>[INFO] Apache Royale: Framework: Themes: JewelTheme
>[swc]
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Primary-Blue-Theme [swc]
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Secondary-Blue-Theme [swc]
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Emphasized-Blue-Theme [swc]
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Primary-Topaz-Theme [swc]
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Secondary-Topaz-Theme [swc]
>[INFO]pache Royale: Framework: Themes:
>Jewel-Light-NoFlat-Emphasized-Topaz-Tme [swc]
>[INFO] Apache Royale: Framework: Themes:
>Jewel-Light-Flat-Primary-Emerald-Theme [swc]
>[INFO] Apache Royale: Framework: Tmes:
>Jewel-Light-NoFlat-Secondary-Emerald-Theme [swc]
>[INFO] Apacheoyale: Framework: Themes:
>Jewel-Light-NoFlat-Emphasized-Emerald-Tme [swc]
>[INFO] Apache Royale: Framework: Archetypes
>[pom]
>[INF Apache Royale: Framework: Archetypes: Simple Royale Application
>[jar]
>[IO] Apache Royale: Framework: Archetypes: Simple Royale Pure-JS
>Applicaon [jar]
>[INFO] Apache Royale: Framework: Archetypes: Simple Royale PurSWF
>Application [jar]
>[INFO] Apache Royale: Framework: Archetype Simple Royale Library
>[maven-archetype]
>[INFO] Apache Royale: Framewo: Archetypes: Simple Royale Typedef
>Library [maven-archetype]
>[INF
>[INFO] < org.apache.royale.framework:royale-framework-parent
> >-
>[INFO] Building Apache Royale: Framework: Parent 0.9.3-SNAPSHOT
>   [1/51]
>[INFO] 

RE: Work on Emulation

[Alina Kazi]

Hi Carlos,

How can I add my Pull Request to Emulation Components ?

and How can i change the status 

https://github.com/apache/royale-asjs/projects/4

To do -> In progress ->Done

 

Thanks,

Alina Kazi

From: carlos.rov...@gmail.com [mailto:carlos.rov...@gmail.com] On Behalf Of 
Carlos Rovira
Sent: Monday, April 09, 2018 7:06 PM
To: users@royale.apache.org
Subject: Re: Work on Emulation

 

Hi Alina,

 

I added some of your PRs to new project "Emulation Components", please if you 
create new add to this project so the tickets can be handler automatically.

As well if you can configure for new (and old issues) the info in the right 
sidebar of GitHub, that would be of much help to better organize the effort

 

thanks :)

 

 

 

2018-04-09 14:17 GMT+02:00 Alina Kazi :

 

https://github.com/apache/royale-asjs/pull/157

 

for mx.core.EventPriority

 

-Alina Kazi

 

From: Alina Kazi [mailto:alina.k...@d-bz.com] 
Sent: Monday, April 09, 2018 4:45 PM
To: users@royale.apache.org
Subject: RE: Work on Emulation

 

https://github.com/apache/royale-asjs/pull/156

for IViewCursor and ICollectionView 

 

-Alina Kazi

From: Alina Kazi [mailto:alina.k...@d-bz.com] 
Sent: Monday, April 09, 2018 3:55 PM
To: users@royale.apache.org
Subject: RE: Work on Emulation

 

Please review and/or comment on the changes in pull request For 
SandboxMouseEvent and ResizeEvent

https://github.com/apache/royale-asjs/pull/155

 

Thanks in Advance J

Alina Kazi

 

 

From: Alina Kazi [mailto:alina.k...@d-bz.com] 
Sent: Monday, April 09, 2018 2:57 PM
To: users@royale.apache.org
Subject: RE: Work on Emulation

 

Also review Pull Request for mx.effects.IEffectInstance and 
mx.events.EffectEvent

https://github.com/apache/royale-asjs/pull/153

 

Thanks in Advance J

Alina Kazi

 

From: Alina Kazi [mailto:alina.k...@d-bz.com] 
Sent: Monday, April 09, 2018 12:04 PM
To: users@royale.apache.org
Subject: RE: Work on Emulation

 

 

Could Someone Please Review these Pull Requests

https://github.com/apache/royale-asjs/pull/150

https://github.com/apache/royale-asjs/pull/151

https://github.com/apache/royale-asjs/pull/152

 

Thanks in Advance J

Alina Kazi

 

 

From: Alina Kazi [mailto:alina.k...@d-bz.com] 
Sent: Monday, April 09, 2018 10:25 AM
To: users@royale.apache.org
Subject: RE: Work on Emulation

 

Thanks Peter.

 

From: Peter Ent [mailto:p...@adobe.com] 
Sent: Friday, April 06, 2018 7:59 PM
To: users@royale.apache.org
Subject: Re: Work on Emulation

 

I merged these changes into the MXRoyale branch. They compiled cleanly.

 

Great job!

—peter

 

From: Alina Kazi 
Reply-To: "users@royale.apache.org" 
Date: Friday, April 6, 2018 at 6:56 AM
To: "users@royale.apache.org" , 
"d...@royale.apache.org" 
Subject: RE: Work on Emulation

 

 

Please Review : 

https://github.com/apache/royale-asjs/pull/145 

 

https://github.com/apache/royale-asjs/pull/149 

 

 

Thanks,

Alina Kazi

 

From: Alina Kazi [mailto:alina.k...@d-bz.com] 
Sent: Friday, April 06, 2018 2:33 PM
To: users@royale.apache.org
Subject: RE: Work on Emulation

 

Thanks Piotr.

 

From: Piotr Zarzycki [mailto:piotrzarzyck...@gmail.com] 
Sent: Friday, April 06, 2018 12:32 PM
To: users@royale.apache.org
Subject: Re: Work on Emulation

 

Hi Alina,

 

One suggestion to the reporting in [1] - Could you please bold "in progress" 
status ? I just did for you now, but in the next which you will work please do 
so. It's much better visible. 

 

[1] https://github.com/apache/royale-asjs/issues/136 

 

 

Thanks,

Piotr

 

2018-04-06 9:28 GMT+02:00 Alina Kazi :

Currently I am working on mx.collections.Sort and mx.collections.SortField from 
list.
Dependencies Added :
mx.collections.errors.SortError , mx.collections.ISort and 
mx.collections.ISortField are emulated as these API's were used in 
mx.collections.Sort and mx.collections.SortField.

Dependencies Commented :
mx.resources.IResourceManager and mx.resources.ResourceManager
What are the alternative API's for
import 

Re: MXRoyale build problem

[serkan . tas]

Hi Alex,

When i chekck the pom.xml of MXRoyale on github, i see that the  
version is 0.9.2 is it normal ?


And here is the output of mvn clean install of royale-asjs

**

hostname:~/royale/royale-asjs$ mvn clean install
[WARNING] The POM for  
org.apache.flex.utilities.converter:flex-sdk-converter-maven-extension:jar:1.0.0-SNAPSHOT is missing, no dependency information  
available
[WARNING] Failed to read extensions descriptor  
/royale/royale-asjs/.mvn/extensions.xml: Plugin  
org.apache.flex.utilities.converter:flex-sdk-converter-maven-extension:1.0.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact  
org.apache.flex.utilities.converter:flex-sdk-converter-maven-extension:jar:1.0.0-SNAPSHOT

[INFO] Scanning for projects...
[INFO]  


[INFO] Reactor Build Order:
[INFO]
[INFO] Apache Royale: Framework: Parent 
   [pom]
[INFO] Apache Royale: Framework 
   [pom]
[INFO] Apache Royale: Framework: Fonts  
   [war]
[INFO] Apache Royale: Framework: Libs   
   [pom]
[INFO] Apache Royale: Framework: Libs: Core 
   [swc]
[INFO] Apache Royale: Framework: Libs: Binding  
   [swc]
[INFO] Apache Royale: Framework: Libs: Collections  
   [swc]
[INFO] Apache Royale: Framework: Libs: Graphics 
   [swc]
[INFO] Apache Royale: Framework: Libs: Basic
   [swc]
[INFO] Apache Royale: Framework: Libs: Charts   
   [swc]
[INFO] Apache Royale: Framework: Libs: Effects  
   [swc]
[INFO] Apache Royale: Framework: Libs: CreateJS 
   [swc]
[INFO] Apache Royale: Framework: Libs: DragDrop 
   [swc]
[INFO] Apache Royale: Framework: Libs: Express  
   [swc]
[INFO] Apache Royale: Framework: Libs: Flat 
   [swc]
[INFO] Apache Royale: Framework: Libs: Formatters   
   [swc]
[INFO] Apache Royale: Framework: Libs: FontAwesome  
   [swc]
[INFO] Apache Royale: Framework: Libs: GoogleMaps   
   [swc]
[INFO] Apache Royale: Framework: Libs: HTML 
   [swc]
[INFO] Apache Royale: Framework: Libs: HTML5
   [swc]
[INFO] Apache Royale: Framework: Libs: JQuery   
   [swc]
[INFO] Apache Royale: Framework: Libs: Language 
   [swc]
[INFO] Apache Royale: Framework: Libs: Material Design Lite 
   [swc]
[INFO] Apache Royale: Framework: Libs: Mobile   
   [swc]
[INFO] Apache Royale: Framework: Libs: Reflection   
   [swc]
[INFO] Apache Royale: Framework: Libs: Network  
   [swc]
[INFO] Apache Royale: Framework: Libs: Storage  
   [swc]
[INFO] Apache Royale: Framework: Libs: XML  
   [swc]
[INFO] Apache Royale: Framework: Libs: Text 
   [swc]
[INFO] Apache Royale: Framework: Libs: TLF  
   [swc]
[INFO] Apache Royale: Framework: Libs: RoyaleSite   
   [swc]
[INFO] Apache Royale: Framework: Libs: MXRoyale 
   [swc]
[INFO] Apache Royale: Framework: Libs: Jewel
   [swc]
[INFO] Apache Royale: Framework: Themes 
   [pom]
[INFO] Apache Royale: Framework: Themes: Basic  
   [swc]
[INFO] Apache Royale: Framework: Themes: JewelTheme 
   [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Primary-Blue-Theme [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Secondary-Blue-Theme [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Emphasized-Blue-Theme [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Primary-Topaz-Theme [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Secondary-Topaz-Theme [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Emphasized-Topaz-Theme [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Primary-Emerald-Theme [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Secondary-Emerald-Theme [swc]
[INFO] Apache Royale: Framework: Themes:  
Jewel-Light-NoFlat-Emphasized-Emerald-Theme [swc]
[INFO] Apache Royale: Framework: Archetypes 
   [pom]
[INFO] Apache Royale: Framework: Archetypes: Simple Royale Application  
   [jar]
[INFO] Apache Royale: Framework: Archetypes: Simple Royale Pure-JS  
Application [jar]