Re: Website help doc links not working

[Berty Tonta]

all links below "High Level View" not working


​

*Berty Tonta*
Sales Enablement Specialist


4 BENGALI STREET, BEAU BASSIN, MAURITIUS
T +230 57 43 81 34 | berty.to...@leadstalk.pro | WWW.LEADSTALK.PRO
BRN 17149323

On Fri, Feb 16, 2018 at 7:19 AM, Alex Harui 
wrote:

> What do you mean by "links not working".  I went to the [1], clicked on
> "High Level View" and ended up on a new page.
>
> -Alex
>
> On 2/15/18, 5:02 PM, "Andrew Wetmore"  wrote:
>
> >Almost all of the links on the help docs page [1] are not working.
> >
> >More than that, I am afraid that the pattern I thought was correct for
> >linking from one page to another is not working; however, since I can't
> >get
> >past the first page I can't check.
> >
> >[1]
> >https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fapache.gi
> >thub.io%2Froyale-docs%2F=02%7C01%7Caharui%40adobe.com
> %7C8196919a76e24
> >168278c08d574d8f20d%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636543397
> >479499116=MBzKg394LAJnmI436RNnHhj%2B13txLCjQ0WwmHcTlgPw%3D&
> reserved=
> >0
> >
> >
> >--
> >Andrew Wetmore
> >
> >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14
> .
> >blogspot.com%2F=02%7C01%7Caharui%40adobe.com%
> 7C8196919a76e24168278c08
> >d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636543397479499116
> >=dQZk%2Fci12V3lRl7VKbkSL965flWhdHg6ZiFS%2FkXmDEI%3D=0
>
>

Re: Website help doc links not working

[Alex Harui]

What do you mean by "links not working".  I went to the [1], clicked on
"High Level View" and ended up on a new page.

-Alex

On 2/15/18, 5:02 PM, "Andrew Wetmore"  wrote:

>Almost all of the links on the help docs page [1] are not working.
>
>More than that, I am afraid that the pattern I thought was correct for
>linking from one page to another is not working; however, since I can't
>get
>past the first page I can't check.
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache.gi
>thub.io%2Froyale-docs%2F=02%7C01%7Caharui%40adobe.com%7C8196919a76e24
>168278c08d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636543397
>479499116=MBzKg394LAJnmI436RNnHhj%2B13txLCjQ0WwmHcTlgPw%3D=
>0
>
>
>-- 
>Andrew Wetmore
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14.
>blogspot.com%2F=02%7C01%7Caharui%40adobe.com%7C8196919a76e24168278c08
>d574d8f20d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636543397479499116
>=dQZk%2Fci12V3lRl7VKbkSL965flWhdHg6ZiFS%2FkXmDEI%3D=0

[GitHub] cottage14 closed pull request #6: Develop

[GitBox]

cottage14 closed pull request #6: Develop
URL: https://github.com/apache/royale-docs/pull/6
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] cottage14 opened a new pull request #6: Develop

[GitBox]

cottage14 opened a new pull request #6: Develop
URL: https://github.com/apache/royale-docs/pull/6
 
 
   Fixing some text issues and added a page about Royale CLI


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Website help doc links not working

[Andrew Wetmore]

Almost all of the links on the help docs page [1] are not working.

More than that, I am afraid that the pattern I thought was correct for
linking from one page to another is not working; however, since I can't get
past the first page I can't check.

[1] https://apache.github.io/royale-docs/


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: ArrayCollection in Royale

[Carlos Rovira]

Hi Alex,

I only expose what I think is better for the project. The same I said for
AMF and RemoteObject.
If you check today to Royale in twitter, many people asked if we have
AMF/RemoteObject support.
So as I mentioned, that is key for many people out there. Now thanks to
past effort, I can respond in twitter
"Hey! Yes we implemented that! Come on check it yourself".

With ArrayCollection, I'm telling you all what I think about it. You can
said that's not your task, or that is not
something needed. This is all subjective. My point is that ArrayCollection
will make Royale more successful
since people starting to work with Royale, soon will need it, or they will
end saying "...no ArrayCollection? oooh..."
And will see that they must change all their client communication layer.
Something  doable, but maybe we can make
this less painful for them.

About making AC myself, I thinkI'm not the right person for that task. I
agree with you that not all components should be
done by Adobe people, but I think that's not the point now. We want Royale
to be a successfull project, I doesn't mind
how task are assigned. I'm more in the UX-front end with website, look and
feel, and if have time I'd like to collaborate with
docs and reference. If I stop the rest of things to start working on AC, I
think this not would be the best decision, since is not
where I can make my best work. Honestly.

As I already said, for me the first point is to have AC, then how is
internally implemented is less important since smart people here
can end evolving the internals to make it work blazing fast, I'm sure of
that. But name and api can remain constant.

Just my 2





2018-02-15 20:46 GMT+01:00 Alex Harui :

> Hi Carlos,
>
> Looking at the screenshot Alina shared, plus some past discussion, lots of
> folks just used the default skins.  I don't think they care too much if
> the Royale skin looks like Spark or not, but those who disagree should
> speak up now.
>
> s:Button has over 100 APIs. Many of which are inherited from Flash Sprite.
>  It would take us a long time to replicate everything.  On the other hand,
> many folks use s:Button in mxml with only a few attributes, and a bunch
> more also reference it in their code to dynamically manage the UI.
>
> ArrayCollection may or may not be that different from s:Button.  I've
> definitely seen ArrayCollection used in fx:Declaration blocks in MXML.
> Seems like a simple search and replace should also work here.  If that's
> too risky, then it is time to find a volunteer to mimic these classes
> using the same package name.  But in theory, 99% of your business logic
> shouldn't be working off of ResultEvent handlers.  The handler should be
> calling some entry point in your business logic.
>
> The key points here is, as I mentioned in the other thread, expectations
> and time.  You want an org.apache.royale.collections.ArrayCollection?  Go
> build it.  Don't wait for me or Peter.  We need to change the mindset that
> the components are being created by Adobe.  They need to be created by
> everybody.  You don't even need agreement from others.  We've proven that
> the tool chain can handle different component sets.  Create a component
> set or two that reduces the number of lines you have to change when
> migrating.
>
> On the technical issue:  In order for ArrayCollection to support array
> access in Flash (myAC[0]) ArrayCollection extends Proxy.  Array accesses
> call a function that has to do a string to int and then access the
> internal array.  It is much slower than getItemAt.  I have implemented
> Proxy in JavaScript.  It has to make the same slow function call.  There
> are alternative implementations available for JavaScript if you make
> certain assumptions.  For example, if there won't be add/remove on the
> ArrayCollection, you could prepopulate the index properties on the
> instance.  Might not be fast for 10,000 rows at conversion time, but
> access afterwards would be faster than getItemAt.  And there are options
> in-between where for add/remove you take the time to repopulate the index
> properties.
>
> That is another reason in Royale we have beads and multiple component
> sets.  We don't have to choose just one implementation.  There might be a
> "ReallyFastArrayCollectionForImmutableArrays".  And so on.
>
> My 2 cents,
> -Alex
>
> On 2/15/18, 1:44 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi Alex,
> >
> >I assume that UX is very different and although we have a "s:Button" lots
> >of changes must be done, so in the end, I think people must rewrite UX.
> >But AS3 classes are almost the same (lots of vars type String, Number,
> >int,
> >Boolean,and ArrayCollection). In this point, it will be a shame to
> >make
> >people to go each file making changes to get ArrayCollections to match
> >other classes methods and signatures...
> >
> >In the other hand, 

Re: ArrayCollection in Royale

[Alex Harui]

Hi Carlos,

Looking at the screenshot Alina shared, plus some past discussion, lots of
folks just used the default skins.  I don't think they care too much if
the Royale skin looks like Spark or not, but those who disagree should
speak up now.

s:Button has over 100 APIs. Many of which are inherited from Flash Sprite.
 It would take us a long time to replicate everything.  On the other hand,
many folks use s:Button in mxml with only a few attributes, and a bunch
more also reference it in their code to dynamically manage the UI.

ArrayCollection may or may not be that different from s:Button.  I've
definitely seen ArrayCollection used in fx:Declaration blocks in MXML.
Seems like a simple search and replace should also work here.  If that's
too risky, then it is time to find a volunteer to mimic these classes
using the same package name.  But in theory, 99% of your business logic
shouldn't be working off of ResultEvent handlers.  The handler should be
calling some entry point in your business logic.

The key points here is, as I mentioned in the other thread, expectations
and time.  You want an org.apache.royale.collections.ArrayCollection?  Go
build it.  Don't wait for me or Peter.  We need to change the mindset that
the components are being created by Adobe.  They need to be created by
everybody.  You don't even need agreement from others.  We've proven that
the tool chain can handle different component sets.  Create a component
set or two that reduces the number of lines you have to change when
migrating. 

On the technical issue:  In order for ArrayCollection to support array
access in Flash (myAC[0]) ArrayCollection extends Proxy.  Array accesses
call a function that has to do a string to int and then access the
internal array.  It is much slower than getItemAt.  I have implemented
Proxy in JavaScript.  It has to make the same slow function call.  There
are alternative implementations available for JavaScript if you make
certain assumptions.  For example, if there won't be add/remove on the
ArrayCollection, you could prepopulate the index properties on the
instance.  Might not be fast for 10,000 rows at conversion time, but
access afterwards would be faster than getItemAt.  And there are options
in-between where for add/remove you take the time to repopulate the index
properties.

That is another reason in Royale we have beads and multiple component
sets.  We don't have to choose just one implementation.  There might be a
"ReallyFastArrayCollectionForImmutableArrays".  And so on.

My 2 cents,
-Alex

On 2/15/18, 1:44 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>I assume that UX is very different and although we have a "s:Button" lots
>of changes must be done, so in the end, I think people must rewrite UX.
>But AS3 classes are almost the same (lots of vars type String, Number,
>int,
>Boolean,and ArrayCollection). In this point, it will be a shame to
>make
>people to go each file making changes to get ArrayCollections to match
>other classes methods and signatures...
>
>In the other hand, about internals of how ArrayCollection operates, I
>think
>that can be reworked in order to perform better, right?
>
>
>
>2018-02-15 9:20 GMT+01:00 Alex Harui :
>
>> If the goal is to further reduce the number of changes to migrated code,
>> we should just start a new component set.  IIRC, ArrayCollection usually
>> has very bad performance if you use array indexing to access it.
>> ArrayList should perform much better but you can't use array indexing.
>> Filtering and sorting should be written as beads.
>>
>> My 2 cents,
>> -Alex
>>
>> On 2/15/18, 12:11 AM, "Piotr Zarzycki" 
>>wrote:
>>
>> >Hi Carlos,
>> >
>> >We have ArrayList which is enough close to ArrayCollection. I have with
>> >success replace ArrayCollection to ArrayList in my examples.
>> >
>> >Thanks, Piotr
>> >
>> >2018-02-15 8:47 GMT+01:00 Carlos Rovira :
>> >
>> >> Hi
>> >>
>> >> I saw Alina post in user list about substitutes and I think one
>> >>important
>> >> one is:
>> >>
>> >> import mx.collections.ArrayCollection; //very similar to
>> >> org.apache.royale.collections.TreeData
>> >>
>> >> In order to ease the port of Flex apps to Royale, one thing we try
>>is to
>> >> reuse as much AS3 logic, while in UX we need to create all new code
>> >>
>> >> ArrayCollection is very close to business logic, and widely used in
>>AMF
>> >> calls.
>> >>
>> >> I suggest we should have ArrayCollection in Royale and even respect
>> >> namespace to avoid users to change any line in AS3 code.
>> >>
>> >> Only with this point we can remove lots of pain in migration process
>> >>from
>> >> Flex to Royale
>> >>
>> >> what do you think?
>> >>
>> >> --
>> >> Carlos Rovira
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fabout.me%
>> 

Re: Introducing Royale CLI tool

[OmPrakash Muppirala]

On Feb 15, 2018 7:15 AM, "Andrew Wetmore"  wrote:

I have added a page in the help docs describing this cool tool.



Thanks for taking care of that.

Sorry - like a typical developer, I started writing documentation but ended
up writing a tool 


On Thu, Feb 15, 2018 at 10:30 AM, Andrew Wetmore 
wrote:

> Very good idea!
>
> On Thu, Feb 15, 2018 at 5:46 AM, Carlos Rovira 
> wrote:
>
>> So cool Om! Great!
>> I'm very busy right now with lots of fronts, but let me know if you need
>> help from me in order to create the blog post.
>> You can contact me offline in order to support in this task as much as
you
>> can
>> thanks for making this!
>>
>> 2018-02-15 10:20 GMT+01:00 Gabe Harbs :
>>
>> > Very cool! Great initiative!
>> >
>> > I’ll try to give it a spin later.
>> >
>> > Is there a way of creating different templates for the “new” command?
>> >
>> > BTW, it would be really great to try to stick to dog-fooding to have as
>> > many samples of Royale use as possible.
>> >
>> > This tool can be written in ActionScript and compiled for node.js using
>> > Royale.
>> >
>> > Harbs
>> >
>> > > On Feb 15, 2018, at 10:16 AM, OmPrakash Muppirala 
>> > wrote:
>> > >
>> > > As I was trying to write a `Setting up Royale with npm `blog post, I
>> > > realized that things could be much easier for npm users.  So, I built
>> the
>> > > Royale CLI tool.  It takes inspiration from the create-react-app and
>> the
>> > > angular cli projects.
>> > >
>> > > Here are the details:
>> > >
>> > > *To Install: *
>> > > npm install @apache-royale/royale-js -g
>> > > npm install @apache-royale/cli -g
>> > >
>> > > After installation:
>> > >
>> > > *Help *
>> > > royale help
>> > >
>> > > *Setup *
>> > > royale new  my-royale-app
>> > > cd my-royale-app
>> > >
>> > > This creates a simple app: my-royale-app/src/Main.mxml
>> > >
>> > >
>> > > *Run in debug mode *
>> > > royale serve:debug
>> > >
>> > > Compiles the project in debug mode
>> > > Compiles with source map option
>> > > Starts a http server and serves the files from the bin/js-debug
>> directory
>> > > Opens the default browser and navigates to http://localhost:3000
>> > > Listens to src folder
>> > > When any file changes, it will recompile the app
>> > > Automatically reloads the browser to show the updated application
>> > >
>> > > *Run in release mode *
>> > > royale serve:release
>> > >
>> > > Compiles the project in release mode
>> > > Starts a http server and serves the files from the bin/js-release
>> > > directory
>> > > Opens the default browser and navigates to http://localhost:3001
>> > >
>> > >
>> > > Please test and provide feedback.  It would be greatly appreciated.
>> > >
>> > > Thanks,
>> > > Om
>> >
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>


--
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Introducing Royale CLI tool

[OmPrakash Muppirala]

On Feb 15, 2018 1:47 AM, "Carlos Rovira"  wrote:

So cool Om! Great!
I'm very busy right now with lots of fronts, but let me know if you need
help from me in order to create the blog post.
You can contact me offline in order to support in this task as much as you
can
thanks for making this!


Yes, that is what I plan on doing next.

Thanks,
Om


2018-02-15 10:20 GMT+01:00 Gabe Harbs :

> Very cool! Great initiative!
>
> I’ll try to give it a spin later.
>
> Is there a way of creating different templates for the “new” command?
>
> BTW, it would be really great to try to stick to dog-fooding to have as
> many samples of Royale use as possible.
>
> This tool can be written in ActionScript and compiled for node.js using
> Royale.
>
> Harbs
>
> > On Feb 15, 2018, at 10:16 AM, OmPrakash Muppirala 
> wrote:
> >
> > As I was trying to write a `Setting up Royale with npm `blog post, I
> > realized that things could be much easier for npm users.  So, I built
the
> > Royale CLI tool.  It takes inspiration from the create-react-app and the
> > angular cli projects.
> >
> > Here are the details:
> >
> > *To Install: *
> > npm install @apache-royale/royale-js -g
> > npm install @apache-royale/cli -g
> >
> > After installation:
> >
> > *Help *
> > royale help
> >
> > *Setup *
> > royale new  my-royale-app
> > cd my-royale-app
> >
> > This creates a simple app: my-royale-app/src/Main.mxml
> >
> >
> > *Run in debug mode *
> > royale serve:debug
> >
> > Compiles the project in debug mode
> > Compiles with source map option
> > Starts a http server and serves the files from the bin/js-debug
directory
> > Opens the default browser and navigates to http://localhost:3000
> > Listens to src folder
> > When any file changes, it will recompile the app
> > Automatically reloads the browser to show the updated application
> >
> > *Run in release mode *
> > royale serve:release
> >
> > Compiles the project in release mode
> > Starts a http server and serves the files from the bin/js-release
> > directory
> > Opens the default browser and navigates to http://localhost:3001
> >
> >
> > Please test and provide feedback.  It would be greatly appreciated.
> >
> > Thanks,
> > Om
>
>


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

Re: Introducing Royale CLI tool

[OmPrakash Muppirala]

On Feb 15, 2018 1:20 AM, "Gabe Harbs"  wrote:

Very cool! Great initiative!

I’ll try to give it a spin later.

Is there a way of creating different templates for the “new” command?


Sure,  it's possible.  There is a template directory that gets shipped with
the cli tool.  We could add more starter apps and let user select one of
them with a switch.

The other option is to directly download an app from a github repo.



BTW, it would be really great to try to stick to dog-fooding to have as
many samples of Royale use as possible.

This tool can be written in ActionScript and compiled for node.js using
Royale.


That has been on my to do list.  Others are welcome to start porting these
node/npm related scripts to AS.

Thanks,
Om


Harbs

> On Feb 15, 2018, at 10:16 AM, OmPrakash Muppirala 
wrote:
>
> As I was trying to write a `Setting up Royale with npm `blog post, I
> realized that things could be much easier for npm users.  So, I built the
> Royale CLI tool.  It takes inspiration from the create-react-app and the
> angular cli projects.
>
> Here are the details:
>
> *To Install: *
> npm install @apache-royale/royale-js -g
> npm install @apache-royale/cli -g
>
> After installation:
>
> *Help *
> royale help
>
> *Setup *
> royale new  my-royale-app
> cd my-royale-app
>
> This creates a simple app: my-royale-app/src/Main.mxml
>
>
> *Run in debug mode *
> royale serve:debug
>
> Compiles the project in debug mode
> Compiles with source map option
> Starts a http server and serves the files from the bin/js-debug directory
> Opens the default browser and navigates to http://localhost:3000
> Listens to src folder
> When any file changes, it will recompile the app
> Automatically reloads the browser to show the updated application
>
> *Run in release mode *
> royale serve:release
>
> Compiles the project in release mode
> Starts a http server and serves the files from the bin/js-release
> directory
> Opens the default browser and navigates to http://localhost:3001
>
>
> Please test and provide feedback.  It would be greatly appreciated.
>
> Thanks,
> Om

Re: Introducing Royale CLI tool

[Andrew Wetmore]

I have added a page in the help docs describing this cool tool.

On Thu, Feb 15, 2018 at 10:30 AM, Andrew Wetmore 
wrote:

> Very good idea!
>
> On Thu, Feb 15, 2018 at 5:46 AM, Carlos Rovira 
> wrote:
>
>> So cool Om! Great!
>> I'm very busy right now with lots of fronts, but let me know if you need
>> help from me in order to create the blog post.
>> You can contact me offline in order to support in this task as much as you
>> can
>> thanks for making this!
>>
>> 2018-02-15 10:20 GMT+01:00 Gabe Harbs :
>>
>> > Very cool! Great initiative!
>> >
>> > I’ll try to give it a spin later.
>> >
>> > Is there a way of creating different templates for the “new” command?
>> >
>> > BTW, it would be really great to try to stick to dog-fooding to have as
>> > many samples of Royale use as possible.
>> >
>> > This tool can be written in ActionScript and compiled for node.js using
>> > Royale.
>> >
>> > Harbs
>> >
>> > > On Feb 15, 2018, at 10:16 AM, OmPrakash Muppirala 
>> > wrote:
>> > >
>> > > As I was trying to write a `Setting up Royale with npm `blog post, I
>> > > realized that things could be much easier for npm users.  So, I built
>> the
>> > > Royale CLI tool.  It takes inspiration from the create-react-app and
>> the
>> > > angular cli projects.
>> > >
>> > > Here are the details:
>> > >
>> > > *To Install: *
>> > > npm install @apache-royale/royale-js -g
>> > > npm install @apache-royale/cli -g
>> > >
>> > > After installation:
>> > >
>> > > *Help *
>> > > royale help
>> > >
>> > > *Setup *
>> > > royale new  my-royale-app
>> > > cd my-royale-app
>> > >
>> > > This creates a simple app: my-royale-app/src/Main.mxml
>> > >
>> > >
>> > > *Run in debug mode *
>> > > royale serve:debug
>> > >
>> > > Compiles the project in debug mode
>> > > Compiles with source map option
>> > > Starts a http server and serves the files from the bin/js-debug
>> directory
>> > > Opens the default browser and navigates to http://localhost:3000
>> > > Listens to src folder
>> > > When any file changes, it will recompile the app
>> > > Automatically reloads the browser to show the updated application
>> > >
>> > > *Run in release mode *
>> > > royale serve:release
>> > >
>> > > Compiles the project in release mode
>> > > Starts a http server and serves the files from the bin/js-release
>> > > directory
>> > > Opens the default browser and navigates to http://localhost:3001
>> > >
>> > >
>> > > Please test and provide feedback.  It would be greatly appreciated.
>> > >
>> > > Thanks,
>> > > Om
>> >
>> >
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>
>
>
>
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Introducing Royale CLI tool

[Andrew Wetmore]

Very good idea!

On Thu, Feb 15, 2018 at 5:46 AM, Carlos Rovira 
wrote:

> So cool Om! Great!
> I'm very busy right now with lots of fronts, but let me know if you need
> help from me in order to create the blog post.
> You can contact me offline in order to support in this task as much as you
> can
> thanks for making this!
>
> 2018-02-15 10:20 GMT+01:00 Gabe Harbs :
>
> > Very cool! Great initiative!
> >
> > I’ll try to give it a spin later.
> >
> > Is there a way of creating different templates for the “new” command?
> >
> > BTW, it would be really great to try to stick to dog-fooding to have as
> > many samples of Royale use as possible.
> >
> > This tool can be written in ActionScript and compiled for node.js using
> > Royale.
> >
> > Harbs
> >
> > > On Feb 15, 2018, at 10:16 AM, OmPrakash Muppirala 
> > wrote:
> > >
> > > As I was trying to write a `Setting up Royale with npm `blog post, I
> > > realized that things could be much easier for npm users.  So, I built
> the
> > > Royale CLI tool.  It takes inspiration from the create-react-app and
> the
> > > angular cli projects.
> > >
> > > Here are the details:
> > >
> > > *To Install: *
> > > npm install @apache-royale/royale-js -g
> > > npm install @apache-royale/cli -g
> > >
> > > After installation:
> > >
> > > *Help *
> > > royale help
> > >
> > > *Setup *
> > > royale new  my-royale-app
> > > cd my-royale-app
> > >
> > > This creates a simple app: my-royale-app/src/Main.mxml
> > >
> > >
> > > *Run in debug mode *
> > > royale serve:debug
> > >
> > > Compiles the project in debug mode
> > > Compiles with source map option
> > > Starts a http server and serves the files from the bin/js-debug
> directory
> > > Opens the default browser and navigates to http://localhost:3000
> > > Listens to src folder
> > > When any file changes, it will recompile the app
> > > Automatically reloads the browser to show the updated application
> > >
> > > *Run in release mode *
> > > royale serve:release
> > >
> > > Compiles the project in release mode
> > > Starts a http server and serves the files from the bin/js-release
> > > directory
> > > Opens the default browser and navigates to http://localhost:3001
> > >
> > >
> > > Please test and provide feedback.  It would be greatly appreciated.
> > >
> > > Thanks,
> > > Om
> >
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Royale substitutes for Flex features

[Andrew Wetmore]

I think a Royale user would not bless us if we shrugged them off with
"check ASDoc". I, for one, only find ASDoc useful if I already know what I
want and basically need a syntax reminder. If there is tutorial-grade
material in there, we should give it greater visibility.

I think the "Flex equivalents" page in the help docs does not have to be
comprehensive, but should address issues about which we are getting
questions. In that line, I think we should have material there on topics
that have recently been in discussion:

- PopUpManager
- BorderContainer
- Advanced DataGrid
- Remote Object (?)

PMC members for Royale are the most knowledgeable meat minds on the planet
about what Royale can do. What are other non-obscure things that a Flex
user would reach for, and not find, when trying to create an app in Royale?

a



On Tue, Feb 6, 2018 at 3:29 PM, Alex Harui  wrote:

> I wouldn't link to ASDoc, but if we have a reverse-search feature, explain
> in the main docs how to use it.
>
> I think your suggestions for royale-docs is fine.  The advantage of having
> it all in ASDoc is the committer working on the component doesn't have to
> go to another repo to document it, but discoverability is probably more
> important.
>
> -Alex
>
> On 2/6/18, 10:26 AM, "Andrew Wetmore"  wrote:
>
> >We have created a placeholder in the documentation for migrating an
> >existing project from Flex to Royale. That is where I would look for such
> >help. Would you suggest that we add links from there to the ASDoc? That
> >seems a little awkward to me.
> >
> >For me, holding an existing Flex application, it would be lovely to be
> >able
> >to look in the help docs and see quickly:
> >
> >== This stuff maps to Royale stuff
> >== You can do this in Royale by following these steps (popups, Canvas,
> >title windows...)
> >== Royale will have these things, but does not yet (menu bar...)
> >== Royale will not have these things so you need to go about them in a
> >different way or forget about them (virtual renderers).
> >
> >This would be an exercise in capturing the tribal knowledge of the Royale
> >development team and making some of it available to the Alinas out there
> >who are hovering on the edge of Royale.
> >
> >Opinions?
> >
> >
> >
> >On Tue, Feb 6, 2018 at 2:05 PM, Alex Harui 
> >wrote:
> >
> >> I don't think we have a list.  Some components are just missing (no
> >> Menu/MenuBar).  Some components are missing things (locked rows/columns,
> >> virtual renderers).  I don't really know how to manage such a list.  The
> >> Spark Button has over 100 public APIs.  Tracking all of that would be
> >> daunting.
> >>
> >> Some stuff may never happen (weak references).
> >>
> >> Some other stuff like PopUpManager can often just be done differently.
> >> Although if there is enough demand, we might create shims to ease
> >> migration pain.  I know people would love it if Royale eventually had
> >>1:1
> >> parity with Flex, but that will take quite a while and I'm just not sure
> >> it is worth it.  We have a different pattern under-the-hood in Royale in
> >> order to best ensure performance in production.  IMO, it would be a
> >> mistake to make the port compilation easy but have the results not
> >>perform
> >> well enough.  We've opted for requiring a bit more work in porting code
> >>in
> >> order to try to ensure adequate performance in production.
> >>
> >> So, from Alina's emails today, some documentation around popups is
> >>needed.
> >>  We've seen that question several times already  Maybe a FAQ?  We've
> >>added
> >> some ASDoc tags in the Royale classes (@flexdocurl and @flexcomponent
> >>that
> >> could be added to a few more components that indicate what they can
> >> replace from Flex.  But there isn't a reverse search.  A volunteer could
> >> add that to the ASDoc app though.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 2/6/18, 9:26 AM, "Andrew Wetmore"  wrote:
> >>
> >> >Do we have a list of Flex features not (yet) available in Royale, and
> >> >known
> >> >ways of getting to the desired result using Royale? Recent
> >>conversations
> >> >regarding Alina's product migration make me think that would be a
> >>useful
> >> >feature in the help documentation.
> >> >
> >> >a
> >> >
> >> >--
> >> >Andrew Wetmore
> >> >
> >>
> >>>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fcottage1
> >>>4
> >> .
> >> >blogspot.com%2F=02%7C01%7Caharui%40adobe.com%
> >> 7Cab1132be823a4a9550a908
> >> >d56d86b83a%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%
> >> 7C636535347739075363
> >> >=9GmPciqGZmuYdFrUz12LS%2FIkMACatH4VwrMoEzLllcA%3D=0
> >>
> >>
> >
> >
> >--
> >Andrew Wetmore
> >
> >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcottage14
> .
> >blogspot.com%2F=02%7C01%7Caharui%40adobe.com%
> 7Cb606bc597d3e4cb895c408
> >d56d8f2bbc%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%
> 7C636535384047818534
> 

Re: Introducing Royale CLI tool

[Carlos Rovira]

So cool Om! Great!
I'm very busy right now with lots of fronts, but let me know if you need
help from me in order to create the blog post.
You can contact me offline in order to support in this task as much as you
can
thanks for making this!

2018-02-15 10:20 GMT+01:00 Gabe Harbs :

> Very cool! Great initiative!
>
> I’ll try to give it a spin later.
>
> Is there a way of creating different templates for the “new” command?
>
> BTW, it would be really great to try to stick to dog-fooding to have as
> many samples of Royale use as possible.
>
> This tool can be written in ActionScript and compiled for node.js using
> Royale.
>
> Harbs
>
> > On Feb 15, 2018, at 10:16 AM, OmPrakash Muppirala 
> wrote:
> >
> > As I was trying to write a `Setting up Royale with npm `blog post, I
> > realized that things could be much easier for npm users.  So, I built the
> > Royale CLI tool.  It takes inspiration from the create-react-app and the
> > angular cli projects.
> >
> > Here are the details:
> >
> > *To Install: *
> > npm install @apache-royale/royale-js -g
> > npm install @apache-royale/cli -g
> >
> > After installation:
> >
> > *Help *
> > royale help
> >
> > *Setup *
> > royale new  my-royale-app
> > cd my-royale-app
> >
> > This creates a simple app: my-royale-app/src/Main.mxml
> >
> >
> > *Run in debug mode *
> > royale serve:debug
> >
> > Compiles the project in debug mode
> > Compiles with source map option
> > Starts a http server and serves the files from the bin/js-debug directory
> > Opens the default browser and navigates to http://localhost:3000
> > Listens to src folder
> > When any file changes, it will recompile the app
> > Automatically reloads the browser to show the updated application
> >
> > *Run in release mode *
> > royale serve:release
> >
> > Compiles the project in release mode
> > Starts a http server and serves the files from the bin/js-release
> > directory
> > Opens the default browser and navigates to http://localhost:3001
> >
> >
> > Please test and provide feedback.  It would be greatly appreciated.
> >
> > Thanks,
> > Om
>
>


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

Re: How I can use multiple CSS files

[Piotr Zarzycki]

If you end up with the issue let's fill a bug on github! Let's track some
things through the github issues.

Piotr

2018-02-15 10:21 GMT+01:00 Alex Harui :

> Right now, all css files are combined into one final css file.  If you
> compile App.mxml, you will get an App.css with all selectors from all SWCs
> that applied to the classes in the output.  I've actually been thinking
> about changing that so that if you specify a css file in an fx:Style we
> copy it as-is to the output folder.  That way you could update the source
> CSS and copy it over and see the changes without a recompile.
>
> The code sure looks like if VividBlueTheme is listed in the -theme option
> that the compiler would pick it up.  Did you actually look in the final
> .css file?  It could be an ordering problem where some other css stomps on
> the things you specified in VividBlueTheme.
>
> Also, unzip VividBlueTheme.swc and make sure the .css files are in the SWC.
>
> If that all looks good, post a small test case so I can look into it.
>
> -Alex
>
>
> On 2/14/18, 11:16 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
>
> >Hi Alex,
> >
> >I'm a bit confused here. I created the thread since I'm already trying it.
> >In VividBlueTheme, I added in pom.xml two 
> >one for typical defaults.css and another for TextField.css
> >Both, are in theme SWC thanks to maven build, at that point is ok.
> >
> >The problem is that final app is not using TextField.css, but is using
> >defaults.css
> >
> >So I think I only need to know how defaults.css is been applied to be used
> >in final example App and get Textfield.css be applied as well in the same
> >way so the final user don't need to link in the final App.
> >
> >One thing that could be great to make this better is to make all
> >components
> >css files developed at "creation time" be joined into one single
> >"defaults.css" file (or other name) for production purposes and remove the
> >load of lots of css files. But this is an improvement over the first part
> >
> >thanks for looking into this
> >
> >
> >
> >
> >2018-02-14 23:38 GMT+01:00 Alex Harui :
> >
> >> Hi Carlos,
> >>
> >> I looked at the compiler some more.  It appears that this feature
> >>already
> >> exists.  When I answered earlier, I was looking at code that loads SWCs
> >> off the library path and the compiler only looks at defaults.css in
> >>those
> >> files, but I just saw that in SWCs specified as themes it will use every
> >> .css file.
> >>
> >> Please try it and let us know if it works.  One thing to be careful of
> >>is
> >> that I'm not sure you can control the order of the .css files.  Maybe by
> >> specifying the order they are specified to COMPC (the SWC compiler).
> >> Order will only matter for overriding style properties.
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 2/14/18, 2:26 PM, "carlos.rov...@gmail.com on behalf of Carlos
> >>Rovira"
> >>  wrote:
> >>
> >> >Hi Alex,
> >> >
> >> >I read @import and seems is not recommended for many reasons
> >>(concurrence
> >> >mainly) so I think is not a solution.
> >> >My bet is that this will make more easy to develop themes since I can
> >>go
> >> >directly to the css file "Textfield.css" and make changes over a few
> >>set
> >> >of
> >> >lines.
> >> >I never touched the compiler, so If you could add support for this
> >>feature
> >> >in order to use all css files included (I think this would must be the
> >> >ones
> >> >listed in the pom.xml)
> >> >It would be more easy to me to continue developing this feature. Could
> >>you
> >> >help me with this? For what you said maybe for you is not a long task
> >>and
> >> >can be ready in moderate few time,
> >> >
> >> >@Harbs, could you tell us a bit more of you MXML proposal, maybe some
> >> >explanation with few example names could help me see your method
> >> >
> >> >Thanks both with this!
> >> >
> >> >Carlos
> >> >
> >> >
> >> >
> >> >2018-02-13 19:44 GMT+01:00 Gabe Harbs :
> >> >
> >> >> Why not just use MXML files?
> >> >>
> >> >> You can use MXML files to subclass components and specify the CSS in
> >>the
> >> >>  section.
> >> >>
> >> >> > On Feb 13, 2018, at 1:20 PM, Carlos Rovira
> >>
> >> >> wrote:
> >> >> >
> >> >> > Hi,
> >> >> >
> >> >> > I'm organizing CSS files in Vivid (new ui set) - VividBlueTheme
> >>(first
> >> >> > theme) - VividExample (example to show all working)
> >> >> >
> >> >> > I want to develop each component look-and-feel and style in a
> >>single
> >> >>file
> >> >> > in the theme project:
> >> >> >
> >> >> > default.css (this could hold global styling like body, headers,
> >> >> background
> >> >> > color, and more)
> >> >> > TextField.css (all css to make a TextField be represented in a
> >> >>particular
> >> >> > way)
> >> >> > Button.css
> >> >> > Slider.css
> 

Re: Introducing Royale CLI tool

[Gabe Harbs]

Very cool! Great initiative!

I’ll try to give it a spin later.

Is there a way of creating different templates for the “new” command?

BTW, it would be really great to try to stick to dog-fooding to have as many 
samples of Royale use as possible.

This tool can be written in ActionScript and compiled for node.js using Royale.

Harbs

> On Feb 15, 2018, at 10:16 AM, OmPrakash Muppirala  wrote:
> 
> As I was trying to write a `Setting up Royale with npm `blog post, I
> realized that things could be much easier for npm users.  So, I built the
> Royale CLI tool.  It takes inspiration from the create-react-app and the
> angular cli projects.
> 
> Here are the details:
> 
> *To Install: *
> npm install @apache-royale/royale-js -g
> npm install @apache-royale/cli -g
> 
> After installation:
> 
> *Help *
> royale help
> 
> *Setup *
> royale new  my-royale-app
> cd my-royale-app
> 
> This creates a simple app: my-royale-app/src/Main.mxml
> 
> 
> *Run in debug mode *
> royale serve:debug
> 
> Compiles the project in debug mode
> Compiles with source map option
> Starts a http server and serves the files from the bin/js-debug directory
> Opens the default browser and navigates to http://localhost:3000
> Listens to src folder
> When any file changes, it will recompile the app
> Automatically reloads the browser to show the updated application
> 
> *Run in release mode *
> royale serve:release
> 
> Compiles the project in release mode
> Starts a http server and serves the files from the bin/js-release
> directory
> Opens the default browser and navigates to http://localhost:3001
> 
> 
> Please test and provide feedback.  It would be greatly appreciated.
> 
> Thanks,
> Om

Re: Introducing Royale CLI tool

[OmPrakash Muppirala]

I will leave this Pull Request here, in case anyone wants to review it.
https://github.com/apache/royale-asjs/pull/118/files

Thanks,
Om

On Thu, Feb 15, 2018 at 12:21 AM, OmPrakash Muppirala 
wrote:

> BTW, I have tested this on Windows: power shell, command prompt and git
> bash.  They all work fine.
> Someone needs to test on Mac and tell me what happens :-)
>
> Thanks,
> Om
>
> On Thu, Feb 15, 2018 at 12:16 AM, OmPrakash Muppirala 
> wrote:
>
>> As I was trying to write a `Setting up Royale with npm `blog post, I
>> realized that things could be much easier for npm users.  So, I built the
>> Royale CLI tool.  It takes inspiration from the create-react-app and the
>> angular cli projects.
>>
>> Here are the details:
>>
>> *To Install: *
>> npm install @apache-royale/royale-js -g
>> npm install @apache-royale/cli -g
>>
>> After installation:
>>
>> *Help *
>> royale help
>>
>> *Setup *
>> royale new  my-royale-app
>> cd my-royale-app
>>
>>  This creates a simple app: my-royale-app/src/Main.mxml
>>
>>
>> *Run in debug mode *
>> royale serve:debug
>>
>>  Compiles the project in debug mode
>>  Compiles with source map option
>>  Starts a http server and serves the files from the bin/js-debug
>> directory
>>  Opens the default browser and navigates to http://localhost:3000
>>  Listens to src folder
>>  When any file changes, it will recompile the app
>>  Automatically reloads the browser to show the updated application
>>
>> *Run in release mode *
>> royale serve:release
>>
>>  Compiles the project in release mode
>>  Starts a http server and serves the files from the bin/js-release
>> directory
>>  Opens the default browser and navigates to http://localhost:3001
>>
>>
>> Please test and provide feedback.  It would be greatly appreciated.
>>
>> Thanks,
>> Om
>>
>>
>>
>
>

Re: Introducing Royale CLI tool

[OmPrakash Muppirala]

BTW, I have tested this on Windows: power shell, command prompt and git
bash.  They all work fine.
Someone needs to test on Mac and tell me what happens :-)

Thanks,
Om

On Thu, Feb 15, 2018 at 12:16 AM, OmPrakash Muppirala 
wrote:

> As I was trying to write a `Setting up Royale with npm `blog post, I
> realized that things could be much easier for npm users.  So, I built the
> Royale CLI tool.  It takes inspiration from the create-react-app and the
> angular cli projects.
>
> Here are the details:
>
> *To Install: *
> npm install @apache-royale/royale-js -g
> npm install @apache-royale/cli -g
>
> After installation:
>
> *Help *
> royale help
>
> *Setup *
> royale new  my-royale-app
> cd my-royale-app
>
>  This creates a simple app: my-royale-app/src/Main.mxml
>
>
> *Run in debug mode *
> royale serve:debug
>
>  Compiles the project in debug mode
>  Compiles with source map option
>  Starts a http server and serves the files from the bin/js-debug directory
>  Opens the default browser and navigates to http://localhost:3000
>  Listens to src folder
>  When any file changes, it will recompile the app
>  Automatically reloads the browser to show the updated application
>
> *Run in release mode *
> royale serve:release
>
>  Compiles the project in release mode
>  Starts a http server and serves the files from the bin/js-release
> directory
>  Opens the default browser and navigates to http://localhost:3001
>
>
> Please test and provide feedback.  It would be greatly appreciated.
>
> Thanks,
> Om
>
>
>

Re: Introducing Royale CLI tool

[Alex Harui]

Great idea!

On 2/15/18, 12:16 AM, "OmPrakash Muppirala"  wrote:

>As I was trying to write a `Setting up Royale with npm `blog post, I
>realized that things could be much easier for npm users.  So, I built the
>Royale CLI tool.  It takes inspiration from the create-react-app and the
>angular cli projects.
>
>Here are the details:
>
>*To Install: *
>npm install @apache-royale/royale-js -g
>npm install @apache-royale/cli -g
>
>After installation:
>
>*Help *
>royale help
>
>*Setup *
>royale new  my-royale-app
>cd my-royale-app
>
> This creates a simple app: my-royale-app/src/Main.mxml
>
>
>*Run in debug mode *
>royale serve:debug
>
> Compiles the project in debug mode
> Compiles with source map option
> Starts a http server and serves the files from the bin/js-debug directory
> Opens the default browser and navigates to http://localhost:3000
> Listens to src folder
> When any file changes, it will recompile the app
> Automatically reloads the browser to show the updated application
>
>*Run in release mode *
>royale serve:release
>
> Compiles the project in release mode
> Starts a http server and serves the files from the bin/js-release
>directory
> Opens the default browser and navigates to http://localhost:3001
>
>
>Please test and provide feedback.  It would be greatly appreciated.
>
>Thanks,
>Om

Re: ArrayCollection in Royale

[Alex Harui]

If the goal is to further reduce the number of changes to migrated code,
we should just start a new component set.  IIRC, ArrayCollection usually
has very bad performance if you use array indexing to access it.
ArrayList should perform much better but you can't use array indexing.
Filtering and sorting should be written as beads.

My 2 cents,
-Alex

On 2/15/18, 12:11 AM, "Piotr Zarzycki"  wrote:

>Hi Carlos,
>
>We have ArrayList which is enough close to ArrayCollection. I have with
>success replace ArrayCollection to ArrayList in my examples.
>
>Thanks, Piotr
>
>2018-02-15 8:47 GMT+01:00 Carlos Rovira :
>
>> Hi
>>
>> I saw Alina post in user list about substitutes and I think one
>>important
>> one is:
>>
>> import mx.collections.ArrayCollection; //very similar to
>> org.apache.royale.collections.TreeData
>>
>> In order to ease the port of Flex apps to Royale, one thing we try is to
>> reuse as much AS3 logic, while in UX we need to create all new code
>>
>> ArrayCollection is very close to business logic, and widely used in AMF
>> calls.
>>
>> I suggest we should have ArrayCollection in Royale and even respect
>> namespace to avoid users to change any line in AS3 code.
>>
>> Only with this point we can remove lots of pain in migration process
>>from
>> Flex to Royale
>>
>> what do you think?
>>
>> --
>> Carlos Rovira
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2Fcarlosrovira=02%7C01%7Caharui%40adobe.com%7C10ecbb5b8c464b4ed36708
>>d5744bcadb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63654279123032447
>>4=RY6LraL22n2Yt9QiNyJc0FQms64yALaKy16%2FNW7XHJc%3D=0
>>
>
>
>
>-- 
>
>Piotr Zarzycki
>
>Patreon: 
>*https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patr
>eon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7C10ecbb5b8c464b
>4ed36708d5744bcadb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365427912
>30324474=mwO%2FFFYUAHHA8VlHeJQreNzUOMKzd%2BeqaMV6%2FNPhIKk%3D
>ed=0
>eon.com%2Fpiotrzarzycki=02%7C01%7Caharui%40adobe.com%7C10ecbb5b8c464b
>4ed36708d5744bcadb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6365427912
>30324474=mwO%2FFFYUAHHA8VlHeJQreNzUOMKzd%2BeqaMV6%2FNPhIKk%3D
>ed=0>*

Introducing Royale CLI tool

[OmPrakash Muppirala]

As I was trying to write a `Setting up Royale with npm `blog post, I
realized that things could be much easier for npm users.  So, I built the
Royale CLI tool.  It takes inspiration from the create-react-app and the
angular cli projects.

Here are the details:

*To Install: *
npm install @apache-royale/royale-js -g
npm install @apache-royale/cli -g

After installation:

*Help *
royale help

*Setup *
royale new  my-royale-app
cd my-royale-app

 This creates a simple app: my-royale-app/src/Main.mxml


*Run in debug mode *
royale serve:debug

 Compiles the project in debug mode
 Compiles with source map option
 Starts a http server and serves the files from the bin/js-debug directory
 Opens the default browser and navigates to http://localhost:3000
 Listens to src folder
 When any file changes, it will recompile the app
 Automatically reloads the browser to show the updated application

*Run in release mode *
royale serve:release

 Compiles the project in release mode
 Starts a http server and serves the files from the bin/js-release
directory
 Opens the default browser and navigates to http://localhost:3001


Please test and provide feedback.  It would be greatly appreciated.

Thanks,
Om

Re: ArrayCollection in Royale

[Piotr Zarzycki]

Hi Carlos,

We have ArrayList which is enough close to ArrayCollection. I have with
success replace ArrayCollection to ArrayList in my examples.

Thanks, Piotr

2018-02-15 8:47 GMT+01:00 Carlos Rovira :

> Hi
>
> I saw Alina post in user list about substitutes and I think one important
> one is:
>
> import mx.collections.ArrayCollection; //very similar to
> org.apache.royale.collections.TreeData
>
> In order to ease the port of Flex apps to Royale, one thing we try is to
> reuse as much AS3 logic, while in UX we need to create all new code
>
> ArrayCollection is very close to business logic, and widely used in AMF
> calls.
>
> I suggest we should have ArrayCollection in Royale and even respect
> namespace to avoid users to change any line in AS3 code.
>
> Only with this point we can remove lots of pain in migration process from
> Flex to Royale
>
> what do you think?
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>



-- 

Piotr Zarzycki

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