Re: User docs entry for strands and beads

Answers/Opinions inline On 12/28/18, 5:07 AM, "Andrew Wetmore" wrote: Hi, all: I am working on the user doc page for strands and beads [1]. This is intended for application developers using Royale; there is unfinished material available for developers working on Royale

Re: Royale XML and QNames

Well, I don't think we want to require folks to use XMLQName in their code. However, your idea of ClassQName made me think that maybe we can have the compiler set a flag on the QName whenever it is used in bracket syntax on non-XML. I will try to remember to try that next week. -Alex On

Re: [royale-asjs] branch develop updated: improve IActivable to not rely on ids and use new activableName property

Hi, In the code you posted, I agree you don't need to change the name of the "name" parameter. I am more interested in every place I see "IActivable" and isActive. I haven't looked at the code in detail, but it sounds like you are working on something like a Navigator and IIRC, Flex

Build failed in Jenkins: royale-asjs_MXTests #306

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

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

See

RE: User docs entry for strands and beads

>> 2. Is the order of beads on a strand significant? >good question, maybe this should be answered by other. >I think usually not if each bead is an isolated funcionality. But maybe you >can think on some bead that requiere other beads, in that case, I suppose >the bead that require the other

Re: [royale-asjs] branch develop updated: improve IActivable to not rely on ids and use new activableName property

Hi, while doing the refactor for "name" to "selectedContent", I saw that maybe the discussion is not having the real code into account. I think what we really want to change is the method in the components that are responsible to select the content, not the property "name" itself. In this case,

Re: User docs entry for strands and beads

Hi Andrew, El vie., 28 dic. 2018 a las 14:07, Andrew Wetmore () escribió: > > 1. There are three ways of adding beads to a component: baked in using > , through CSS, and dynamically using addBead(). Which method is > best to use for what purposes? > Don't think one is better than other, adding

User docs entry for strands and beads

Hi, all: I am working on the user doc page for strands and beads [1]. This is intended for application developers using Royale; there is unfinished material available for developers working on Royale itself in the wiki [2], [3]. >From the app developer point of view, I want to answer these

[GitHub] cottage14 opened a new pull request #13: Cottage14 patch 1

cottage14 opened a new pull request #13: Cottage14 patch 1 URL: https://github.com/apache/royale-docs/pull/13 Updating page on strands and beads This is an automated message from the Apache Git Service. To respond to the

[GitHub] cottage14 closed pull request #13: Cottage14 patch 1

cottage14 closed pull request #13: Cottage14 patch 1 URL: https://github.com/apache/royale-docs/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the

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

See

Re: Royale XML and QNames

Gotcha. I think the simplest solution is to replace Name with XMLQName for XML. The other similar option is to create a ClassQName that the compiler would use instead of QName for namespaces in classes. > On Dec 28, 2018, at 10:32 AM, Alex Harui wrote: > > Most URIs in QNames have something

Build failed in Jenkins: royale-asjs_MXTests #305

See Changes: [noreply] Update TextInput.as -- [...truncated 2.36 MB...] [mxmlc] using source file:

Re: Build SDK with ANT fails in test

Thanks Alex, that worked :) El vie., 28 dic. 2018 a las 9:24, Alex Harui () escribió: > The CI servers are building successfully. > > Run "ant wipe-all" in royale-compiler, then "ant". > > -Alex > > On 12/28/18, 12:11 AM, "Carlos Rovira" wrote: > > Hi > > latest changes are still

Re: Royale XML and QNames

Most URIs in QNames have something like: "library://ns.adobe.com/mx/core/internal". That is not a legal JavaScript property name. IOW, you can't run: someObject.library://ns.adobe.com/mx/core/internal::foo = 1; So, we used to output bracket syntax:

Re: Build SDK with ANT fails in test

The CI servers are building successfully. Run "ant wipe-all" in royale-compiler, then "ant". -Alex On 12/28/18, 12:11 AM, "Carlos Rovira" wrote: Hi latest changes are still causing some problems in build. Can you point me to some flag I can use to avoid this tests when

Build SDK with ANT fails in test

Hi latest changes are still causing some problems in build. Can you point me to some flag I can use to avoid this tests when building SDK with ANT while this problems are fixed? thanks main: [mkdir] Created dir:

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

See