>>
>>>>>> I personally prefer having Bead for such things.
>>>>>>
>>>>>> 2018-02-08 14:01 GMT+01:00 Yishay Weiss >>>>> <mailto:yishayj...@hotmail.com>>:
>>>>>>
>>>>>>> I agree, that’s
,
>> >>otherwise
>> >> > use the default which is more performance oriented.
>> >> >
>> >> > Another option is to just use a utility function for calculating
>>that
>> >> > actual screen position when necessary. The uti
tual screen position when necessary. The util function can get the
> >> > element using (component as IRenderedObject).element and then do
> >>whatever
> >> > DOM/flash/wasm queries you need.
> >> >
> >> > From: Carlos Rovira<mailto:carlosro
reen position when necessary. The util function can get the
>> > element using (component as IRenderedObject).element and then do
>>whatever
>> > DOM/flash/wasm queries you need.
>> >
>> > From: Carlos Rovira<mailto:carlosrov...@apache.org>
>>
mailto:carlosrov...@apache.org>
> > Sent: Thursday, February 8, 2018 12:33 PM
> > To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> > Subject: Re: What is x and y? What is width and height?
> >
> > I don't have right now a proposal for this, but it
ent and then do whatever
> DOM/flash/wasm queries you need.
>
> From: Carlos Rovira<mailto:carlosrov...@apache.org>
> Sent: Thursday, February 8, 2018 12:33 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: What is x and y? What is width and heigh
ursday, February 8, 2018 12:33 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: What is x and y? What is width and height?
I don't have right now a proposal for this, but it seems to me that
introduce calculations that affects performance will be a bad idea. That
February 7, 2018 6:24 PM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: What is x and y? What is width and height?
>
> FWIW, I do think we need a “constrained layout” which places *everything*
> absolutely and does not rely on browser layout. If that layout wer
.
From: Gabe Harbs<mailto:harbs.li...@gmail.com>
Sent: Wednesday, February 7, 2018 6:24 PM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: What is x and y? What is width and height?
FWIW, I do think we need a “constrained layout” which places *everything*
absolut
Hmm. Maybe we need to understand the circumstances. It makes no sense to
me to have x,y return useless values just because it is easy or fast to
do. The main point is that in the HTML/JS/CSS world there is no x,y
values so we can make them do anything we want, but do we want it to work
like Flex
Can you post into the separate thread if it's even possible any of those
case ?
2018-02-07 17:36 GMT+01:00 Gabe Harbs :
> Yes. Flexbox solves a lot of problems, and I use the “flex” layouts pretty
> extensively.
>
> However, I have run into lots of cases which are hard to solve and the old
> Flex
Yes. Flexbox solves a lot of problems, and I use the “flex” layouts pretty
extensively.
However, I have run into lots of cases which are hard to solve and the old
Flex-style layouts would have been helpful.
> On Feb 7, 2018, at 6:34 PM, Piotr Zarzycki wrote:
>
> Lately I had huge exercises wi
Lately I had huge exercises with FlexBox mechanism and it is finally
something. I have never seen better working things in HTML than this. If I
wanted to make elements on the right they are really displays on the right.
- Without FlexBox I would be nowhere.
Maybe it is not the answer for the const
FWIW, I do think we need a “constrained layout” which places *everything*
absolutely and does not rely on browser layout. If that layout were to be used,
the bounding box values would be correct.
> On Feb 7, 2018, at 6:00 PM, Peter Ent wrote:
>
> I think I agree with Harbs about x,y,width,heig
I think I agree with Harbs about x,y,width,height just returning the set
values if the calculation would be expensive. I wonder what the
circumstances are that we actually need to have precise values in
calculations. For example, if I wanted to make a circulate layout, how
would I go about doing th
The offset values are very expensive.
They are also not completely accurate. I’ve found it’s difficult to get
accurate values where SVG and transforms are in play.
I would suggest that x,y,widht and height should reflect *set* values even if
they are not always the actual ones.
For cases where
16 matches
Mail list logo
