date:20191008

Build failed in Jenkins: royale-asjs #4

2019-10-08 Thread apacheroyaleci

See 


Changes:


--
[...truncated 1.35 MB...]
[mxmlc] scanning for overrides: IApplicationView
[mxmlc] scanning for overrides: IValuesImpl
[mxmlc] scanning for overrides: IDocument
[mxmlc] scanning for overrides: IItemRendererClassFactory
[mxmlc] scanning for overrides: ItemRendererClassFactory
[mxmlc] scanning for overrides: SimpleValuesImpl
[mxmlc] scanning for overrides: ValuesManager
[mxmlc] scanning for overrides: MouseEventConverter
[mxmlc] scanning for overrides: IRoyaleEvent
[mxmlc] scanning for overrides: Event
[mxmlc] scanning for overrides: ValueChangeEvent
[mxmlc] scanning for overrides: MXMLDataInterpreter
[mxmlc] scanning for overrides: IRunListener
[mxmlc] scanning for overrides: IAsyncStartupRunListener
[mxmlc] scanning for overrides: CIListener
[mxmlc] scanning for overrides: Descriptor
[mxmlc] scanning for overrides: IRunNotifier
[mxmlc] scanning for overrides: RunNotifier
[mxmlc] scanning for overrides: ITestRunner
[mxmlc] scanning for overrides: ParentRunner
[mxmlc] scanning for overrides: ChildNotifier
[mxmlc] scanning for overrides: RoyaleUnitCore
[mxmlc] scanning for overrides: ClassesRunner
[mxmlc] scanning for overrides: RootRunNotifier
[mxmlc] scanning for overrides: Runtime
[mxmlc] scanning for overrides: DataGridColumnTest
[mxmlc] scanning for overrides: ButtonAutoRepeatController
[mxmlc] scanning for overrides: DataFieldProviderBead
[mxmlc] scanning for overrides: DownArrowButtonView
[mxmlc] scanning for overrides: HScrollBarThumbView
[mxmlc] scanning for overrides: HScrollBarTrackView
[mxmlc] scanning for overrides: LeftArrowButtonView
[mxmlc] scanning for overrides: RightArrowButtonView
[mxmlc] scanning for overrides: UpArrowButtonView
[mxmlc] scanning for overrides: VScrollBarThumbView
[mxmlc] scanning for overrides: VScrollBarTrackView
[mxmlc] scanning for overrides: IChrome
[mxmlc] scanning for overrides: IViewportScroller
[mxmlc] scanning for overrides: ScrollBar
[mxmlc] scanning for overrides: HScrollBar
[mxmlc] scanning for overrides: VScrollBar
[mxmlc] scanning for overrides: UIButtonBase
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: EdgeData
[mxmlc] scanning for overrides: MarginData
[mxmlc] scanning for overrides: CSSTextField
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: ClassFactory
[mxmlc] scanning for overrides: IBorderPaddingMarginValuesImpl
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IItemRendererProvider
[mxmlc] scanning for overrides: ILayoutParent
[mxmlc] scanning for overrides: IListPresentationModel
[mxmlc] scanning for overrides: IMXMLDocument
[mxmlc] scanning for overrides: IMeasurementBead
[mxmlc] scanning for overrides: IStyleObject
[mxmlc] scanning for overrides: ITextModel
[mxmlc] scanning for overrides: SimpleCSSStyles
[mxmlc] scanning for overrides: StageProxy
[mxmlc] scanning for overrides: IHandlesOriginalEvent
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: DefinitionBase
[mxmlc] scanning for overrides: MetaDataArgDefinition
[mxmlc] scanning for overrides: MetaDataDefinition
[mxmlc] scanning for overrides: DefinitionWithMetaData
[mxmlc] scanning for overrides: TypeDefinition
[mxmlc] scanning for overrides: Failure
[mxmlc] scanning for overrides: Result
[mxmlc] scanning for overrides: ResultListener
[mxmlc] scanning for overrides: IAsyncHandler
[mxmlc] scanning for overrides: MetadataRunner
[mxmlc] scanning for overrides: TestInfo
[mxmlc] scanning for overrides: AsyncHandler
[mxmlc] scanning for overrides: SuiteRunner
[mxmlc] scanning for overrides: TestMetadata
[mxmlc] scanning for overrides: AssertionError
[mxmlc] scanning for overrides: IDataGridColumn
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: LayoutData
[mxmlc] scanning for overrides: BorderStyles
[mxmlc] scanning for overrides: Point
[mxmlc] scanning for overrides: PointUtils
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides:

Build failed in Jenkins: royale-asjs #3

2019-10-08 Thread apacheroyaleci

See 


Changes:


--
[...truncated 1.35 MB...]
[mxmlc] scanning for overrides: IApplicationView
[mxmlc] scanning for overrides: IValuesImpl
[mxmlc] scanning for overrides: IDocument
[mxmlc] scanning for overrides: IItemRendererClassFactory
[mxmlc] scanning for overrides: ItemRendererClassFactory
[mxmlc] scanning for overrides: SimpleValuesImpl
[mxmlc] scanning for overrides: ValuesManager
[mxmlc] scanning for overrides: MouseEventConverter
[mxmlc] scanning for overrides: IRoyaleEvent
[mxmlc] scanning for overrides: Event
[mxmlc] scanning for overrides: ValueChangeEvent
[mxmlc] scanning for overrides: MXMLDataInterpreter
[mxmlc] scanning for overrides: IRunListener
[mxmlc] scanning for overrides: IAsyncStartupRunListener
[mxmlc] scanning for overrides: CIListener
[mxmlc] scanning for overrides: Descriptor
[mxmlc] scanning for overrides: IRunNotifier
[mxmlc] scanning for overrides: RunNotifier
[mxmlc] scanning for overrides: ITestRunner
[mxmlc] scanning for overrides: ParentRunner
[mxmlc] scanning for overrides: ChildNotifier
[mxmlc] scanning for overrides: RoyaleUnitCore
[mxmlc] scanning for overrides: ClassesRunner
[mxmlc] scanning for overrides: RootRunNotifier
[mxmlc] scanning for overrides: Runtime
[mxmlc] scanning for overrides: DataGridColumnTest
[mxmlc] scanning for overrides: ButtonAutoRepeatController
[mxmlc] scanning for overrides: DataFieldProviderBead
[mxmlc] scanning for overrides: DownArrowButtonView
[mxmlc] scanning for overrides: HScrollBarThumbView
[mxmlc] scanning for overrides: HScrollBarTrackView
[mxmlc] scanning for overrides: LeftArrowButtonView
[mxmlc] scanning for overrides: RightArrowButtonView
[mxmlc] scanning for overrides: UpArrowButtonView
[mxmlc] scanning for overrides: VScrollBarThumbView
[mxmlc] scanning for overrides: VScrollBarTrackView
[mxmlc] scanning for overrides: IChrome
[mxmlc] scanning for overrides: IViewportScroller
[mxmlc] scanning for overrides: ScrollBar
[mxmlc] scanning for overrides: HScrollBar
[mxmlc] scanning for overrides: VScrollBar
[mxmlc] scanning for overrides: UIButtonBase
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: EdgeData
[mxmlc] scanning for overrides: MarginData
[mxmlc] scanning for overrides: CSSTextField
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: ClassFactory
[mxmlc] scanning for overrides: IBorderPaddingMarginValuesImpl
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IItemRendererProvider
[mxmlc] scanning for overrides: ILayoutParent
[mxmlc] scanning for overrides: IListPresentationModel
[mxmlc] scanning for overrides: IMXMLDocument
[mxmlc] scanning for overrides: IMeasurementBead
[mxmlc] scanning for overrides: IStyleObject
[mxmlc] scanning for overrides: ITextModel
[mxmlc] scanning for overrides: SimpleCSSStyles
[mxmlc] scanning for overrides: StageProxy
[mxmlc] scanning for overrides: IHandlesOriginalEvent
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: DefinitionBase
[mxmlc] scanning for overrides: MetaDataArgDefinition
[mxmlc] scanning for overrides: MetaDataDefinition
[mxmlc] scanning for overrides: DefinitionWithMetaData
[mxmlc] scanning for overrides: TypeDefinition
[mxmlc] scanning for overrides: Failure
[mxmlc] scanning for overrides: Result
[mxmlc] scanning for overrides: ResultListener
[mxmlc] scanning for overrides: IAsyncHandler
[mxmlc] scanning for overrides: MetadataRunner
[mxmlc] scanning for overrides: TestInfo
[mxmlc] scanning for overrides: AsyncHandler
[mxmlc] scanning for overrides: SuiteRunner
[mxmlc] scanning for overrides: TestMetadata
[mxmlc] scanning for overrides: AssertionError
[mxmlc] scanning for overrides: IDataGridColumn
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: LayoutData
[mxmlc] scanning for overrides: BorderStyles
[mxmlc] scanning for overrides: Point
[mxmlc] scanning for overrides: PointUtils
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides:

Build failed in Jenkins: royale-asjs #2

2019-10-08 Thread apacheroyaleci

See 


Changes:


--
[...truncated 1.34 MB...]
[mxmlc] scanning for overrides: IApplicationView
[mxmlc] scanning for overrides: IValuesImpl
[mxmlc] scanning for overrides: IDocument
[mxmlc] scanning for overrides: IItemRendererClassFactory
[mxmlc] scanning for overrides: ItemRendererClassFactory
[mxmlc] scanning for overrides: SimpleValuesImpl
[mxmlc] scanning for overrides: ValuesManager
[mxmlc] scanning for overrides: MouseEventConverter
[mxmlc] scanning for overrides: IRoyaleEvent
[mxmlc] scanning for overrides: Event
[mxmlc] scanning for overrides: ValueChangeEvent
[mxmlc] scanning for overrides: MXMLDataInterpreter
[mxmlc] scanning for overrides: IRunListener
[mxmlc] scanning for overrides: IAsyncStartupRunListener
[mxmlc] scanning for overrides: CIListener
[mxmlc] scanning for overrides: Descriptor
[mxmlc] scanning for overrides: IRunNotifier
[mxmlc] scanning for overrides: RunNotifier
[mxmlc] scanning for overrides: ITestRunner
[mxmlc] scanning for overrides: ParentRunner
[mxmlc] scanning for overrides: ChildNotifier
[mxmlc] scanning for overrides: RoyaleUnitCore
[mxmlc] scanning for overrides: ClassesRunner
[mxmlc] scanning for overrides: RootRunNotifier
[mxmlc] scanning for overrides: Runtime
[mxmlc] scanning for overrides: DataGridColumnTest
[mxmlc] scanning for overrides: ButtonAutoRepeatController
[mxmlc] scanning for overrides: DataFieldProviderBead
[mxmlc] scanning for overrides: DownArrowButtonView
[mxmlc] scanning for overrides: HScrollBarThumbView
[mxmlc] scanning for overrides: HScrollBarTrackView
[mxmlc] scanning for overrides: LeftArrowButtonView
[mxmlc] scanning for overrides: RightArrowButtonView
[mxmlc] scanning for overrides: UpArrowButtonView
[mxmlc] scanning for overrides: VScrollBarThumbView
[mxmlc] scanning for overrides: VScrollBarTrackView
[mxmlc] scanning for overrides: IChrome
[mxmlc] scanning for overrides: IViewportScroller
[mxmlc] scanning for overrides: ScrollBar
[mxmlc] scanning for overrides: HScrollBar
[mxmlc] scanning for overrides: VScrollBar
[mxmlc] scanning for overrides: UIButtonBase
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: EdgeData
[mxmlc] scanning for overrides: MarginData
[mxmlc] scanning for overrides: CSSTextField
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: ClassFactory
[mxmlc] scanning for overrides: IBorderPaddingMarginValuesImpl
[mxmlc] scanning for overrides: IContainer
[mxmlc] scanning for overrides: IItemRendererProvider
[mxmlc] scanning for overrides: ILayoutParent
[mxmlc] scanning for overrides: IListPresentationModel
[mxmlc] scanning for overrides: IMXMLDocument
[mxmlc] scanning for overrides: IMeasurementBead
[mxmlc] scanning for overrides: IStyleObject
[mxmlc] scanning for overrides: ITextModel
[mxmlc] scanning for overrides: SimpleCSSStyles
[mxmlc] scanning for overrides: StageProxy
[mxmlc] scanning for overrides: IHandlesOriginalEvent
[mxmlc] scanning for overrides: CustomEvent
[mxmlc] scanning for overrides: ItemAddedEvent
[mxmlc] scanning for overrides: ItemClickedEvent
[mxmlc] scanning for overrides: ItemRemovedEvent
[mxmlc] scanning for overrides: ItemRendererEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: Size
[mxmlc] scanning for overrides: CSSBorderUtils
[mxmlc] scanning for overrides: CSSUtils
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: DefinitionBase
[mxmlc] scanning for overrides: MetaDataArgDefinition
[mxmlc] scanning for overrides: MetaDataDefinition
[mxmlc] scanning for overrides: DefinitionWithMetaData
[mxmlc] scanning for overrides: TypeDefinition
[mxmlc] scanning for overrides: Failure
[mxmlc] scanning for overrides: Result
[mxmlc] scanning for overrides: ResultListener
[mxmlc] scanning for overrides: IAsyncHandler
[mxmlc] scanning for overrides: MetadataRunner
[mxmlc] scanning for overrides: TestInfo
[mxmlc] scanning for overrides: AsyncHandler
[mxmlc] scanning for overrides: SuiteRunner
[mxmlc] scanning for overrides: TestMetadata
[mxmlc] scanning for overrides: AssertionError
[mxmlc] scanning for overrides: IDataGridColumn
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: LayoutData
[mxmlc] scanning for overrides: BorderStyles
[mxmlc] scanning for overrides: Point
[mxmlc] scanning for overrides: PointUtils
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides:

Build failed in Jenkins: royale-asjs #1

2019-10-08 Thread apacheroyaleci

See 


Changes:


--
[...truncated 145.79 KB...]
create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:
[mkdir] Created dir: 


stage-source:

clean-temp:
[mkdir] Created dir: 

 [copy] Copying 5814 files to 

 [copy] Copied 2033 empty directories to 1 empty directory under 

 [echo] Updating config file air-config.xml with version 0.9.7.20191009
 [echo] Updating config file royale-config.xml with version 0.9.7.20191009
 [echo] Updating config file js-config.xml with version 0.9.7.20191009
 [echo] Updating config file jquery-config.xml with version 0.9.7.20191009
 [echo] Updating config file ace-config.xml with version 0.9.7.20191009
 [echo] Updating config file createjs-config.xml with version 0.9.7.20191009
 [echo] Updating config file node-config.xml with version 0.9.7.20191009

stage-compiler:

wipe-all:

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-build-tools\target\classes

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-build-tools\target

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-jburg-types\target\classes

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-jburg-types\target

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-test-utils\target\classes

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-test-utils\target
 [echo] RELEASE_VERSION IS: 0.9.7

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-common\target\classes

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-common\target

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-externc\target\classes
   [delete] Deleting: 
C:\jenkins\workspace\royale-compiler\compiler-externc\target\js.swc

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-externc\target

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler\target

wipe:
   [delete] Deleting directory C:\jenkins\workspace\royale-compiler\compiler\lib

clean:

wipe:

thirdparty-clean:
 [echo] basedir is 
C:\jenkins\workspace\royale-compiler\compiler-jx\src\main\resources
 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is 
C:\jenkins\workspace\royale-compiler\compiler-jx

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-jx\target

clean:

super-clean:

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-jx\src\test\results

wipe:

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\flex-compiler-oem\target\classes

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\flex-compiler-oem\target

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\swfutils\target\classes

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\swfutils\target

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\royale-ant-tasks\target

wipe:

clean:
 [echo] basedir is C:\jenkins\workspace\royale-compiler\royaleunit-ant-tasks
 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is C:\compiler-jx

clean:
   [delete] Deleting

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

2019-10-08 Thread apacheroyaleci

See

Build failed in Jenkins: royale-asjs_jsonly #3

2019-10-08 Thread apacheroyaleci

See 


Changes:


--
[...truncated 1.66 MB...]
 [java] public static var waitForExcludes:Boolean = false;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var waitForIncludes:Boolean = false;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var blockActivationEvents:Boolean = true;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var callback:Function;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var sawStartEvent:Boolean = false;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var pendingOutput:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var lastPendingOutput:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var frameWaitCount:int = 0;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var isApollo:Boolean = false;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var waitForWindow:String;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var checkEmbeddedFonts:Boolean = false;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var createBitmapReferences:Boolean = false;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var verboseMode:Boolean = false;
 [java] ^
 [java] 
 [java] 
:
 col: 2 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var runnerPort:int = ;
 [java] ^
 [java] 
 [java] 
:
 col: 5 public var may not work in minified JS output.  Use getter/setter 
instead.
 [java] 
 [java] public static var noScriptComplete:Boolean = false;
 [java] ^
 [java] 
 [java]

Build failed in Jenkins: royale-asjs_jsonly #2

2019-10-08 Thread apacheroyaleci

y/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

check-for-tests:

clean-tests:

package-clean:

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

checkintests-clean:

mxtests-clean:

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

clean:

super-clean:
   [delete] Deleting directory 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/themes/Spark>

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

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

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

tweak-for-jsonly:

tweak-for-jsonly:
 [copy] Warning: Could not find file 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/js/libs/js.swc>
 to copy.
 [copy] Copying 1 file to 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp>

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

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

stage-source:

clean-temp:
[mkdir] Created dir: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp/royale-asjs>
 [copy] Copying 5814 files to 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp/royale-asjs>
 [copy] Copied 2033 empty directories to 1 empty directory under 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp/royale-asjs>
 [echo] Updating config file air-config.xml with version 0.9.7.20191008
 [echo] Updating config file royale-config.xml with version 0.9.7.20191008
 [echo] Updating config file js-config.xml with version 0.9.7.20191008
 [echo] Updating config file jquery-config.xml with version 0.9.7.20191008
 [echo] Updating config file ace-config.xml with version 0.9.7.20191008
 [echo] Updating config file createjs-config.xml with version 0.9.7.20191008
 [echo] Updating config file node-config.xml with version 0.9.7.20191008

stage-compiler:

BUILD FAILED
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/build.xml>:791:
 The following error occurred while executing this line:
java.io.FileNotFoundException: C:\jenkins\royale-compiler\build.xml (The system 
cannot find the file specified)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at 
org.apache.tools.ant.helper.ProjectHelper2

Build failed in Jenkins: royale-asjs_jsonly #1

2019-10-08 Thread apacheroyaleci

/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

clean:
 [echo] swc-date is 10/08/19 23:02 +
   [delete] Deleting: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/js/projects/RoyaleSiteJS/RoyaleSiteJS.swc.properties>

check-for-tests:

clean-tests:

package-clean:

clean-temp:

checkintests-clean:

mxtests-clean:

clean:
 [echo] ROYALE_HOME = 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/>
 [echo] royalelib = 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks>
 [echo] doc_output = 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/asdoc-output>
 [echo] compiler.source-path = 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/frameworks/projects/*/src/main/royale>

clean:

super-clean:

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

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

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

tweak-for-jsonly:

tweak-for-jsonly:
 [copy] Warning: Could not find file 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/js/libs/js.swc>
 to copy.
 [copy] Copying 1 file to 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp>

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

tweak-for-jsonly:

playerglobal-setswfversion:

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

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

stage-source:

clean-temp:
[mkdir] Created dir: 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp/royale-asjs>
 [copy] Copying 5814 files to 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp/royale-asjs>
 [copy] Copied 2033 empty directories to 1 empty directory under 
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/temp/royale-asjs>
 [echo] Updating config file air-config.xml with version 0.9.7.20191008
 [echo] Updating config file royale-config.xml with version 0.9.7.20191008
 [echo] Updating config file js-config.xml with version 0.9.7.20191008
 [echo] Updating config file jquery-config.xml with version 0.9.7.20191008
 [echo] Updating config file ace-config.xml with version 0.9.7.20191008
 [echo] Updating config file createjs-config.xml with version 0.9.7.20191008
 [echo] Updating config file node-config.xml with version 0.9.7.20191008

stage-compiler:

BUILD FAILED
<http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/ws/build.xml>:791:
 The following error occurred while executing this line:
java.io.FileNotFoundException: C:\Program Files 
(x86)\Jenkins\workspace\royale-compiler\build.xml (The system cannot find the 
file specified)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at 
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:250)
at 
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:178)
at 
org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:392)
at org.apache.tools.ant.Unknown

New apache-royale questions for Oct 8 - Stack Exchange

2019-10-08 Thread Stack Exchange

***2 new questions in [ApacheRoyale Tag Notifications 
filter]()
 on stackexchange.com***


[issue with material-icons : no picture icon on Apache 
Royale]()

I want to use an icon image like in TourDeJewel, but when I use this code then 
the text "MENU" is showing instead of icon picture. (sdk 0.9.6) 
j:IconButton  j:icon ...

Tagged: google-material-icons

by [Fred]() on 




[Issue using express\DataGridExample on Apache Royale sdk 
0.9.6]()

Can someone tell me if 
apache-royale-0.9.6-bin-js\royale-asjs\examples\express\DataGridExample is 
working or not ? (using sdk 0.9.6). I do no modification, just run it... When I 
launch it I have ...

Tagged: datagrid

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: Acceptance of Royale by Flex Developers

2019-10-08 Thread Alex Harui

The migration page I linked to earlier attempts to help people get started with 
MXRoyale and SparkRoyale (by changing the namespaces).  After that, the goal is 
for the components to work similar to the Flex components, so from an ASDoc 
standpoint, they “should” be able to use the Flex ASDoc and then ask for help 
when some API they need isn’t emulated.

HTH,
-Alex

From: Carlos Rovira 
Date: Tuesday, October 8, 2019 at 11:59 AM
To: "dev@royale.apache.org" 
Cc: Alex Harui 
Subject: Re: Acceptance of Royale by Flex Developers

Hi

I think we could remove one level or even two.

Have at first level

MIGRATE AN EXISTING APPLICATION
  (instead of inside
CREATE AN 
APPLICATION
 )

then MIGRATE FROM 
FLEX
 (nested)

And inside this we can add other entries to help that migration.


We still don't have anything about MX / SPARK emulation components in docs, so 
more info should be added if we want to make it people use it.

just my 2

Carlos




El mar., 8 oct. 2019 a las 19:00, Andrew Wetmore 
(mailto:cottag...@gmail.com>>) escribió:
Really good suggestions, @Alex Harui 
mailto:aha...@adobe.com>> . I could add text
and links to the "migrating" page based on what you outlined. I can get
that done sometime this week, but am not going to jump on it today in case
the conversation continues and an enhanced idea bubbles up.

Andrew

On Tue, Oct 8, 2019 at 12:48 PM Alex Harui  wrote:

> I'm going to try to address all of Chris Velevitch's several threads from
> today in this response.
>
> We have a page on Migrating Flex Apps here:
> https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html
> But it is hard to find (took me several clicks to find it).  And it
> doesn't address the questions that I think Chris is asking, which are:
>
> -Which component sets should I use?
> -After I choose a component set, how do I figure out how something that
> worked in Flex works in that component set?
>
> We've offered Chris the opportunity to help with the doc, which would be
> great, but I'd settle for having Chris and others simply add the kinds of
> questions they have so we can add them to our FAQ and/or the docs.
>
> We may need to make it easier for Chris and others to decide on component
> sets first.  The way I think of it now, the trade offs are:
> A) I need the result to be as small and fast as possible and have time to
> rewrite the UI -> Use Basic and Strands and Beads
> B) I want to rewrite the UI to get a more modern look-and-feel -> Use Jewel
> C) I want to touch as little code as possible -> Use MXRoyale and
> SparkRoyale.
>
> If you choose C, you should not have to know anything about Strands and
> Beads.  MXRoyale and SparkRoyale should hide that from you.  Skinning
> should work like it used to.  Your app will not be as small and fast as if
> you spend more time rewriting it to Basic or Jewel, but TourDeFlex seems to
> be running ok.  As Alina and Pashmina finish up, we'll see how a really big
> Flex migration performs in Royale.
>
> It has taken them longer than expected, but for every bug or missing
> feature that is emulated correctly, the time to migrate for the next person
> goes down.  And as 2019 becomes 2020, there will be less time to migrate
> for some folks, so having more people on the emulation helps everyone else.
>
> So, we should figure out where to place information like this so Chris and
> others find it more easily.  Once a component set/migration strategy is
> chosen, it focuses a lot of other questions, such as how to do skinning, or
> how much about Strands and Beads you have to know.  In fact, it would be
> great to find a place to recommend to folks that when they write to us with
> questions that they specify which component set(s) they are using because
> the answer can be quite different based on the component sets involved.
>
> Suggestions from Chris and others as to how to make this information

maven fails on build royale-asjs 0.9.7-SNAPSHOT

2019-10-08 Thread Carlos Rovira

Hi,

just trying to build as usual, but now with new 0.9.7-SNAPSHOT
when reach royale-asjs try to build with:

mvn clean install -Pgenerate-swcs-for-swf,main -DskipTests

and getting this error:

https://paste.apache.org/kt8wi

Maybe I miss some latest change?

thanks

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

Re: Acceptance of Royale by Flex Developers

2019-10-08 Thread Carlos Rovira

Hi

I think we could remove one level or even two.

Have at first level

MIGRATE AN EXISTING APPLICATION  (instead of inside CREATE AN APPLICATION

 )

then MIGRATE FROM FLEX

 (nested)

And inside this we can add other entries to help that migration.


We still don't have anything about MX / SPARK emulation components in docs,
so more info should be added if we want to make it people use it.

just my 2

Carlos




El mar., 8 oct. 2019 a las 19:00, Andrew Wetmore ()
escribió:

> Really good suggestions, @Alex Harui  . I could add text
> and links to the "migrating" page based on what you outlined. I can get
> that done sometime this week, but am not going to jump on it today in case
> the conversation continues and an enhanced idea bubbles up.
>
> Andrew
>
> On Tue, Oct 8, 2019 at 12:48 PM Alex Harui 
> wrote:
>
> > I'm going to try to address all of Chris Velevitch's several threads from
> > today in this response.
> >
> > We have a page on Migrating Flex Apps here:
> >
> https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html
> > But it is hard to find (took me several clicks to find it).  And it
> > doesn't address the questions that I think Chris is asking, which are:
> >
> > -Which component sets should I use?
> > -After I choose a component set, how do I figure out how something that
> > worked in Flex works in that component set?
> >
> > We've offered Chris the opportunity to help with the doc, which would be
> > great, but I'd settle for having Chris and others simply add the kinds of
> > questions they have so we can add them to our FAQ and/or the docs.
> >
> > We may need to make it easier for Chris and others to decide on component
> > sets first.  The way I think of it now, the trade offs are:
> > A) I need the result to be as small and fast as possible and have time to
> > rewrite the UI -> Use Basic and Strands and Beads
> > B) I want to rewrite the UI to get a more modern look-and-feel -> Use
> Jewel
> > C) I want to touch as little code as possible -> Use MXRoyale and
> > SparkRoyale.
> >
> > If you choose C, you should not have to know anything about Strands and
> > Beads.  MXRoyale and SparkRoyale should hide that from you.  Skinning
> > should work like it used to.  Your app will not be as small and fast as
> if
> > you spend more time rewriting it to Basic or Jewel, but TourDeFlex seems
> to
> > be running ok.  As Alina and Pashmina finish up, we'll see how a really
> big
> > Flex migration performs in Royale.
> >
> > It has taken them longer than expected, but for every bug or missing
> > feature that is emulated correctly, the time to migrate for the next
> person
> > goes down.  And as 2019 becomes 2020, there will be less time to migrate
> > for some folks, so having more people on the emulation helps everyone
> else.
> >
> > So, we should figure out where to place information like this so Chris
> and
> > others find it more easily.  Once a component set/migration strategy is
> > chosen, it focuses a lot of other questions, such as how to do skinning,
> or
> > how much about Strands and Beads you have to know.  In fact, it would be
> > great to find a place to recommend to folks that when they write to us
> with
> > questions that they specify which component set(s) they are using because
> > the answer can be quite different based on the component sets involved.
> >
> > Suggestions from Chris and others as to how to make this information more
> > accessible are encouraged.
> >
> > My 2 cents,
> > -Alex
> >
> >
> > On 10/8/19, 8:18 AM, "Carlos Rovira"  wrote:
> >
> > Hi,
> >
> > I mean that like RO, that's a non visual component used to perform
> > communications, we have other "components" or "code" that can be
> > implemented as beads or strands.
> > The concept behind is that Royale have the minimum code needed for
> > functionality, and compose other parts (whatever the purpose of the
> > code
> > could be). So while UI Components use to refer to code that are
> visual
> > and
> > use to be a Button, a List or a Checkbox, strands are more agonistic
> > about
> > that particular use case, so seems, IMHO a better way to describe it
> > from
> > that point of view.
> >
> > El mar., 8 oct. 2019 a las 10:14, Chris Velevitch (<
> > chris.velevi...@gmail.com>) escribió:
> >
> > > So you are suggesting a RemoteObject is a headless component who's
> > > base class only supports the model and controller plugins and that
> UI
> > > classes extend the headless component to add in the view?
> > >
> > > On Tue, 8 Oct 2019 at 15:52, Carlos Rovira <
> carlosrov...@apache.org>
> > > wrote:
> > > >
> > > > Hi Chris,
> > > >
> > > > thanks for sharing

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Carlos Rovira

Hi

website is updated.
@Piotr Zarzycki   do you want to share 0.9.6 in
social media? or wait for announcement?

thanks


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

> Hi Andrew,
>
> if you don't mind I take into account for next release, since I'm this
> days a bit out of time.
> Thanks for taking the review. I'll try to publish now
>
> Carlos
>
>
>
> El mar., 8 oct. 2019 a las 18:57, Andrew Wetmore ()
> escribió:
>
>> I have edited the release. The only thing I would improve, if I could, is
>> the graphic at the top. The release number appears as "v0.9.6". I am
>> pretty
>> sure it would be better as "v. 0.9.6", but this is obviously not something
>> to delay the release for.
>>
>> Andrew
>>
>> On Tue, Oct 8, 2019 at 11:56 AM Andrew Wetmore 
>> wrote:
>>
>> > Got it! Thanks!
>> >
>> > On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira 
>> > wrote:
>> >
>> >> Yes! that's it :)
>> >>
>> >>
>> >> El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (<
>> >> piotrzarzyck...@gmail.com>)
>> >> escribió:
>> >>
>> >> > I think that would be the link:
>> >> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>> >> >
>> >> > wt., 8 paź 2019 o 16:29 Andrew Wetmore 
>> >> napisał(a):
>> >> >
>> >> > > @Carlos Rovira  where is the draft post?
>> I
>> >> had
>> >> > a
>> >> > > hard disk failure this past weekend and am slowly rebuilding my
>> >> system.
>> >> > > Have to find all my links again.
>> >> > >
>> >> > > a
>> >> > >
>> >> > > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore > >
>> >> > wrote:
>> >> > >
>> >> > > > I can do this in a couple of hours
>> >> > > >
>> >> > > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, <
>> >> carlosrov...@apache.org>
>> >> > > > wrote:
>> >> > > >
>> >> > > >> Hi Piotr,
>> >> > > >>
>> >> > > >> I'll wait Andrew's review and then will publish it. If Andrew
>> make
>> >> his
>> >> > > >> changes this afternoon, I can follow up and publish it.
>> >> > > >> Then we can post on social networks next or wait to tomorrow
>> >> > > >>
>> >> > > >>
>> >> > > >>
>> >> > > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
>> >> > > >> piotrzarzyck...@gmail.com>)
>> >> > > >> escribió:
>> >> > > >>
>> >> > > >> > Just to make sure that you understand why I asked you to post
>> >> > download
>> >> > > >> > links on website along with source code.
>> >> > > >> >
>> >> > > >> > I will announce on dev, users and announce list - someone who
>> >> read
>> >> > > >> email -
>> >> > > >> > will have two options:
>> >> > > >> > 1) Can click in that email on royale.apache.org
>> >> > > >> > 2) Can download directly binaries or source code from provided
>> >> links
>> >> > > in
>> >> > > >> the
>> >> > > >> > email
>> >> > > >> >
>> >> > > >> > If user do #1 he will see old links on website which will be
>> >> > > >> misleading. -
>> >> > > >> > Do you understand now why I asked you to publish stuff first ?
>> >> > > >> >
>> >> > > >> > However as I said if you prefer do this in a opposite way
>> that's
>> >> > fine
>> >> > > >> with
>> >> > > >> > me. :)
>> >> > > >> >
>> >> > > >> >
>> >> > > >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki <
>> >> piotrzarzyck...@gmail.com>
>> >> > > >> > napisał(a):
>> >> > > >> >
>> >> > > >> > > This is the goal of syncing everything tomorrow. I asked
>> you to
>> >> > > >> publish
>> >> > > >> > > first link and source code on website, cause my announce
>> >> probably
>> >> > go
>> >> > > >> > first
>> >> > > >> > > one and I didn't want to mislead with what will be on
>> website.
>> >> > > >> However if
>> >> > > >> > > you wanted to do that differently I'm fine - Couple of
>> hours of
>> >> > > >> > misleading
>> >> > > >> > > doesn't hurts anyone maybe. - We will see tomorrow.
>> >> > > >> > >
>> >> > > >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira <
>> carlosrov...@apache.org
>> >> >
>> >> > > >> > > napisał(a):
>> >> > > >> > >
>> >> > > >> > >> Hi,
>> >> > > >> > >> ok, is normal,
>> >> > > >> > >> as people following our dev, are as well using links to
>> 0.9.6
>> >> > > >> releases.
>> >> > > >> > >> The update of links in website is more about to announce to
>> >> the
>> >> > > rest
>> >> > > >> of
>> >> > > >> > >> the
>> >> > > >> > >> world that is not as close to us as the rest of community.
>> >> > > >> > >> So it's important to communicate in the most organized way
>> we
>> >> > can.
>> >> > > >> > >>
>> >> > > >> > >> thanks!
>> >> > > >> > >>
>> >> > > >> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
>> >> > > >> > >> piotrzarzyck...@gmail.com>)
>> >> > > >> > >> escribió:
>> >> > > >> > >>
>> >> > > >> > >> > Just FYI: npm stuff and Maven artifacts are being
>> published
>> >> for
>> >> > > >> couple
>> >> > > >> > >> of
>> >> > > >> > >> > days already, so people are using released 0.9.6 trough
>> >> npm. -
>> >> > > It's
>> >> > > >> > >> happen
>> >> > > >> > >> > automatically in case of npm.
>> >> > > >> > >> >
>> >> > > >> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki <
>> >> > > piotrzarzyck...@gmail.com>

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Carlos Rovira

Hi Andrew,

if you don't mind I take into account for next release, since I'm this days
a bit out of time.
Thanks for taking the review. I'll try to publish now

Carlos



El mar., 8 oct. 2019 a las 18:57, Andrew Wetmore ()
escribió:

> I have edited the release. The only thing I would improve, if I could, is
> the graphic at the top. The release number appears as "v0.9.6". I am pretty
> sure it would be better as "v. 0.9.6", but this is obviously not something
> to delay the release for.
>
> Andrew
>
> On Tue, Oct 8, 2019 at 11:56 AM Andrew Wetmore 
> wrote:
>
> > Got it! Thanks!
> >
> > On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira 
> > wrote:
> >
> >> Yes! that's it :)
> >>
> >>
> >> El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >> escribió:
> >>
> >> > I think that would be the link:
> >> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> >> >
> >> > wt., 8 paź 2019 o 16:29 Andrew Wetmore 
> >> napisał(a):
> >> >
> >> > > @Carlos Rovira  where is the draft post? I
> >> had
> >> > a
> >> > > hard disk failure this past weekend and am slowly rebuilding my
> >> system.
> >> > > Have to find all my links again.
> >> > >
> >> > > a
> >> > >
> >> > > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore 
> >> > wrote:
> >> > >
> >> > > > I can do this in a couple of hours
> >> > > >
> >> > > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, <
> >> carlosrov...@apache.org>
> >> > > > wrote:
> >> > > >
> >> > > >> Hi Piotr,
> >> > > >>
> >> > > >> I'll wait Andrew's review and then will publish it. If Andrew
> make
> >> his
> >> > > >> changes this afternoon, I can follow up and publish it.
> >> > > >> Then we can post on social networks next or wait to tomorrow
> >> > > >>
> >> > > >>
> >> > > >>
> >> > > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
> >> > > >> piotrzarzyck...@gmail.com>)
> >> > > >> escribió:
> >> > > >>
> >> > > >> > Just to make sure that you understand why I asked you to post
> >> > download
> >> > > >> > links on website along with source code.
> >> > > >> >
> >> > > >> > I will announce on dev, users and announce list - someone who
> >> read
> >> > > >> email -
> >> > > >> > will have two options:
> >> > > >> > 1) Can click in that email on royale.apache.org
> >> > > >> > 2) Can download directly binaries or source code from provided
> >> links
> >> > > in
> >> > > >> the
> >> > > >> > email
> >> > > >> >
> >> > > >> > If user do #1 he will see old links on website which will be
> >> > > >> misleading. -
> >> > > >> > Do you understand now why I asked you to publish stuff first ?
> >> > > >> >
> >> > > >> > However as I said if you prefer do this in a opposite way
> that's
> >> > fine
> >> > > >> with
> >> > > >> > me. :)
> >> > > >> >
> >> > > >> >
> >> > > >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com>
> >> > > >> > napisał(a):
> >> > > >> >
> >> > > >> > > This is the goal of syncing everything tomorrow. I asked you
> to
> >> > > >> publish
> >> > > >> > > first link and source code on website, cause my announce
> >> probably
> >> > go
> >> > > >> > first
> >> > > >> > > one and I didn't want to mislead with what will be on
> website.
> >> > > >> However if
> >> > > >> > > you wanted to do that differently I'm fine - Couple of hours
> of
> >> > > >> > misleading
> >> > > >> > > doesn't hurts anyone maybe. - We will see tomorrow.
> >> > > >> > >
> >> > > >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira <
> carlosrov...@apache.org
> >> >
> >> > > >> > > napisał(a):
> >> > > >> > >
> >> > > >> > >> Hi,
> >> > > >> > >> ok, is normal,
> >> > > >> > >> as people following our dev, are as well using links to
> 0.9.6
> >> > > >> releases.
> >> > > >> > >> The update of links in website is more about to announce to
> >> the
> >> > > rest
> >> > > >> of
> >> > > >> > >> the
> >> > > >> > >> world that is not as close to us as the rest of community.
> >> > > >> > >> So it's important to communicate in the most organized way
> we
> >> > can.
> >> > > >> > >>
> >> > > >> > >> thanks!
> >> > > >> > >>
> >> > > >> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> >> > > >> > >> piotrzarzyck...@gmail.com>)
> >> > > >> > >> escribió:
> >> > > >> > >>
> >> > > >> > >> > Just FYI: npm stuff and Maven artifacts are being
> published
> >> for
> >> > > >> couple
> >> > > >> > >> of
> >> > > >> > >> > days already, so people are using released 0.9.6 trough
> >> npm. -
> >> > > It's
> >> > > >> > >> happen
> >> > > >> > >> > automatically in case of npm.
> >> > > >> > >> >
> >> > > >> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki <
> >> > > piotrzarzyck...@gmail.com>
> >> > > >> > >> > napisał(a):
> >> > > >> > >> >
> >> > > >> > >> > > Fine with me. I make announce tomorrow morning and
> review
> >> > what
> >> > > >> was
> >> > > >> > >> your
> >> > > >> > >> > > change and update Draft.
> >> > > >> > >> > >
> >> > > >> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira <
> >> > carlosrov...@apache.org
> >> > > >
> >>

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Andrew Wetmore

I have edited the release. The only thing I would improve, if I could, is
the graphic at the top. The release number appears as "v0.9.6". I am pretty
sure it would be better as "v. 0.9.6", but this is obviously not something
to delay the release for.

Andrew

On Tue, Oct 8, 2019 at 11:56 AM Andrew Wetmore  wrote:

> Got it! Thanks!
>
> On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira 
> wrote:
>
>> Yes! that's it :)
>>
>>
>> El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > I think that would be the link:
>> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>> >
>> > wt., 8 paź 2019 o 16:29 Andrew Wetmore 
>> napisał(a):
>> >
>> > > @Carlos Rovira  where is the draft post? I
>> had
>> > a
>> > > hard disk failure this past weekend and am slowly rebuilding my
>> system.
>> > > Have to find all my links again.
>> > >
>> > > a
>> > >
>> > > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore 
>> > wrote:
>> > >
>> > > > I can do this in a couple of hours
>> > > >
>> > > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, <
>> carlosrov...@apache.org>
>> > > > wrote:
>> > > >
>> > > >> Hi Piotr,
>> > > >>
>> > > >> I'll wait Andrew's review and then will publish it. If Andrew make
>> his
>> > > >> changes this afternoon, I can follow up and publish it.
>> > > >> Then we can post on social networks next or wait to tomorrow
>> > > >>
>> > > >>
>> > > >>
>> > > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
>> > > >> piotrzarzyck...@gmail.com>)
>> > > >> escribió:
>> > > >>
>> > > >> > Just to make sure that you understand why I asked you to post
>> > download
>> > > >> > links on website along with source code.
>> > > >> >
>> > > >> > I will announce on dev, users and announce list - someone who
>> read
>> > > >> email -
>> > > >> > will have two options:
>> > > >> > 1) Can click in that email on royale.apache.org
>> > > >> > 2) Can download directly binaries or source code from provided
>> links
>> > > in
>> > > >> the
>> > > >> > email
>> > > >> >
>> > > >> > If user do #1 he will see old links on website which will be
>> > > >> misleading. -
>> > > >> > Do you understand now why I asked you to publish stuff first ?
>> > > >> >
>> > > >> > However as I said if you prefer do this in a opposite way that's
>> > fine
>> > > >> with
>> > > >> > me. :)
>> > > >> >
>> > > >> >
>> > > >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> > > >> > napisał(a):
>> > > >> >
>> > > >> > > This is the goal of syncing everything tomorrow. I asked you to
>> > > >> publish
>> > > >> > > first link and source code on website, cause my announce
>> probably
>> > go
>> > > >> > first
>> > > >> > > one and I didn't want to mislead with what will be on website.
>> > > >> However if
>> > > >> > > you wanted to do that differently I'm fine - Couple of hours of
>> > > >> > misleading
>> > > >> > > doesn't hurts anyone maybe. - We will see tomorrow.
>> > > >> > >
>> > > >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira > >
>> > > >> > > napisał(a):
>> > > >> > >
>> > > >> > >> Hi,
>> > > >> > >> ok, is normal,
>> > > >> > >> as people following our dev, are as well using links to 0.9.6
>> > > >> releases.
>> > > >> > >> The update of links in website is more about to announce to
>> the
>> > > rest
>> > > >> of
>> > > >> > >> the
>> > > >> > >> world that is not as close to us as the rest of community.
>> > > >> > >> So it's important to communicate in the most organized way we
>> > can.
>> > > >> > >>
>> > > >> > >> thanks!
>> > > >> > >>
>> > > >> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
>> > > >> > >> piotrzarzyck...@gmail.com>)
>> > > >> > >> escribió:
>> > > >> > >>
>> > > >> > >> > Just FYI: npm stuff and Maven artifacts are being published
>> for
>> > > >> couple
>> > > >> > >> of
>> > > >> > >> > days already, so people are using released 0.9.6 trough
>> npm. -
>> > > It's
>> > > >> > >> happen
>> > > >> > >> > automatically in case of npm.
>> > > >> > >> >
>> > > >> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki <
>> > > piotrzarzyck...@gmail.com>
>> > > >> > >> > napisał(a):
>> > > >> > >> >
>> > > >> > >> > > Fine with me. I make announce tomorrow morning and review
>> > what
>> > > >> was
>> > > >> > >> your
>> > > >> > >> > > change and update Draft.
>> > > >> > >> > >
>> > > >> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira <
>> > carlosrov...@apache.org
>> > > >
>> > > >> > >> > > napisał(a):
>> > > >> > >> > >
>> > > >> > >> > >> Hi, Piotr,
>> > > >> > >> > >>
>> > > >> > >> > >> I think we should update all at the same time, since we
>> want
>> > > to
>> > > >> > post
>> > > >> > >> in
>> > > >> > >> > >> twitter, Facebook and linkedin.
>> > > >> > >> > >> Doesn't have sense to me upload just a few links since
>> > almost
>> > > >> > nobody
>> > > >> > >> > will
>> > > >> > >> > >> notice it (and are already in GitHub releases). If we
>> need
>> > to
>> > > >> wait
>> > > >> > a
>> > > >> > >> day
>> > > >> > >> > >> to
>> >

Re: Acceptance of Royale by Flex Developers

2019-10-08 Thread Alex Harui

I'm going to try to address all of Chris Velevitch's several threads from today 
in this response.

We have a page on Migrating Flex Apps here: 
https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html
But it is hard to find (took me several clicks to find it).  And it doesn't 
address the questions that I think Chris is asking, which are:

-Which component sets should I use?
-After I choose a component set, how do I figure out how something that worked 
in Flex works in that component set?

We've offered Chris the opportunity to help with the doc, which would be great, 
but I'd settle for having Chris and others simply add the kinds of questions 
they have so we can add them to our FAQ and/or the docs.

We may need to make it easier for Chris and others to decide on component sets 
first.  The way I think of it now, the trade offs are:
A) I need the result to be as small and fast as possible and have time to 
rewrite the UI -> Use Basic and Strands and Beads
B) I want to rewrite the UI to get a more modern look-and-feel -> Use Jewel
C) I want to touch as little code as possible -> Use MXRoyale and SparkRoyale.

If you choose C, you should not have to know anything about Strands and Beads.  
MXRoyale and SparkRoyale should hide that from you.  Skinning should work like 
it used to.  Your app will not be as small and fast as if you spend more time 
rewriting it to Basic or Jewel, but TourDeFlex seems to be running ok.  As 
Alina and Pashmina finish up, we'll see how a really big Flex migration 
performs in Royale.  

It has taken them longer than expected, but for every bug or missing feature 
that is emulated correctly, the time to migrate for the next person goes down.  
And as 2019 becomes 2020, there will be less time to migrate for some folks, so 
having more people on the emulation helps everyone else.

So, we should figure out where to place information like this so Chris and 
others find it more easily.  Once a component set/migration strategy is chosen, 
it focuses a lot of other questions, such as how to do skinning, or how much 
about Strands and Beads you have to know.  In fact, it would be great to find a 
place to recommend to folks that when they write to us with questions that they 
specify which component set(s) they are using because the answer can be quite 
different based on the component sets involved.

Suggestions from Chris and others as to how to make this information more 
accessible are encouraged.

My 2 cents,
-Alex

On 10/8/19, 8:18 AM, "Carlos Rovira"  wrote:

Hi,

I mean that like RO, that's a non visual component used to perform
communications, we have other "components" or "code" that can be
implemented as beads or strands.
The concept behind is that Royale have the minimum code needed for
functionality, and compose other parts (whatever the purpose of the code
could be). So while UI Components use to refer to code that are visual and
use to be a Button, a List or a Checkbox, strands are more agonistic about
that particular use case, so seems, IMHO a better way to describe it from
that point of view.

El mar., 8 oct. 2019 a las 10:14, Chris Velevitch (<
chris.velevi...@gmail.com>) escribió:

> So you are suggesting a RemoteObject is a headless component who's
> base class only supports the model and controller plugins and that UI
> classes extend the headless component to add in the view?
>
> On Tue, 8 Oct 2019 at 15:52, Carlos Rovira 
> wrote:
> >
> > Hi Chris,
> >
> > thanks for sharing your thoughts.
> >
> > IMHO, not always a "strand" is a "visual component". This relation is 
not
> > always true. a strand could be a non visual component (for example the
> > implementation of RemoteObject in the Network library). And a bead could
> be
> > a strand itself.
> >
> > I think the term component is right in most cases and accomplish a
> meaning
> > purpose, but strand/beads concept comes to give another subset of 
meaning
> >
> > just my opinion about this.
> >
> > Carlos
> >
> >
> >
> > El mar., 8 oct. 2019 a las 9:23, Chris Velevitch (<
> chris.velevi...@gmail.com>)
> > escribió:
> >
> > > The use of the terms "strands" and "beads" still doesn't make sense to
> > > me because they are concepts I have never heard before and it is
> > > creating a barrier to acceptance and deepens the learning curve. As
> > > far as I can tell, it's something to do with visual/UI components.
> > >
> > > The section "Strands and Beads" should ideally be titled "Visual
> > > Components" because that section is about visual components and is
> > > alluding to the fact visual components are standalone microcosms of
> > > the MVC pattern and the ability to treat the model, view and
> > > controller as plugins to the component.

Re: Pay as You Go (PAYG) Suggestion

2019-10-08 Thread Alex Harui

The compiler is theoretically designed to allow for different Emitters and 
Publishers that can output different JS to support other module and 
minification systems.  Volunteers are welcome to work on those.

However, the Strands and Beads idea is not about minification for Google 
Closure or WebPack at all.  Royale (and Flex) are designed for "Really Really 
Big" applications where the source code is not compiled all at once.  It might 
be broken into what Flex and Royale still call Modules, or in some cases, 
SubApplications.  In these cases, it is should not be a requirement to be able 
to statically know what APIs in one compilation will be used by another 
compilation.  Some of these compilations will be done by different teams, or 
written once and never compiled again (think of a government's form filling 
app).   That's why in Royale today, we automatically export all public APIs to 
prevent them from being removed as dead-code by the Google Closure minifier.  
We just don't know if that API is going to be used by a Module later.

Royale and Flex also allow syntax that prevents (or at least complicates) 
static analysis and dead code removal.  You can write code that does:

Var obj:*;
Obj["w" + "idth"] = 0;

That's a contrived example, but I've seen more practical ones that would take 
longer to describe.

So, Strands and Beads are intended to implement PAYG to allow the developer to:
1) get better granularity over what APIs are in the final output
2) reduce choices in the IDE code assist
3) re-use as much code as possible to optimize download size and runtime 
performance.

HTH,
-Alex

On 10/8/19, 8:45 AM, "Josh Tynjala"  wrote:

It is worth mentioning that Royale uses Google's Closure compiler when
creating release builds. Closure compiler does very advanced JavaScript
code analysis that eliminates unused code from the final output, so it has
a very similar effect to tree shaking.

The ability to integrate into a webpack build pipeline would be really
nice, though, since webpack is such a popular tool in the JS ecosystem.

--
Josh Tynjala
Bowler Hat LLC 

On Tue, Oct 8, 2019 at 1:00 AM Chris Velevitch 
wrote:

> If the whole point of PAYG is to eliminate unused code from being
> included in the final app distribution, then I'd like to suggest that
> we take advantage of the tools the JavaScript ecosystem already has
> for eliminating unused code.
>
> I think we should take a look at Webpack [1] and create a compilation
> pipeline that feeds into Webpack to create the final compacted
> distributable app.
>
>
>
> [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwebpack.js.org%2Fguides%2Ftree-shaking%2Fdata=02%7C01%7Caharui%40adobe.com%7Cc7d79fa2927d4e731b8b08d74c068e25%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637061463354123380sdata=4BJ5JjTodiGxukbMgSO%2FAhhapC0q5FqONCaCe3KQcks%3Dreserved=0
>

Re: Nightly Build Server going offline

2019-10-08 Thread Alex Harui

I am definitely planning to start rebuilding the server today.  Keep your 
fingers crossed.

-Alex

On 10/7/19, 8:47 AM, "Alex Harui"  wrote:

I think the merge happened, so I am going to try to do the rebuild this 
week, probably on my Tuesday if I can finish up some fixes to 
releasecandidate.xml needed for Windows today.

-Alex

On 10/7/19, 12:39 AM, "Carlos Rovira"  wrote:

Hi,

don't think a day be a problem. When can better warn in social networks
about that 24h unavailability.
Other option is to store in pre web server (Royale.codeoscopic.com). You
have credentials and can upload to Wordpress and then we can share that
link.
Whatever option could be fine, but for a day, I don't think we should
invest much time.

thanks!



El dom., 6 oct. 2019 a las 9:28, Harbs () 
escribió:

> Seems fine to me.
>
> > On Oct 6, 2019, at 1:33 AM, Alex Harui  
wrote:
> >
> > I was only thinking about temporary distribution of the nightly 
build
> while the CI server is offline.  I'm not sure it makes sense to 
always copy
> the nightly build somewhere else.  I think the bandwidth would add up.
> >
> > I'm mainly asking if anyone thinks it would be a problem if the 
nightly
> builds were unavailable for a day (hopefully only a day).
> >
> > -Alex
> >
> > On 10/5/19, 6:41 AM, "Carlos Rovira"  carlosrov...@apache.org>> wrote:
> >
> >Hi Alex,
> >
> >you're talking about just storing nightly builds? what about 
using
> some
> >free storage out there, like a google drive, dropbox, or other
> service like
> >this. We can create an "apacheroyale" account and share 
credentials in
> >private.
> >
> >El sáb., 5 oct. 2019 a las 2:18, Alex Harui 
( >)
> >escribió:
> >
> >> Hi,
> >>
> >> To prove that we can rebuild our nightly build server (so that 
someone
> >> else can host a build server someday and to prove we know what our
> >> dependencies are), I'm going to try to rebuild it once the release
> branch
> >> is merged into develop.  Could just take a day if I've saved a 
record of
> >> everything we need.  Or not...
> >>
> >> There will be other emails when I finally shut it down to try it.  
If
> >> someone wants to host the last nightly somewhere and update our 
links to
> >> it, great, otherwise we'll just cross our fingers...
> >>
> >> Thanks,
> >> -Alex
> >>
> >>
> >
> >--
> >Carlos Rovira
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C6f4957799c04453d1ef308d74b3da007%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637060600359555721sdata=AB%2BoIdhv4B5EMHSvpOwX9XEZTPgZVdW5Rs7mOEI0fHw%3Dreserved=0
> <
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C6f4957799c04453d1ef308d74b3da007%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637060600359565716sdata=O6hyvC%2FH%2BuPOuD8K%2FHBC4YYM71aEPEcvMs8ufKZkXqU%3Dreserved=0
> >
>


-- 
Carlos Rovira

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosroviradata=02%7C01%7Caharui%40adobe.com%7C6f4957799c04453d1ef308d74b3da007%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637060600359565716sdata=O6hyvC%2FH%2BuPOuD8K%2FHBC4YYM71aEPEcvMs8ufKZkXqU%3Dreserved=0

Re: Pay as You Go (PAYG) Suggestion

2019-10-08 Thread Josh Tynjala

It is worth mentioning that Royale uses Google's Closure compiler when
creating release builds. Closure compiler does very advanced JavaScript
code analysis that eliminates unused code from the final output, so it has
a very similar effect to tree shaking.

The ability to integrate into a webpack build pipeline would be really
nice, though, since webpack is such a popular tool in the JS ecosystem.

--
Josh Tynjala
Bowler Hat LLC 

On Tue, Oct 8, 2019 at 1:00 AM Chris Velevitch 
wrote:

> If the whole point of PAYG is to eliminate unused code from being
> included in the final app distribution, then I'd like to suggest that
> we take advantage of the tools the JavaScript ecosystem already has
> for eliminating unused code.
>
> I think we should take a look at Webpack [1] and create a compilation
> pipeline that feeds into Webpack to create the final compacted
> distributable app.
>
>
>
> [1] https://webpack.js.org/guides/tree-shaking/
>

Re: How to skin components

2019-10-08 Thread Carlos Rovira

Hi Chris,
before going far beyond, I want that you consider the way you are referring
to the concepts you don't share. Talk about that as "silly" seems not very
appropriate.
We try to respect as much as possible, the work and proposals from others.
You can disagree, but please maintain a level of respect since that way
will make others not want to enter the conversation.

Thanks in advance.

El mar., 8 oct. 2019 a las 9:47, Chris Velevitch ()
escribió:

> When I was going through the documentation and code to get my head
> around this silly notation of "beads" and "strands", I realised the
> component plugins are very similar to the concept of skinning
> components that Adobe Flex talks about. And there doesn't seem to be
> any discussions on how to skin a component.
>
> I also noticed, there's no discussion on how plugins and components
> talk to each other and whether that is bidirectional or one-way.
>


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

Re: Acceptance of Royale by Flex Developers

2019-10-08 Thread Carlos Rovira

Hi,

I mean that like RO, that's a non visual component used to perform
communications, we have other "components" or "code" that can be
implemented as beads or strands.
The concept behind is that Royale have the minimum code needed for
functionality, and compose other parts (whatever the purpose of the code
could be). So while UI Components use to refer to code that are visual and
use to be a Button, a List or a Checkbox, strands are more agonistic about
that particular use case, so seems, IMHO a better way to describe it from
that point of view.

El mar., 8 oct. 2019 a las 10:14, Chris Velevitch (<
chris.velevi...@gmail.com>) escribió:

> So you are suggesting a RemoteObject is a headless component who's
> base class only supports the model and controller plugins and that UI
> classes extend the headless component to add in the view?
>
> On Tue, 8 Oct 2019 at 15:52, Carlos Rovira 
> wrote:
> >
> > Hi Chris,
> >
> > thanks for sharing your thoughts.
> >
> > IMHO, not always a "strand" is a "visual component". This relation is not
> > always true. a strand could be a non visual component (for example the
> > implementation of RemoteObject in the Network library). And a bead could
> be
> > a strand itself.
> >
> > I think the term component is right in most cases and accomplish a
> meaning
> > purpose, but strand/beads concept comes to give another subset of meaning
> >
> > just my opinion about this.
> >
> > Carlos
> >
> >
> >
> > El mar., 8 oct. 2019 a las 9:23, Chris Velevitch (<
> chris.velevi...@gmail.com>)
> > escribió:
> >
> > > The use of the terms "strands" and "beads" still doesn't make sense to
> > > me because they are concepts I have never heard before and it is
> > > creating a barrier to acceptance and deepens the learning curve. As
> > > far as I can tell, it's something to do with visual/UI components.
> > >
> > > The section "Strands and Beads" should ideally be titled "Visual
> > > Components" because that section is about visual components and is
> > > alluding to the fact visual components are standalone microcosms of
> > > the MVC pattern and the ability to treat the model, view and
> > > controller as plugins to the component. The statement that components
> > > are "strands" is, in my mind, misleading because it doesn't make sense
> > > to interchange terms components and strands if a strand is a
> > > component. In fact, diving into the code, the "addBead" function gives
> > > the "bead" a reference to the component the "bead" is being added to.
> > >
> > > It is clear from the documentation that "beads" are "plugins" and the
> > > documentation should be talking about extending components with
> > > plugins. All references to "bead" should be replaced with "plugin" and
> > > all references to "strand" be replaced with either "hostComponent", or
> > > "parent" or appropriately something else.
> > >
> > > We seem to be neglecting the rich heritage that we have gotten from
> > > Adobe Flex and I don't see the point giving existing concepts new
> > > names.
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
>
> --
>
>
> Chris
> --
> Chris Velevitch
> m: 0415 469 095
>


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

Re: Component Sets

2019-10-08 Thread Carlos Rovira

Hi Chris,

although we get a much better docswith the work in the latest months,
there's still many missing points to cover, some with its own reserved
place, but still empty, and others will need to reserve its place. As
always we'll try our best to cover it as soon as possible. To be fastest we
want others to join us and help us to make Royale better and bigger. You're
welcome to join and contribute if you consider worth it and fun :)

El mar., 8 oct. 2019 a las 10:36, Andrew Wetmore ()
escribió:

> There is not such a document yet, no. Help creating one would be welcome.
>
> On Tue, Oct 8, 2019 at 4:22 AM Chris Velevitch 
> wrote:
>
> > There doesn't seem to be an all-encompassing document describing, MX,
> > Spark and Jewel components and as well as the pros and cons of each
> > nor is there a discussion on using third party web components,
> > creating custom web components and how to the material design
> > components.
> >
>
>
> --
> Andrew Wetmore
>
> http://cottage14.blogspot.com/
>

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

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Andrew Wetmore

Got it! Thanks!

On Tue, Oct 8, 2019 at 10:49 AM Carlos Rovira 
wrote:

> Yes! that's it :)
>
>
> El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > I think that would be the link:
> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> >
> > wt., 8 paź 2019 o 16:29 Andrew Wetmore  napisał(a):
> >
> > > @Carlos Rovira  where is the draft post? I
> had
> > a
> > > hard disk failure this past weekend and am slowly rebuilding my system.
> > > Have to find all my links again.
> > >
> > > a
> > >
> > > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore 
> > wrote:
> > >
> > > > I can do this in a couple of hours
> > > >
> > > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira,  >
> > > > wrote:
> > > >
> > > >> Hi Piotr,
> > > >>
> > > >> I'll wait Andrew's review and then will publish it. If Andrew make
> his
> > > >> changes this afternoon, I can follow up and publish it.
> > > >> Then we can post on social networks next or wait to tomorrow
> > > >>
> > > >>
> > > >>
> > > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
> > > >> piotrzarzyck...@gmail.com>)
> > > >> escribió:
> > > >>
> > > >> > Just to make sure that you understand why I asked you to post
> > download
> > > >> > links on website along with source code.
> > > >> >
> > > >> > I will announce on dev, users and announce list - someone who read
> > > >> email -
> > > >> > will have two options:
> > > >> > 1) Can click in that email on royale.apache.org
> > > >> > 2) Can download directly binaries or source code from provided
> links
> > > in
> > > >> the
> > > >> > email
> > > >> >
> > > >> > If user do #1 he will see old links on website which will be
> > > >> misleading. -
> > > >> > Do you understand now why I asked you to publish stuff first ?
> > > >> >
> > > >> > However as I said if you prefer do this in a opposite way that's
> > fine
> > > >> with
> > > >> > me. :)
> > > >> >
> > > >> >
> > > >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki  >
> > > >> > napisał(a):
> > > >> >
> > > >> > > This is the goal of syncing everything tomorrow. I asked you to
> > > >> publish
> > > >> > > first link and source code on website, cause my announce
> probably
> > go
> > > >> > first
> > > >> > > one and I didn't want to mislead with what will be on website.
> > > >> However if
> > > >> > > you wanted to do that differently I'm fine - Couple of hours of
> > > >> > misleading
> > > >> > > doesn't hurts anyone maybe. - We will see tomorrow.
> > > >> > >
> > > >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira 
> > > >> > > napisał(a):
> > > >> > >
> > > >> > >> Hi,
> > > >> > >> ok, is normal,
> > > >> > >> as people following our dev, are as well using links to 0.9.6
> > > >> releases.
> > > >> > >> The update of links in website is more about to announce to the
> > > rest
> > > >> of
> > > >> > >> the
> > > >> > >> world that is not as close to us as the rest of community.
> > > >> > >> So it's important to communicate in the most organized way we
> > can.
> > > >> > >>
> > > >> > >> thanks!
> > > >> > >>
> > > >> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> > > >> > >> piotrzarzyck...@gmail.com>)
> > > >> > >> escribió:
> > > >> > >>
> > > >> > >> > Just FYI: npm stuff and Maven artifacts are being published
> for
> > > >> couple
> > > >> > >> of
> > > >> > >> > days already, so people are using released 0.9.6 trough npm.
> -
> > > It's
> > > >> > >> happen
> > > >> > >> > automatically in case of npm.
> > > >> > >> >
> > > >> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki <
> > > piotrzarzyck...@gmail.com>
> > > >> > >> > napisał(a):
> > > >> > >> >
> > > >> > >> > > Fine with me. I make announce tomorrow morning and review
> > what
> > > >> was
> > > >> > >> your
> > > >> > >> > > change and update Draft.
> > > >> > >> > >
> > > >> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira <
> > carlosrov...@apache.org
> > > >
> > > >> > >> > > napisał(a):
> > > >> > >> > >
> > > >> > >> > >> Hi, Piotr,
> > > >> > >> > >>
> > > >> > >> > >> I think we should update all at the same time, since we
> want
> > > to
> > > >> > post
> > > >> > >> in
> > > >> > >> > >> twitter, Facebook and linkedin.
> > > >> > >> > >> Doesn't have sense to me upload just a few links since
> > almost
> > > >> > nobody
> > > >> > >> > will
> > > >> > >> > >> notice it (and are already in GitHub releases). If we need
> > to
> > > >> wait
> > > >> > a
> > > >> > >> day
> > > >> > >> > >> to
> > > >> > >> > >> send the official announcement it's ok for me. We can
> finish
> > > to
> > > >> > >> improve
> > > >> > >> > >> the
> > > >> > >> > >> blog post in the meanwhile to do it better.
> > > >> > >> > >>
> > > >> > >> > >> For example, I changed a bit the wording, since we are not
> > as
> > > >> > >> "early" or
> > > >> > >> > >> "alpha" and I mention as well that we have Apps in
> > production,
> > > >> what
> > > >> > >> is
> > > >> > >> > now
> > > >> > >> > >> important.
> > > >> > >> > >> And finally talk about the

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Carlos Rovira

Yes! that's it :)


El mar., 8 oct. 2019 a las 16:31, Piotr Zarzycki ()
escribió:

> I think that would be the link:
> https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>
> wt., 8 paź 2019 o 16:29 Andrew Wetmore  napisał(a):
>
> > @Carlos Rovira  where is the draft post? I had
> a
> > hard disk failure this past weekend and am slowly rebuilding my system.
> > Have to find all my links again.
> >
> > a
> >
> > On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore 
> wrote:
> >
> > > I can do this in a couple of hours
> > >
> > > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, 
> > > wrote:
> > >
> > >> Hi Piotr,
> > >>
> > >> I'll wait Andrew's review and then will publish it. If Andrew make his
> > >> changes this afternoon, I can follow up and publish it.
> > >> Then we can post on social networks next or wait to tomorrow
> > >>
> > >>
> > >>
> > >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
> > >> piotrzarzyck...@gmail.com>)
> > >> escribió:
> > >>
> > >> > Just to make sure that you understand why I asked you to post
> download
> > >> > links on website along with source code.
> > >> >
> > >> > I will announce on dev, users and announce list - someone who read
> > >> email -
> > >> > will have two options:
> > >> > 1) Can click in that email on royale.apache.org
> > >> > 2) Can download directly binaries or source code from provided links
> > in
> > >> the
> > >> > email
> > >> >
> > >> > If user do #1 he will see old links on website which will be
> > >> misleading. -
> > >> > Do you understand now why I asked you to publish stuff first ?
> > >> >
> > >> > However as I said if you prefer do this in a opposite way that's
> fine
> > >> with
> > >> > me. :)
> > >> >
> > >> >
> > >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
> > >> > napisał(a):
> > >> >
> > >> > > This is the goal of syncing everything tomorrow. I asked you to
> > >> publish
> > >> > > first link and source code on website, cause my announce probably
> go
> > >> > first
> > >> > > one and I didn't want to mislead with what will be on website.
> > >> However if
> > >> > > you wanted to do that differently I'm fine - Couple of hours of
> > >> > misleading
> > >> > > doesn't hurts anyone maybe. - We will see tomorrow.
> > >> > >
> > >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira 
> > >> > > napisał(a):
> > >> > >
> > >> > >> Hi,
> > >> > >> ok, is normal,
> > >> > >> as people following our dev, are as well using links to 0.9.6
> > >> releases.
> > >> > >> The update of links in website is more about to announce to the
> > rest
> > >> of
> > >> > >> the
> > >> > >> world that is not as close to us as the rest of community.
> > >> > >> So it's important to communicate in the most organized way we
> can.
> > >> > >>
> > >> > >> thanks!
> > >> > >>
> > >> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> > >> > >> piotrzarzyck...@gmail.com>)
> > >> > >> escribió:
> > >> > >>
> > >> > >> > Just FYI: npm stuff and Maven artifacts are being published for
> > >> couple
> > >> > >> of
> > >> > >> > days already, so people are using released 0.9.6 trough npm. -
> > It's
> > >> > >> happen
> > >> > >> > automatically in case of npm.
> > >> > >> >
> > >> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > >> > >> > napisał(a):
> > >> > >> >
> > >> > >> > > Fine with me. I make announce tomorrow morning and review
> what
> > >> was
> > >> > >> your
> > >> > >> > > change and update Draft.
> > >> > >> > >
> > >> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira <
> carlosrov...@apache.org
> > >
> > >> > >> > > napisał(a):
> > >> > >> > >
> > >> > >> > >> Hi, Piotr,
> > >> > >> > >>
> > >> > >> > >> I think we should update all at the same time, since we want
> > to
> > >> > post
> > >> > >> in
> > >> > >> > >> twitter, Facebook and linkedin.
> > >> > >> > >> Doesn't have sense to me upload just a few links since
> almost
> > >> > nobody
> > >> > >> > will
> > >> > >> > >> notice it (and are already in GitHub releases). If we need
> to
> > >> wait
> > >> > a
> > >> > >> day
> > >> > >> > >> to
> > >> > >> > >> send the official announcement it's ok for me. We can finish
> > to
> > >> > >> improve
> > >> > >> > >> the
> > >> > >> > >> blog post in the meanwhile to do it better.
> > >> > >> > >>
> > >> > >> > >> For example, I changed a bit the wording, since we are not
> as
> > >> > >> "early" or
> > >> > >> > >> "alpha" and I mention as well that we have Apps in
> production,
> > >> what
> > >> > >> is
> > >> > >> > now
> > >> > >> > >> important.
> > >> > >> > >> And finally talk about the improved Royale Docs that will be
> > of
> > >> > help
> > >> > >> for
> > >> > >> > >> newcomers.
> > >> > >> > >>
> > >> > >> > >> I think Andrew can review the blog post and improve it and
> > then
> > >> be
> > >> > >> ready
> > >> > >> > >> to
> > >> > >> > >> publish all tomorrow.
> > >> > >> > >>
> > >> > >> > >> As well if someone notice something that needs to be updated
> > can
> > >> > >> notify
> > >> > >> > >>

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki

I think that would be the link:
https://royale.codeoscopic.com/apache-royale-v0-9-6-released/

wt., 8 paź 2019 o 16:29 Andrew Wetmore  napisał(a):

> @Carlos Rovira  where is the draft post? I had a
> hard disk failure this past weekend and am slowly rebuilding my system.
> Have to find all my links again.
>
> a
>
> On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore  wrote:
>
> > I can do this in a couple of hours
> >
> > On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, 
> > wrote:
> >
> >> Hi Piotr,
> >>
> >> I'll wait Andrew's review and then will publish it. If Andrew make his
> >> changes this afternoon, I can follow up and publish it.
> >> Then we can post on social networks next or wait to tomorrow
> >>
> >>
> >>
> >> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >> escribió:
> >>
> >> > Just to make sure that you understand why I asked you to post download
> >> > links on website along with source code.
> >> >
> >> > I will announce on dev, users and announce list - someone who read
> >> email -
> >> > will have two options:
> >> > 1) Can click in that email on royale.apache.org
> >> > 2) Can download directly binaries or source code from provided links
> in
> >> the
> >> > email
> >> >
> >> > If user do #1 he will see old links on website which will be
> >> misleading. -
> >> > Do you understand now why I asked you to publish stuff first ?
> >> >
> >> > However as I said if you prefer do this in a opposite way that's fine
> >> with
> >> > me. :)
> >> >
> >> >
> >> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
> >> > napisał(a):
> >> >
> >> > > This is the goal of syncing everything tomorrow. I asked you to
> >> publish
> >> > > first link and source code on website, cause my announce probably go
> >> > first
> >> > > one and I didn't want to mislead with what will be on website.
> >> However if
> >> > > you wanted to do that differently I'm fine - Couple of hours of
> >> > misleading
> >> > > doesn't hurts anyone maybe. - We will see tomorrow.
> >> > >
> >> > > wt., 8 paź 2019 o 11:05 Carlos Rovira 
> >> > > napisał(a):
> >> > >
> >> > >> Hi,
> >> > >> ok, is normal,
> >> > >> as people following our dev, are as well using links to 0.9.6
> >> releases.
> >> > >> The update of links in website is more about to announce to the
> rest
> >> of
> >> > >> the
> >> > >> world that is not as close to us as the rest of community.
> >> > >> So it's important to communicate in the most organized way we can.
> >> > >>
> >> > >> thanks!
> >> > >>
> >> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> >> > >> piotrzarzyck...@gmail.com>)
> >> > >> escribió:
> >> > >>
> >> > >> > Just FYI: npm stuff and Maven artifacts are being published for
> >> couple
> >> > >> of
> >> > >> > days already, so people are using released 0.9.6 trough npm. -
> It's
> >> > >> happen
> >> > >> > automatically in case of npm.
> >> > >> >
> >> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> > >> > napisał(a):
> >> > >> >
> >> > >> > > Fine with me. I make announce tomorrow morning and review what
> >> was
> >> > >> your
> >> > >> > > change and update Draft.
> >> > >> > >
> >> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira  >
> >> > >> > > napisał(a):
> >> > >> > >
> >> > >> > >> Hi, Piotr,
> >> > >> > >>
> >> > >> > >> I think we should update all at the same time, since we want
> to
> >> > post
> >> > >> in
> >> > >> > >> twitter, Facebook and linkedin.
> >> > >> > >> Doesn't have sense to me upload just a few links since almost
> >> > nobody
> >> > >> > will
> >> > >> > >> notice it (and are already in GitHub releases). If we need to
> >> wait
> >> > a
> >> > >> day
> >> > >> > >> to
> >> > >> > >> send the official announcement it's ok for me. We can finish
> to
> >> > >> improve
> >> > >> > >> the
> >> > >> > >> blog post in the meanwhile to do it better.
> >> > >> > >>
> >> > >> > >> For example, I changed a bit the wording, since we are not as
> >> > >> "early" or
> >> > >> > >> "alpha" and I mention as well that we have Apps in production,
> >> what
> >> > >> is
> >> > >> > now
> >> > >> > >> important.
> >> > >> > >> And finally talk about the improved Royale Docs that will be
> of
> >> > help
> >> > >> for
> >> > >> > >> newcomers.
> >> > >> > >>
> >> > >> > >> I think Andrew can review the blog post and improve it and
> then
> >> be
> >> > >> ready
> >> > >> > >> to
> >> > >> > >> publish all tomorrow.
> >> > >> > >>
> >> > >> > >> As well if someone notice something that needs to be updated
> can
> >> > >> notify
> >> > >> > >> us.
> >> > >> > >>
> >> > >> > >> Thanks
> >> > >> > >>
> >> > >> > >>
> >> > >> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> >> > >> > >> piotrzarzyck...@gmail.com>)
> >> > >> > >> escribió:
> >> > >> > >>
> >> > >> > >> > Download and source code websites looks good to me. In blog
> >> post
> >> > >> you
> >> > >> > >> have
> >> > >> > >> > broken github links - review them and fix.
> >> > >> > >> >
> >> > >> > >>

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Andrew Wetmore

@Carlos Rovira  where is the draft post? I had a
hard disk failure this past weekend and am slowly rebuilding my system.
Have to find all my links again.

a

On Tue, Oct 8, 2019 at 9:48 AM Andrew Wetmore  wrote:

> I can do this in a couple of hours
>
> On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira, 
> wrote:
>
>> Hi Piotr,
>>
>> I'll wait Andrew's review and then will publish it. If Andrew make his
>> changes this afternoon, I can follow up and publish it.
>> Then we can post on social networks next or wait to tomorrow
>>
>>
>>
>> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > Just to make sure that you understand why I asked you to post download
>> > links on website along with source code.
>> >
>> > I will announce on dev, users and announce list - someone who read
>> email -
>> > will have two options:
>> > 1) Can click in that email on royale.apache.org
>> > 2) Can download directly binaries or source code from provided links in
>> the
>> > email
>> >
>> > If user do #1 he will see old links on website which will be
>> misleading. -
>> > Do you understand now why I asked you to publish stuff first ?
>> >
>> > However as I said if you prefer do this in a opposite way that's fine
>> with
>> > me. :)
>> >
>> >
>> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
>> > napisał(a):
>> >
>> > > This is the goal of syncing everything tomorrow. I asked you to
>> publish
>> > > first link and source code on website, cause my announce probably go
>> > first
>> > > one and I didn't want to mislead with what will be on website.
>> However if
>> > > you wanted to do that differently I'm fine - Couple of hours of
>> > misleading
>> > > doesn't hurts anyone maybe. - We will see tomorrow.
>> > >
>> > > wt., 8 paź 2019 o 11:05 Carlos Rovira 
>> > > napisał(a):
>> > >
>> > >> Hi,
>> > >> ok, is normal,
>> > >> as people following our dev, are as well using links to 0.9.6
>> releases.
>> > >> The update of links in website is more about to announce to the rest
>> of
>> > >> the
>> > >> world that is not as close to us as the rest of community.
>> > >> So it's important to communicate in the most organized way we can.
>> > >>
>> > >> thanks!
>> > >>
>> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
>> > >> piotrzarzyck...@gmail.com>)
>> > >> escribió:
>> > >>
>> > >> > Just FYI: npm stuff and Maven artifacts are being published for
>> couple
>> > >> of
>> > >> > days already, so people are using released 0.9.6 trough npm. - It's
>> > >> happen
>> > >> > automatically in case of npm.
>> > >> >
>> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
>> > >> > napisał(a):
>> > >> >
>> > >> > > Fine with me. I make announce tomorrow morning and review what
>> was
>> > >> your
>> > >> > > change and update Draft.
>> > >> > >
>> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira 
>> > >> > > napisał(a):
>> > >> > >
>> > >> > >> Hi, Piotr,
>> > >> > >>
>> > >> > >> I think we should update all at the same time, since we want to
>> > post
>> > >> in
>> > >> > >> twitter, Facebook and linkedin.
>> > >> > >> Doesn't have sense to me upload just a few links since almost
>> > nobody
>> > >> > will
>> > >> > >> notice it (and are already in GitHub releases). If we need to
>> wait
>> > a
>> > >> day
>> > >> > >> to
>> > >> > >> send the official announcement it's ok for me. We can finish to
>> > >> improve
>> > >> > >> the
>> > >> > >> blog post in the meanwhile to do it better.
>> > >> > >>
>> > >> > >> For example, I changed a bit the wording, since we are not as
>> > >> "early" or
>> > >> > >> "alpha" and I mention as well that we have Apps in production,
>> what
>> > >> is
>> > >> > now
>> > >> > >> important.
>> > >> > >> And finally talk about the improved Royale Docs that will be of
>> > help
>> > >> for
>> > >> > >> newcomers.
>> > >> > >>
>> > >> > >> I think Andrew can review the blog post and improve it and then
>> be
>> > >> ready
>> > >> > >> to
>> > >> > >> publish all tomorrow.
>> > >> > >>
>> > >> > >> As well if someone notice something that needs to be updated can
>> > >> notify
>> > >> > >> us.
>> > >> > >>
>> > >> > >> Thanks
>> > >> > >>
>> > >> > >>
>> > >> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
>> > >> > >> piotrzarzyck...@gmail.com>)
>> > >> > >> escribió:
>> > >> > >>
>> > >> > >> > Download and source code websites looks good to me. In blog
>> post
>> > >> you
>> > >> > >> have
>> > >> > >> > broken github links - review them and fix.
>> > >> > >> >
>> > >> > >> > Apart of that publish only Download and Source code. Blog post
>> > >> should
>> > >> > be
>> > >> > >> > publish after I think official announce on dev, users and
>> > announce
>> > >> > >> mailing
>> > >> > >> > list. I'm going to do that tomorrow, cause there is still time
>> > for
>> > >> > >> review
>> > >> > >> > Draft of announcement.
>> > >> > >> >
>> > >> > >> > Thanks,
>> > >> > >> > Piotr
>> > >> > >> >
>> > >> > >> > wt., 8 paź 2019 o 10:32 Carlos Rovira <
>>

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Andrew Wetmore

I can do this in a couple of hours

On Tue, Oct 8, 2019, 9:24 AM Carlos Rovira,  wrote:

> Hi Piotr,
>
> I'll wait Andrew's review and then will publish it. If Andrew make his
> changes this afternoon, I can follow up and publish it.
> Then we can post on social networks next or wait to tomorrow
>
>
>
> El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Just to make sure that you understand why I asked you to post download
> > links on website along with source code.
> >
> > I will announce on dev, users and announce list - someone who read email
> -
> > will have two options:
> > 1) Can click in that email on royale.apache.org
> > 2) Can download directly binaries or source code from provided links in
> the
> > email
> >
> > If user do #1 he will see old links on website which will be misleading.
> -
> > Do you understand now why I asked you to publish stuff first ?
> >
> > However as I said if you prefer do this in a opposite way that's fine
> with
> > me. :)
> >
> >
> > wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
> > napisał(a):
> >
> > > This is the goal of syncing everything tomorrow. I asked you to publish
> > > first link and source code on website, cause my announce probably go
> > first
> > > one and I didn't want to mislead with what will be on website. However
> if
> > > you wanted to do that differently I'm fine - Couple of hours of
> > misleading
> > > doesn't hurts anyone maybe. - We will see tomorrow.
> > >
> > > wt., 8 paź 2019 o 11:05 Carlos Rovira 
> > > napisał(a):
> > >
> > >> Hi,
> > >> ok, is normal,
> > >> as people following our dev, are as well using links to 0.9.6
> releases.
> > >> The update of links in website is more about to announce to the rest
> of
> > >> the
> > >> world that is not as close to us as the rest of community.
> > >> So it's important to communicate in the most organized way we can.
> > >>
> > >> thanks!
> > >>
> > >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> > >> piotrzarzyck...@gmail.com>)
> > >> escribió:
> > >>
> > >> > Just FYI: npm stuff and Maven artifacts are being published for
> couple
> > >> of
> > >> > days already, so people are using released 0.9.6 trough npm. - It's
> > >> happen
> > >> > automatically in case of npm.
> > >> >
> > >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
> > >> > napisał(a):
> > >> >
> > >> > > Fine with me. I make announce tomorrow morning and review what was
> > >> your
> > >> > > change and update Draft.
> > >> > >
> > >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira 
> > >> > > napisał(a):
> > >> > >
> > >> > >> Hi, Piotr,
> > >> > >>
> > >> > >> I think we should update all at the same time, since we want to
> > post
> > >> in
> > >> > >> twitter, Facebook and linkedin.
> > >> > >> Doesn't have sense to me upload just a few links since almost
> > nobody
> > >> > will
> > >> > >> notice it (and are already in GitHub releases). If we need to
> wait
> > a
> > >> day
> > >> > >> to
> > >> > >> send the official announcement it's ok for me. We can finish to
> > >> improve
> > >> > >> the
> > >> > >> blog post in the meanwhile to do it better.
> > >> > >>
> > >> > >> For example, I changed a bit the wording, since we are not as
> > >> "early" or
> > >> > >> "alpha" and I mention as well that we have Apps in production,
> what
> > >> is
> > >> > now
> > >> > >> important.
> > >> > >> And finally talk about the improved Royale Docs that will be of
> > help
> > >> for
> > >> > >> newcomers.
> > >> > >>
> > >> > >> I think Andrew can review the blog post and improve it and then
> be
> > >> ready
> > >> > >> to
> > >> > >> publish all tomorrow.
> > >> > >>
> > >> > >> As well if someone notice something that needs to be updated can
> > >> notify
> > >> > >> us.
> > >> > >>
> > >> > >> Thanks
> > >> > >>
> > >> > >>
> > >> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> > >> > >> piotrzarzyck...@gmail.com>)
> > >> > >> escribió:
> > >> > >>
> > >> > >> > Download and source code websites looks good to me. In blog
> post
> > >> you
> > >> > >> have
> > >> > >> > broken github links - review them and fix.
> > >> > >> >
> > >> > >> > Apart of that publish only Download and Source code. Blog post
> > >> should
> > >> > be
> > >> > >> > publish after I think official announce on dev, users and
> > announce
> > >> > >> mailing
> > >> > >> > list. I'm going to do that tomorrow, cause there is still time
> > for
> > >> > >> review
> > >> > >> > Draft of announcement.
> > >> > >> >
> > >> > >> > Thanks,
> > >> > >> > Piotr
> > >> > >> >
> > >> > >> > wt., 8 paź 2019 o 10:32 Carlos Rovira  >
> > >> > >> > napisał(a):
> > >> > >> >
> > >> > >> > > Hi,
> > >> > >> > >
> > >> > >> > > Thanks Piotr, for the link :)
> > >> > >> > >
> > >> > >> > > I just updated website on pre site please take a quick look
> and
> > >> I'll
> > >> > >> > > publish it:
> > >> > >> > >
> > >> > >> > >
> https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> > >> > >> > >

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Carlos Rovira

Hi Piotr,

I'll wait Andrew's review and then will publish it. If Andrew make his
changes this afternoon, I can follow up and publish it.
Then we can post on social networks next or wait to tomorrow



El mar., 8 oct. 2019 a las 11:21, Piotr Zarzycki ()
escribió:

> Just to make sure that you understand why I asked you to post download
> links on website along with source code.
>
> I will announce on dev, users and announce list - someone who read email -
> will have two options:
> 1) Can click in that email on royale.apache.org
> 2) Can download directly binaries or source code from provided links in the
> email
>
> If user do #1 he will see old links on website which will be misleading. -
> Do you understand now why I asked you to publish stuff first ?
>
> However as I said if you prefer do this in a opposite way that's fine with
> me. :)
>
>
> wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
> napisał(a):
>
> > This is the goal of syncing everything tomorrow. I asked you to publish
> > first link and source code on website, cause my announce probably go
> first
> > one and I didn't want to mislead with what will be on website. However if
> > you wanted to do that differently I'm fine - Couple of hours of
> misleading
> > doesn't hurts anyone maybe. - We will see tomorrow.
> >
> > wt., 8 paź 2019 o 11:05 Carlos Rovira 
> > napisał(a):
> >
> >> Hi,
> >> ok, is normal,
> >> as people following our dev, are as well using links to 0.9.6 releases.
> >> The update of links in website is more about to announce to the rest of
> >> the
> >> world that is not as close to us as the rest of community.
> >> So it's important to communicate in the most organized way we can.
> >>
> >> thanks!
> >>
> >> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >> escribió:
> >>
> >> > Just FYI: npm stuff and Maven artifacts are being published for couple
> >> of
> >> > days already, so people are using released 0.9.6 trough npm. - It's
> >> happen
> >> > automatically in case of npm.
> >> >
> >> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
> >> > napisał(a):
> >> >
> >> > > Fine with me. I make announce tomorrow morning and review what was
> >> your
> >> > > change and update Draft.
> >> > >
> >> > > wt., 8 paź 2019 o 10:46 Carlos Rovira 
> >> > > napisał(a):
> >> > >
> >> > >> Hi, Piotr,
> >> > >>
> >> > >> I think we should update all at the same time, since we want to
> post
> >> in
> >> > >> twitter, Facebook and linkedin.
> >> > >> Doesn't have sense to me upload just a few links since almost
> nobody
> >> > will
> >> > >> notice it (and are already in GitHub releases). If we need to wait
> a
> >> day
> >> > >> to
> >> > >> send the official announcement it's ok for me. We can finish to
> >> improve
> >> > >> the
> >> > >> blog post in the meanwhile to do it better.
> >> > >>
> >> > >> For example, I changed a bit the wording, since we are not as
> >> "early" or
> >> > >> "alpha" and I mention as well that we have Apps in production, what
> >> is
> >> > now
> >> > >> important.
> >> > >> And finally talk about the improved Royale Docs that will be of
> help
> >> for
> >> > >> newcomers.
> >> > >>
> >> > >> I think Andrew can review the blog post and improve it and then be
> >> ready
> >> > >> to
> >> > >> publish all tomorrow.
> >> > >>
> >> > >> As well if someone notice something that needs to be updated can
> >> notify
> >> > >> us.
> >> > >>
> >> > >> Thanks
> >> > >>
> >> > >>
> >> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> >> > >> piotrzarzyck...@gmail.com>)
> >> > >> escribió:
> >> > >>
> >> > >> > Download and source code websites looks good to me. In blog post
> >> you
> >> > >> have
> >> > >> > broken github links - review them and fix.
> >> > >> >
> >> > >> > Apart of that publish only Download and Source code. Blog post
> >> should
> >> > be
> >> > >> > publish after I think official announce on dev, users and
> announce
> >> > >> mailing
> >> > >> > list. I'm going to do that tomorrow, cause there is still time
> for
> >> > >> review
> >> > >> > Draft of announcement.
> >> > >> >
> >> > >> > Thanks,
> >> > >> > Piotr
> >> > >> >
> >> > >> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
> >> > >> > napisał(a):
> >> > >> >
> >> > >> > > Hi,
> >> > >> > >
> >> > >> > > Thanks Piotr, for the link :)
> >> > >> > >
> >> > >> > > I just updated website on pre site please take a quick look and
> >> I'll
> >> > >> > > publish it:
> >> > >> > >
> >> > >> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> >> > >> > > https://royale.codeoscopic.com/download/
> >> > >> > > https://royale.codeoscopic.com/source-code/
> >> > >> > >
> >> > >> > > thanks
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
> >> > >> > carlosrov...@apache.org
> >> > >> > > >)
> >> > >> > > escribió:
> >> > >> > >
> >> > >> > > > Hi,
> >> > >> > > >
> >> > >> > > > I'm updating all website in pre. I changed download and
> source
> >> > code

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki

Just to make sure that you understand why I asked you to post download
links on website along with source code.

I will announce on dev, users and announce list - someone who read email -
will have two options:
1) Can click in that email on royale.apache.org
2) Can download directly binaries or source code from provided links in the
email

If user do #1 he will see old links on website which will be misleading. -
Do you understand now why I asked you to publish stuff first ?

However as I said if you prefer do this in a opposite way that's fine with
me. :)


wt., 8 paź 2019 o 11:17 Piotr Zarzycki 
napisał(a):

> This is the goal of syncing everything tomorrow. I asked you to publish
> first link and source code on website, cause my announce probably go first
> one and I didn't want to mislead with what will be on website. However if
> you wanted to do that differently I'm fine - Couple of hours of misleading
> doesn't hurts anyone maybe. - We will see tomorrow.
>
> wt., 8 paź 2019 o 11:05 Carlos Rovira 
> napisał(a):
>
>> Hi,
>> ok, is normal,
>> as people following our dev, are as well using links to 0.9.6 releases.
>> The update of links in website is more about to announce to the rest of
>> the
>> world that is not as close to us as the rest of community.
>> So it's important to communicate in the most organized way we can.
>>
>> thanks!
>>
>> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > Just FYI: npm stuff and Maven artifacts are being published for couple
>> of
>> > days already, so people are using released 0.9.6 trough npm. - It's
>> happen
>> > automatically in case of npm.
>> >
>> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
>> > napisał(a):
>> >
>> > > Fine with me. I make announce tomorrow morning and review what was
>> your
>> > > change and update Draft.
>> > >
>> > > wt., 8 paź 2019 o 10:46 Carlos Rovira 
>> > > napisał(a):
>> > >
>> > >> Hi, Piotr,
>> > >>
>> > >> I think we should update all at the same time, since we want to post
>> in
>> > >> twitter, Facebook and linkedin.
>> > >> Doesn't have sense to me upload just a few links since almost nobody
>> > will
>> > >> notice it (and are already in GitHub releases). If we need to wait a
>> day
>> > >> to
>> > >> send the official announcement it's ok for me. We can finish to
>> improve
>> > >> the
>> > >> blog post in the meanwhile to do it better.
>> > >>
>> > >> For example, I changed a bit the wording, since we are not as
>> "early" or
>> > >> "alpha" and I mention as well that we have Apps in production, what
>> is
>> > now
>> > >> important.
>> > >> And finally talk about the improved Royale Docs that will be of help
>> for
>> > >> newcomers.
>> > >>
>> > >> I think Andrew can review the blog post and improve it and then be
>> ready
>> > >> to
>> > >> publish all tomorrow.
>> > >>
>> > >> As well if someone notice something that needs to be updated can
>> notify
>> > >> us.
>> > >>
>> > >> Thanks
>> > >>
>> > >>
>> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
>> > >> piotrzarzyck...@gmail.com>)
>> > >> escribió:
>> > >>
>> > >> > Download and source code websites looks good to me. In blog post
>> you
>> > >> have
>> > >> > broken github links - review them and fix.
>> > >> >
>> > >> > Apart of that publish only Download and Source code. Blog post
>> should
>> > be
>> > >> > publish after I think official announce on dev, users and announce
>> > >> mailing
>> > >> > list. I'm going to do that tomorrow, cause there is still time for
>> > >> review
>> > >> > Draft of announcement.
>> > >> >
>> > >> > Thanks,
>> > >> > Piotr
>> > >> >
>> > >> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
>> > >> > napisał(a):
>> > >> >
>> > >> > > Hi,
>> > >> > >
>> > >> > > Thanks Piotr, for the link :)
>> > >> > >
>> > >> > > I just updated website on pre site please take a quick look and
>> I'll
>> > >> > > publish it:
>> > >> > >
>> > >> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>> > >> > > https://royale.codeoscopic.com/download/
>> > >> > > https://royale.codeoscopic.com/source-code/
>> > >> > >
>> > >> > > thanks
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
>> > >> > carlosrov...@apache.org
>> > >> > > >)
>> > >> > > escribió:
>> > >> > >
>> > >> > > > Hi,
>> > >> > > >
>> > >> > > > I'm updating all website in pre. I changed download and source
>> > code
>> > >> > > pages.
>> > >> > > > I'm going to do the blog post, for this I need the Annoucment,
>> > but I
>> > >> > > can't
>> > >> > > > see it in my mail client.
>> > >> > > > @Piotr Zarzycki  can you send me
>> that
>> > >> email
>> > >> > > > off list? I'm going to start from the 0.9.4 one in the
>> meanwhile
>> > >> > > >
>> > >> > > > thanks
>> > >> > > >
>> > >> > > > Carlos
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
>> > >> > > > piotrzarzyck...@gmail.com>) escribió:
>> >

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki

This is the goal of syncing everything tomorrow. I asked you to publish
first link and source code on website, cause my announce probably go first
one and I didn't want to mislead with what will be on website. However if
you wanted to do that differently I'm fine - Couple of hours of misleading
doesn't hurts anyone maybe. - We will see tomorrow.

wt., 8 paź 2019 o 11:05 Carlos Rovira  napisał(a):

> Hi,
> ok, is normal,
> as people following our dev, are as well using links to 0.9.6 releases.
> The update of links in website is more about to announce to the rest of the
> world that is not as close to us as the rest of community.
> So it's important to communicate in the most organized way we can.
>
> thanks!
>
> El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Just FYI: npm stuff and Maven artifacts are being published for couple of
> > days already, so people are using released 0.9.6 trough npm. - It's
> happen
> > automatically in case of npm.
> >
> > wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
> > napisał(a):
> >
> > > Fine with me. I make announce tomorrow morning and review what was your
> > > change and update Draft.
> > >
> > > wt., 8 paź 2019 o 10:46 Carlos Rovira 
> > > napisał(a):
> > >
> > >> Hi, Piotr,
> > >>
> > >> I think we should update all at the same time, since we want to post
> in
> > >> twitter, Facebook and linkedin.
> > >> Doesn't have sense to me upload just a few links since almost nobody
> > will
> > >> notice it (and are already in GitHub releases). If we need to wait a
> day
> > >> to
> > >> send the official announcement it's ok for me. We can finish to
> improve
> > >> the
> > >> blog post in the meanwhile to do it better.
> > >>
> > >> For example, I changed a bit the wording, since we are not as "early"
> or
> > >> "alpha" and I mention as well that we have Apps in production, what is
> > now
> > >> important.
> > >> And finally talk about the improved Royale Docs that will be of help
> for
> > >> newcomers.
> > >>
> > >> I think Andrew can review the blog post and improve it and then be
> ready
> > >> to
> > >> publish all tomorrow.
> > >>
> > >> As well if someone notice something that needs to be updated can
> notify
> > >> us.
> > >>
> > >> Thanks
> > >>
> > >>
> > >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> > >> piotrzarzyck...@gmail.com>)
> > >> escribió:
> > >>
> > >> > Download and source code websites looks good to me. In blog post you
> > >> have
> > >> > broken github links - review them and fix.
> > >> >
> > >> > Apart of that publish only Download and Source code. Blog post
> should
> > be
> > >> > publish after I think official announce on dev, users and announce
> > >> mailing
> > >> > list. I'm going to do that tomorrow, cause there is still time for
> > >> review
> > >> > Draft of announcement.
> > >> >
> > >> > Thanks,
> > >> > Piotr
> > >> >
> > >> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
> > >> > napisał(a):
> > >> >
> > >> > > Hi,
> > >> > >
> > >> > > Thanks Piotr, for the link :)
> > >> > >
> > >> > > I just updated website on pre site please take a quick look and
> I'll
> > >> > > publish it:
> > >> > >
> > >> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> > >> > > https://royale.codeoscopic.com/download/
> > >> > > https://royale.codeoscopic.com/source-code/
> > >> > >
> > >> > > thanks
> > >> > >
> > >> > >
> > >> > >
> > >> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
> > >> > carlosrov...@apache.org
> > >> > > >)
> > >> > > escribió:
> > >> > >
> > >> > > > Hi,
> > >> > > >
> > >> > > > I'm updating all website in pre. I changed download and source
> > code
> > >> > > pages.
> > >> > > > I'm going to do the blog post, for this I need the Annoucment,
> > but I
> > >> > > can't
> > >> > > > see it in my mail client.
> > >> > > > @Piotr Zarzycki  can you send me
> that
> > >> email
> > >> > > > off list? I'm going to start from the 0.9.4 one in the meanwhile
> > >> > > >
> > >> > > > thanks
> > >> > > >
> > >> > > > Carlos
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> > >> > > > piotrzarzyck...@gmail.com>) escribió:
> > >> > > >
> > >> > > >> Carlos,
> > >> > > >>
> > >> > > >> Let me know if you have problems with updating links on
> website.
> > If
> > >> > yes
> > >> > > I
> > >> > > >> will try to figure out how to do that.
> > >> > > >>
> > >> > > >> Thanks,
> > >> > > >> Piotr
> > >> > > >>
> > >> > > >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > >> > > >> napisał(a):
> > >> > > >>
> > >> > > >> > Hey Andrew,
> > >> > > >> >
> > >> > > >> > Thank you!
> > >> > > >> >
> > >> > > >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore <
> > >> cottag...@gmail.com>
> > >> > > >> wrote:
> > >> > > >> >
> > >> > > >> >> I looked over the draft announcement, Piotr, and it seems
> fine
> > >> as
> > >> > to
> > >> > > >> the
> > >> > > >> >> English. I cannot

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Carlos Rovira

Hi,
ok, is normal,
as people following our dev, are as well using links to 0.9.6 releases.
The update of links in website is more about to announce to the rest of the
world that is not as close to us as the rest of community.
So it's important to communicate in the most organized way we can.

thanks!

El mar., 8 oct. 2019 a las 10:51, Piotr Zarzycki ()
escribió:

> Just FYI: npm stuff and Maven artifacts are being published for couple of
> days already, so people are using released 0.9.6 trough npm. - It's happen
> automatically in case of npm.
>
> wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
> napisał(a):
>
> > Fine with me. I make announce tomorrow morning and review what was your
> > change and update Draft.
> >
> > wt., 8 paź 2019 o 10:46 Carlos Rovira 
> > napisał(a):
> >
> >> Hi, Piotr,
> >>
> >> I think we should update all at the same time, since we want to post in
> >> twitter, Facebook and linkedin.
> >> Doesn't have sense to me upload just a few links since almost nobody
> will
> >> notice it (and are already in GitHub releases). If we need to wait a day
> >> to
> >> send the official announcement it's ok for me. We can finish to improve
> >> the
> >> blog post in the meanwhile to do it better.
> >>
> >> For example, I changed a bit the wording, since we are not as "early" or
> >> "alpha" and I mention as well that we have Apps in production, what is
> now
> >> important.
> >> And finally talk about the improved Royale Docs that will be of help for
> >> newcomers.
> >>
> >> I think Andrew can review the blog post and improve it and then be ready
> >> to
> >> publish all tomorrow.
> >>
> >> As well if someone notice something that needs to be updated can notify
> >> us.
> >>
> >> Thanks
> >>
> >>
> >> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> >> piotrzarzyck...@gmail.com>)
> >> escribió:
> >>
> >> > Download and source code websites looks good to me. In blog post you
> >> have
> >> > broken github links - review them and fix.
> >> >
> >> > Apart of that publish only Download and Source code. Blog post should
> be
> >> > publish after I think official announce on dev, users and announce
> >> mailing
> >> > list. I'm going to do that tomorrow, cause there is still time for
> >> review
> >> > Draft of announcement.
> >> >
> >> > Thanks,
> >> > Piotr
> >> >
> >> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
> >> > napisał(a):
> >> >
> >> > > Hi,
> >> > >
> >> > > Thanks Piotr, for the link :)
> >> > >
> >> > > I just updated website on pre site please take a quick look and I'll
> >> > > publish it:
> >> > >
> >> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> >> > > https://royale.codeoscopic.com/download/
> >> > > https://royale.codeoscopic.com/source-code/
> >> > >
> >> > > thanks
> >> > >
> >> > >
> >> > >
> >> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
> >> > carlosrov...@apache.org
> >> > > >)
> >> > > escribió:
> >> > >
> >> > > > Hi,
> >> > > >
> >> > > > I'm updating all website in pre. I changed download and source
> code
> >> > > pages.
> >> > > > I'm going to do the blog post, for this I need the Annoucment,
> but I
> >> > > can't
> >> > > > see it in my mail client.
> >> > > > @Piotr Zarzycki  can you send me that
> >> email
> >> > > > off list? I'm going to start from the 0.9.4 one in the meanwhile
> >> > > >
> >> > > > thanks
> >> > > >
> >> > > > Carlos
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> >> > > > piotrzarzyck...@gmail.com>) escribió:
> >> > > >
> >> > > >> Carlos,
> >> > > >>
> >> > > >> Let me know if you have problems with updating links on website.
> If
> >> > yes
> >> > > I
> >> > > >> will try to figure out how to do that.
> >> > > >>
> >> > > >> Thanks,
> >> > > >> Piotr
> >> > > >>
> >> > > >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> > > >> napisał(a):
> >> > > >>
> >> > > >> > Hey Andrew,
> >> > > >> >
> >> > > >> > Thank you!
> >> > > >> >
> >> > > >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore <
> >> cottag...@gmail.com>
> >> > > >> wrote:
> >> > > >> >
> >> > > >> >> I looked over the draft announcement, Piotr, and it seems fine
> >> as
> >> > to
> >> > > >> the
> >> > > >> >> English. I cannot speak to the technical details as well as
> >> other
> >> > > >> >> committers can.
> >> > > >> >>
> >> > > >> >> Andrew
> >> > > >> >>
> >> > > >> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
> >> > > >> piotrzarzyck...@gmail.com>
> >> > > >> >> wrote:
> >> > > >> >>
> >> > > >> >> > Currently I'm waiting for review of Draft of announcement.
> >> Till
> >> > > >> maximum
> >> > > >> >> > Wednesday. Than I will send announce to dev, users and
> >> announce
> >> > > >> mailing
> >> > > >> >> > list.
> >> > > >> >> >
> >> > > >> >> > I think you should create draft and post it once announce
> >> will be
> >> > > >> sent.
> >> > > >> >> >
> >> > > >> >> > Apart of that I should add our release somewhere in the
> whimsy
> >> > but
> >> > >

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki

Just FYI: npm stuff and Maven artifacts are being published for couple of
days already, so people are using released 0.9.6 trough npm. - It's happen
automatically in case of npm.

wt., 8 paź 2019 o 10:48 Piotr Zarzycki 
napisał(a):

> Fine with me. I make announce tomorrow morning and review what was your
> change and update Draft.
>
> wt., 8 paź 2019 o 10:46 Carlos Rovira 
> napisał(a):
>
>> Hi, Piotr,
>>
>> I think we should update all at the same time, since we want to post in
>> twitter, Facebook and linkedin.
>> Doesn't have sense to me upload just a few links since almost nobody will
>> notice it (and are already in GitHub releases). If we need to wait a day
>> to
>> send the official announcement it's ok for me. We can finish to improve
>> the
>> blog post in the meanwhile to do it better.
>>
>> For example, I changed a bit the wording, since we are not as "early" or
>> "alpha" and I mention as well that we have Apps in production, what is now
>> important.
>> And finally talk about the improved Royale Docs that will be of help for
>> newcomers.
>>
>> I think Andrew can review the blog post and improve it and then be ready
>> to
>> publish all tomorrow.
>>
>> As well if someone notice something that needs to be updated can notify
>> us.
>>
>> Thanks
>>
>>
>> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>)
>> escribió:
>>
>> > Download and source code websites looks good to me. In blog post you
>> have
>> > broken github links - review them and fix.
>> >
>> > Apart of that publish only Download and Source code. Blog post should be
>> > publish after I think official announce on dev, users and announce
>> mailing
>> > list. I'm going to do that tomorrow, cause there is still time for
>> review
>> > Draft of announcement.
>> >
>> > Thanks,
>> > Piotr
>> >
>> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
>> > napisał(a):
>> >
>> > > Hi,
>> > >
>> > > Thanks Piotr, for the link :)
>> > >
>> > > I just updated website on pre site please take a quick look and I'll
>> > > publish it:
>> > >
>> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
>> > > https://royale.codeoscopic.com/download/
>> > > https://royale.codeoscopic.com/source-code/
>> > >
>> > > thanks
>> > >
>> > >
>> > >
>> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
>> > carlosrov...@apache.org
>> > > >)
>> > > escribió:
>> > >
>> > > > Hi,
>> > > >
>> > > > I'm updating all website in pre. I changed download and source code
>> > > pages.
>> > > > I'm going to do the blog post, for this I need the Annoucment, but I
>> > > can't
>> > > > see it in my mail client.
>> > > > @Piotr Zarzycki  can you send me that
>> email
>> > > > off list? I'm going to start from the 0.9.4 one in the meanwhile
>> > > >
>> > > > thanks
>> > > >
>> > > > Carlos
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
>> > > > piotrzarzyck...@gmail.com>) escribió:
>> > > >
>> > > >> Carlos,
>> > > >>
>> > > >> Let me know if you have problems with updating links on website. If
>> > yes
>> > > I
>> > > >> will try to figure out how to do that.
>> > > >>
>> > > >> Thanks,
>> > > >> Piotr
>> > > >>
>> > > >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
>> > > >> napisał(a):
>> > > >>
>> > > >> > Hey Andrew,
>> > > >> >
>> > > >> > Thank you!
>> > > >> >
>> > > >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore <
>> cottag...@gmail.com>
>> > > >> wrote:
>> > > >> >
>> > > >> >> I looked over the draft announcement, Piotr, and it seems fine
>> as
>> > to
>> > > >> the
>> > > >> >> English. I cannot speak to the technical details as well as
>> other
>> > > >> >> committers can.
>> > > >> >>
>> > > >> >> Andrew
>> > > >> >>
>> > > >> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
>> > > >> piotrzarzyck...@gmail.com>
>> > > >> >> wrote:
>> > > >> >>
>> > > >> >> > Currently I'm waiting for review of Draft of announcement.
>> Till
>> > > >> maximum
>> > > >> >> > Wednesday. Than I will send announce to dev, users and
>> announce
>> > > >> mailing
>> > > >> >> > list.
>> > > >> >> >
>> > > >> >> > I think you should create draft and post it once announce
>> will be
>> > > >> sent.
>> > > >> >> >
>> > > >> >> > Apart of that I should add our release somewhere in the whimsy
>> > but
>> > > I
>> > > >> >> don't
>> > > >> >> > remember where - I need to find that.
>> > > >> >> >
>> > > >> >> > Piotr
>> > > >> >> >
>> > > >> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore <
>> cottag...@gmail.com
>> > >
>> > > >> >> wrote:
>> > > >> >> >
>> > > >> >> > > That would be good
>> > > >> >> > >
>> > > >> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
>> > > >> carlosrov...@apache.org>
>> > > >> >> > > wrote:
>> > > >> >> > >
>> > > >> >> > > > Hi,
>> > > >> >> > > > I'll be updating website in next few hours, but I was
>> > thinking
>> > > we
>> > > >> >> don't
>> > > >> >> > > > have the habitual blog post for 0.9.6 release.
>> > > >> >> > > > Should I create one from scratch based on

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki

Fine with me. I make announce tomorrow morning and review what was your
change and update Draft.

wt., 8 paź 2019 o 10:46 Carlos Rovira  napisał(a):

> Hi, Piotr,
>
> I think we should update all at the same time, since we want to post in
> twitter, Facebook and linkedin.
> Doesn't have sense to me upload just a few links since almost nobody will
> notice it (and are already in GitHub releases). If we need to wait a day to
> send the official announcement it's ok for me. We can finish to improve the
> blog post in the meanwhile to do it better.
>
> For example, I changed a bit the wording, since we are not as "early" or
> "alpha" and I mention as well that we have Apps in production, what is now
> important.
> And finally talk about the improved Royale Docs that will be of help for
> newcomers.
>
> I think Andrew can review the blog post and improve it and then be ready to
> publish all tomorrow.
>
> As well if someone notice something that needs to be updated can notify us.
>
> Thanks
>
>
> El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>)
> escribió:
>
> > Download and source code websites looks good to me. In blog post you have
> > broken github links - review them and fix.
> >
> > Apart of that publish only Download and Source code. Blog post should be
> > publish after I think official announce on dev, users and announce
> mailing
> > list. I'm going to do that tomorrow, cause there is still time for review
> > Draft of announcement.
> >
> > Thanks,
> > Piotr
> >
> > wt., 8 paź 2019 o 10:32 Carlos Rovira 
> > napisał(a):
> >
> > > Hi,
> > >
> > > Thanks Piotr, for the link :)
> > >
> > > I just updated website on pre site please take a quick look and I'll
> > > publish it:
> > >
> > > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> > > https://royale.codeoscopic.com/download/
> > > https://royale.codeoscopic.com/source-code/
> > >
> > > thanks
> > >
> > >
> > >
> > > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
> > carlosrov...@apache.org
> > > >)
> > > escribió:
> > >
> > > > Hi,
> > > >
> > > > I'm updating all website in pre. I changed download and source code
> > > pages.
> > > > I'm going to do the blog post, for this I need the Annoucment, but I
> > > can't
> > > > see it in my mail client.
> > > > @Piotr Zarzycki  can you send me that
> email
> > > > off list? I'm going to start from the 0.9.4 one in the meanwhile
> > > >
> > > > thanks
> > > >
> > > > Carlos
> > > >
> > > >
> > > >
> > > >
> > > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > >> Carlos,
> > > >>
> > > >> Let me know if you have problems with updating links on website. If
> > yes
> > > I
> > > >> will try to figure out how to do that.
> > > >>
> > > >> Thanks,
> > > >> Piotr
> > > >>
> > > >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
> > > >> napisał(a):
> > > >>
> > > >> > Hey Andrew,
> > > >> >
> > > >> > Thank you!
> > > >> >
> > > >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore  >
> > > >> wrote:
> > > >> >
> > > >> >> I looked over the draft announcement, Piotr, and it seems fine as
> > to
> > > >> the
> > > >> >> English. I cannot speak to the technical details as well as other
> > > >> >> committers can.
> > > >> >>
> > > >> >> Andrew
> > > >> >>
> > > >> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
> > > >> piotrzarzyck...@gmail.com>
> > > >> >> wrote:
> > > >> >>
> > > >> >> > Currently I'm waiting for review of Draft of announcement. Till
> > > >> maximum
> > > >> >> > Wednesday. Than I will send announce to dev, users and announce
> > > >> mailing
> > > >> >> > list.
> > > >> >> >
> > > >> >> > I think you should create draft and post it once announce will
> be
> > > >> sent.
> > > >> >> >
> > > >> >> > Apart of that I should add our release somewhere in the whimsy
> > but
> > > I
> > > >> >> don't
> > > >> >> > remember where - I need to find that.
> > > >> >> >
> > > >> >> > Piotr
> > > >> >> >
> > > >> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore <
> cottag...@gmail.com
> > >
> > > >> >> wrote:
> > > >> >> >
> > > >> >> > > That would be good
> > > >> >> > >
> > > >> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
> > > >> carlosrov...@apache.org>
> > > >> >> > > wrote:
> > > >> >> > >
> > > >> >> > > > Hi,
> > > >> >> > > > I'll be updating website in next few hours, but I was
> > thinking
> > > we
> > > >> >> don't
> > > >> >> > > > have the habitual blog post for 0.9.6 release.
> > > >> >> > > > Should I create one from scratch based on 0.9.4?
> > > >> >> > > >
> > > >> >> > > > thanks
> > > >> >> > > >
> > > >> >> > > > --
> > > >> >> > > > Carlos Rovira
> > > >> >> > > > http://about.me/carlosrovira
> > > >> >> > > >
> > > >> >> > >
> > > >> >> >
> > > >> >>
> > > >> >>
> > > >> >> --
> > > >> >> Andrew Wetmore
> > > >> >>
> > > >> >> http://cottage14.blogspot.com/
> > > >> >>
> > > >> >
> > > >>
> > > >> --
> > > >>
> > > >> Piotr Zarzycki
> > > >>
> > > >> Patreon:

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Carlos Rovira

Hi, Piotr,

I think we should update all at the same time, since we want to post in
twitter, Facebook and linkedin.
Doesn't have sense to me upload just a few links since almost nobody will
notice it (and are already in GitHub releases). If we need to wait a day to
send the official announcement it's ok for me. We can finish to improve the
blog post in the meanwhile to do it better.

For example, I changed a bit the wording, since we are not as "early" or
"alpha" and I mention as well that we have Apps in production, what is now
important.
And finally talk about the improved Royale Docs that will be of help for
newcomers.

I think Andrew can review the blog post and improve it and then be ready to
publish all tomorrow.

As well if someone notice something that needs to be updated can notify us.

Thanks


El mar., 8 oct. 2019 a las 10:37, Piotr Zarzycki ()
escribió:

> Download and source code websites looks good to me. In blog post you have
> broken github links - review them and fix.
>
> Apart of that publish only Download and Source code. Blog post should be
> publish after I think official announce on dev, users and announce mailing
> list. I'm going to do that tomorrow, cause there is still time for review
> Draft of announcement.
>
> Thanks,
> Piotr
>
> wt., 8 paź 2019 o 10:32 Carlos Rovira 
> napisał(a):
>
> > Hi,
> >
> > Thanks Piotr, for the link :)
> >
> > I just updated website on pre site please take a quick look and I'll
> > publish it:
> >
> > https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> > https://royale.codeoscopic.com/download/
> > https://royale.codeoscopic.com/source-code/
> >
> > thanks
> >
> >
> >
> > El mar., 8 oct. 2019 a las 10:06, Carlos Rovira (<
> carlosrov...@apache.org
> > >)
> > escribió:
> >
> > > Hi,
> > >
> > > I'm updating all website in pre. I changed download and source code
> > pages.
> > > I'm going to do the blog post, for this I need the Annoucment, but I
> > can't
> > > see it in my mail client.
> > > @Piotr Zarzycki  can you send me that email
> > > off list? I'm going to start from the 0.9.4 one in the meanwhile
> > >
> > > thanks
> > >
> > > Carlos
> > >
> > >
> > >
> > >
> > > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > >> Carlos,
> > >>
> > >> Let me know if you have problems with updating links on website. If
> yes
> > I
> > >> will try to figure out how to do that.
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
> > >> napisał(a):
> > >>
> > >> > Hey Andrew,
> > >> >
> > >> > Thank you!
> > >> >
> > >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore 
> > >> wrote:
> > >> >
> > >> >> I looked over the draft announcement, Piotr, and it seems fine as
> to
> > >> the
> > >> >> English. I cannot speak to the technical details as well as other
> > >> >> committers can.
> > >> >>
> > >> >> Andrew
> > >> >>
> > >> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
> > >> piotrzarzyck...@gmail.com>
> > >> >> wrote:
> > >> >>
> > >> >> > Currently I'm waiting for review of Draft of announcement. Till
> > >> maximum
> > >> >> > Wednesday. Than I will send announce to dev, users and announce
> > >> mailing
> > >> >> > list.
> > >> >> >
> > >> >> > I think you should create draft and post it once announce will be
> > >> sent.
> > >> >> >
> > >> >> > Apart of that I should add our release somewhere in the whimsy
> but
> > I
> > >> >> don't
> > >> >> > remember where - I need to find that.
> > >> >> >
> > >> >> > Piotr
> > >> >> >
> > >> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore  >
> > >> >> wrote:
> > >> >> >
> > >> >> > > That would be good
> > >> >> > >
> > >> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
> > >> carlosrov...@apache.org>
> > >> >> > > wrote:
> > >> >> > >
> > >> >> > > > Hi,
> > >> >> > > > I'll be updating website in next few hours, but I was
> thinking
> > we
> > >> >> don't
> > >> >> > > > have the habitual blog post for 0.9.6 release.
> > >> >> > > > Should I create one from scratch based on 0.9.4?
> > >> >> > > >
> > >> >> > > > thanks
> > >> >> > > >
> > >> >> > > > --
> > >> >> > > > Carlos Rovira
> > >> >> > > > http://about.me/carlosrovira
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >> >>
> > >> >>
> > >> >> --
> > >> >> Andrew Wetmore
> > >> >>
> > >> >> http://cottage14.blogspot.com/
> > >> >>
> > >> >
> > >>
> > >> --
> > >>
> > >> Piotr Zarzycki
> > >>
> > >> Patreon: *https://www.patreon.com/piotrzarzycki
> > >> *
> > >>
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki

Download and source code websites looks good to me. In blog post you have
broken github links - review them and fix.

Apart of that publish only Download and Source code. Blog post should be
publish after I think official announce on dev, users and announce mailing
list. I'm going to do that tomorrow, cause there is still time for review
Draft of announcement.

Thanks,
Piotr

wt., 8 paź 2019 o 10:32 Carlos Rovira  napisał(a):

> Hi,
>
> Thanks Piotr, for the link :)
>
> I just updated website on pre site please take a quick look and I'll
> publish it:
>
> https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
> https://royale.codeoscopic.com/download/
> https://royale.codeoscopic.com/source-code/
>
> thanks
>
>
>
> El mar., 8 oct. 2019 a las 10:06, Carlos Rovira ( >)
> escribió:
>
> > Hi,
> >
> > I'm updating all website in pre. I changed download and source code
> pages.
> > I'm going to do the blog post, for this I need the Annoucment, but I
> can't
> > see it in my mail client.
> > @Piotr Zarzycki  can you send me that email
> > off list? I'm going to start from the 0.9.4 one in the meanwhile
> >
> > thanks
> >
> > Carlos
> >
> >
> >
> >
> > El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> >> Carlos,
> >>
> >> Let me know if you have problems with updating links on website. If yes
> I
> >> will try to figure out how to do that.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
> >> napisał(a):
> >>
> >> > Hey Andrew,
> >> >
> >> > Thank you!
> >> >
> >> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore 
> >> wrote:
> >> >
> >> >> I looked over the draft announcement, Piotr, and it seems fine as to
> >> the
> >> >> English. I cannot speak to the technical details as well as other
> >> >> committers can.
> >> >>
> >> >> Andrew
> >> >>
> >> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com>
> >> >> wrote:
> >> >>
> >> >> > Currently I'm waiting for review of Draft of announcement. Till
> >> maximum
> >> >> > Wednesday. Than I will send announce to dev, users and announce
> >> mailing
> >> >> > list.
> >> >> >
> >> >> > I think you should create draft and post it once announce will be
> >> sent.
> >> >> >
> >> >> > Apart of that I should add our release somewhere in the whimsy but
> I
> >> >> don't
> >> >> > remember where - I need to find that.
> >> >> >
> >> >> > Piotr
> >> >> >
> >> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore 
> >> >> wrote:
> >> >> >
> >> >> > > That would be good
> >> >> > >
> >> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
> >> carlosrov...@apache.org>
> >> >> > > wrote:
> >> >> > >
> >> >> > > > Hi,
> >> >> > > > I'll be updating website in next few hours, but I was thinking
> we
> >> >> don't
> >> >> > > > have the habitual blog post for 0.9.6 release.
> >> >> > > > Should I create one from scratch based on 0.9.4?
> >> >> > > >
> >> >> > > > thanks
> >> >> > > >
> >> >> > > > --
> >> >> > > > Carlos Rovira
> >> >> > > > http://about.me/carlosrovira
> >> >> > > >
> >> >> > >
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >> Andrew Wetmore
> >> >>
> >> >> http://cottage14.blogspot.com/
> >> >>
> >> >
> >>
> >> --
> >>
> >> Piotr Zarzycki
> >>
> >> Patreon: *https://www.patreon.com/piotrzarzycki
> >> *
> >>
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>


-- 

Piotr Zarzycki

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

Re: Component Sets

2019-10-08 Thread Andrew Wetmore

There is not such a document yet, no. Help creating one would be welcome.

On Tue, Oct 8, 2019 at 4:22 AM Chris Velevitch 
wrote:

> There doesn't seem to be an all-encompassing document describing, MX,
> Spark and Jewel components and as well as the pros and cons of each
> nor is there a discussion on using third party web components,
> creating custom web components and how to the material design
> components.
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Carlos Rovira

Hi,

Thanks Piotr, for the link :)

I just updated website on pre site please take a quick look and I'll
publish it:

https://royale.codeoscopic.com/apache-royale-v0-9-6-released/
https://royale.codeoscopic.com/download/
https://royale.codeoscopic.com/source-code/

thanks



El mar., 8 oct. 2019 a las 10:06, Carlos Rovira ()
escribió:

> Hi,
>
> I'm updating all website in pre. I changed download and source code pages.
> I'm going to do the blog post, for this I need the Annoucment, but I can't
> see it in my mail client.
> @Piotr Zarzycki  can you send me that email
> off list? I'm going to start from the 0.9.4 one in the meanwhile
>
> thanks
>
> Carlos
>
>
>
>
> El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
>> Carlos,
>>
>> Let me know if you have problems with updating links on website. If yes I
>> will try to figure out how to do that.
>>
>> Thanks,
>> Piotr
>>
>> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
>> napisał(a):
>>
>> > Hey Andrew,
>> >
>> > Thank you!
>> >
>> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore 
>> wrote:
>> >
>> >> I looked over the draft announcement, Piotr, and it seems fine as to
>> the
>> >> English. I cannot speak to the technical details as well as other
>> >> committers can.
>> >>
>> >> Andrew
>> >>
>> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> >> wrote:
>> >>
>> >> > Currently I'm waiting for review of Draft of announcement. Till
>> maximum
>> >> > Wednesday. Than I will send announce to dev, users and announce
>> mailing
>> >> > list.
>> >> >
>> >> > I think you should create draft and post it once announce will be
>> sent.
>> >> >
>> >> > Apart of that I should add our release somewhere in the whimsy but I
>> >> don't
>> >> > remember where - I need to find that.
>> >> >
>> >> > Piotr
>> >> >
>> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore 
>> >> wrote:
>> >> >
>> >> > > That would be good
>> >> > >
>> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
>> carlosrov...@apache.org>
>> >> > > wrote:
>> >> > >
>> >> > > > Hi,
>> >> > > > I'll be updating website in next few hours, but I was thinking we
>> >> don't
>> >> > > > have the habitual blog post for 0.9.6 release.
>> >> > > > Should I create one from scratch based on 0.9.4?
>> >> > > >
>> >> > > > thanks
>> >> > > >
>> >> > > > --
>> >> > > > Carlos Rovira
>> >> > > > http://about.me/carlosrovira
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >>
>> >> --
>> >> Andrew Wetmore
>> >>
>> >> http://cottage14.blogspot.com/
>> >>
>> >
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> *
>>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

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

Component Sets

2019-10-08 Thread Chris Velevitch

There doesn't seem to be an all-encompassing document describing, MX,
Spark and Jewel components and as well as the pros and cons of each
nor is there a discussion on using third party web components,
creating custom web components and how to the material design
components.

Re: Acceptance of Royale by Flex Developers

2019-10-08 Thread Chris Velevitch

So you are suggesting a RemoteObject is a headless component who's
base class only supports the model and controller plugins and that UI
classes extend the headless component to add in the view?

On Tue, 8 Oct 2019 at 15:52, Carlos Rovira  wrote:
>
> Hi Chris,
>
> thanks for sharing your thoughts.
>
> IMHO, not always a "strand" is a "visual component". This relation is not
> always true. a strand could be a non visual component (for example the
> implementation of RemoteObject in the Network library). And a bead could be
> a strand itself.
>
> I think the term component is right in most cases and accomplish a meaning
> purpose, but strand/beads concept comes to give another subset of meaning
>
> just my opinion about this.
>
> Carlos
>
>
>
> El mar., 8 oct. 2019 a las 9:23, Chris Velevitch ()
> escribió:
>
> > The use of the terms "strands" and "beads" still doesn't make sense to
> > me because they are concepts I have never heard before and it is
> > creating a barrier to acceptance and deepens the learning curve. As
> > far as I can tell, it's something to do with visual/UI components.
> >
> > The section "Strands and Beads" should ideally be titled "Visual
> > Components" because that section is about visual components and is
> > alluding to the fact visual components are standalone microcosms of
> > the MVC pattern and the ability to treat the model, view and
> > controller as plugins to the component. The statement that components
> > are "strands" is, in my mind, misleading because it doesn't make sense
> > to interchange terms components and strands if a strand is a
> > component. In fact, diving into the code, the "addBead" function gives
> > the "bead" a reference to the component the "bead" is being added to.
> >
> > It is clear from the documentation that "beads" are "plugins" and the
> > documentation should be talking about extending components with
> > plugins. All references to "bead" should be replaced with "plugin" and
> > all references to "strand" be replaced with either "hostComponent", or
> > "parent" or appropriately something else.
> >
> > We seem to be neglecting the rich heritage that we have gotten from
> > Adobe Flex and I don't see the point giving existing concepts new
> > names.
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira



-- 


Chris
--
Chris Velevitch
m: 0415 469 095

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki

Sorry it meant to be on dev.

wt., 8 paź 2019 o 10:11 Piotr Zarzycki 
napisał(a):

> Carlos,
>
> Here you have link to pony archive [1] and if you prefer nabble [2]
>
> [1]
> https://lists.apache.org/thread.html/3eb43d9ad3796179965ce7e91bee1e6cf864bf17044db3c6201adcbd@%3Cdev.royale.apache.org%3E
> [2]
> http://apache-royale-development.20373.n8.nabble.com/DRAFT-ANNOUNCE-Apache-Royale-0-9-6-released-td12408.html
>
> Thanks,
> Piotr
>
> wt., 8 paź 2019 o 10:06 Carlos Rovira 
> napisał(a):
>
>> Hi,
>>
>> I'm updating all website in pre. I changed download and source code pages.
>> I'm going to do the blog post, for this I need the Annoucment, but I
>> can't see it in my mail client.
>> @Piotr Zarzycki  can you send me that email
>> off list? I'm going to start from the 0.9.4 one in the meanwhile
>>
>> thanks
>>
>> Carlos
>>
>>
>>
>>
>> El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki (<
>> piotrzarzyck...@gmail.com>) escribió:
>>
>>> Carlos,
>>>
>>> Let me know if you have problems with updating links on website. If yes I
>>> will try to figure out how to do that.
>>>
>>> Thanks,
>>> Piotr
>>>
>>> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
>>> napisał(a):
>>>
>>> > Hey Andrew,
>>> >
>>> > Thank you!
>>> >
>>> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore 
>>> wrote:
>>> >
>>> >> I looked over the draft announcement, Piotr, and it seems fine as to
>>> the
>>> >> English. I cannot speak to the technical details as well as other
>>> >> committers can.
>>> >>
>>> >> Andrew
>>> >>
>>> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
>>> >> wrote:
>>> >>
>>> >> > Currently I'm waiting for review of Draft of announcement. Till
>>> maximum
>>> >> > Wednesday. Than I will send announce to dev, users and announce
>>> mailing
>>> >> > list.
>>> >> >
>>> >> > I think you should create draft and post it once announce will be
>>> sent.
>>> >> >
>>> >> > Apart of that I should add our release somewhere in the whimsy but I
>>> >> don't
>>> >> > remember where - I need to find that.
>>> >> >
>>> >> > Piotr
>>> >> >
>>> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore 
>>> >> wrote:
>>> >> >
>>> >> > > That would be good
>>> >> > >
>>> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
>>> carlosrov...@apache.org>
>>> >> > > wrote:
>>> >> > >
>>> >> > > > Hi,
>>> >> > > > I'll be updating website in next few hours, but I was thinking
>>> we
>>> >> don't
>>> >> > > > have the habitual blog post for 0.9.6 release.
>>> >> > > > Should I create one from scratch based on 0.9.4?
>>> >> > > >
>>> >> > > > thanks
>>> >> > > >
>>> >> > > > --
>>> >> > > > Carlos Rovira
>>> >> > > > http://about.me/carlosrovira
>>> >> > > >
>>> >> > >
>>> >> >
>>> >>
>>> >>
>>> >> --
>>> >> Andrew Wetmore
>>> >>
>>> >> http://cottage14.blogspot.com/
>>> >>
>>> >
>>>
>>> --
>>>
>>> Piotr Zarzycki
>>>
>>> Patreon: *https://www.patreon.com/piotrzarzycki
>>> *
>>>
>>
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


-- 

Piotr Zarzycki

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

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Carlos Rovira

Hi,

I'm updating all website in pre. I changed download and source code pages.
I'm going to do the blog post, for this I need the Annoucment, but I can't
see it in my mail client.
@Piotr Zarzycki  can you send me that email off
list? I'm going to start from the 0.9.4 one in the meanwhile

thanks

Carlos




El mar., 8 oct. 2019 a las 9:54, Piotr Zarzycki ()
escribió:

> Carlos,
>
> Let me know if you have problems with updating links on website. If yes I
> will try to figure out how to do that.
>
> Thanks,
> Piotr
>
> wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
> napisał(a):
>
> > Hey Andrew,
> >
> > Thank you!
> >
> > On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore 
> wrote:
> >
> >> I looked over the draft announcement, Piotr, and it seems fine as to the
> >> English. I cannot speak to the technical details as well as other
> >> committers can.
> >>
> >> Andrew
> >>
> >> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>
> >> > Currently I'm waiting for review of Draft of announcement. Till
> maximum
> >> > Wednesday. Than I will send announce to dev, users and announce
> mailing
> >> > list.
> >> >
> >> > I think you should create draft and post it once announce will be
> sent.
> >> >
> >> > Apart of that I should add our release somewhere in the whimsy but I
> >> don't
> >> > remember where - I need to find that.
> >> >
> >> > Piotr
> >> >
> >> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore 
> >> wrote:
> >> >
> >> > > That would be good
> >> > >
> >> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, <
> carlosrov...@apache.org>
> >> > > wrote:
> >> > >
> >> > > > Hi,
> >> > > > I'll be updating website in next few hours, but I was thinking we
> >> don't
> >> > > > have the habitual blog post for 0.9.6 release.
> >> > > > Should I create one from scratch based on 0.9.4?
> >> > > >
> >> > > > thanks
> >> > > >
> >> > > > --
> >> > > > Carlos Rovira
> >> > > > http://about.me/carlosrovira
> >> > > >
> >> > >
> >> >
> >>
> >>
> >> --
> >> Andrew Wetmore
> >>
> >> http://cottage14.blogspot.com/
> >>
> >
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>


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

Pay as You Go (PAYG) Suggestion

2019-10-08 Thread Chris Velevitch

If the whole point of PAYG is to eliminate unused code from being
included in the final app distribution, then I'd like to suggest that
we take advantage of the tools the JavaScript ecosystem already has
for eliminating unused code.

I think we should take a look at Webpack [1] and create a compilation
pipeline that feeds into Webpack to create the final compacted
distributable app.



[1] https://webpack.js.org/guides/tree-shaking/

Re: Release 0.9.6 Announce for web post?

2019-10-08 Thread Piotr Zarzycki

Carlos,

Let me know if you have problems with updating links on website. If yes I
will try to figure out how to do that.

Thanks,
Piotr

wt., 8 paź 2019 o 06:54 Piotr Zarzycki 
napisał(a):

> Hey Andrew,
>
> Thank you!
>
> On Mon, Oct 7, 2019, 11:17 PM Andrew Wetmore  wrote:
>
>> I looked over the draft announcement, Piotr, and it seems fine as to the
>> English. I cannot speak to the technical details as well as other
>> committers can.
>>
>> Andrew
>>
>> On Mon, Oct 7, 2019 at 5:01 PM Piotr Zarzycki 
>> wrote:
>>
>> > Currently I'm waiting for review of Draft of announcement. Till maximum
>> > Wednesday. Than I will send announce to dev, users and announce mailing
>> > list.
>> >
>> > I think you should create draft and post it once announce will be sent.
>> >
>> > Apart of that I should add our release somewhere in the whimsy but I
>> don't
>> > remember where - I need to find that.
>> >
>> > Piotr
>> >
>> > On Mon, Oct 7, 2019, 9:33 PM Andrew Wetmore 
>> wrote:
>> >
>> > > That would be good
>> > >
>> > > On Mon, Oct 7, 2019, 4:10 PM Carlos Rovira, 
>> > > wrote:
>> > >
>> > > > Hi,
>> > > > I'll be updating website in next few hours, but I was thinking we
>> don't
>> > > > have the habitual blog post for 0.9.6 release.
>> > > > Should I create one from scratch based on 0.9.4?
>> > > >
>> > > > thanks
>> > > >
>> > > > --
>> > > > Carlos Rovira
>> > > > http://about.me/carlosrovira
>> > > >
>> > >
>> >
>>
>>
>> --
>> Andrew Wetmore
>>
>> http://cottage14.blogspot.com/
>>
>

-- 

Piotr Zarzycki

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

Re: Acceptance of Royale by Flex Developers

2019-10-08 Thread Carlos Rovira

Hi Chris,

thanks for sharing your thoughts.

IMHO, not always a "strand" is a "visual component". This relation is not
always true. a strand could be a non visual component (for example the
implementation of RemoteObject in the Network library). And a bead could be
a strand itself.

I think the term component is right in most cases and accomplish a meaning
purpose, but strand/beads concept comes to give another subset of meaning

just my opinion about this.

Carlos



El mar., 8 oct. 2019 a las 9:23, Chris Velevitch ()
escribió:

> The use of the terms "strands" and "beads" still doesn't make sense to
> me because they are concepts I have never heard before and it is
> creating a barrier to acceptance and deepens the learning curve. As
> far as I can tell, it's something to do with visual/UI components.
>
> The section "Strands and Beads" should ideally be titled "Visual
> Components" because that section is about visual components and is
> alluding to the fact visual components are standalone microcosms of
> the MVC pattern and the ability to treat the model, view and
> controller as plugins to the component. The statement that components
> are "strands" is, in my mind, misleading because it doesn't make sense
> to interchange terms components and strands if a strand is a
> component. In fact, diving into the code, the "addBead" function gives
> the "bead" a reference to the component the "bead" is being added to.
>
> It is clear from the documentation that "beads" are "plugins" and the
> documentation should be talking about extending components with
> plugins. All references to "bead" should be replaced with "plugin" and
> all references to "strand" be replaced with either "hostComponent", or
> "parent" or appropriately something else.
>
> We seem to be neglecting the rich heritage that we have gotten from
> Adobe Flex and I don't see the point giving existing concepts new
> names.
>


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

How to skin components

2019-10-08 Thread Chris Velevitch

When I was going through the documentation and code to get my head
around this silly notation of "beads" and "strands", I realised the
component plugins are very similar to the concept of skinning
components that Adobe Flex talks about. And there doesn't seem to be
any discussions on how to skin a component.

I also noticed, there's no discussion on how plugins and components
talk to each other and whether that is bidirectional or one-way.

Re: issues with Sourcetree in Mac

2019-10-08 Thread Carlos Rovira

Hi Piotr,

no, I'll do from command line now, and will check the source tree issue
later. Just asking to see if was something I was missing
thanks

Re: Heads up on XML

2019-10-08 Thread Piotr Zarzycki

Hi Greg,

Questions inline.

pon., 7 paź 2019 o 01:49 Greg Dove  napisał(a):

> Hi Piotr, just a quick follow-up to let you know that was all good, I had
> already tested the merge and conflict resolution myself and was ready to
> step in and help with that if that was necessary, but you already did it
> before I got a chance to send my email about that. :)
>
> I have to say: well done for getting through the release process. I could
> sense your frustration at times, and I know it must have seemed like it
> took far too long, but I am sure you have made a huge difference for the
> future in terms of that process.
>
>
> also fyi, I had to use -Dgenerate.swf.swcs=true in my local maven build
> today, and I was vaguely aware of discussions about this during release
> prep.
> But I wonder if this is necessary. Can't we just use the top level profiles
> at the lower levels instead of creating new profiles? There's probably a
> gap in my understanding of why this was necessary, but I would have
> expected that we could simply use something like:
>
> 
> generate-swcs-for-swf
> 
> 
> org.apache.royale.framework
> Core
> 0.9.7-SNAPSHOT
> swc
> swf
> 
> 
> 
>
>
How this activates  generate.swf.swcs ? What should I do if I wanted to
build only one module ? Doing that in above way how will change main
command which launches maven build ?


> in the framework modules, instead of:
>
>   
>   swf-dependencies
>   
>   
>   generate.swf.swcs
>   
>   
>   
>   
>   org.apache.royale.framework
>   Core
>   0.9.7-SNAPSHOT
>   swc
>   swf
>   
>   
>   
>
> (the above approach works locally for me just using the maven profile
> itself, if I make the changes to all framework modules, but as I said I
> could be missing something in relation to the issue that is being
> addressed)
>
>
> On Sun, Oct 6, 2019 at 11:20 PM Greg Dove  wrote:
>
> > Hi Piotr, I will check that in the morning local time... in about 8
> hours.
> >
> > On Sun, 6 Oct 2019, 21:54 Piotr Zarzycki, 
> > wrote:
> >
> >> Hi Greg,
> >>
> >> I run into merge conflict during merge release branch to develop into
> file
> >> which you have changed lately. Could you please verify on develop if I
> >> didn't remove anything, if I resolve conflict correctly. [1]
> >>
> >> [1]
> >>
> >>
> https://github.com/apache/royale-compiler/blob/develop/compiler-jx/src/main/java/org/apache/royale/compiler/internal/codegen/js/jx/MemberAccessEmitter.java
> >>
> >> Thanks,
> >> Piotr
> >>
> >> śr., 2 paź 2019 o 11:06 Harbs  napisał(a):
> >>
> >> > OK.
> >> >
> >> > I’ll test memory with and without your changes and let you know the
> >> > differences. :-)
> >> >
> >> > Harbs
> >> >
> >> > > On Oct 2, 2019, at 11:29 AM, Greg Dove  wrote:
> >> > >
> >> > > @harbs
> >> > >
> >> > > FYI in addition to some other stuff, I am close to pushing my
> updates
> >> to
> >> > > XML. This should be in the next hour or so.
> >> > >
> >> > > I kept the QName caching pretty close to how you had it, with only
> >> some
> >> > > minor changes.
> >> > > I tried to do some extra memory optimization, and in theory it
> should
> >> > > provide better results, but to be honest I don't have a good way to
> >> > measure
> >> > > this in the browser. I tried the Chrome performance.memory
> extensions
> >> > but I
> >> > > don't have much confidence in that given how much it varies between
> >> > reloads
> >> > > without changing anything else. The extra code changes I made were
> to
> >> > make
> >> > > the '_nodeKind' strings into String object references, so they only
> >> refer
> >> > > to a single reference to a string instead of multiple copies of
> >> > primitives.
> >> > > That change is isolated to a single commit so can easily be reversed
> >> if
> >> > > there is something not good about it... but all my local tests
> >> continue
> >> > to
> >> > > pass. I will get the new tests into RoyaleUnit in the coming days.
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On Thu, Sep 5, 2019 at 7:39 AM Greg Dove 
> wrote:
> >> > >
> >> > >> Yeah, I saw that ;) Don't worry, I am aware of it.
> >> > >>
> >> > >> My first goal is to make sure it works like it should, because that
> >> > comes
> >> > >> first, and then to optimize. I'll check the memory side of things
> and
> >> > make
> >> > >> sure it's at least the same as before. If you can point me to some
> >> > >> publicly accessible large test cases that would be really helpful.
> I
> >> > will
> >> > >> work through that before I push anything.
> >> > >>
> >> > >> On Thu, Sep 5, 2019 at 7:26 AM Harbs 
> wrote:
> >> > >>
> >> > >>> Heads up:
> >> > >>>
> >> > >>> I did some (on first blush) odd things in XML related to QNames.
> >>

Acceptance of Royale by Flex Developers

2019-10-08 Thread Chris Velevitch

The use of the terms "strands" and "beads" still doesn't make sense to
me because they are concepts I have never heard before and it is
creating a barrier to acceptance and deepens the learning curve. As
far as I can tell, it's something to do with visual/UI components.

The section "Strands and Beads" should ideally be titled "Visual
Components" because that section is about visual components and is
alluding to the fact visual components are standalone microcosms of
the MVC pattern and the ability to treat the model, view and
controller as plugins to the component. The statement that components
are "strands" is, in my mind, misleading because it doesn't make sense
to interchange terms components and strands if a strand is a
component. In fact, diving into the code, the "addBead" function gives
the "bead" a reference to the component the "bead" is being added to.

It is clear from the documentation that "beads" are "plugins" and the
documentation should be talking about extending components with
plugins. All references to "bead" should be replaced with "plugin" and
all references to "strand" be replaced with either "hostComponent", or
"parent" or appropriately something else.

We seem to be neglecting the rich heritage that we have gotten from
Adobe Flex and I don't see the point giving existing concepts new
names.

Build failed in Jenkins: royale-asjs_MXTests #1223

2019-10-08 Thread Apache Royale CI Server

See 


--
[...truncated 1.01 MB...]
[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

49 matches

Mail list logo