Build failed in Jenkins: royale-asjs #2760

2019-10-01 Thread Apache Royale CI Server
See 


--
[...truncated 1.20 MB...]
 [java] module.exports = os;
 [java] ^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [path]:97: WARNING - name module is not defined in the 
externs.
 [java] module.exports = path;
 [java] ^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [punycode]:74: WARNING - name module is not defined in the 
externs.
 [java] module.exports = punycode;
 [java] ^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [querystring]:66: WARNING - name module is not defined in 
the externs.
 [java] module.exports = querystring;
 [java] ^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:22: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = readline;
 [java] ^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:48: WARNING - name module is not defined in the 
externs.
 [java] module.exports = repl;
 [java] ^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 02, 2019 4:58:36 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:254: WARNING - name module is not defined in the 
externs.
 [java] module.exports = stream;
 [java] ^^
 [java] 
 [java] Oct 02, 2019 4:58:37 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [string_decoder]:52: WARNING - name module is not defined 
in the externs.
 [java] module.exports = StringDecoder;
 [java] ^^
 [java] 
 [java] Oct 02, 2019 4:58:37 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var crypto = require('crypto');
 [java]  ^^^
 [java] 
 [java] Oct 02, 2019 4:58:37 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 02, 2019 4:58:37 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:25: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var net = require('net');
 [java]   ^^^
 [java] 
 [java] Oct 02, 2019 4:58:37 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:26: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Oct 02, 2019 4:58:37 AM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [tls]:148: WARNING - name module 

Build failed in Jenkins: royale-asjs_MXTests #1207

2019-10-01 Thread Apache Royale CI Server
See 


--
[...truncated 1004.11 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[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

Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread OmPrakash Muppirala
On Tue, Oct 1, 2019 at 8:32 AM Alex Harui  wrote:

> The releasecandidate.xml script will tell you what to do on
> repository.apache.org to release the Maven stuff, and release the npm
> stuff as well.  The whole point of these scripts is so you don't have to
> ask for help.  If you do end up needing help, then the scripts need
> improving.  We want to capture knowledge in these scripts and on the wiki.
>
>
Alex, did you merge your fixes to the npm related stuff into the release
branch?  If yes, I think we should be good to go.

Thanks,
Om


> -Alex
>
> On 10/1/19, 12:30 AM, "Piotr Zarzycki"  wrote:
>
> Hi Om,
>
> What I need to do in order to release stuff on npm. Can you do this
> for me
> once I push release to svn ?
>
> Thanks,
> Piotr
>
> wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
> napisał(a):
>
> > Hi Harbs,
> >
> > I think we have enough votes. I still have to gather info how
> actually
> > release Maven artifacts. However I'm going to push binaries today in
> svn.
> >
> > Thanks,
> > Piotr
> >
> > sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):
> >
> >> FYI, I will not be able to test the release until Wednesday.
> >>
> >> If the vote is still open, I plan on testing then.
> >>
> >> Thanks,
> >> Harbs
> >>
> >> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >> >
> >> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
> >> myself
> >> > yet, but will do that tomorrow or next week.
> >> >
> >> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> >> apacheroyal...@gmail.com>
> >> > napisał(a):
> >> >
> >> >> This is the discussion thread.
> >> >>
> >> >> Thanks,
> >> >> Piotr
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Piotr Zarzycki
> >> >
> >> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> >> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> >*
> >>
> >>
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> >*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> >*
>
>
>


Build failed in Jenkins: royale-asjs_MXTests #1206

2019-10-01 Thread Apache Royale CI Server
See 


Changes:

[noreply] Create validator.properties

--
[...truncated 1004.40 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[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: 

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

2019-10-01 Thread Apache Royale CI Server
See 




New apache-royale questions for Oct 1 - Stack Exchange

2019-10-01 Thread Stack Exchange
***1 new question in [ApacheRoyale Tag Notifications 
filter]()
 on stackexchange.com***


[How to center childs in a layout on Apache 
Royale?]()

I search for a easy and efficient way to center all childs in a container using 
basic package. (Because mixing basic and jewel layouts leads to some unwanted 
sides effects) Must I use CSS, beads ? If ...

Tagged: layout

by [Fred]() on 






[Unsubscribe from this 
filter]()
 or change your email preferences by visitingyour [filter subscriptions page on 
stackexchange.com]().

If you no longer want to receive mail from Stack Exchange, unsubscribe from all 
stackexchange.com emails 

Questions? Comments? Let us know on our feedback site at 
.

Stack Exchange, Inc. 110 William St, 28th Floor, NY NY 10038



Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Carlos Rovira
Yeah! that would be great Andrew :)

Other things I have planned to is to go over ASDoc visuals to make it more
near to Royale Docs and more mobile friendly when possible.

I think we're getting a really good product with all the current efforts in
progress :D

El mar., 1 oct. 2019 a las 20:40, Andrew Wetmore ()
escribió:

> I have not forgotten "Royale in a Week", the reworking of "Flex in a Week"
> which I undertook to do. Will be working on that.
>
> On Tue, Oct 1, 2019 at 2:37 PM Alex Harui 
> wrote:
>
> > The showcase would be great, but if it is easier/faster to simply have a
> > page of links to blogs of our committers like you and Harbs that just
> > contain a paragraph or two about how Royale has helped, that might be a
> > good place to start.
> >
> > -Alex
> >
> > On 10/1/19, 10:02 AM, "Carlos Rovira"  wrote:
> >
> > Hi Alex,
> >
> > El mar., 1 oct. 2019 a las 17:50, Alex Harui
> ( > >)
> > escribió:
> >
> > > Thanks for working on the docs.
> > >
> > > Beyond the docs, what I would most like to see is "success
> > stories".  I
> > > keep thinking it would help if it was easier for folks to read
> about
> > how
> > > Royale has helped.
> > >
> >
> > You refer to "showcase" page?
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2Fdata=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3Dreserved=0
> > I still has that on my plate. I have to plan the info to showcase and
> > post
> > so people can submit about it
> > But yes is one of the important pieces to work on. I'll try to get
> > over it
> > soon.
> >
> > thanks
> >
> >
> > > My 2 cents,
> > > -Alex
> > >
> > > On 10/1/19, 3:54 AM, "Andrew Wetmore"  wrote:
> > >
> > > This is great progress!
> > >
> > > I think one other area where we are still very thin is on using
> > > RoyaleUnit
> > > for testing.
> > >
> > > On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <
> > carlosrov...@apache.org>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > about latest changes in docs done is latest months. This is a
> > > summary of
> > > > the work done (still in progress at some points):
> > > >
> > > > About layout, search and usability:
> > > >
> > > > * Now we have a more polished layout that should work right
> on
> > > desktop,
> > > > tablet and mobile, making more easy for new users coming to
> > Royale
> > > learn
> > > > about it
> > > > * The sidebar menu will show on the right as normal in tablet
> > and
> > > desktop.
> > > > In mobile shows a button on the right side that make the menu
> > slide
> > > from
> > > > the right
> > > > * Now we have search functionality implemented thanks to
> > Algolia
> > > search.
> > > > The index is crawled every 24h. Take into account if you make
> > some
> > > change
> > > > and don't see it when searching as you upload the change.
> > > > * Main menu now turns to dropdown if there's no enough room
> to
> > show
> > > it
> > > > horizontally
> > > >
> > > > About content:
> > > >
> > > > * Added global styles for better readability and support of
> > most of
> > > the
> > > > markdown options and highlighting of code (specially for AS3
> > and
> > > MXML)
> > > > * Now all pages has "description" and "permalink" in the head
> > > section to
> > > > improve sharing and searching on internet. Remember to add
> this
> > > lines so we
> > > > make all navigation consistent with the rest of pages. If
> > someone
> > > notice a
> > > > page without this, please add it or report it.
> > > > * Added metadata for sharing in social networks more easily
> > > capturing the
> > > > previous point plus screenshot and name.
> > > > * I tried to bring pages to the index that was still missing
> > so we
> > > have
> > > > most of the overall structure in place. I'm pretty sure
> > there's still
> > > > missing concepts and things to bring to the docs, so keep
> your
> > eyes
> > > open to
> > > > see what could still be missing and report it or add
> yourself.
> > > > * Notice that some of that content is still a page mostly
> > empty and
> > > waiting
> > > > to be filled. You're all invited to do so, just let others
> know
> > > about it to
> > > > avoid duplicate efforts.
> > > > * For Component Sets, I started to create a page per
> component
> > where
> > > we add
> > > > the most needed info to start with the component. 

Testimonials Page (Was: Re: About Royale Docs Improvements over latest months)

2019-10-01 Thread Carlos Rovira
Hi all,

we are talking about add a new "Testimonials" page were people could share
"How ApacheRoyale has helped" (you, your project, your company...) with a
new app, or a migration from Flex.

Please submit to this thread a phrase or a paragraph that will capture that
topic for you and help us to fill that page with useful information for
others that come to Apache Royale.
(Note: Take into account that anyone that do this contribution is under the
assumption that allows us to use his phrase, name and info submitted in out
website as a Testimonial in that page and submitting implies give us
permission to do that :))

Please provide an image as well for the profile. It can be your portrait,
or if you don't want your photo in our website, you can send us other
image(photo, logo or graphic) that represents you, to enhance the
testimonial. We reserve the option to use it or not depending on the image
provided if we think is not appropriate or could infringe some copyright or
rule. For this reason, please try to use original content and nothing that
could be offensive or problematic with any of the Apache rules or the
common sense :)

This will help others to decide to join us or use Royale since others had
success in using it.

Thanks all for your contribution to this page!! That will be of great help!
:)

Carlos



El mar., 1 oct. 2019 a las 20:39, Carlos Rovira ()
escribió:

> Hi,
> we can add testimonials page (as an additional page a part from showcase
> page). The actual theme has that integrated that will be easy to do.
> Will start a thread so others can write its own testimonial to be added.
>
> Thanks for the suggestion :)
>
>
>
> El mar., 1 oct. 2019 a las 19:37, Alex Harui ()
> escribió:
>
>> The showcase would be great, but if it is easier/faster to simply have a
>> page of links to blogs of our committers like you and Harbs that just
>> contain a paragraph or two about how Royale has helped, that might be a
>> good place to start.
>>
>> -Alex
>>
>> On 10/1/19, 10:02 AM, "Carlos Rovira"  wrote:
>>
>> Hi Alex,
>>
>> El mar., 1 oct. 2019 a las 17:50, Alex Harui
>> ()
>> escribió:
>>
>> > Thanks for working on the docs.
>> >
>> > Beyond the docs, what I would most like to see is "success
>> stories".  I
>> > keep thinking it would help if it was easier for folks to read
>> about how
>> > Royale has helped.
>> >
>>
>> You refer to "showcase" page?
>>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2Fdata=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3Dreserved=0
>> I still has that on my plate. I have to plan the info to showcase and
>> post
>> so people can submit about it
>> But yes is one of the important pieces to work on. I'll try to get
>> over it
>> soon.
>>
>> thanks
>>
> --
Carlos Rovira
http://about.me/carlosrovira


Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Andrew Wetmore
I have not forgotten "Royale in a Week", the reworking of "Flex in a Week"
which I undertook to do. Will be working on that.

On Tue, Oct 1, 2019 at 2:37 PM Alex Harui  wrote:

> The showcase would be great, but if it is easier/faster to simply have a
> page of links to blogs of our committers like you and Harbs that just
> contain a paragraph or two about how Royale has helped, that might be a
> good place to start.
>
> -Alex
>
> On 10/1/19, 10:02 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> El mar., 1 oct. 2019 a las 17:50, Alex Harui ( >)
> escribió:
>
> > Thanks for working on the docs.
> >
> > Beyond the docs, what I would most like to see is "success
> stories".  I
> > keep thinking it would help if it was easier for folks to read about
> how
> > Royale has helped.
> >
>
> You refer to "showcase" page?
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2Fdata=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3Dreserved=0
> I still has that on my plate. I have to plan the info to showcase and
> post
> so people can submit about it
> But yes is one of the important pieces to work on. I'll try to get
> over it
> soon.
>
> thanks
>
>
> > My 2 cents,
> > -Alex
> >
> > On 10/1/19, 3:54 AM, "Andrew Wetmore"  wrote:
> >
> > This is great progress!
> >
> > I think one other area where we are still very thin is on using
> > RoyaleUnit
> > for testing.
> >
> > On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > about latest changes in docs done is latest months. This is a
> > summary of
> > > the work done (still in progress at some points):
> > >
> > > About layout, search and usability:
> > >
> > > * Now we have a more polished layout that should work right on
> > desktop,
> > > tablet and mobile, making more easy for new users coming to
> Royale
> > learn
> > > about it
> > > * The sidebar menu will show on the right as normal in tablet
> and
> > desktop.
> > > In mobile shows a button on the right side that make the menu
> slide
> > from
> > > the right
> > > * Now we have search functionality implemented thanks to
> Algolia
> > search.
> > > The index is crawled every 24h. Take into account if you make
> some
> > change
> > > and don't see it when searching as you upload the change.
> > > * Main menu now turns to dropdown if there's no enough room to
> show
> > it
> > > horizontally
> > >
> > > About content:
> > >
> > > * Added global styles for better readability and support of
> most of
> > the
> > > markdown options and highlighting of code (specially for AS3
> and
> > MXML)
> > > * Now all pages has "description" and "permalink" in the head
> > section to
> > > improve sharing and searching on internet. Remember to add this
> > lines so we
> > > make all navigation consistent with the rest of pages. If
> someone
> > notice a
> > > page without this, please add it or report it.
> > > * Added metadata for sharing in social networks more easily
> > capturing the
> > > previous point plus screenshot and name.
> > > * I tried to bring pages to the index that was still missing
> so we
> > have
> > > most of the overall structure in place. I'm pretty sure
> there's still
> > > missing concepts and things to bring to the docs, so keep your
> eyes
> > open to
> > > see what could still be missing and report it or add yourself.
> > > * Notice that some of that content is still a page mostly
> empty and
> > waiting
> > > to be filled. You're all invited to do so, just let others know
> > about it to
> > > avoid duplicate efforts.
> > > * For Component Sets, I started to create a page per component
> where
> > we add
> > > the most needed info to start with the component. It then
> refers to
> > ASDocs
> > > for a full spec and access to all classes. I'm working on
> Jewel.
> > Others are
> > > invited to use Jewel finished pages and use it as template for
> Basic,
> > > MXRoyale and other sets, and/or create new ones for components
> that
> > are not
> > > similar and there's no counterpart on Jewel.
> > > * I added live content on Jewel components, since visual
> running
> > examples
> > > are very powerful.
> > > * I added live example on the GitHub tutorial app.
> > > * I added 

Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Carlos Rovira
Hi,
we can add testimonials page (as an additional page a part from showcase
page). The actual theme has that integrated that will be easy to do.
Will start a thread so others can write its own testimonial to be added.

Thanks for the suggestion :)



El mar., 1 oct. 2019 a las 19:37, Alex Harui ()
escribió:

> The showcase would be great, but if it is easier/faster to simply have a
> page of links to blogs of our committers like you and Harbs that just
> contain a paragraph or two about how Royale has helped, that might be a
> good place to start.
>
> -Alex
>
> On 10/1/19, 10:02 AM, "Carlos Rovira"  wrote:
>
> Hi Alex,
>
> El mar., 1 oct. 2019 a las 17:50, Alex Harui ( >)
> escribió:
>
> > Thanks for working on the docs.
> >
> > Beyond the docs, what I would most like to see is "success
> stories".  I
> > keep thinking it would help if it was easier for folks to read about
> how
> > Royale has helped.
> >
>
> You refer to "showcase" page?
>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2Fdata=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3Dreserved=0
> I still has that on my plate. I have to plan the info to showcase and
> post
> so people can submit about it
> But yes is one of the important pieces to work on. I'll try to get
> over it
> soon.
>
> thanks
>
>
> > My 2 cents,
> > -Alex
> >
> > On 10/1/19, 3:54 AM, "Andrew Wetmore"  wrote:
> >
> > This is great progress!
> >
> > I think one other area where we are still very thin is on using
> > RoyaleUnit
> > for testing.
> >
> > On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > about latest changes in docs done is latest months. This is a
> > summary of
> > > the work done (still in progress at some points):
> > >
> > > About layout, search and usability:
> > >
> > > * Now we have a more polished layout that should work right on
> > desktop,
> > > tablet and mobile, making more easy for new users coming to
> Royale
> > learn
> > > about it
> > > * The sidebar menu will show on the right as normal in tablet
> and
> > desktop.
> > > In mobile shows a button on the right side that make the menu
> slide
> > from
> > > the right
> > > * Now we have search functionality implemented thanks to
> Algolia
> > search.
> > > The index is crawled every 24h. Take into account if you make
> some
> > change
> > > and don't see it when searching as you upload the change.
> > > * Main menu now turns to dropdown if there's no enough room to
> show
> > it
> > > horizontally
> > >
> > > About content:
> > >
> > > * Added global styles for better readability and support of
> most of
> > the
> > > markdown options and highlighting of code (specially for AS3
> and
> > MXML)
> > > * Now all pages has "description" and "permalink" in the head
> > section to
> > > improve sharing and searching on internet. Remember to add this
> > lines so we
> > > make all navigation consistent with the rest of pages. If
> someone
> > notice a
> > > page without this, please add it or report it.
> > > * Added metadata for sharing in social networks more easily
> > capturing the
> > > previous point plus screenshot and name.
> > > * I tried to bring pages to the index that was still missing
> so we
> > have
> > > most of the overall structure in place. I'm pretty sure
> there's still
> > > missing concepts and things to bring to the docs, so keep your
> eyes
> > open to
> > > see what could still be missing and report it or add yourself.
> > > * Notice that some of that content is still a page mostly
> empty and
> > waiting
> > > to be filled. You're all invited to do so, just let others know
> > about it to
> > > avoid duplicate efforts.
> > > * For Component Sets, I started to create a page per component
> where
> > we add
> > > the most needed info to start with the component. It then
> refers to
> > ASDocs
> > > for a full spec and access to all classes. I'm working on
> Jewel.
> > Others are
> > > invited to use Jewel finished pages and use it as template for
> Basic,
> > > MXRoyale and other sets, and/or create new ones for components
> that
> > are not
> > > similar and there's no counterpart on Jewel.
> > > * I added live content on Jewel components, since visual
> running
> 

Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Alex Harui
The showcase would be great, but if it is easier/faster to simply have a page 
of links to blogs of our committers like you and Harbs that just contain a 
paragraph or two about how Royale has helped, that might be a good place to 
start.

-Alex

On 10/1/19, 10:02 AM, "Carlos Rovira"  wrote:

Hi Alex,

El mar., 1 oct. 2019 a las 17:50, Alex Harui ()
escribió:

> Thanks for working on the docs.
>
> Beyond the docs, what I would most like to see is "success stories".  I
> keep thinking it would help if it was easier for folks to read about how
> Royale has helped.
>

You refer to "showcase" page?

https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Froyale.apache.org%2Fshowcase%2Fdata=02%7C01%7Caharui%40adobe.com%7C2738afd6ca5c4c4807bf08d746912887%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055461576181142sdata=%2BN%2FcdilLG3C%2F2wPoJHWts04%2FxO0%2BVDRlqtW%2Bw%2BMrh9I%3Dreserved=0
I still has that on my plate. I have to plan the info to showcase and post
so people can submit about it
But yes is one of the important pieces to work on. I'll try to get over it
soon.

thanks


> My 2 cents,
> -Alex
>
> On 10/1/19, 3:54 AM, "Andrew Wetmore"  wrote:
>
> This is great progress!
>
> I think one other area where we are still very thin is on using
> RoyaleUnit
> for testing.
>
> On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > about latest changes in docs done is latest months. This is a
> summary of
> > the work done (still in progress at some points):
> >
> > About layout, search and usability:
> >
> > * Now we have a more polished layout that should work right on
> desktop,
> > tablet and mobile, making more easy for new users coming to Royale
> learn
> > about it
> > * The sidebar menu will show on the right as normal in tablet and
> desktop.
> > In mobile shows a button on the right side that make the menu slide
> from
> > the right
> > * Now we have search functionality implemented thanks to Algolia
> search.
> > The index is crawled every 24h. Take into account if you make some
> change
> > and don't see it when searching as you upload the change.
> > * Main menu now turns to dropdown if there's no enough room to show
> it
> > horizontally
> >
> > About content:
> >
> > * Added global styles for better readability and support of most of
> the
> > markdown options and highlighting of code (specially for AS3 and
> MXML)
> > * Now all pages has "description" and "permalink" in the head
> section to
> > improve sharing and searching on internet. Remember to add this
> lines so we
> > make all navigation consistent with the rest of pages. If someone
> notice a
> > page without this, please add it or report it.
> > * Added metadata for sharing in social networks more easily
> capturing the
> > previous point plus screenshot and name.
> > * I tried to bring pages to the index that was still missing so we
> have
> > most of the overall structure in place. I'm pretty sure there's 
still
> > missing concepts and things to bring to the docs, so keep your eyes
> open to
> > see what could still be missing and report it or add yourself.
> > * Notice that some of that content is still a page mostly empty and
> waiting
> > to be filled. You're all invited to do so, just let others know
> about it to
> > avoid duplicate efforts.
> > * For Component Sets, I started to create a page per component where
> we add
> > the most needed info to start with the component. It then refers to
> ASDocs
> > for a full spec and access to all classes. I'm working on Jewel.
> Others are
> > invited to use Jewel finished pages and use it as template for 
Basic,
> > MXRoyale and other sets, and/or create new ones for components that
> are not
> > similar and there's no counterpart on Jewel.
> > * I added live content on Jewel components, since visual running
> examples
> > are very powerful.
> > * I added live example on the GitHub tutorial app.
> > * I added many cross link references between Royale-docs, blog
> examples and
> > ASDocs pages. Content must be in only one place but that content
> should be
> > linked with the rest of royale contents in our network.
> > * I tried to format all the pages I could to get most of the new
> visuals
> > created, but I'm sure threr's still content to format, we can do 
this
> > between all here, and 

Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Carlos Rovira
Hi Alex,

El mar., 1 oct. 2019 a las 17:50, Alex Harui ()
escribió:

> Thanks for working on the docs.
>
> Beyond the docs, what I would most like to see is "success stories".  I
> keep thinking it would help if it was easier for folks to read about how
> Royale has helped.
>

You refer to "showcase" page?
https://royale.apache.org/showcase/
I still has that on my plate. I have to plan the info to showcase and post
so people can submit about it
But yes is one of the important pieces to work on. I'll try to get over it
soon.

thanks


> My 2 cents,
> -Alex
>
> On 10/1/19, 3:54 AM, "Andrew Wetmore"  wrote:
>
> This is great progress!
>
> I think one other area where we are still very thin is on using
> RoyaleUnit
> for testing.
>
> On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira 
> wrote:
>
> > Hi,
> >
> > about latest changes in docs done is latest months. This is a
> summary of
> > the work done (still in progress at some points):
> >
> > About layout, search and usability:
> >
> > * Now we have a more polished layout that should work right on
> desktop,
> > tablet and mobile, making more easy for new users coming to Royale
> learn
> > about it
> > * The sidebar menu will show on the right as normal in tablet and
> desktop.
> > In mobile shows a button on the right side that make the menu slide
> from
> > the right
> > * Now we have search functionality implemented thanks to Algolia
> search.
> > The index is crawled every 24h. Take into account if you make some
> change
> > and don't see it when searching as you upload the change.
> > * Main menu now turns to dropdown if there's no enough room to show
> it
> > horizontally
> >
> > About content:
> >
> > * Added global styles for better readability and support of most of
> the
> > markdown options and highlighting of code (specially for AS3 and
> MXML)
> > * Now all pages has "description" and "permalink" in the head
> section to
> > improve sharing and searching on internet. Remember to add this
> lines so we
> > make all navigation consistent with the rest of pages. If someone
> notice a
> > page without this, please add it or report it.
> > * Added metadata for sharing in social networks more easily
> capturing the
> > previous point plus screenshot and name.
> > * I tried to bring pages to the index that was still missing so we
> have
> > most of the overall structure in place. I'm pretty sure there's still
> > missing concepts and things to bring to the docs, so keep your eyes
> open to
> > see what could still be missing and report it or add yourself.
> > * Notice that some of that content is still a page mostly empty and
> waiting
> > to be filled. You're all invited to do so, just let others know
> about it to
> > avoid duplicate efforts.
> > * For Component Sets, I started to create a page per component where
> we add
> > the most needed info to start with the component. It then refers to
> ASDocs
> > for a full spec and access to all classes. I'm working on Jewel.
> Others are
> > invited to use Jewel finished pages and use it as template for Basic,
> > MXRoyale and other sets, and/or create new ones for components that
> are not
> > similar and there's no counterpart on Jewel.
> > * I added live content on Jewel components, since visual running
> examples
> > are very powerful.
> > * I added live example on the GitHub tutorial app.
> > * I added many cross link references between Royale-docs, blog
> examples and
> > ASDocs pages. Content must be in only one place but that content
> should be
> > linked with the rest of royale contents in our network.
> > * I tried to format all the pages I could to get most of the new
> visuals
> > created, but I'm sure threr's still content to format, we can do this
> > between all here, and anyone coming to Royale and browse content is
> invited
> > to help in this point as well to submit more content to be reviewed
> and
> > added.
> > * I refactored all license pages to make all consistent with one
> style.
> >
> > To Help:
> >
> > I think there's many content already done and formatted in the right
> way to
> > make others be able to add content that aligns to the rest of the doc
> > pages. Andrew and I are here to help to give the finished results
> that
> > conform to actual specs.
> >
> > There's still many things to do to get a full docs site. This is the
> list
> > of things I see:
> >
> > * Fill Features and concepts pages still empty (View States, Data
> Binding,
> > RPC methods pages, ). I think this can be the most important
> ones since
> > are core concepts in Royale.
> > * Complete Jewel and other sets reference pages. Very important for
> people
> > coming. Here I plan to add for Jewel "style 

Re: ASDoc fails to compile with ANT

2019-10-01 Thread Carlos Rovira
Seem all is ok. As Alex pointed, I forgot to restore env vars after testing
RC3.
So seems dev version is ok just seems to have many warnings:

https://paste.apache.org/fsev9

if you think is ok, I can upload changes for ASDoc to website (unless you
think there's something needed from release branch)

thanks


El mar., 1 oct. 2019 a las 17:46, Piotr Zarzycki ()
escribió:

> I will run tomorrow releasecandidate script and see what will happen, so
> expect some merge tomorrow ;)
>
> wt., 1 paź 2019 o 17:41 Alex Harui  napisał(a):
>
> > That was fixed in the release branch.  I think Piotr will merge soon to
> > develop.  For now, define the Adobe environment variables (AIR_HOME,
> > PLAYERGLOBAL_HOME, FLASHPLAYER_DEBUGGER).
> >
> > -Alex
> >
> > On 10/1/19, 3:39 AM, "Carlos Rovira"  wrote:
> >
> > Hi,
> >
> > I tried to run ASDoc to update site with latest reference. I remember
> > that
> > ASDoc can only be compiled right with ANT.
> > This is what I get after run "ant" in ASDoc folder:
> >
> > build_example.check-air:
> >
> >
> > build_example.copy-app-xml:
> >
> >
> > main:
> >
> >
> > json:
> >
> >  [echo] ROYALE_COMPILER_HOME:
> > /Users/carlosrovira/Dev/Royale/Source/royale-asjs/js
> >
> >  [java] 0.673472226 seconds
> >
> >  [java]
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml(145):
> > col: 0 unable to open
> >
> >
> '/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config//11.1'.
> >
> >  [java]
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> > (line: 145)
> >
> >  [java]
> >
> >  [java]   
> >
> >  [java]
> >
> >  [java]
> >
> >  [java] Java Result: 5
> >
> >
> > BUILD FAILED
> >
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:48:
> > The following error occurred while executing this line:
> >
> >
> >
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:107:
> > condition satisfied
> >
> >
> > Total time: 14 seconds
> >
> >
> >
> > I suppose that some of the latest changes in building must be
> > propagated to
> > ASDoc as well.
> >
> >
> > Can someone take a look to see what could be the problem?
> >
> >
> > thanks
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C3c194c67a3ff4cbbc02508d7465baa7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637055231831849685sdata=wUmzvVFO%2By9l8G45rJkOKqu3%2FFeid%2FYrvU0f%2Bcfhb80%3Dreserved=0
> >
> >
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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


Re: [RESULT][VOTE] Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Carlos Rovira
Thanks for all the hard work on getting releases more robust.

Probably you'll know better than me, but 0.9.7 could be very easy to do :)

El mar., 1 oct. 2019 a las 14:55, Piotr Zarzycki ()
escribió:

> Vote passes with 4 +1 votes.
>
> Thank you for voting! We are finally having release.
> Piotr
>
> pon., 30 wrz 2019 o 16:23 Piotr Zarzycki 
> napisał(a):
>
> > +1 (Binding)
> >
> > Package
> >
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-src.zip
> > Java 1.8
> > OS: Windows 10 amd64 10.0
> > Source kit signatures match: y
> > Source kit builds: y
> > README is ok: y
> > RELEASE_NOTES is ok: y
> > NOTICE is ok: y
> > LICENSE is ok: y
> > No unapproved licenses or archives: y
> > No unapproved binaries: y
> >
> > Package
> >
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/binaries/apache-royale-0.9.6-bin-js-swf.zip
> > Binary kit signatures match: y
> > NOTICE is ok: y
> > LICENSE is ok: y
> > No unapproved licenses or archives in binary package: y
> > No unapproved binaries in binary package: y
> >
> > Additionally I was able build and run big Apache Royale application
> > I was able build PureMVC source code to swc.
> >
> > sob., 28 wrz 2019 o 02:40 Carlos Rovira 
> > napisał(a):
> >
> >> +1
> >>
> >> approve:
> >>
> >>
> >> +1
> >>
> >> Package
> >>
> >>
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-src.tar.gz
> >>
> >> Java 1.8
> >>
> >> OS: Mac OS X x86_64 10.14.6
> >>
> >> Source kit signatures match: y
> >>
> >> Source kit builds: y
> >>
> >> README is ok: y
> >>
> >> RELEASE_NOTES is ok: y
> >>
> >> NOTICE is ok: y
> >>
> >> LICENSE is ok: y
> >>
> >> No unapproved licenses or archives: y
> >>
> >> No unapproved binaries: y
> >>
> >>
> >> Package
> >>
> >>
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
> >>
> >> Binary kit signatures match: y
> >>
> >> NOTICE is ok: y
> >>
> >> LICENSE is ok: y
> >>
> >> No unapproved licenses or archives in binary package: y
> >>
> >> No unapproved binaries in binary package: y
> >>
> >>
> >>
> >>
> >> El jue., 26 sept. 2019 a las 21:05, Alex Harui
> ( >> >)
> >> escribió:
> >>
> >> > +1
> >> > Package
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-src.tar.gz
> >> > Java 1.8
> >> > OS: Mac OS X x86_64 10.12.6
> >> > Source kit signatures match: y
> >> > Source kit builds: y
> >> > README is ok: y
> >> > RELEASE_NOTES is ok: y
> >> > NOTICE is ok: y
> >> > LICENSE is ok: y
> >> > No unapproved licenses or archives: y
> >> > No unapproved binaries: y
> >> >
> >> > Package
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
> >> > Binary kit signatures match: y
> >> > NOTICE is ok: y
> >> > LICENSE is ok: y
> >> > No unapproved licenses or archives in binary package: y
> >> > No unapproved binaries in binary package: y
> >> >
> >> > I tested with both a clean js-only and clean js-swf configuration.
> >> >
> >> > -Alex
> >> >
> >> > On 9/25/19, 7:23 AM, "Apache Royale CI Server" <
> >> apacheroyal...@gmail.com>
> >> > wrote:
> >> >
> >> > Hi,
> >> >
> >> > This is the vote for the 0.9.6 release of Apache Royale.
> >> >
> >> > The release candidate can be found here;
> >> >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.6%2Frc3%2Fdata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=7mgOGrzL7RpQR%2FmCwIrw1EZzmUN2UpfkqvuuXPcVTDo%3Dreserved=0
> >> >
> >> > Before voting please review the section,'What are the ASF
> >> requirements
> >> > on
> >> > approving a release?', at:
> >> >
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-releasedata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=svKLd3TVFay9L5Yupvom3se2fcfyEG3ak8sw9vrUn7I%3Dreserved=0
> >> >
> >> > At a minimum you would be expected to check that:
> >> > - SHA and signed packages are correct
> >> > - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> >> > - That the build script completes successfully
> >> > - That you can compile and cross-compile a simple example using
> the
> >> > SDK.
> >> >
> >> > The KEYS file is at
> >> >
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2FKEYSdata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=v%2FZGMgkMvSEuznLYzRE%2FTTIWOPBLU20CS1C2pd2FFhs%3Dreserved=0
> >> >
> >> > The source package is a combination of the 3 main Royale repos.
> >> >
> >> > To use the binary package, unzip it into a 

Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Alex Harui
Thanks for working on the docs.

Beyond the docs, what I would most like to see is "success stories".  I keep 
thinking it would help if it was easier for folks to read about how Royale has 
helped.

My 2 cents,
-Alex

On 10/1/19, 3:54 AM, "Andrew Wetmore"  wrote:

This is great progress!

I think one other area where we are still very thin is on using RoyaleUnit
for testing.

On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira 
wrote:

> Hi,
>
> about latest changes in docs done is latest months. This is a summary of
> the work done (still in progress at some points):
>
> About layout, search and usability:
>
> * Now we have a more polished layout that should work right on desktop,
> tablet and mobile, making more easy for new users coming to Royale learn
> about it
> * The sidebar menu will show on the right as normal in tablet and desktop.
> In mobile shows a button on the right side that make the menu slide from
> the right
> * Now we have search functionality implemented thanks to Algolia search.
> The index is crawled every 24h. Take into account if you make some change
> and don't see it when searching as you upload the change.
> * Main menu now turns to dropdown if there's no enough room to show it
> horizontally
>
> About content:
>
> * Added global styles for better readability and support of most of the
> markdown options and highlighting of code (specially for AS3 and MXML)
> * Now all pages has "description" and "permalink" in the head section to
> improve sharing and searching on internet. Remember to add this lines so 
we
> make all navigation consistent with the rest of pages. If someone notice a
> page without this, please add it or report it.
> * Added metadata for sharing in social networks more easily capturing the
> previous point plus screenshot and name.
> * I tried to bring pages to the index that was still missing so we have
> most of the overall structure in place. I'm pretty sure there's still
> missing concepts and things to bring to the docs, so keep your eyes open 
to
> see what could still be missing and report it or add yourself.
> * Notice that some of that content is still a page mostly empty and 
waiting
> to be filled. You're all invited to do so, just let others know about it 
to
> avoid duplicate efforts.
> * For Component Sets, I started to create a page per component where we 
add
> the most needed info to start with the component. It then refers to ASDocs
> for a full spec and access to all classes. I'm working on Jewel. Others 
are
> invited to use Jewel finished pages and use it as template for Basic,
> MXRoyale and other sets, and/or create new ones for components that are 
not
> similar and there's no counterpart on Jewel.
> * I added live content on Jewel components, since visual running examples
> are very powerful.
> * I added live example on the GitHub tutorial app.
> * I added many cross link references between Royale-docs, blog examples 
and
> ASDocs pages. Content must be in only one place but that content should be
> linked with the rest of royale contents in our network.
> * I tried to format all the pages I could to get most of the new visuals
> created, but I'm sure threr's still content to format, we can do this
> between all here, and anyone coming to Royale and browse content is 
invited
> to help in this point as well to submit more content to be reviewed and
> added.
> * I refactored all license pages to make all consistent with one style.
>
> To Help:
>
> I think there's many content already done and formatted in the right way 
to
> make others be able to add content that aligns to the rest of the doc
> pages. Andrew and I are here to help to give the finished results that
> conform to actual specs.
>
> There's still many things to do to get a full docs site. This is the list
> of things I see:
>
> * Fill Features and concepts pages still empty (View States, Data Binding,
> RPC methods pages, ). I think this can be the most important ones 
since
> are core concepts in Royale.
> * Complete Jewel and other sets reference pages. Very important for people
> coming. Here I plan to add for Jewel "style specs" too as someone 
mentioned
> some days ago, and I think this will be a very good idea.
> * Add Crux documentation, that should come in part from swiz framework 
docs
>
> What more things you still think are missing?
>
> Thanks
>
>
> --
> Carlos Rovira
> 

Re: ASDoc fails to compile with ANT

2019-10-01 Thread Piotr Zarzycki
I will run tomorrow releasecandidate script and see what will happen, so
expect some merge tomorrow ;)

wt., 1 paź 2019 o 17:41 Alex Harui  napisał(a):

> That was fixed in the release branch.  I think Piotr will merge soon to
> develop.  For now, define the Adobe environment variables (AIR_HOME,
> PLAYERGLOBAL_HOME, FLASHPLAYER_DEBUGGER).
>
> -Alex
>
> On 10/1/19, 3:39 AM, "Carlos Rovira"  wrote:
>
> Hi,
>
> I tried to run ASDoc to update site with latest reference. I remember
> that
> ASDoc can only be compiled right with ANT.
> This is what I get after run "ant" in ASDoc folder:
>
> build_example.check-air:
>
>
> build_example.copy-app-xml:
>
>
> main:
>
>
> json:
>
>  [echo] ROYALE_COMPILER_HOME:
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/js
>
>  [java] 0.673472226 seconds
>
>  [java]
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml(145):
> col: 0 unable to open
>
> '/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config//11.1'.
>
>  [java]
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
> (line: 145)
>
>  [java]
>
>  [java]   
>
>  [java]
>
>  [java]
>
>  [java] Java Result: 5
>
>
> BUILD FAILED
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:48:
> The following error occurred while executing this line:
>
>
> /Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:107:
> condition satisfied
>
>
> Total time: 14 seconds
>
>
>
> I suppose that some of the latest changes in building must be
> propagated to
> ASDoc as well.
>
>
> Can someone take a look to see what could be the problem?
>
>
> thanks
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C3c194c67a3ff4cbbc02508d7465baa7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637055231831849685sdata=wUmzvVFO%2By9l8G45rJkOKqu3%2FFeid%2FYrvU0f%2Bcfhb80%3Dreserved=0
>
>
>

-- 

Piotr Zarzycki

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


Re: ASDoc fails to compile with ANT

2019-10-01 Thread Alex Harui
That was fixed in the release branch.  I think Piotr will merge soon to 
develop.  For now, define the Adobe environment variables (AIR_HOME, 
PLAYERGLOBAL_HOME, FLASHPLAYER_DEBUGGER).

-Alex

On 10/1/19, 3:39 AM, "Carlos Rovira"  wrote:

Hi,

I tried to run ASDoc to update site with latest reference. I remember that
ASDoc can only be compiled right with ANT.
This is what I get after run "ant" in ASDoc folder:

build_example.check-air:


build_example.copy-app-xml:


main:


json:

 [echo] ROYALE_COMPILER_HOME:
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/js

 [java] 0.673472226 seconds

 [java]

/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml(145):
col: 0 unable to open

'/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config//11.1'.

 [java]

/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
(line: 145)

 [java]

 [java]   

 [java]

 [java]

 [java] Java Result: 5


BUILD FAILED


/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:48:
The following error occurred while executing this line:


/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:107:
condition satisfied


Total time: 14 seconds



I suppose that some of the latest changes in building must be propagated to
ASDoc as well.


Can someone take a look to see what could be the problem?


thanks

-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C3c194c67a3ff4cbbc02508d7465baa7b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637055231831849685sdata=wUmzvVFO%2By9l8G45rJkOKqu3%2FFeid%2FYrvU0f%2Bcfhb80%3Dreserved=0




Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Alex Harui
Releasecandidate.xml can't do steps on repository.apache.org.  It will remind 
you to go there and release the staged artifacts.

-Alex

On 10/1/19, 6:55 AM, "Piotr Zarzycki"  wrote:

I see that releasecandidate.xml script can help me with last steps. Does it
doing Maven releases as well ?
That steps includes also push to svn - I just did it manually, so I will
probably comment out commit part and run script. - I think tomorrow.

wt., 1 paź 2019 o 09:29 Piotr Zarzycki 
napisał(a):

> Hi Om,
>
> What I need to do in order to release stuff on npm. Can you do this for me
> once I push release to svn ?
>
> Thanks,
> Piotr
>
> wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
> napisał(a):
>
>> Hi Harbs,
>>
>> I think we have enough votes. I still have to gather info how actually
>> release Maven artifacts. However I'm going to push binaries today in svn.
>>
>> Thanks,
>> Piotr
>>
>> sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):
>>
>>> FYI, I will not be able to test the release until Wednesday.
>>>
>>> If the vote is still open, I plan on testing then.
>>>
>>> Thanks,
>>> Harbs
>>>
>>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki 

>>> wrote:
>>> >
>>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>>> myself
>>> > yet, but will do that tomorrow or next week.
>>> >
>>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>>> apacheroyal...@gmail.com>
>>> > napisał(a):
>>> >
>>> >> This is the discussion thread.
>>> >>
>>> >> Thanks,
>>> >> Piotr
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3Dreserved=0
>>> > 
*
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3Dreserved=0
>> 
*
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3Dreserved=0
> 
*
>


-- 

Piotr Zarzycki

Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7C6393850c281646e4a2fd08d74676fc91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055349164603152sdata=2bHGyBtNo%2Fae9L07W688ICEXmgEMk9tHNY63WzHcv%2Bw%3Dreserved=0

*




Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Alex Harui
The releasecandidate.xml script will tell you what to do on 
repository.apache.org to release the Maven stuff, and release the npm stuff as 
well.  The whole point of these scripts is so you don't have to ask for help.  
If you do end up needing help, then the scripts need improving.  We want to 
capture knowledge in these scripts and on the wiki.

-Alex

On 10/1/19, 12:30 AM, "Piotr Zarzycki"  wrote:

Hi Om,

What I need to do in order to release stuff on npm. Can you do this for me
once I push release to svn ?

Thanks,
Piotr

wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
napisał(a):

> Hi Harbs,
>
> I think we have enough votes. I still have to gather info how actually
> release Maven artifacts. However I'm going to push binaries today in svn.
>
> Thanks,
> Piotr
>
> sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):
>
>> FYI, I will not be able to test the release until Wednesday.
>>
>> If the vote is still open, I plan on testing then.
>>
>> Thanks,
>> Harbs
>>
>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki 
>> wrote:
>> >
>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>> myself
>> > yet, but will do that tomorrow or next week.
>> >
>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>> apacheroyal...@gmail.com>
>> > napisał(a):
>> >
>> >> This is the discussion thread.
>> >>
>> >> Thanks,
>> >> Piotr
>> >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
>> > 
*
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0
> 
*
>


-- 

Piotr Zarzycki

Patreon: 
*https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzyckidata=02%7C01%7Caharui%40adobe.com%7Caf00b9a67e8c4b44d80a08d746412ce3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637055118045596516sdata=Aa%2Fw%2BVPv2UEsCiAvAOywY4Hn7mFl8yXVBAeLHrl39nA%3Dreserved=0

*




Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Piotr Zarzycki
I see that releasecandidate.xml script can help me with last steps. Does it
doing Maven releases as well ?
That steps includes also push to svn - I just did it manually, so I will
probably comment out commit part and run script. - I think tomorrow.

wt., 1 paź 2019 o 09:29 Piotr Zarzycki 
napisał(a):

> Hi Om,
>
> What I need to do in order to release stuff on npm. Can you do this for me
> once I push release to svn ?
>
> Thanks,
> Piotr
>
> wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
> napisał(a):
>
>> Hi Harbs,
>>
>> I think we have enough votes. I still have to gather info how actually
>> release Maven artifacts. However I'm going to push binaries today in svn.
>>
>> Thanks,
>> Piotr
>>
>> sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):
>>
>>> FYI, I will not be able to test the release until Wednesday.
>>>
>>> If the vote is still open, I plan on testing then.
>>>
>>> Thanks,
>>> Harbs
>>>
>>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki 
>>> wrote:
>>> >
>>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>>> myself
>>> > yet, but will do that tomorrow or next week.
>>> >
>>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>>> apacheroyal...@gmail.com>
>>> > napisał(a):
>>> >
>>> >> This is the discussion thread.
>>> >>
>>> >> Thanks,
>>> >> Piotr
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > Piotr Zarzycki
>>> >
>>> > Patreon: *https://www.patreon.com/piotrzarzycki
>>> > *
>>>
>>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

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


Build failed in Jenkins: royale-asjs #2757

2019-10-01 Thread Apache Royale CI Server
See 


--
[...truncated 1.19 MB...]
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var http = require('http');
 [java]^^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:24: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var tls = require('tls');
 [java]   ^^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [https]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = https;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [net]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [net]:219: WARNING - name module is not defined in the 
externs.
 [java] module.exports = net;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [os]:113: WARNING - name module is not defined in the 
externs.
 [java] module.exports = os;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [path]:97: WARNING - name module is not defined in the 
externs.
 [java] module.exports = path;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [punycode]:74: WARNING - name module is not defined in the 
externs.
 [java] module.exports = punycode;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [querystring]:66: WARNING - name module is not defined in 
the externs.
 [java] module.exports = querystring;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:22: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [readline]:84: WARNING - name module is not defined in the 
externs.
 [java] module.exports = readline;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:23: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:24: WARNING - accessing name require in externs has 
no effect. Perhaps you forgot to add a var keyword?
 [java] var stream = require('stream');
 [java]  ^^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [repl]:48: WARNING - name module is not defined in the 
externs.
 [java] module.exports = repl;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:23: WARNING - accessing name require in externs 
has no effect. Perhaps you forgot to add a var keyword?
 [java] var events = require('events');
 [java]  ^^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 
com.google.javascript.jscomp.LoggerErrorManager println
 [java] WARNING: [stream]:254: WARNING - name module is not defined in the 
externs.
 [java] module.exports = stream;
 [java] ^^
 [java] 
 [java] Oct 01, 2019 12:41:49 PM 

[RESULT][VOTE] Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Piotr Zarzycki
Vote passes with 4 +1 votes.

Thank you for voting! We are finally having release.
Piotr

pon., 30 wrz 2019 o 16:23 Piotr Zarzycki 
napisał(a):

> +1 (Binding)
>
> Package
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-src.zip
> Java 1.8
> OS: Windows 10 amd64 10.0
> Source kit signatures match: y
> Source kit builds: y
> README is ok: y
> RELEASE_NOTES is ok: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives: y
> No unapproved binaries: y
>
> Package
> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/binaries/apache-royale-0.9.6-bin-js-swf.zip
> Binary kit signatures match: y
> NOTICE is ok: y
> LICENSE is ok: y
> No unapproved licenses or archives in binary package: y
> No unapproved binaries in binary package: y
>
> Additionally I was able build and run big Apache Royale application
> I was able build PureMVC source code to swc.
>
> sob., 28 wrz 2019 o 02:40 Carlos Rovira 
> napisał(a):
>
>> +1
>>
>> approve:
>>
>>
>> +1
>>
>> Package
>>
>> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-src.tar.gz
>>
>> Java 1.8
>>
>> OS: Mac OS X x86_64 10.14.6
>>
>> Source kit signatures match: y
>>
>> Source kit builds: y
>>
>> README is ok: y
>>
>> RELEASE_NOTES is ok: y
>>
>> NOTICE is ok: y
>>
>> LICENSE is ok: y
>>
>> No unapproved licenses or archives: y
>>
>> No unapproved binaries: y
>>
>>
>> Package
>>
>> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
>>
>> Binary kit signatures match: y
>>
>> NOTICE is ok: y
>>
>> LICENSE is ok: y
>>
>> No unapproved licenses or archives in binary package: y
>>
>> No unapproved binaries in binary package: y
>>
>>
>>
>>
>> El jue., 26 sept. 2019 a las 21:05, Alex Harui (> >)
>> escribió:
>>
>> > +1
>> > Package
>> >
>> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/apache-royale-0.9.6-src.tar.gz
>> > Java 1.8
>> > OS: Mac OS X x86_64 10.12.6
>> > Source kit signatures match: y
>> > Source kit builds: y
>> > README is ok: y
>> > RELEASE_NOTES is ok: y
>> > NOTICE is ok: y
>> > LICENSE is ok: y
>> > No unapproved licenses or archives: y
>> > No unapproved binaries: y
>> >
>> > Package
>> >
>> https://dist.apache.org/repos/dist/dev/royale/0.9.6/rc3/binaries/apache-royale-0.9.6-bin-js-swf.tar.gz
>> > Binary kit signatures match: y
>> > NOTICE is ok: y
>> > LICENSE is ok: y
>> > No unapproved licenses or archives in binary package: y
>> > No unapproved binaries in binary package: y
>> >
>> > I tested with both a clean js-only and clean js-swf configuration.
>> >
>> > -Alex
>> >
>> > On 9/25/19, 7:23 AM, "Apache Royale CI Server" <
>> apacheroyal...@gmail.com>
>> > wrote:
>> >
>> > Hi,
>> >
>> > This is the vote for the 0.9.6 release of Apache Royale.
>> >
>> > The release candidate can be found here;
>> >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2F0.9.6%2Frc3%2Fdata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=7mgOGrzL7RpQR%2FmCwIrw1EZzmUN2UpfkqvuuXPcVTDo%3Dreserved=0
>> >
>> > Before voting please review the section,'What are the ASF
>> requirements
>> > on
>> > approving a release?', at:
>> >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-releasedata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=svKLd3TVFay9L5Yupvom3se2fcfyEG3ak8sw9vrUn7I%3Dreserved=0
>> >
>> > At a minimum you would be expected to check that:
>> > - SHA and signed packages are correct
>> > - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
>> > - That the build script completes successfully
>> > - That you can compile and cross-compile a simple example using the
>> > SDK.
>> >
>> > The KEYS file is at
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2FKEYSdata=02%7C01%7Caharui%40adobe.com%7Cb8881952698c4de9211a08d741c3e343%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637050181900826730sdata=v%2FZGMgkMvSEuznLYzRE%2FTTIWOPBLU20CS1C2pd2FFhs%3Dreserved=0
>> >
>> > The source package is a combination of the 3 main Royale repos.
>> >
>> > To use the binary package, unzip it into a folder.  The -js package
>> is
>> > ready-to-use in an IDE or command-line.  If you need SWF output, use
>> > the
>> > -js-swf package and use Apache Ant to run the InstallAdobeSDKs
>> script
>> > via:
>> >   ant -f InstallAdobeSDKs.xml
>> >
>> > You may also get the binary packages via NPM.  The -js package can
>> be
>> > installed via:
>> >
>> > npm install
>> >
>> 

Build failed in Jenkins: royale-asjs_MXTests #1205

2019-10-01 Thread Apache Royale CI Server
See 


Changes:

[piotrzarzycki21] Spark DropDownList: Fix selectedIndex/selectedItem properties

--
[...truncated 1004.49 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[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: 

Re: About Royale Docs Improvements over latest months

2019-10-01 Thread Andrew Wetmore
This is great progress!

I think one other area where we are still very thin is on using RoyaleUnit
for testing.

On Tue, Oct 1, 2019 at 6:56 AM Carlos Rovira 
wrote:

> Hi,
>
> about latest changes in docs done is latest months. This is a summary of
> the work done (still in progress at some points):
>
> About layout, search and usability:
>
> * Now we have a more polished layout that should work right on desktop,
> tablet and mobile, making more easy for new users coming to Royale learn
> about it
> * The sidebar menu will show on the right as normal in tablet and desktop.
> In mobile shows a button on the right side that make the menu slide from
> the right
> * Now we have search functionality implemented thanks to Algolia search.
> The index is crawled every 24h. Take into account if you make some change
> and don't see it when searching as you upload the change.
> * Main menu now turns to dropdown if there's no enough room to show it
> horizontally
>
> About content:
>
> * Added global styles for better readability and support of most of the
> markdown options and highlighting of code (specially for AS3 and MXML)
> * Now all pages has "description" and "permalink" in the head section to
> improve sharing and searching on internet. Remember to add this lines so we
> make all navigation consistent with the rest of pages. If someone notice a
> page without this, please add it or report it.
> * Added metadata for sharing in social networks more easily capturing the
> previous point plus screenshot and name.
> * I tried to bring pages to the index that was still missing so we have
> most of the overall structure in place. I'm pretty sure there's still
> missing concepts and things to bring to the docs, so keep your eyes open to
> see what could still be missing and report it or add yourself.
> * Notice that some of that content is still a page mostly empty and waiting
> to be filled. You're all invited to do so, just let others know about it to
> avoid duplicate efforts.
> * For Component Sets, I started to create a page per component where we add
> the most needed info to start with the component. It then refers to ASDocs
> for a full spec and access to all classes. I'm working on Jewel. Others are
> invited to use Jewel finished pages and use it as template for Basic,
> MXRoyale and other sets, and/or create new ones for components that are not
> similar and there's no counterpart on Jewel.
> * I added live content on Jewel components, since visual running examples
> are very powerful.
> * I added live example on the GitHub tutorial app.
> * I added many cross link references between Royale-docs, blog examples and
> ASDocs pages. Content must be in only one place but that content should be
> linked with the rest of royale contents in our network.
> * I tried to format all the pages I could to get most of the new visuals
> created, but I'm sure threr's still content to format, we can do this
> between all here, and anyone coming to Royale and browse content is invited
> to help in this point as well to submit more content to be reviewed and
> added.
> * I refactored all license pages to make all consistent with one style.
>
> To Help:
>
> I think there's many content already done and formatted in the right way to
> make others be able to add content that aligns to the rest of the doc
> pages. Andrew and I are here to help to give the finished results that
> conform to actual specs.
>
> There's still many things to do to get a full docs site. This is the list
> of things I see:
>
> * Fill Features and concepts pages still empty (View States, Data Binding,
> RPC methods pages, ). I think this can be the most important ones since
> are core concepts in Royale.
> * Complete Jewel and other sets reference pages. Very important for people
> coming. Here I plan to add for Jewel "style specs" too as someone mentioned
> some days ago, and I think this will be a very good idea.
> * Add Crux documentation, that should come in part from swiz framework docs
>
> What more things you still think are missing?
>
> Thanks
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/


ASDoc fails to compile with ANT

2019-10-01 Thread Carlos Rovira
Hi,

I tried to run ASDoc to update site with latest reference. I remember that
ASDoc can only be compiled right with ANT.
This is what I get after run "ant" in ASDoc folder:

build_example.check-air:


build_example.copy-app-xml:


main:


json:

 [echo] ROYALE_COMPILER_HOME:
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/js

 [java] 0.673472226 seconds

 [java]
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml(145):
col: 0 unable to open
'/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config//11.1'.

 [java]
/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/src/main/config/asdoc-js-config.xml
(line: 145)

 [java]

 [java]   

 [java]

 [java]

 [java] Java Result: 5


BUILD FAILED

/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:48:
The following error occurred while executing this line:

/Users/carlosrovira/Dev/Royale/Source/royale-asjs/examples/royale/ASDoc/build.xml:107:
condition satisfied


Total time: 14 seconds



I suppose that some of the latest changes in building must be propagated to
ASDoc as well.


Can someone take a look to see what could be the problem?


thanks

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


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

2019-10-01 Thread Apache Royale CI Server
See 




About Royale Docs Improvements over latest months

2019-10-01 Thread Carlos Rovira
Hi,

about latest changes in docs done is latest months. This is a summary of
the work done (still in progress at some points):

About layout, search and usability:

* Now we have a more polished layout that should work right on desktop,
tablet and mobile, making more easy for new users coming to Royale learn
about it
* The sidebar menu will show on the right as normal in tablet and desktop.
In mobile shows a button on the right side that make the menu slide from
the right
* Now we have search functionality implemented thanks to Algolia search.
The index is crawled every 24h. Take into account if you make some change
and don't see it when searching as you upload the change.
* Main menu now turns to dropdown if there's no enough room to show it
horizontally

About content:

* Added global styles for better readability and support of most of the
markdown options and highlighting of code (specially for AS3 and MXML)
* Now all pages has "description" and "permalink" in the head section to
improve sharing and searching on internet. Remember to add this lines so we
make all navigation consistent with the rest of pages. If someone notice a
page without this, please add it or report it.
* Added metadata for sharing in social networks more easily capturing the
previous point plus screenshot and name.
* I tried to bring pages to the index that was still missing so we have
most of the overall structure in place. I'm pretty sure there's still
missing concepts and things to bring to the docs, so keep your eyes open to
see what could still be missing and report it or add yourself.
* Notice that some of that content is still a page mostly empty and waiting
to be filled. You're all invited to do so, just let others know about it to
avoid duplicate efforts.
* For Component Sets, I started to create a page per component where we add
the most needed info to start with the component. It then refers to ASDocs
for a full spec and access to all classes. I'm working on Jewel. Others are
invited to use Jewel finished pages and use it as template for Basic,
MXRoyale and other sets, and/or create new ones for components that are not
similar and there's no counterpart on Jewel.
* I added live content on Jewel components, since visual running examples
are very powerful.
* I added live example on the GitHub tutorial app.
* I added many cross link references between Royale-docs, blog examples and
ASDocs pages. Content must be in only one place but that content should be
linked with the rest of royale contents in our network.
* I tried to format all the pages I could to get most of the new visuals
created, but I'm sure threr's still content to format, we can do this
between all here, and anyone coming to Royale and browse content is invited
to help in this point as well to submit more content to be reviewed and
added.
* I refactored all license pages to make all consistent with one style.

To Help:

I think there's many content already done and formatted in the right way to
make others be able to add content that aligns to the rest of the doc
pages. Andrew and I are here to help to give the finished results that
conform to actual specs.

There's still many things to do to get a full docs site. This is the list
of things I see:

* Fill Features and concepts pages still empty (View States, Data Binding,
RPC methods pages, ). I think this can be the most important ones since
are core concepts in Royale.
* Complete Jewel and other sets reference pages. Very important for people
coming. Here I plan to add for Jewel "style specs" too as someone mentioned
some days ago, and I think this will be a very good idea.
* Add Crux documentation, that should come in part from swiz framework docs

What more things you still think are missing?

Thanks


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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Piotr Zarzycki
Hi Om,

What I need to do in order to release stuff on npm. Can you do this for me
once I push release to svn ?

Thanks,
Piotr

wt., 1 paź 2019 o 09:25 Piotr Zarzycki 
napisał(a):

> Hi Harbs,
>
> I think we have enough votes. I still have to gather info how actually
> release Maven artifacts. However I'm going to push binaries today in svn.
>
> Thanks,
> Piotr
>
> sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):
>
>> FYI, I will not be able to test the release until Wednesday.
>>
>> If the vote is still open, I plan on testing then.
>>
>> Thanks,
>> Harbs
>>
>> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki 
>> wrote:
>> >
>> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript
>> myself
>> > yet, but will do that tomorrow or next week.
>> >
>> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
>> apacheroyal...@gmail.com>
>> > napisał(a):
>> >
>> >> This is the discussion thread.
>> >>
>> >> Thanks,
>> >> Piotr
>> >
>> >
>> >
>> > --
>> >
>> > Piotr Zarzycki
>> >
>> > Patreon: *https://www.patreon.com/piotrzarzycki
>> > *
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

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


Re: [DISCUSS] Discuss Release Apache Royale 0.9.6 RC3

2019-10-01 Thread Piotr Zarzycki
Hi Harbs,

I think we have enough votes. I still have to gather info how actually
release Maven artifacts. However I'm going to push binaries today in svn.

Thanks,
Piotr

sob., 28 wrz 2019 o 20:02 Harbs  napisał(a):

> FYI, I will not be able to test the release until Wednesday.
>
> If the vote is still open, I plan on testing then.
>
> Thanks,
> Harbs
>
> > On Sep 25, 2019, at 5:24 PM, Piotr Zarzycki 
> wrote:
> >
> > Ok, new and hopefully the last one RC3. I didn't run ApproveScript myself
> > yet, but will do that tomorrow or next week.
> >
> > śr., 25 wrz 2019 o 16:23 Apache Royale CI Server <
> apacheroyal...@gmail.com>
> > napisał(a):
> >
> >> This is the discussion thread.
> >>
> >> Thanks,
> >> Piotr
> >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > *
>
>

-- 

Piotr Zarzycki

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


Build failed in Jenkins: royale-asjs_MXTests #1204

2019-10-01 Thread Apache Royale CI Server
See 


--
[...truncated 1005.00 KB...]
[mxmlc] scanning for overrides: ObjectUtil
[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