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

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

See

RE: Problems dealing with bead substitution in Royale

I agree writing ‘null’ in the css is a hack. I also noticed places in Jewel’s defauts.css that had IBeadLayout: ClassReference("org.apache.royale.jewel.beads.layouts.NullLayout"); Which seems pretty similar. I’m still not sure I understand the scenario. If you just need to create

Re: [royale-asjs] branch develop updated: Jewel Group: Fix dynamic adding Horizontal/Vertical layout

Hi Piotr, thinking on it better, I prefer your proposal or revert the change of the removal of basic layout css and manage as part of your app code for now, since I think it will be easy for you to solve on your code as specialized case, and we can avoid that code in framework for now until we

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

Build failed in Jenkins: royale-asjs_MXTests #410

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

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.

Problems dealing with bead substitution in Royale

Hi, Piotr and I found a situation where we don't know how to solve with some generalist solution. Hope others here could give some ideas. The setup: We have a layout bead that decorates the strand with a css class selector. The bead is configured in CSS as a default bead The problem: We found

Re: [royale-asjs] branch develop updated: Jewel Group: Fix dynamic adding Horizontal/Vertical layout

Hi Piotr, I'll create a thread to talk about how to do this kind of thing with clear explanation, so others could suggest how to deal with it. This is not something related only to Jewel. Any Royale bead that set up a css selector on the strand will suffer this issue, so I think is important