Hi, I always say that MDL should be treated as a separate case. Take into
account that MDL use to have its own examples and ways to make things and
that doesn't has nothing to do with our layouts.
just my 2 cents :)
2017-05-05 21:51 GMT+02:00 piotrz :
> I will try to look into that deeply and pr
I will try to look into that deeply and probably will go through this path in
MDL.
Thanks Peter!
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Layouts-tp61120p61505.html
Sent from the Apache Flex Dev
Well, the LayoutBase assume's the host/strand implements ILayoutParent and
provides the ILayoutHost. The ILayoutHost then provides the ILayoutView.
These can all be the same thing.
The layouts in Basic assume the items being laid out are ILayoutChild
compliant. So if MDL components followed that p
Well maybe that's not bad idea - to make similar set of layouts, but, what
would be the difference ?
In general MDL should be like our Basic set of components, should be able to
use such beads.
Maybe I should implement to the containers View parts and move there
appropriate logic. - In that case
Maybe MDL should have its own set of layouts and layout-compliant
interfaces. Opinions?
‹peter
On 5/5/17, 2:15 AM, "piotrz" wrote:
>Hi Peter,
>
>I have found one scenario where there is a null pointer exception, but I'm
>not sure whether even we should cover such case. Let me know what do you
>t
Hi Peter,
I have found one scenario where there is a null pointer exception, but I'm
not sure whether even we should cover such case. Let me know what do you
think.
If I have in MDL Grid with GridCell and I add to it HorizontalFlexLayout
bead [1] I will get NPE [2], cause GridCell do not have Vie
Hi,
I've just pushed an update to flex-asjs develop branch with
AbsolutePositioningViewBeadBase as described below. This should make it
much easier to build control component which do not need to use layout
beads and can handle resizing events on their own.
—peter
On 4/26/17, 9:05 AM, "Peter Ent
Let's do this then, after the merge of dual into develop:
AbsolutePositioningViewBeadBase will be the view bead to use for controls.
On the HTML platform, this bead will set its strand's style position to
"relative" if it is not set to either "absolute" or "relative" already. In
addition, this bea
On 4/25/17, 12:35 PM, "Peter Ent" wrote:
>Perhaps I am not understanding this.
>
>You create a control component extending UIBase. You create your view bead
>extending AbsolutePositioningViewBase. This bead makes sure that the
>strand/host has position:relative set.
>
>So how do you set positio
Perhaps I am not understanding this.
You create a control component extending UIBase. You create your view bead
extending AbsolutePositioningViewBase. This bead makes sure that the
strand/host has position:relative set.
So how do you set position:absolute on each of the control's parts?
Setting p
If AbsolutePositioningViewBase is for creating controls it sounds like a good
idea. Answers my previous post.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Layouts-tp61120p61341.html
Sent from the Apache Flex Development mailing list archive at Nab
On 4/25/17, 10:55 AM, "yishayw" wrote:
>App devs may want to write custom controls and would expect flash and js
>behaviour to be the same. I think we should strive to eliminate use of
>conditional compilation for app devs. If that's so we don't want them
>changing an HTML only style (position)
App devs may want to write custom controls and would expect flash and js
behaviour to be the same. I think we should strive to eliminate use of
conditional compilation for app devs. If that's so we don't want them
changing an HTML only style (position).
--
View this message in context:
http://a
More thinking on this.
Some Containers have both assignable children and assignable layout, where
"assignable" means the application developer gets to decide on the
children and layout.
Controls should not have assignable children, but may have assignable
layout. List, DataGrid can have differen
IMO, in FlexJS we want to make a distinction between Containers and
Controls.
Containers can contain arbitrary sets of children determined by the app
logic and have a layout. I'm still leaning towards renaming Group to
Container and make Container be called something like
ContainerWithViewport, b
The x and y properties in Flash are always relative to their parent
container. The browser world is, well I'll just say "complex" and leave it
at that.
If you do position:relative then x (left) and y (top) become positions
relative to the nearest element in the "flow" the browser lays down. That
i
Peter Ent wrote
> I first encourage you to base any new components on Group and then add in
> BasicLayout. Nothing will happen until you dispatch a layout needed event.
> You should be able to add multiple children and then dispatch the event.
That's what I'm doing right now.
> We could also mak
This is still a little bit of a conundrum. Automatically setting
position:absolute when setting x and y (effectively left and top styles)
runs into several problems as you can imagine.
One issue is that you have to make sure the parent container's position is
either relative or absolute, otherwise
Also, what if I'm adding elements to a UIBase (no layout)? Shouldn't I be
able to set the absolute x and y on the added element?
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-Layouts-tp61120p61330.html
Sent from the Apache Flex Development mailing
After having another look, BasicLayout loops over its children and sets their
positions to absolute. The problem with that is it requires a
dispatchEvent('layoutNeeded') every time I add an item, which is expensive.
--
View this message in context:
http://apache-flex-development.247.n4.nabb
Hi Peter,
I noticed setting UIBase.x no longer changes positioning to absolute. This
probably makes sense because it was a strong side effect which could be
counter-intuitive, but what's the method for setting items absolutely now? I
searched the code base but couldn't find anywhere position in se
The merge is complete. Alex is doing something big too but I am done.
We should put together a task list for a proper release. I think some
renaming/refacotoring is in order as well as documentation.
Peter
> On Apr 15, 2017, at 12:43 PM, piotrz wrote:
>
> Hi Peter,
>
> I'm following and c
Hi Peter,
I'm following and constantly checking your changes in this branch. It look
good. Do you think that is the last big changes in framework Api?
Do you plan merge it to develop next week?
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
h
Hi,
I have merged the feature/layout branch with develop. I will check the
build periodically over the weekend and fix anything if I see it has
broken because I my commit/push.
I still have to get MobileTrader example to run completely. It now looks
OK, just doesn't fully work. Once I get that do
24 matches
Mail list logo
