Jenkins build is back to normal : royale-asjs_MXTests #1086

[Apache Royale CI Server]

See 

Re: Sub-Menu in royale-docs: "Fundamental Concepts", "Core Concepts" or "Technology features"

[Carlos Rovira]

Excelent Andrew, thanks! :)

El sáb., 24 ago. 2019 a las 21:35, Andrew Wetmore ()
escribió:

> I have edited the Strands and Beads page for readability.
>
> On Sat, Aug 24, 2019 at 7:55 AM Carlos Rovira 
> wrote:
>
> > Hi Chris,
> >
> > another one page you can need about Strands and Beads:
> >
> >
> >
> https://apache.github.io/royale-docs/welcome/features/strands-and-beads.html
> >
> >
> >
> > El sáb., 24 ago. 2019 a las 10:58, Carlos Rovira (<
> carlosrov...@apache.org
> > >)
> > escribió:
> >
> > > Hi Chris,
> > >
> > > great to see you here :)
> > >
> > > This the actual page on Royale-docs about that concepts:
> > >
> > >
> https://apache.github.io/royale-docs/welcome/features-and-concepts.html
> > >
> > > That links to this other one (more concrete):
> > > https://apache.github.io/royale-docs/welcome/features/payg.html
> > >
> > > Notice that docs are this days in continuous developement.
> > >
> > > You can find short examples like (ala flex examples blog) to get you
> > > started here:
> > >
> > > https://royale.apache.org/category/royale-examples/
> > >
> > > In the Royale-docs I'm trying this days to document the list of beads
> > that
> > > could be used per bead, for example Jewel Button docs is this:
> > >
> > >
> >
> https://apache.github.io/royale-docs/component-sets/jewel/jewel-button.html
> > >
> > > HTH
> > >
> > > Carlos
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > El sáb., 24 ago. 2019 a las 5:48, Chris Velevitch (<
> > > chris.velevi...@gmail.com>) escribió:
> > >
> > >> As a Flex developer exploring Royale, I've come across the terms
> > "beads",
> > >> "strands" and "pay as you go" (PAYG), but I can't find any details,
> > >> documentation or tutorials on them. How do these map into existing
> Flex
> > >> concepts? As for PAYG, as far as I can tell, this is just another name
> > for
> > >> the concept of "tree-shaking" [1] that other javascript frameworks
> > >> have/use.
> > >>
> > >> So, where can I find more information on these?
> > >>
> > >> [1] https://en.wikipedia.org/wiki/Tree_shaking
> > >>
> > >> On Thu, 22 Aug 2019 at 18:35, Carlos Rovira 
> > >> wrote:
> > >>
> > >> > Hi,
> > >> >
> > >> > while adding yesterday all "Where to go from here" sections in all
> > blog
> > >> > examples, I found that Royale docs need a sub menu in the sidebar
> with
> > >> some
> > >> > royale important concepts.
> > >> >
> > >> > So after "*Get Started*" and before "*Component Sets*" I think we
> need
> > >> > something like a "*Fundamental Concepts*" (maybe this title is not
> the
> > >> best
> > >> > and others can get other that match better, I'll try to think in
> other
> > >> that
> > >> > fits better too. I try to refer to "Core Concepts" or a "Technology
> > >> > features" here).
> > >> >
> > >> > Is what a user should need to know just after finish "Get Started"
> > guide
> > >> > and a hello world...know the tools avaialble in the royale arsenal,
> > know
> > >> > that they have available things like binding, states, modules...
> > >> >
> > >> > In this submenu we need to cover the things that are still not
> covered
> > >> in
> > >> > the docs and others that are covered but seems a bit lost in places
> > >> > difficult to find or that are not the best way where a user should
> > find
> > >> it,
> > >> > or try to search for it.
> > >> >
> > >> > Options will be all core concepts:
> > >> >
> > >> >  - *Fundamental Concepts *
> > >> >   - *View States* (just created an empty page yesterday)
> > >> >   - *Data Binding* (page exists too but is empty now and needs
> to
> > be
> > >> > relocated)
> > >> >   - *Modules* (This already exist, I think just need to be
> > >> relocated)
> > >> >   - *Externs* (this one was created yesterday by Andrew, again
> the
> > >> > problem is still not referenced in menu, and is under
> > "user-interface",
> > >> but
> > >> > is more a "core concept" or a "technology feature").
> > >> >   - *Loading Data* or *Data Access*: This should have a sub menu
> > >> with
> > >> > the main ways to access data :
> > >> >- *HTTPService*
> > >> >- *JSON*
> > >> >- *AMF*
> > >> >- ...
> > >> >   - *Metadata*
> > >> >   - *Styles and CSS*
> > >> >   - ...  I'm sure there are more to bring here...
> > >> >
> > >> > For me this is the main missing piece we need to address, and of
> > course
> > >> > completing not only that menu but many other pages still to fill.
> > >> >
> > >> > Just one thing to end: In each page after main title the template
> > expect
> > >> > the next line to be a short subtitle. For example, in the new
> > "Externs"
> > >> > page y added a new line after title "Use external javascript
> libraries
> > >> in
> > >> > ActiopnScript" So that line is shown in blue and with a bit more
> size
> > to
> > >> > match the web style. That line should help a user to quickly
> > understand
> > >> > what's that page about, since just "Externs" probably will not be of
> > 

Re: Sub-Menu in royale-docs: "Fundamental Concepts", "Core Concepts" or "Technology features"

[Andrew Wetmore]

I have edited the Strands and Beads page for readability.

On Sat, Aug 24, 2019 at 7:55 AM Carlos Rovira 
wrote:

> Hi Chris,
>
> another one page you can need about Strands and Beads:
>
>
> https://apache.github.io/royale-docs/welcome/features/strands-and-beads.html
>
>
>
> El sáb., 24 ago. 2019 a las 10:58, Carlos Rovira ( >)
> escribió:
>
> > Hi Chris,
> >
> > great to see you here :)
> >
> > This the actual page on Royale-docs about that concepts:
> >
> > https://apache.github.io/royale-docs/welcome/features-and-concepts.html
> >
> > That links to this other one (more concrete):
> > https://apache.github.io/royale-docs/welcome/features/payg.html
> >
> > Notice that docs are this days in continuous developement.
> >
> > You can find short examples like (ala flex examples blog) to get you
> > started here:
> >
> > https://royale.apache.org/category/royale-examples/
> >
> > In the Royale-docs I'm trying this days to document the list of beads
> that
> > could be used per bead, for example Jewel Button docs is this:
> >
> >
> https://apache.github.io/royale-docs/component-sets/jewel/jewel-button.html
> >
> > HTH
> >
> > Carlos
> >
> >
> >
> >
> >
> >
> >
> >
> > El sáb., 24 ago. 2019 a las 5:48, Chris Velevitch (<
> > chris.velevi...@gmail.com>) escribió:
> >
> >> As a Flex developer exploring Royale, I've come across the terms
> "beads",
> >> "strands" and "pay as you go" (PAYG), but I can't find any details,
> >> documentation or tutorials on them. How do these map into existing Flex
> >> concepts? As for PAYG, as far as I can tell, this is just another name
> for
> >> the concept of "tree-shaking" [1] that other javascript frameworks
> >> have/use.
> >>
> >> So, where can I find more information on these?
> >>
> >> [1] https://en.wikipedia.org/wiki/Tree_shaking
> >>
> >> On Thu, 22 Aug 2019 at 18:35, Carlos Rovira 
> >> wrote:
> >>
> >> > Hi,
> >> >
> >> > while adding yesterday all "Where to go from here" sections in all
> blog
> >> > examples, I found that Royale docs need a sub menu in the sidebar with
> >> some
> >> > royale important concepts.
> >> >
> >> > So after "*Get Started*" and before "*Component Sets*" I think we need
> >> > something like a "*Fundamental Concepts*" (maybe this title is not the
> >> best
> >> > and others can get other that match better, I'll try to think in other
> >> that
> >> > fits better too. I try to refer to "Core Concepts" or a "Technology
> >> > features" here).
> >> >
> >> > Is what a user should need to know just after finish "Get Started"
> guide
> >> > and a hello world...know the tools avaialble in the royale arsenal,
> know
> >> > that they have available things like binding, states, modules...
> >> >
> >> > In this submenu we need to cover the things that are still not covered
> >> in
> >> > the docs and others that are covered but seems a bit lost in places
> >> > difficult to find or that are not the best way where a user should
> find
> >> it,
> >> > or try to search for it.
> >> >
> >> > Options will be all core concepts:
> >> >
> >> >  - *Fundamental Concepts *
> >> >   - *View States* (just created an empty page yesterday)
> >> >   - *Data Binding* (page exists too but is empty now and needs to
> be
> >> > relocated)
> >> >   - *Modules* (This already exist, I think just need to be
> >> relocated)
> >> >   - *Externs* (this one was created yesterday by Andrew, again the
> >> > problem is still not referenced in menu, and is under
> "user-interface",
> >> but
> >> > is more a "core concept" or a "technology feature").
> >> >   - *Loading Data* or *Data Access*: This should have a sub menu
> >> with
> >> > the main ways to access data :
> >> >- *HTTPService*
> >> >- *JSON*
> >> >- *AMF*
> >> >- ...
> >> >   - *Metadata*
> >> >   - *Styles and CSS*
> >> >   - ...  I'm sure there are more to bring here...
> >> >
> >> > For me this is the main missing piece we need to address, and of
> course
> >> > completing not only that menu but many other pages still to fill.
> >> >
> >> > Just one thing to end: In each page after main title the template
> expect
> >> > the next line to be a short subtitle. For example, in the new
> "Externs"
> >> > page y added a new line after title "Use external javascript libraries
> >> in
> >> > ActiopnScript" So that line is shown in blue and with a bit more size
> to
> >> > match the web style. That line should help a user to quickly
> understand
> >> > what's that page about, since just "Externs" probably will not be of
> >> much
> >> > help for a beginner.
> >> >
> >> > many pages are still without subtitle, but as we go over all docs, we
> >> > should add this lines to help users reaching that pages.
> >> >
> >> > Thanks
> >> >
> >> > --
> >> > Carlos Rovira
> >> > http://about.me/carlosrovira
> >> >
> >>
> >>
> >> --
> >>
> >>
> >> Chris
> >> --
> >> Chris Velevitch
> >> m: 0415 469 095
> >>
> >
> >
> > --
> > Carlos Rovira
> > 

Build failed in Jenkins: royale-asjs_MXTests #1085

[Apache Royale CI Server]

See 


--
[...truncated 968.50 KB...]
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout
[mxmlc] scanning for overrides: IBinaryDataInput
  

Jenkins build is back to normal : Royale_ASDoc_Example #2372

[Apache Royale CI Server]

See 

Release Step 011 Succeeded

[Apache Royale CI Server]

>From the royale-asjs repo:
1. Run ant -f releasesteps.xml Release_Step_011 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_011_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_011_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Verify that 
the compiler and typedefs artifacts are there along with the asjs artifacts, 
then hit the close to close the staging repo. (https://repository.apache.org)

Release Step 010 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_010 and run the following commands:
git push
git push origin org.apache.royale.framework-0.9.6-rc1

You will need your Apache/Github username and 2FA token.

Release Step 009 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_009 and run the following commands:
git push

You will need your Apache/Github username and 2FA token.

Release Step 008 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_008 and run the following commands:
git push
git checkout release/0.9.6
git push -u origin release/0.9.6

You will need your Apache/Github username and 2FA token.

Release Step 007 Succeeded

[Apache Royale CI Server]

>From the royale-typedefs repo:
1. Run ant -f releasesteps.xml Release_Step_007 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_007_Sign 
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_007_Upload 
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging.  Do not "Close" 
the staging repository until the other repos have been added.

Release Step 006 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_006 and run the following commands:
git push
git push origin org.apache.royale.typedefs-0.9.6-rc1

You will need your Apache/Github username and 2FA token.

Release Step 005a Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005a_If_Utils and run the following 
commands:
git push

You will need your Apache/Github username and 2FA token.

Re: Sub-Menu in royale-docs: "Fundamental Concepts", "Core Concepts" or "Technology features"

[Carlos Rovira]

Hi Chris,

another one page you can need about Strands and Beads:

https://apache.github.io/royale-docs/welcome/features/strands-and-beads.html



El sáb., 24 ago. 2019 a las 10:58, Carlos Rovira ()
escribió:

> Hi Chris,
>
> great to see you here :)
>
> This the actual page on Royale-docs about that concepts:
>
> https://apache.github.io/royale-docs/welcome/features-and-concepts.html
>
> That links to this other one (more concrete):
> https://apache.github.io/royale-docs/welcome/features/payg.html
>
> Notice that docs are this days in continuous developement.
>
> You can find short examples like (ala flex examples blog) to get you
> started here:
>
> https://royale.apache.org/category/royale-examples/
>
> In the Royale-docs I'm trying this days to document the list of beads that
> could be used per bead, for example Jewel Button docs is this:
>
> https://apache.github.io/royale-docs/component-sets/jewel/jewel-button.html
>
> HTH
>
> Carlos
>
>
>
>
>
>
>
>
> El sáb., 24 ago. 2019 a las 5:48, Chris Velevitch (<
> chris.velevi...@gmail.com>) escribió:
>
>> As a Flex developer exploring Royale, I've come across the terms "beads",
>> "strands" and "pay as you go" (PAYG), but I can't find any details,
>> documentation or tutorials on them. How do these map into existing Flex
>> concepts? As for PAYG, as far as I can tell, this is just another name for
>> the concept of "tree-shaking" [1] that other javascript frameworks
>> have/use.
>>
>> So, where can I find more information on these?
>>
>> [1] https://en.wikipedia.org/wiki/Tree_shaking
>>
>> On Thu, 22 Aug 2019 at 18:35, Carlos Rovira 
>> wrote:
>>
>> > Hi,
>> >
>> > while adding yesterday all "Where to go from here" sections in all blog
>> > examples, I found that Royale docs need a sub menu in the sidebar with
>> some
>> > royale important concepts.
>> >
>> > So after "*Get Started*" and before "*Component Sets*" I think we need
>> > something like a "*Fundamental Concepts*" (maybe this title is not the
>> best
>> > and others can get other that match better, I'll try to think in other
>> that
>> > fits better too. I try to refer to "Core Concepts" or a "Technology
>> > features" here).
>> >
>> > Is what a user should need to know just after finish "Get Started" guide
>> > and a hello world...know the tools avaialble in the royale arsenal, know
>> > that they have available things like binding, states, modules...
>> >
>> > In this submenu we need to cover the things that are still not covered
>> in
>> > the docs and others that are covered but seems a bit lost in places
>> > difficult to find or that are not the best way where a user should find
>> it,
>> > or try to search for it.
>> >
>> > Options will be all core concepts:
>> >
>> >  - *Fundamental Concepts *
>> >   - *View States* (just created an empty page yesterday)
>> >   - *Data Binding* (page exists too but is empty now and needs to be
>> > relocated)
>> >   - *Modules* (This already exist, I think just need to be
>> relocated)
>> >   - *Externs* (this one was created yesterday by Andrew, again the
>> > problem is still not referenced in menu, and is under "user-interface",
>> but
>> > is more a "core concept" or a "technology feature").
>> >   - *Loading Data* or *Data Access*: This should have a sub menu
>> with
>> > the main ways to access data :
>> >- *HTTPService*
>> >- *JSON*
>> >- *AMF*
>> >- ...
>> >   - *Metadata*
>> >   - *Styles and CSS*
>> >   - ...  I'm sure there are more to bring here...
>> >
>> > For me this is the main missing piece we need to address, and of course
>> > completing not only that menu but many other pages still to fill.
>> >
>> > Just one thing to end: In each page after main title the template expect
>> > the next line to be a short subtitle. For example, in the new "Externs"
>> > page y added a new line after title "Use external javascript libraries
>> in
>> > ActiopnScript" So that line is shown in blue and with a bit more size to
>> > match the web style. That line should help a user to quickly understand
>> > what's that page about, since just "Externs" probably will not be of
>> much
>> > help for a beginner.
>> >
>> > many pages are still without subtitle, but as we go over all docs, we
>> > should add this lines to help users reaching that pages.
>> >
>> > Thanks
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>>
>>
>> --
>>
>>
>> Chris
>> --
>> Chris Velevitch
>> m: 0415 469 095
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

Release Step 005 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands:
git push

You will need your Apache/Github username and 2FA token.

Release Step 004 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands:
git push
git checkout release/0.9.6
git push -u origin release/0.9.6

You will need your Apache/Github username and 2FA token.

Royale_Release_Step_006 - Build # 34 - Failure!

[Apache Royale CI Server]

Royale_Release_Step_006 - Build # 34 - Failure:

Check console output at 
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/Royale_Release_Step_006/34/
 to view the results.

Release Step 005a Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005a_If_Utils and run the following 
commands:
git push

You will need your Apache/Github username and 2FA token.

Release Step 005 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_005 and run the following commands:
git push

You will need your Apache/Github username and 2FA token.

Release Step 004 Succeeded

[Apache Royale CI Server]

Log in to the server, open a command prompt, change directory to 
C:\jenkins\workspace\Royale_Release_Step_004 and run the following commands:
git push
git checkout release/0.9.6
git push -u origin release/0.9.6

You will need your Apache/Github username and 2FA token.

Re: Sub-Menu in royale-docs: "Fundamental Concepts", "Core Concepts" or "Technology features"

[Carlos Rovira]

Hi Chris,

great to see you here :)

This the actual page on Royale-docs about that concepts:

https://apache.github.io/royale-docs/welcome/features-and-concepts.html

That links to this other one (more concrete):
https://apache.github.io/royale-docs/welcome/features/payg.html

Notice that docs are this days in continuous developement.

You can find short examples like (ala flex examples blog) to get you
started here:

https://royale.apache.org/category/royale-examples/

In the Royale-docs I'm trying this days to document the list of beads that
could be used per bead, for example Jewel Button docs is this:

https://apache.github.io/royale-docs/component-sets/jewel/jewel-button.html

HTH

Carlos








El sáb., 24 ago. 2019 a las 5:48, Chris Velevitch (<
chris.velevi...@gmail.com>) escribió:

> As a Flex developer exploring Royale, I've come across the terms "beads",
> "strands" and "pay as you go" (PAYG), but I can't find any details,
> documentation or tutorials on them. How do these map into existing Flex
> concepts? As for PAYG, as far as I can tell, this is just another name for
> the concept of "tree-shaking" [1] that other javascript frameworks
> have/use.
>
> So, where can I find more information on these?
>
> [1] https://en.wikipedia.org/wiki/Tree_shaking
>
> On Thu, 22 Aug 2019 at 18:35, Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > while adding yesterday all "Where to go from here" sections in all blog
> > examples, I found that Royale docs need a sub menu in the sidebar with
> some
> > royale important concepts.
> >
> > So after "*Get Started*" and before "*Component Sets*" I think we need
> > something like a "*Fundamental Concepts*" (maybe this title is not the
> best
> > and others can get other that match better, I'll try to think in other
> that
> > fits better too. I try to refer to "Core Concepts" or a "Technology
> > features" here).
> >
> > Is what a user should need to know just after finish "Get Started" guide
> > and a hello world...know the tools avaialble in the royale arsenal, know
> > that they have available things like binding, states, modules...
> >
> > In this submenu we need to cover the things that are still not covered in
> > the docs and others that are covered but seems a bit lost in places
> > difficult to find or that are not the best way where a user should find
> it,
> > or try to search for it.
> >
> > Options will be all core concepts:
> >
> >  - *Fundamental Concepts *
> >   - *View States* (just created an empty page yesterday)
> >   - *Data Binding* (page exists too but is empty now and needs to be
> > relocated)
> >   - *Modules* (This already exist, I think just need to be relocated)
> >   - *Externs* (this one was created yesterday by Andrew, again the
> > problem is still not referenced in menu, and is under "user-interface",
> but
> > is more a "core concept" or a "technology feature").
> >   - *Loading Data* or *Data Access*: This should have a sub menu with
> > the main ways to access data :
> >- *HTTPService*
> >- *JSON*
> >- *AMF*
> >- ...
> >   - *Metadata*
> >   - *Styles and CSS*
> >   - ...  I'm sure there are more to bring here...
> >
> > For me this is the main missing piece we need to address, and of course
> > completing not only that menu but many other pages still to fill.
> >
> > Just one thing to end: In each page after main title the template expect
> > the next line to be a short subtitle. For example, in the new "Externs"
> > page y added a new line after title "Use external javascript libraries in
> > ActiopnScript" So that line is shown in blue and with a bit more size to
> > match the web style. That line should help a user to quickly understand
> > what's that page about, since just "Externs" probably will not be of much
> > help for a beginner.
> >
> > many pages are still without subtitle, but as we go over all docs, we
> > should add this lines to help users reaching that pages.
> >
> > Thanks
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
>
> Chris
> --
> Chris Velevitch
> m: 0415 469 095
>


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