AIUI, the issue is how it is possible, if at all, to use position:absolute or
position:relative selectively in the DOM. IIRC, it isn't a matter of creating
a descendant selector for the object you want to position, it is setting the
position style on all of its parents without affecting any
Not disagreeing with anything you write here…
FWIW, I was thinking of adding a “constrainment” bead which would allow
left/right/top/bottom values. This would likely work in the context of other
layouts and be applied to components directly.
> On Jun 11, 2018, at 6:43 PM, Alex Harui wrote:
>
IMO, regarding layouts, there will be many kinds of layouts. In Royale we want
to give people choices.
-The emulation component sets will mimic Flex layout behavior where % is
calculated on available space. I'm pretty sure these will use absolute
positioning and never set element.style.width
Hi Harbs,
I just check it and all seems to work ok :)
2018-06-11 13:30 GMT+02:00 Carlos Rovira :
>
>
> 2018-06-11 13:26 GMT+02:00 Harbs :
>
>> I changed toString() to be a pointer to readUTFBytes.
>>
>
> ok, I'll check if it works for UID generation as I can
>
>
>>
>> Uint16Array will not work
2018-06-11 13:26 GMT+02:00 Harbs :
> I changed toString() to be a pointer to readUTFBytes.
>
ok, I'll check if it works for UID generation as I can
>
> Uint16Array will not work for UTF8. It might work for UTF16. Not sure. It
> might be interesting to see if the String.fromCharCode.apply
I think Yishay is on track. I'm still changing my mind on how things are on
html, different to flex.
For example, in flexbox there's no gap number, but the layout knows it
should be gap between elements (with "space-between").
So Flexbox put the space, how many? that depends on parent sizes...to
Hi Harbs,
see my fix, and if you think is not ok, feel free to update as you think.
Then I can try AMF generation of UID and see if it continues working right
ok?
I think with my latest commit I revert to how this was working...if I'm not
missing something
thanks
2018-06-11 13:14 GMT+02:00
Hi, just committed a solution that does the same done in "readUTFBytes" on
line 985
Let me know if this solves the issue
2018-06-11 13:07 GMT+02:00 Carlos Rovira :
> Hi,
>
> no problem, we can go back to how it was that line before. I changed it be
> have the same in all that class, but wasn't
Why do you need toString rather than readUTFBytes()? FWIW, readUTFBytes()
already falls back to TextDecoder when available.
> On Jun 11, 2018, at 2:07 PM, Carlos Rovira wrote:
>
> Hi,
>
> no problem, we can go back to how it was that line before. I changed it be
> have the same in all that
Hi,
no problem, we can go back to how it was that line before. I changed it be
have the same in all that class, but wasn't aware of that problem.
So I'll change to what we had, and make to String do the same. I think it
should work the same and as well work on IE/Edge
I'll take a look right now
The problem is that the child does not have a way of knowing what the extra
space surrounding the parent (such as padding) will be.
One day, I’m probably going to work on a constrained layout…
> On Jun 11, 2018, at 1:20 PM, Yishay Weiss wrote:
>
> I guess we’re a bit prejudiced coming from
I guess we’re a bit prejudiced coming from Flex. Once you let go of the notion
that percentages are not of the available space but of the total parent space,
it sort of makes sense.
From: Harbs
Sent: Monday, June 11, 2018 11:29:38 AM
To: dev@royale.apache.org
I think is important that we reach the most simple and cross browser way to
get things work. At least Royale should be able to make all most used
layouts
only declaring containers and layouts in its simplest forms. Then people
that want to make some not conventional things could need to make some
FWIW, I always check web API support in MDN and caniuse.com before using them
in Royale.
Some more details win this specific issue:
It looks like you added toString() to BinaryData and changed UIDUtils to use
that.
I don’t think a toString method in BinaryData makes sense. Flash was very
Carols,
This breaks our app on IE and Edge, as they don’t support TextDecoder. Can you
fix this?
From: carlosrov...@apache.org
Sent: Sunday, May 27, 2018 11:29:14 PM
To: comm...@royale.apache.org
Subject: [royale-asjs] branch develop updated: fix latest
FWIW, I’ve found that the single-most painful part of developing using Royale
has been layouts.
I *think* defaulting to relative might help some issues, but things like
percentages simply don’t work as you’d expect in HTML. I have been forced to
stick calc() css in at least 12 places in my
Hi,
I'm finding some problems with all this in Jewel as I go deeper with
layouts. I'll write about it soon, I hope to solve some issue and left most
important to discuss.
As I get something working, I see a collateral effect that makes other
thing that was working fail on some way...it's like a
We could always have a bead which sets:
.foo *{
position: static;
}
To reset the defaults of all elements below “foo” to static.
Of course to change it to something else, you’d need:
.foo .baz{
position: absolute;
}
I’m not sure how well this would work with the Jewel layout beads. I’m
Alex,
I will suggest them for sure to subscribe. Maybe they are doing it already!
In the other words I should look closer to those errors in the code.
Thanks,
Piotr
pon., 11 cze 2018 o 08:09 Alex Harui napisał(a):
> Hi Piotr,
>
> Chris and Scott should just subscribe to dev@ and/or users@
The emulation Application is based on Container and thus creates a Div. It may
not stay that way, but we did it so that the SystemManager can parent the app
like it does in Flex.
Feel free to commit the bead. It won't hurt anything and some folks will be
able to use it. I'm still wondering
Hi Piotr,
Chris and Scott should just subscribe to dev@ and/or users@ and ask their
questions directly.
The compiler errors might be hiding some APIs from the report, plus we want the
Royale Compiler to be able to compile existing Flex code, so we should see what
the source code looks like
21 matches
Mail list logo
