Build failed in Jenkins: royale-asjs_MXTests #361

See -- [...truncated 2.01 MB...] [mxmlc] using source file:

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

See

Build failed in Jenkins: royale-asjs_MXTests #360

See Changes: [aharui] MXRoyale AdvancedDataGrid shows summary row. Next: get it to open [aharui] ADG expands items -- [...truncated 2.01

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

See

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

See

Jenkins build is back to normal : royale-compiler #682

See

Re: [royale-docs] branch master updated: Create routing.md

copying Alex's comment into the bug report, as this is all new stuff to me. On Wed, Jan 16, 2019 at 3:06 PM Alex Harui wrote: > We don't have enough information to create a routing implementation that > would work everywhere for everybody. I'm not even sure such a thing could > exist. There

Re: [royale-docs] branch master updated: Create routing.md

We don't have enough information to create a routing implementation that would work everywhere for everybody. I'm not even sure such a thing could exist. There would probably be different choices for "routes-as-paths" and "routes-as-queries" and probably others. I think the ASDoc app

Re: [royale-docs] branch master updated: Create routing.md

Very interesting, didn't know we have infrastructure already to do this. I thought we only have ASDoc app that does this, but no reusable API in a SWC to perform routing. Can someone point me to the code? Thanks El mié., 16 ene. 2019 a las 19:31, escribió: > This is an automated email from the

Re: Issues with the first-app tutorial

Thank you. On Wed, Jan 16, 2019 at 1:12 PM Alex Harui wrote: > I put links to the source in the GH issue. > > The missing pages do not exist yet. I'm hoping someone else will take a > stab at writing them. > > Thanks, > -Alex > > On 1/16/19, 2:37 AM, "Andrew Wetmore" wrote: > > If

Re: Issue with Jewel popup

IMO, MDI is a specific implementation of an "overlapping windows" implementation. In some scenarios (like AIR apps) the true MDI windows (equivalent to other top-level windows of other apps) was the AIR NativeWindow itself and no ActionScript code managed how those MDI windows behaved. But

Re: Issues with the first-app tutorial

I put links to the source in the GH issue. The missing pages do not exist yet. I'm hoping someone else will take a stab at writing them. Thanks, -Alex On 1/16/19, 2:37 AM, "Andrew Wetmore" wrote: If someone will point me to where the pages are, I could make such small changes. In

Build failed in Jenkins: royale-asjs #1801

Deleting: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/localfonts.ser> [delete] Deleting: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/ws/frameworks/mxml-manifest.xml> [delete] Deleting: <http://apacheroyaleci.w

Build failed in Jenkins: royale-compiler #681

See -- [...truncated 213.19 KB...] [junit] Running org.apache.royale.compiler.internal.tree.mxml.MXMLXMLNodeTests [junit] Tests run: 7, Failures: 0,

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

See

Re: Issues with the first-app tutorial

If someone will point me to where the pages are, I could make such small changes. In the second bug report I ask if the missing page exist yet, as I don't know want to duplicate efforts On Wed, Jan 16, 2019, 12:44 AM Alex Harui Hi Andrew, > > I see you filed some issues. Is there some action

Re: Should we change width/height to use EM instead PX?? (was: Re: Using em vs px)

Ok Alex, for what I read, I understand that we already has mechanism in Royale to handle this. So I think Mark, should try to do some easy test case that showcase the problem and he/we can work over that to see the easiest solution. Maybe is just a matter of supporting that in Jewel cause I

Re: [Non-DoD Source] Re: Things that we still doesn't have and need in UIBase sizing

Hi Alex, El mar., 15 ene. 2019 a las 18:44, Alex Harui () escribió: > Hi Carlos, > > IMO, we want to abstract away platform/runtime-specific implementations in > the API surface. It is not a good idea to have our user's application rely > on API practices that may not work on all targets. So

Re: Issue with Jewel popup

Ok, I always refer to that concept as MDII (Multiple Document Interface). And in Flex we had external MDI library to do that. For me that's a concrete case and people that wants to do MDI should start that effort and make a new library. So IMO we should start to that need to invest time in this.