[FlexJS] FlexJS Wiki Update

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[FlexJS] FlexJS Wiki Update

Peter Ent
Hi,

I've added a new page to the FlexJS Wiki[1] and updated a few other pages to reflect the changes I've made over the last couple of weeks.

—peter

[1] https://cwiki.apache.org/confluence/display/FLEX/FlexJS+Container+Classes+and+Layouts



Reply | Threaded
Open this post in threaded view
|

Re: [FlexJS] FlexJS Wiki Update

piotrz
Hi Peter,

Nice job! I think it is really worth put this link with some infor on twitter and facebook. It's really useful and I bet that people will ask.

Thank you,
Piotr
Reply | Threaded
Open this post in threaded view
|

Re: [FlexJS] FlexJS Wiki Update

Olaf Krueger
In reply to this post by Peter Ent
Hi Peter,
thanks for this!
I probably not yet understand the whole story but it's a great entry point.

Would be great if you could answer some questions that come to my mind:

1)
Group vs Container:
Does it mean that if we need a scrollable container and would like to target HTML only it's recommended to use Group instead of Container and if we'd like to target Flash and HTML we always have to use Container?

2)
Does it make sense to introduce HGroup and VGroup as Express beads?

3)
There are two implementations of e.g. HorizontalLayout (Basic and HTML):
- frameworks/projects/Basic/src/main/flex/org/apache/flex/html/beads/layouts/HorizontalLayout.as [1]
- frameworks/projects/HTML/src/main/flex/org/apache/flex/html/beads/layouts/HorizontalLayout.as [2]

What is the difference and when we have to use the one or the other?

4)
Could we compose/use the container and layout classes with any FlexJS component set, including MDL?

Thank you!

Olaf


[1]
https://github.com/apache/flex-asjs/blob/develop/frameworks/projects/Basic/src/main/flex/org/apache/flex/html/beads/layouts/HorizontalLayout.as

[2]
https://github.com/apache/flex-asjs/blob/develop/frameworks/projects/HTML/src/main/flex/org/apache/flex/html/beads/layouts/HorizontalLayout.as
Reply | Threaded
Open this post in threaded view
|

Re: [FlexJS] FlexJS Wiki Update

Peter Ent
Hi,

I've placed my answers in-line.

On 4/24/17, 4:17 AM, "OK" <[hidden email]> wrote:

>Hi Peter,
>thanks for this!
>I probably not yet understand the whole story but it's a great entry
>point.
>
>Would be great if you could answer some questions that come to my mind:
>
>1)
>Group vs Container:
>Does it mean that if we need a scrollable container and would like to
>target
>HTML only it's recommended to use Group instead of Container and if we'd
>like to target Flash and HTML we always have to use Container?

If you are targeting HTML only, then you can use Group and just add
overflow:auto to its style and you will have scrolling. If you use
Container with a ScrollingViewport it will do the exact same thing; all
ScrollingView does on the HTML side is add overflow:auto to the DIV's
style.
>
>2)
>Does it make sense to introduce HGroup and VGroup as Express beads?

I think it does make sense to do that.

>
>3)
>There are two implementations of e.g. HorizontalLayout (Basic and HTML):
>-
>frameworks/projects/Basic/src/main/flex/org/apache/flex/html/beads/layouts
>/HorizontalLayout.as
>[1]
>-
>frameworks/projects/HTML/src/main/flex/org/apache/flex/html/beads/layouts/
>HorizontalLayout.as
>[2]
>
>What is the difference and when we have to use the one or the other?

I have been ignoring Basic project for now. We should discuss what is to
become of it. Personally, I would keep the HTML-specific components in the
HTML project and move the others into Basic, replacing what's already
there. But I'm not sure how safe or practical that is right now. I believe
we should resolve this for the Flex 0.8 release.

The HorizontalLayout in the Basic project is completely incompatible with
the HTML version. The protocols for ILayoutHost etc have been changed. The
layout algorithm is probably close to identical, however.
>
>4)
>Could we compose/use the container and layout classes with any FlexJS
>component set, including MDL?

A number of the MDL "container" classes are based on the HTML Group (I
don't think any use Container since, for reason #1 above, it isn't useful
to HTML-only code). It is probably safe to mix them, but I am not an MDL
expert and I do not know the ramifications of doing that.

>
>Thank you!
>
>Olaf
>
>
>[1]
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2Fapache%2Fflex-asjs%2Fblob%2Fdevelop%2Fframeworks%2Fprojects%2FBasic%2F
>src%2Fmain%2Fflex%2Forg%2Fapache%2Fflex%2Fhtml%2Fbeads%2Flayouts%2FHorizon
>talLayout.as&data=02%7C01%7C%7C6ef80b5dc46a4c66852008d48aec69e8%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636286195376443487&sdata=BBvguzdClc1PuV
>V0LUIgAeyTZznmTG%2FCYxA38EA3vag%3D&reserved=0
>
>[2]
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
>m%2Fapache%2Fflex-asjs%2Fblob%2Fdevelop%2Fframeworks%2Fprojects%2FHTML%2Fs
>rc%2Fmain%2Fflex%2Forg%2Fapache%2Fflex%2Fhtml%2Fbeads%2Flayouts%2FHorizont
>alLayout.as&data=02%7C01%7C%7C6ef80b5dc46a4c66852008d48aec69e8%7Cfa7b1b5a7
>b34438794aed2c178decee1%7C0%7C0%7C636286195376443487&sdata=0ZXB5qAlXETXae9
>Zlpj74bn0D1Qdvb4ce%2FevosJgmzI%3D&reserved=0
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.2333347.n4.nabble.com%2FFlexJS-FlexJS-Wiki-Update-tp61292p61
>304.html&data=02%7C01%7C%7C6ef80b5dc46a4c66852008d48aec69e8%7Cfa7b1b5a7b34
>438794aed2c178decee1%7C0%7C0%7C636286195376443487&sdata=k7rIxjyzhY1inSIdkR
>IZwN5lh1fcqVnyUV7jneJQ%2BNY%3D&reserved=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Reply | Threaded
Open this post in threaded view
|

Re: [FlexJS] FlexJS Wiki Update

yishayw
Peter Ent wrote
>4)
>Could we compose/use the container and layout classes with any FlexJS
>component set, including MDL?

A number of the MDL "container" classes are based on the HTML Group (I
don't think any use Container since, for reason #1 above, it isn't useful
to HTML-only code). It is probably safe to mix them, but I am not an MDL
expert and I do not know the ramifications of doing that.
We've been wrapping mdl elements in DIV fexjs components to integrate them in layouts. Hope that still works...
Reply | Threaded
Open this post in threaded view
|

Re: [FlexJS] FlexJS Wiki Update

Peter Ent
I've run MDLExample and it looks like to works to me. Give it a run with
the latest from develop branch and let us know. I tried to make sure the
MDL project was updated to reflect the changes I made to the Core and HTML
projects.

‹peter

On 4/24/17, 8:25 AM, "yishayw" <[hidden email]> wrote:

>Peter Ent wrote
>>>4)
>>>Could we compose/use the container and layout classes with any FlexJS
>>>component set, including MDL?
>>
>> A number of the MDL "container" classes are based on the HTML Group (I
>> don't think any use Container since, for reason #1 above, it isn't
>>useful
>> to HTML-only code). It is probably safe to mix them, but I am not an MDL
>> expert and I do not know the ramifications of doing that.
>
>We've been wrapping mdl elements in DIV fexjs components to integrate them
>in layouts. Hope that still works...
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.2333347.n4.nabble.com%2FFlexJS-FlexJS-Wiki-Update-tp61292p61
>307.html&data=02%7C01%7C%7Cb1eb1f5332c24bcca97b08d48b0e8a09%7Cfa7b1b5a7b34
>438794aed2c178decee1%7C0%7C0%7C636286341942886874&sdata=HokbLXfdHwUh0cJIsn
>EFqddxh9G0xPYX24%2BS9IosZUE%3D&reserved=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Reply | Threaded
Open this post in threaded view
|

Re: [FlexJS] FlexJS Wiki Update

Olaf Krueger
Thanks Peter!

>I have been ignoring Basic project for now. We should discuss what is to
>become of it. Personally, I would keep the HTML-specific components in the
>HTML project and move the others into Basic, replacing what's already
>there.

From an app developer perspective, I also would expect only pure HTML components from an HTML package which on JS side are equivalent to the regular HTML components including its 'browser built-in features/API'.

Just my 2 cents,
Olaf