ectedColor, highlightColor,
> >>and
> >> >> >> downColor properties is for backward compatibility with Flex item
> >> >> >> renderers and maybe because there is no "down" or "selected"
> >> >> >>pseudo-stat
t;
>> >> >>pseudo-states
>> >> >> in CSS, but I agree those can be moved off of UIItemRendererBase
>>to
>> >>some
>> >> >> other class. And the implementation of those color properties
>>could
>> >>just
>&
le
> >> >>ones
> >> >> can just set x,y,width,height. So maybe MXMLItemRenderer should add
> >> >>the
> >> >> code that calls MXMLDataInterpreter and MXMLItemRendererWithLayout
> >>would
> >> >> add the assig
XMLItemRendererWithLayout
>>would
>> >> add the assignable layout support.
>> >>
>> >> Thoughts?
>> >> -Alex
>> >>
>> >> On 4/15/18, 9:36 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:
>> >>
>> >> >I t
ussed before. As Alex suggested
>> >you can always create a different implementation for
>> >ISelectableItemRenderer (or IItemRenderer).
>> >
>> >
>> >
>> >What I find confusing is that MXMLItemRenderer does not explicitly
>> >implement IMXMLDocume
can always create a different implementation for
> >> >ISelectableItemRenderer (or IItemRenderer).
> >> >
> >> >
> >> >
> >> >What I find confusing is that MXMLItemRenderer does not explicitly
> >> >implement IMXMLDocument, and t
nderer).
>> >
>> >
>> >
>> >What I find confusing is that MXMLItemRenderer does not explicitly
>> >implement IMXMLDocument, and that most of the mxml related code is
>> >actually in UIItemRendererBase. Alex, maybe you can explain what the
>
sing is that MXMLItemRenderer does not explicitly
> >implement IMXMLDocument, and that most of the mxml related code is
> >actually in UIItemRendererBase. Alex, maybe you can explain what the
> >reasoning was for that?
> >
> >
> >
> >____
> >From: carl
was for that?
>
>
>
>
>From: carlos.rov...@gmail.com <carlos.rov...@gmail.com> on behalf of
>Carlos Rovira <carlosrov...@apache.org>
>Sent: Sunday, April 15, 2018 2:29:20 PM
>To: dev@royale.apache.org
>Subject: Re: ItemR
: carlos.rov...@gmail.com <carlos.rov...@gmail.com> on behalf of Carlos
Rovira <carlosrov...@apache.org>
Sent: Sunday, April 15, 2018 2:29:20 PM
To: dev@royale.apache.org
Subject: Re: ItemRenderer is not PAYG
Hi,
the hierarchy chain is "UIItemRendererBase > DataItemRendere
There is no obligation to use UIItemRendererBase for Jewel ItemRenderers.
If you run into places where we assume UIItemRendererBase and not
IItemRenderer, that's either a bug or requires a different controller or
view.
Let us know what you run into.
-Alex
On 4/14/18, 8:33 AM,
Carlos,
It is your way of approach where everything what you are doing is in CSS,
but I don't agree that the way where you are setting some styles in the
code is bad one. It's just different approach which is really good in some
cases.
Thanks,
Piotr
2018-04-14 23:02 GMT+02:00 Carlos Rovira
Hi Piotr,
I have already checked Jewel List and ListItemRenderer before sending this
email.
Jewel is working, I only say that is carrying some overhead of properties,
getters and setters and methods that Jewel users will never user at 100%,
so that's why we want to avoid with PAYG and why we
Hi Carlos,
That's why you are creating your own Item renderer and override that method.
Although if you can propose other solution. Of course on different branch
with checking if you not break anything.
Especially MDL Table.
Thanks,
Piotr
On Sat, Apr 14, 2018, 5:34 PM Carlos Rovira
14 matches
Mail list logo
