Re: Problems dealing with bead substitution in Royale

Then this is a really bad subject line. If you want to replace our event subsystem with true DOM events, feel free to do so. I think it is safe to do so now that we no longer have to support IE10 or older. If, after that work has been done and bead events are still too heavy, then we can

Re: Problems dealing with bead substitution in Royale

Thanks for your thoughts. My motivation for doing this has very little to do with removing beads. I have not been happy with the event system of strands and beads for a long time. I’d be OK with removing removeBead from IStrand, but as it stands now, I think it makes sense to remove the

Re: Problems dealing with bead substitution in Royale

It looks like a reasonable subsystem design, but given that we have a lot of code running just fine without this, and that bead substitution should be a very rare situation, I'm having trouble understanding why we would want to add an entire just-in-case subsystem. Asking beads for their

Re: Problems dealing with bead substitution in Royale

Hi Harbs El mar., 19 feb. 2019 a las 18:30, Harbs () escribió: > > > Yes. Basically, you can ask any bead for a list of its interests, and that > list is used to both add and remove bead references in the strand. The bead > does not need to clean itself. A ututiliy method can completely strip a

Re: Problems dealing with bead substitution in Royale

> On Feb 19, 2019, at 5:14 PM, Carlos Rovira wrote: > > Hi Harbs, > > I finally could take a look at you notification system, I can intuit a > good idea but still need more info or explanation from you to get the > benefits. My questions is more about the global thinking of the > notification

Re: Problems dealing with bead substitution in Royale

Hi Harbs, I finally could take a look at you notification system, I can intuit a good idea but still need more info or explanation from you to get the benefits. My questions is more about the global thinking of the notification idea more than an implementation question: 1.- why we have tow

Re: Problems dealing with bead substitution in Royale

Bump. > On Feb 1, 2019, at 8:36 AM, Harbs wrote: > > https://github.com/apache/royale-asjs/commit/1b2a45c91397e485be93d56925f2c31417726bb7#diff-2b4ced1196f39150a85b0cd61bbb338dL64 > >

Re: Problems dealing with bead substitution in Royale

Sorry Harbs, very busy this days. Very interested in take a look. Just one question. A part from the implementation did you commit some example of use, so I can differentiate clearly the code that is using this notification system thanks! El jue., 31 ene. 2019 a las 18:04, Alex Harui ()

Re: Problems dealing with bead substitution in Royale

I hope to look at this on the weekend. -Alex On 1/31/19, 4:17 AM, "Harbs" wrote: Bump. Anyone have opinions on this? > On Jan 30, 2019, at 12:47 PM, Harbs wrote: > > I implemented the basics of my idea here:

Re: Problems dealing with bead substitution in Royale

Bump. Anyone have opinions on this? > On Jan 30, 2019, at 12:47 PM, Harbs wrote: > > I implemented the basics of my idea here: > https://github.com/apache/royale-asjs/commit/1b2a45c91397e485be93d56925f2c31417726bb7 > >

Re: Problems dealing with bead substitution in Royale

I implemented the basics of my idea here: https://github.com/apache/royale-asjs/commit/1b2a45c91397e485be93d56925f2c31417726bb7 I got my inspiration from PureMVC. I only made enough changes to get rid of

Re: Problems dealing with bead substitution in Royale

Agree too. We can have more beads to give options as already happens in other parts of Royale. So don't see a problem your stacked version could come in. Also, as I have time, I could review and see if I could provide some support so we can get all of it more integrated... Most of the things in

Re: Problems dealing with bead substitution in Royale

That sounds good Harbs, you could that of if you want to save some effort, first make a new email thread with some example of code on how this would look in the end, so we all can understand it and provide some feedback so your effort could be more easy in the end. El lun., 28 ene. 2019 a las

Re: Problems dealing with bead substitution in Royale

Hi Alex, El lun., 28 ene. 2019 a las 17:22, Alex Harui () escribió: > It is fine to have a utility function such as this, but IMO, it doesn't > actually solve the problem. If the original bead does not know how to > remove itself, then a version of that bead needs to be created that does > know

Re: Problems dealing with bead substitution in Royale

Just give your version a different name that describes what it is and commit it to Royale. Royale gives folks choices. My 2 cents, -Alex On 1/28/19, 12:01 PM, "Piotr Zarzycki" wrote: Guys, Many thanks for all your thoughts. Harbs thank you for this utility it will be very

Re: Problems dealing with bead substitution in Royale

Guys, Many thanks for all your thoughts. Harbs thank you for this utility it will be very useful. I think I'm ok with having some specialized stuff which is doing things like removing bead etc. I did small clean up of FormItemView and put it in other thread. I wrote also StackedFormView but I

Re: Problems dealing with bead substitution in Royale

IMO, either use a few more words to describe it here, or show the code in a branch. I don't think the generic problem of cleaning up an instance from an external instance is solvable, but maybe there are sweet spots along the way. -Alex On 1/28/19, 8:26 AM, "Harbs" wrote: Good point.

Re: Problems dealing with bead substitution in Royale

Good point. If we would implement my idea of notifications, we could use utility functions to clean out beads. If anyone is interested in this direction, I can write an implementation in a branch to show what I’m talking about… Harbs > On Jan 28, 2019, at 6:22 PM, Alex Harui wrote: > > It

Re: Problems dealing with bead substitution in Royale

It is fine to have a utility function such as this, but IMO, it doesn't actually solve the problem. If the original bead does not know how to remove itself, then a version of that bead needs to be created that does know how to remove itself. While we could add replaceable versions of every

Re: Problems dealing with bead substitution in Royale

Hi Harbs this seems to me the right way to go. In the current case, I think Jewel should not know about how to clean itself since is not PAYG. So Piotr should subclass the bead and add the clean up functionality an configure as default in this project. Then use your replaceBead to do the change

Re: Problems dealing with bead substitution in Royale

HI Alex mostly agree with your thoughts. Just some points: * While I think beads should be "instantiation time", don't agree with wanting to remove the "removeBead" method. We're a framework, and people will find this problem. So is difficult to explain the we don't have any way to do this * In

RE: Problems dealing with bead substitution in Royale

Sorry, meant this [1] one [1] https://github.com/yishayw/Examples/tree/RunTimeLayout From: Carlos Rovira Sent: Monday, January 28, 2019 10:29:11 AM To: dev@royale.apache.org Subject: Re: Problems dealing with bead substitution in Royale Hi Yishay, you're

Re: Problems dealing with bead substitution in Royale

cenario. If you just need to create > beads in AS3, you can do so while overriding the default bead, as another > [1] example shows. > > > > [1] https://github.com/yishayw/Examples > > > > > From: Carlos Rovira > Sent: Sund

Re: Problems dealing with bead substitution in Royale

I know there have been other responses, but I think this original post is the best place for my response. IMO, sealed classes are another safety/security measure. Changing the code in a class at runtime invites opportunities for hacking that are really hard to detect. The set of beads

RE: Problems dealing with bead substitution in Royale

to create beads in AS3, you can do so while overriding the default bead, as another [1] example shows. [1] https://github.com/yishayw/Examples From: Carlos Rovira Sent: Sunday, January 27, 2019 7:00:51 PM To: dev@royale.apache.org Subject: Re: Problems dealing

Re: Problems dealing with bead substitution in Royale

Hi, Yishay, as Piotr said, it seems you're doing a workaround to solve the current problem. But Royale is a framework. It's ok to use temporary workarounds, but we must focus the way to make things as usable as possible, optimal and with the less code possible. Don't know exactly why Piotr wants

Re: Problems dealing with bead substitution in Royale

I don’t understand the situation. Why is nested components an issue? > On Jan 27, 2019, at 1:26 PM, Piotr Zarzycki wrote: > > Hi Yishay, > > Your example is showing how to avoid it, but user probably won't null > anything in css. That's the situation. As for the scenario - Let's say that >

Re: Problems dealing with bead substitution in Royale

Hi Yishay, Your example is showing how to avoid it, but user probably won't null anything in css. That's the situation. As for the scenario - Let's say that you have component which has inside of View instantiation of another component. Situation looks like that: - first component with bead X

RE: Problems dealing with bead substitution in Royale

Can you explain why this is necessary? Why create a strand with bead X and replace it with bead Y in runtime? If your strand is using loadBeadFromValuesManager() it should be able to receive a null css class reference, like in this example.