On 12/14/15, 9:01 AM, "Marcus Fritze" <marcus.fri...@googlemail.com> wrote:
>Yes, this works. Currently, it’s a little bit confusing for me to code in >flexJS. >Coding flexJS feels actually a little bit like HTML try and error. > >Maybe, I am using FlexSDK too long, but I don’t know exactly what >height=„100%“ in flexJS means. > >Correct me if I am wrong, but in FlexSDK / Flash it means the component >which has the >height=„100%“ property, takes the full height which is available in the >parent. > > >Why doesn’t work this in flexJS? Here I have to set the top / bottom / >margin and so on? >In my personal opinion this is a little step backwards in terms of „easy >coding“. > >Is it planned to fix this some day, or is this one of the disadvantages >we have to live with? A goal of FlexJS is to allow developers a choice of component sets. The most complete component set right now is the Basic component set. I chose to focus on that first because I wanted to create a component set that will be the smallest and fastest. So, it tries to do simple encapsulations of browser behavior. And thus in the Basic set, 100% width does what it would do in the browser which is different than what it does in the regular Flex SDK. Another reason I focused on this kind of component set was because some folks had said that the main value of their code base was in the ActionScript business logic and their Flex UIs were several years old and it might be time to upgrade the UI anyway. More recent feedback has led me to want to try to build out a more Spark-like component set, so folks don't have to spend as much time porting the UI and so that there are fewer behavior differences from the Flex SDK. So I will probably start on that in a week or two and volunteers are welcome to help. I predict that this component set will be bigger and slower. It almost has to be, because instead of just telling the browser to add a div with 100%, we'll have to write code to override browser behavior and loop through all the children twice, once to measure to see how much room is left over, and another to layout at final sizes. And then you'll be able to choose between doing more porting work to get a smaller faster app, or doing less and paying the price. Anyway, thanks for continuing to try out FlexJS. We appreciate the feedback, and if you can help by contributing patches that's even better. Thanks, -Alex
