following commit(s) were added to refs/heads/develop by this push:
> > new bec3d1b The HTML CheckBox use now a span for the label so we
> can customize the look with css
> > new aa7ca1c Merge branch 'develop' of
> https://github.com/apache/royale-asjs into develop
> > bec
x.apache.org/repos/asf/royale-asjs.git
>
>
> The following commit(s) were added to refs/heads/develop by this push:
> new bec3d1b The HTML CheckBox use now a span for the label so we can
> customize the look with css
> new aa7ca1c Merge branch 'develop' of
>
Looks like you missed TreeItemRenderer. I haven’t checked to see if others were
omitted.
From: ha...@apache.org<mailto:ha...@apache.org>
Sent: Sunday, December 19, 2021 11:26 AM
To: comm...@royale.apache.org<mailto:comm...@royale.apache.org>
Subject: [royale-asjs] branch develop up
; Piotr Zarzycki escreveu no dia terça,
> > > > 11/08/2020 à(s) 14:26:
> > > >
> > > > > Hi Hugo,
> > > > >
> > > > > Which FormItem are you referring to ? Basic, Jewel ?
> > > > >
> > > > > wt., 11
gt; > > Piotr Zarzycki escreveu no dia terça,
> > > 11/08/2020 à(s) 14:26:
> > >
> > > > Hi Hugo,
> > > >
> > > > Which FormItem are you referring to ? Basic, Jewel ?
> > > >
> > > > wt., 11 sie 2020 o 15:12 Hugo F
re you referring to ? Basic, Jewel ?
> > >
> > > wt., 11 sie 2020 o 15:12 Hugo Ferreira
> > > napisał(a):
> > >
> > > > There is any property, bead or css style that puts the FormItem label
> > on
> > > > the top of the component instead
08/2020 à(s) 14:26:
>
> > Hi Hugo,
> >
> > Which FormItem are you referring to ? Basic, Jewel ?
> >
> > wt., 11 sie 2020 o 15:12 Hugo Ferreira
> > napisał(a):
> >
> > > There is any property, bead or css style that puts the FormItem label
> o
Hi Piotr,
Jewel.
Piotr Zarzycki escreveu no dia terça,
11/08/2020 à(s) 14:26:
> Hi Hugo,
>
> Which FormItem are you referring to ? Basic, Jewel ?
>
> wt., 11 sie 2020 o 15:12 Hugo Ferreira
> napisał(a):
>
> > There is any property, bead or css style that puts the Fo
Hi Hugo,
Which FormItem are you referring to ? Basic, Jewel ?
wt., 11 sie 2020 o 15:12 Hugo Ferreira napisał(a):
> There is any property, bead or css style that puts the FormItem label on
> the top of the component instead of left ?
>
> What we have:
>
> My Label 1 My Text
There is any property, bead or css style that puts the FormItem label on
the top of the component instead of left ?
What we have:
My Label 1 My TextInput 1
What I would like:
My Label1
My TextInput 1
<mailto:comm...@royale.apache.org>
Subject: Re: [royale-asjs] branch develop updated: Make sure mx combobox shows
label
I'm not sure this is the "right" fix. Accessing model in a constructor
eliminates a bunch of ways of swapping out a model (such as in the beads array).
-Alex
On 3/29/20,
d2c178decee1%7C0%7C0%7C637210812914161239sdata=Tlh2u903Pdjbm%2B%2FbVn2b9%2BGaRi0MAIqiNtiy%2BjAjdew%3Dreserved=0
The following commit(s) were added to refs/heads/develop by this push:
new 8a6ff88 Make sure mx combobox shows label
new 80767c5 Merge branch 'develo
better could be that bead could check listeners and change
> > the cursor to pointer if the strand has a MouseEvent.XXX listeners added
> > automatically, (although this solution needs more process)
> >
> >
> >
> > El lun., 21 ene. 2019 a las 12:44,
heck listeners and change
> the cursor to pointer if the strand has a MouseEvent.XXX listeners added
> automatically, (although this solution needs more process)
>
>
>
> El lun., 21 ene. 2019 a las 12:44, Piotr Zarzycki (<
> piotrzarzyck...@gmail.com>) escribió:
>
> > Hi Car
listeners and change
the cursor to pointer if the strand has a MouseEvent.XXX listeners added
automatically, (although this solution needs more process)
El lun., 21 ene. 2019 a las 12:44, Piotr Zarzycki (<
piotrzarzyck...@gmail.com>) escribió:
> Hi Carlos,
>
> In LabelPlayground example w
Hi Carlos,
In LabelPlayground example we have label which should display hand cursor
when we roll over on it. It's being used there className="cursor-pointer"
[1] - I see in the browser that this class is being applied, but I cannot
find where it is declared ?
In my application
Just published!
Thanks to Andrew for his support as always to get the most of the post and
make it shine! :)
https://royale.apache.org/binding-the-text-property-of-a-jewel-textinput-to-update-a-text-label/
Enjoy!
--
Carlos Rovira
http://about.me/carlosrovira
Hi Andrew,
I finish a new blog post. Can you please review it? This seems a bit more
dense than the others :)
https://royale.codeoscopic.com/binding-the-text-property-of-a-jewel-textinput-to-update-a-text-label/
Thanks in advance for your help
Carlos
--
Carlos Rovira
http://about.me
I’m not trying to prolong this discussion, but I couldn’t help commenting on
this: ;-)
> On Mar 16, 2018, at 6:38 AM, Alex Harui wrote:
>
> Span was an attempt to keep things from unintentionally wrapping, which I
> believe is the browser default.
This is possibly
il.com>
> wrote:
>
> Perhaps we can set display:inline-block for the span which renders the
> Label?
well.
> I thought changing Label from span to div was a simple change and not
> worthy of major discussion. It seems reasonable to specify x/y position,
> width, height, etc. on Label without changing the type (i.e. position:
> block). Either I’m not explaining myself well enough or we’re
Hi
my opinion is that Basic should be Basic, and so Label should be a span
If Label needs to be a div, that's a problem of other UI Set, maybe in
Jewel we can make it default to div
Just my 2
thanks
Carlos
2018-03-16 6:35 GMT+01:00 OmPrakash Muppirala <bigosma...@gmail.com>:
That’s what the current TextOverflow bead does. It only works on elements which
are display: block (which span is not by default).
IMO using div here is not PAYG, but I’m finished discussing this as well. I
thought changing Label from span to div was a simple change and not worthy of
major
omponent set which more
thinly
>> wraps HTML elements.
>>
>> I can’t think of any reason why Label would be better as a span than a
>> div. It seems to me that simply using div instead of span would make
Label
>> more versatile. Am I missing something?
>>
>
Alex, that may have been true for mx Label, but it is not the case for
Spark. In the end it does become relevant for 'migrating users' migrating
Flex 4/Spark apps.
I'm just pointing this out. I was confused/annoyed when I used it last year
expecting it to be similar to what I had been using
On 3/15/18, 8:47 PM, "Greg Dove" <greg.d...@gmail.com> wrote:
> Label is a single-line sequence of text.
>
>I think that is the statement that might be in the process of being
>indirectly debated.
>Is it documented as such?
Really? We're going to nitpick o
Label is a single-line sequence of text.
I think that is the statement that might be in the process of being
indirectly debated.
Is it documented as such?
On Fri, Mar 16, 2018 at 4:37 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:
> Because, this isn't an issue of performance.
If creating a div is more performant than creating a span, why insist on
using a span? How is that pay as you go?
Thanks,
Om
On Thu, Mar 15, 2018 at 5:19 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:
> A Flex Label, and any Flex component was a swiss-army knife of features
>
ense as part of the text value of a label and not as the basis
> for the representation of the Label itself - div seems closer to what I was
> used to with legacy Flex (which may no longer be the 'reference' for
> choosing an implementation).
> I don't think there is any semantic or othe
Observing from the sidelines, fwiw I agree with Harbs here. Span to me
makes more sense as part of the text value of a label and not as the basis
for the representation of the Label itself - div seems closer to what I was
used to with legacy Flex (which may no longer be the 'reference
I’m suggesting to change it because span does not fit the use case of Label.
Width and truncate are just two applications which indicate that span is not
the correct element. I’m pretty sure I had other edge cases which were likely
effected by the fact that Label is a span, although I’m
Label in Flex and Royale is not intended to have any children (other than
bold, italic and other text markup). Span represents that. Div does not.
You are suggesting changing to div JUST IN CASE someone needs to set a
width and/or truncate. Just-in-case code is not PAYG.
My 2 cents,
-Alex
And why not change IBeadView in Label for a view that uses a div when
needed? ;)
in the other cases, maintains the span
2018-03-15 21:05 GMT+01:00 Harbs <harbs.li...@gmail.com>:
> I’m still not understanding you. What about Label says it’s a span instead
> of a div? Why is mak
I’m still not understanding you. What about Label says it’s a span instead of a
div? Why is making it a div not PAYG? Span simply limits Label unnecessarily. I
think span is not the appropriate element for Label.
> A Label without width should grow to the size of its text. Isn't that
Have the truncation bead swap the span for div. Again, some component has
to put a span in the DOM. Label has been just fine for that so far.
A Label without width should grow to the size of its text. Isn't that how
it worked in Flex?
Maybe Label should be refactored to not have width/height
But we already have a truncation bead. The only reason it doesn’t work in Label
is because spans don’t have widths.
Label is not something which should flow beyond its bounds — which is what span
is useful for. I still don’t see why you think span makes more sense.
FWIW, div *is* used
w seconds
of looking at a Google web page, I did not see any divs with text as
children. I saw spans. The Divs all contained other elements.
I don't create HTML web pages for a living, but if I were to place a label
over a control like I often see in Flex, I would not wrap the label in a
Div. The
Why is span lighter than div?
Inline and nowrap is not specific to span. AFAICT, there’s nothing specific to
snap which fits Label better than div.
As far as components which “does” span: Besides Span in HTML, we have HTMLText
in Basic which encapsulates span.
I can revert the change I made
On 3/15/18, 5:34 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>Gotcha. FWIW, we now have the HTML element component set which more
>thinly wraps HTML elements.
>
>I can’t think of any reason why Label would be better as a span than a
>div. It seems to me that s
n?
>
>2018-03-15 13:34 GMT+01:00 Harbs <harbs.li...@gmail.com>:
>
>> Gotcha. FWIW, we now have the HTML element component set which more
>>thinly
>> wraps HTML elements.
>>
>> I can’t think of any reason why Label would be better as a span than a
>> div.
>
>> Gotcha. FWIW, we now have the HTML element component set which more thinly
>> wraps HTML elements.
>>
>> I can’t think of any reason why Label would be better as a span than a
>> div. It seems to me that simply using div instead of span would make Label
>> m
GMT+01:00 Harbs <harbs.li...@gmail.com>:
> Gotcha. FWIW, we now have the HTML element component set which more thinly
> wraps HTML elements.
>
> I can’t think of any reason why Label would be better as a span than a
> div. It seems to me that simply using div instead of span wo
Gotcha. FWIW, we now have the HTML element component set which more thinly
wraps HTML elements.
I can’t think of any reason why Label would be better as a span than a div. It
seems to me that simply using div instead of span would make Label more
versatile. Am I missing something?
> On Mar
s.com>
> AuthorDate: Mon Dec 4 21:18:50 2017 +0200
>
>Added Label
> ---
> .../HTML/src/main/resources/html-manifest.xml | 1 +
> .../org/apache/royale/html/elements/Label.as | 94 ++
> 2 files changed, 95 insertions(+)
>
> d
44 matches
Mail list logo