Sure. I think separating Selection from the Renderer was the right thing to do,
but we also need to figure out how to make it do the “right thing” be default.
I’m wondering if there should be a “selectionBead” property in every item
renderer which could be null.
Maybe DataContainerBase should a
More loosely-coupled pieces often results in head-scratching. But it also
results in PAYG and flexibility.
Our job is to find the common patterns, and pre-compose as needed, such as the
Express component set. This "has" pattern is a new pattern so we'll have to
figure out new best practices.
Yes. If I replace the default SelectableItemRendererClassFactory
My work-around was to use:
js|List{
IItemRendererClassFactory:
ClassReference("org.apache.royale.core.OverridableSelectableItemRendererClassFactory");
}
The average user will be scratching their heads on how to solve this
Just a very quick reply about only one of your questions.
I do have a working port of Cairngorm. I am trying to find time to check
that and release it for others to use. It will be this week but probably
another couple of days. The only part not working that I am aware of is the
ViewHelper (and I w
hello，
First of all, I would like to thank the Apache Royale team for your dedication.
I come from China. Our company has a soft product that needs to be upgraded.
This product is a manufacturing enterprise information system. The frontend is
based on flash, and the backend uses spring +ibatis
On 3/1/20, 12:33 AM, "Harbs" wrote:
I’ve also discovered that setting the selection bead is more difficult than
I would hope it to be.
For example there should be an easy way to specify the selection bead in a
situation like this:
I may not be understanding the problem. The Sp
I’ve also discovered that setting the selection bead is more difficult than I
would hope it to be.
For example there should be an easy way to specify the selection bead in a
situation like this:
>
