Re: What is x and y? What is width and height?

In most cases we do output the most basic code. But let's look at one scenario I expect to run into more than once, which is placing a popup somewhere. Like I said, in most of our code, we rarely read back x and y. I don't even think we read x and y in an absolute positioning container. But I

Re: What is x and y? What is width and height?

Hi Alex, in this case it's hard to prove this will be a problem. Maybe the apps will suffer it very slightly for most people to perceive it, but that's not the problem. The problem is our solution will have additional calculations *always* that other frameworks doesn't have. And that's goes

Re: What is x and y? What is width and height?

I would much rather we decide on an implementation. It makes documentation much easier. I'm all for options, but making fundamental things like geometry have options seems like it would make Royale seem more complex. I would not worry about performance until it actually proves to be a problem.

Re: What is x and y? What is width and height?

Seems more reasonable, since its optional and people wanting it can include... 2018-02-08 14:04 GMT+01:00 Piotr Zarzycki : > I personally prefer having Bead for such things. > > 2018-02-08 14:01 GMT+01:00 Yishay Weiss : > > > I agree, that’s why

Re: What is x and y? What is width and height?

I personally prefer having Bead for such things. 2018-02-08 14:01 GMT+01:00 Yishay Weiss : > I agree, that’s why I’m proposing to have a bead do the calculation. If > you care about integrity with actual position on the screen and are willing > to sacrifice some

RE: What is x and y? What is width and height?

I agree, that’s why I’m proposing to have a bead do the calculation. If you care about integrity with actual position on the screen and are willing to sacrifice some performance use ScreenPositionCalculatorBead, otherwise use the default which is more performance oriented. Another option is to

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 will make us not elegible for some escenarios/people. On e of the things I like from Royale is that in the end we are outputting the most easy code while we

RE: What is x and y? What is width and height?

How about using beads that implement IPositionCalculator. UIBase won’t return x and y directly but use a bead to calculate them. The default SimplePositionCalculatorBead would return x and y based on the setter while the ScreenPositionCalculatorBead would return the values based on DOM access.

Re: What is x and y? What is width and height?

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

Re: What is x and y? What is width and height?

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

Re: What is x and y? What is width and height?

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: > >

Re: What is x and y? What is width and height?

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

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 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

Re: What is x and y? What is width and height?

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

Re: What is x and y? What is width and height?

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