Re: SWF Graphics api emulation -WIP

Mainly for the record, the only other implementation that came to mind (and I rejected) was to track marked things. Something like: /** add a child */ public function addElement(element:IUIBase); /** add an internal child */ public function addInternalElement(element:IUIBase,

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

See

Re: SWF Graphics api emulation -WIP

@Alex - yeah, I was just curious if there could be a sneaky way to keep it to the single level. If not, then so be it. That was only for the UIGraphicsBase class, which I was pretty much using like 'flash.display.Shape' for testing. Anyhow, the Graphics emulation can be used with anything that

Re: SWF Graphics api emulation -WIP

Hi Carlos, What I added is intended mainly useful for emulation purposes, either for easier migration of code that uses that approach in Flex, or the convenience of a familiar api in certain circumstances. It provides a close approximation of (most of) the swf drawing api, but it may only be

Build failed in Jenkins: royale-asjs #650

See Changes: -- [...truncated 1.17 MB...] [java] [java] Jan 29, 2020 3:21:57 AM com.google.javascript.jscomp.LoggerErrorManager println [java]

Build failed in Jenkins: royale-asjs #649

See Changes: [carlosrovira] todomvc-jewel-example: near completion [carlosrovira] todomvc-jewel-example: left from last commit -- [...truncated

Re: SWF Graphics api emulation -WIP

On 1/28/20, 1:01 AM, "Carlos Rovira" wrote: Hi again :), I still didn't see the code, but was imagining how I'd like to use this feature. Some thoughts: 1.- Could be possible to have it as a bead for UIBase components a side of the UIGraphicBase that

Re: [royale-asjs] branch develop updated: ToolTipRemovalWhenItemRemoved: new bead to abstract best practice showcased in #697

Hi Yishay, please go ahead and do the changes thanks! El mar., 28 ene. 2020 a las 11:55, Yishay Weiss () escribió: > Thanks for adding this. Since this behavior could be desirable in all > component sets I’d like to suggest the following: > > > 1. Move it to Basic > 2. Create an interface

RE: [royale-asjs] branch develop updated: ToolTipRemovalWhenItemRemoved: new bead to abstract best practice showcased in #697

Thanks for adding this. Since this behavior could be desirable in all component sets I’d like to suggest the following: 1. Move it to Basic 2. Create an interface ITooltipBead which includes removeTip() 3. Have all tooltip beads implement it 4. Use strand.getBeadByType(ITooltipBead)

Re: SWF Graphics api emulation -WIP

Hi again :), I still didn't see the code, but was imagining how I'd like to use this feature. Some thoughts: 1.- Could be possible to have it as a bead for UIBase components a side of the UIGraphicBase that could still be convenient for some cases? <-- This could be a custom bead

RE: [royale-asjs] branch develop updated: Only contorllers truly intersted in multiselection will dipatch a multiselection event.

If guess I figured most of the beads (and item renderers) were fine for my use-case so I might as well just use them as they are. We were not in immediate needs of anchors, for example. I realize directly instantiating a bead breaks IoC so I might have been following an example, but I don’t see

Re: SWF Graphics api emulation -WIP

Hi Greg, very cool! :) Hope to play with it very soon :) Do you plan to add your "graphics browser example" to examples? Thanks for working on this! :) Carlos El mar., 28 ene. 2020 a las 3:28, Greg Dove () escribió: > FYI, I just pushed the WIP on that. > > to use it in code, there is a

Re: Renderers doesn't support States

ok, I separate States to a new MXMLStatesItemRenderer. For Jewel, that uses StyledItemRenderer as the base class now extend this new one to get states support by default El lun., 27 ene. 2020 a las 21:49, Alex Harui () escribió: > Classes in Basic should remain PAYG. That would imply that MXML