Build failed in Jenkins: TourDeFlexMigration #638

See Changes: [greg.dove] Fix for currentState bindings not working. It is either this fix, or -- Started by upstream project "royale-asjs"

Build failed in Jenkins: Royale_ASDoc_Example #639

See Changes: [greg.dove] Fix for currentState bindings not working. It is either this fix, or -- [...truncated 5.25 KB...] [mxmlc] 14

Re: Let's bump Royale version to 1.0

Today, I received permission to disclose that Alina & Pashmina's team has 88 of their modules ready for release (tested and validated by their QA team). They still have more modules to migrate before they deliver to their customer, but it is a good sign that the emulation is sufficient for many

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

See

Build failed in Jenkins: royale-asjs_MXTests #639

See Changes: -- Started by upstream project "royale-asjs" build number 737 originally caused by: Started by upstream project "royale-asjs_jsonly" build

Build failed in Jenkins: TourDeFlexMigration #637

See Changes: -- Started by upstream project "royale-asjs" build number 737 originally caused by: Started by upstream project "royale-asjs_jsonly" build

Build failed in Jenkins: Royale_ASDoc_Example #638

See Changes: -- [...truncated 5.76 KB...] [mxmlc] 14 [mxmlc] -output=

Build failed in Jenkins: royale-asjs_jsonly #838

See Changes: -- [...truncated 209.91 KB...] download-jar: [echo] basedir is C:\jenkins\workspace\royale-compiler\compiler\src\main\resources [e

Build failed in Jenkins: TourDeFlexMigration #636

See Changes: -- Started by upstream project "royale-asjs" build number 736 originally caused by: Started by upstream project "royale-asjs_jsonly" build

Build failed in Jenkins: Royale_ASDoc_Example #637

See Changes: -- [...truncated 5.12 KB...] [mxmlc] 14 [mxmlc] -output=

Build failed in Jenkins: TourDeFlexMigration #635

See Changes: [carlosrovira] crux: quick start example cleaning and updates [carlosrovira] jewel-themes: update all themes with new DrawerFooter styles ---

Build failed in Jenkins: Royale_ASDoc_Example #636

See Changes: [carlosrovira] crux: quick start example cleaning and updates [carlosrovira] jewel-themes: update all themes with new DrawerFooter styles --

Re: "has" vs "is": sharing code, swapping out subsystems, and more...

Hi Alex, if will be of help if you point us to different links where we can learn about this modifications, since I at least can just imagine what is all about, but will need to get deeper in the concepts to understand the changes and to apply this patterns. In Jewel each "list component has its

Build failed in Jenkins: TourDeFlexMigration #634

See Changes: [carlosrovira] jewel-drawer: New DrawerFooter component [carlosrovira] tour-de-jewel: DrawerFooter example -- Started by upst

Build failed in Jenkins: Royale_ASDoc_Example #635

See Changes: [carlosrovira] jewel-drawer: New DrawerFooter component [carlosrovira] tour-de-jewel: DrawerFooter example -- [...truncated

Re: "has" vs "is": sharing code, swapping out subsystems, and more...

I've pushed the "has" branch that contains a refactoring of the item renderers. Tour De Jewel and MDL Example seem to be working as is Basic List Example and MX AdvancedDataGrid. "has" is really just calls to getBeadByType. If we start to see performance issues, then we'll look into optimizin

Build failed in Jenkins: TourDeFlexMigration #633

See Changes: [yishayjobs] Renamed Moonshine proj file [carlosrovira] jewel-presentation-models: add dispatch of binding events for some [carlosrovira] crux: added AMFStorageBean

Build failed in Jenkins: Royale_ASDoc_Example #634

See Changes: [yishayjobs] Renamed Moonshine proj file [carlosrovira] jewel-presentation-models: add dispatch of binding events for some [carlosrovira] crux: added AMFStorageBean

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

See

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

See

Build failed in Jenkins: royale-asjs_jsonly #832

See Changes: [carlosrovira] jewel-drawer: fix a bug generated from an older refactor where drawer -- [...truncated 1.58 MB...] [java]

Build failed in Jenkins: royale-asjs_jsonly #831

See Changes: [carlosrovira] jewel: some cleaning and organization of imports -- [...truncated 1.58 MB...] [java] [java]

Build failed in Jenkins: royale-asjs_jsonly #830

See Changes: [carlosrovira] crux: clean and organize imports [carlosrovira] crux: fix asconfig.json to work on VSCode -- [...truncated 1.58

Build failed in Jenkins: royale-asjs_jsonly #829

See Changes: [carlosrovira] crux: added AMFStorageBean [carlosrovira] todomvc-crux: use new AMFStorageBean instead of plain AMFStorage -- [

Build failed in Jenkins: royale-asjs #732

See Changes: [yishayjobs] Renamed Moonshine proj file [carlosrovira] jewel-presentation-models: add dispatch of binding events for some -- [...tr

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

See

Re: New TodoMVC Crux version

Right, no backend at all, is based on todomvc.com so our plan is submit to that web, and they only use local storage. Best Carlos El lun., 17 feb. 2020 a las 10:55, Takeshita Shoichiro () escribió: > Carlos, thanks for your explanation. Understood. > > As to TodiMVC, it is front end and no back

Re: New TodoMVC Crux version

Carlos, thanks for your explanation. Understood. As to TodiMVC, it is front end and no back end server code is used. Is my understanding correct? 2020年2月17日(月) 18:45 Carlos Rovira : > Hi Takeshita, > > AMFStorage is like the old Flash LSO (Local Shared Object, already emulated > in MXRoyale) th

Re: New TodoMVC Crux version

Hi Takeshita, AMFStorage is like the old Flash LSO (Local Shared Object, already emulated in MXRoyale) that you use as a cookie, but LSO was better since it allows much more size than a cookie and was encoded in AMF, what means you just need to annotate the class with RemoteClass Metadata like we

Build failed in Jenkins: royale-asjs_jsonly #827

See Changes: [yishayjobs] Renamed Moonshine proj file -- [...truncated 1.17 MB...] [java] var events = require('events'); [java]