Re: [FlexJS] Layout of NumericStepper is broken

I found the problem: the NumericStepper's sizeChange handler was not being called when the NS appears in this simpler test case. It is being called when it is displayed in the FlexJSStore, for example. The more complex app with nested containers and layouts is setting the right conditions so the si

Re: [FlexJS] Layout of NumericStepper is broken

OK, thanks. I'm looking at this now (as soon as my sync of Alex's changes completes). ‹peter On 6/6/17, 3:17 AM, "piotrz" wrote: >Peter, > >I just raised jira -> >https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.ap >ache.org%2Fjira%2Fbrowse%2FFLEX-35322&data=02%7C01%7C%7Ca

Re: [FlexJS] Layout of NumericStepper is broken

Peter, I just raised jira -> https://issues.apache.org/jira/browse/FLEX-35322 Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Layout-of-NumericStepper-is-broken-tp62108p62149.html Sent from

Re: [FlexJS] Layout of NumericStepper is broken

Run the FlexJSStore example and go to the Products tab. NumericStepper looks fine to me there. -Alex On 6/5/17, 7:49 AM, "piotrz" wrote: >Hi Peter, > >It is Windows 10 and Chrome 59.0.3071.82 >I tried also on Firefox: 53.0.3 (32 bits) > >Piotr > > > >- >Apache Flex PMC >piotrzarzyck...@gma

Re: [FlexJS] Layout of NumericStepper is broken

Hi Peter, It is Windows 10 and Chrome 59.0.3071.82 I tried also on Firefox: 53.0.3 (32 bits) Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Layout-of-NumericStepper-is-broken-tp62108p62110

Re: [FlexJS] Layout of NumericStepper is broken

I'm looking into it. The SWF and JS versions are different. There's a border around it, which is specified in the defaults.css. I'm not sure why that is there; maybe I put it there awhile ago I just don't remember. It looks better without it. The SWF version, for me, has some extra graphics in the

[FlexJS] Layout of NumericStepper is broken

Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Layout-of-NumericStepper-is-broken-tp62108.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layout Issue/Change

On 5/2/17, 5:54 AM, "Peter Ent" wrote: >Plus, there is no provision in the base layout for watching for new >children or removed children. In the PAYG world, those feature would be >part of other layouts: > >HorizontalLayoutWatchForAddChild >HorizontalLayoutWatchForRemoveChild >HorizontalLayoutW

Re: [FlexJS] Layout Issue/Change

I'm trying to find the balance between PAYG and mimicking the HTML/JS/CSS side on the SWF side. Take HorizontalLayout for example. On the JS side, this layout waits for "childrenAdded" and then changes each child's display style to "inline-block". If you then programmatically change one child's wi

Re: [FlexJS] Layout Issue/Change

-development.247.n4.nabble.com/FlexJS-Layout-Issue-Change-tp61440p61459.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layout Issue/Change

Without having looked at every layout, it does make sense to me that LayoutBase should not need to watch children for size changes on the JS side. That's because the browser already has installed those listeners and will re-calculate the layout as needed. The SWF-side will continue to need to wat

Re: [FlexJS] Layout Issue/Change

The current listeners in LayoutBase (Basic Project) are for the children of a component. Right now, if you have a Group with 10 buttons and VerticalLayout, and you resize one of those buttons, LayoutBase/VerticalLayout will detect that and automatically re-run the VerticalLayout algorithm. What I

Re: [FlexJS] Layout Issue/Change

il.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Layout-Issue-Change-tp61440p61442.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] Layout Issue/Change

Hi, My main goal of the recent set of changes to containers and layouts was to make the HTML/CSS/JS side as minimal as possible, letting the browser and friends take care of things as much as possible. For the most part, I think it works. But there is an issue that has been bothering me. Righ

Re: [FlexJS]Layout redux

On 2/25/17, 6:33 AM, "Peter Ent" wrote: >Maybe we need a big refactor. Things like effects are pretty advanced and >maybe they should get coupled with more advanced/complex layouts that are >in a different package than HTML. Well, I don't know how to define "big", but we do need to get it righ

Re: [FlexJS]Layout redux

Maybe we need a big refactor. Things like effects are pretty advanced and maybe they should get coupled with more advanced/complex layouts that are in a different package than HTML. The basic packages could be simpler layouts that do minimal settings. The HTML package could be JS only and just

Re: [FlexJS]Layout redux

On 2/24/17, 10:37 PM, "Yishay Weiss" wrote: >One more thing to consider is how effects will fit in here. I can imagine >scenarios where items inside of a container need to have an effect >applied to them. Currently, the move effect relies on changing x, y >values, which implies absolute positio

RE: [FlexJS]Layout redux

Subject: Re: [FlexJS]Layout redux Hi, I've pushed an update to the HorizontalFlexLayout and VerticalFlexLayout that adds code for the SWF side. In general, the SWF and JS sides look the same. There are some differences which I'm working on, but these should be usable. In doing th

Re: [FlexJS]Layout redux

On 2/24/17, 11:42 AM, "Peter Ent" wrote: >Hi, > >I've pushed an update to the HorizontalFlexLayout and VerticalFlexLayout >that adds code for the SWF side. In general, the SWF and JS sides look the >same. There are some differences which I'm working on, but these should be >usable. Sounds pro

Re: [FlexJS]Layout redux

Hi, I've pushed an update to the HorizontalFlexLayout and VerticalFlexLayout that adds code for the SWF side. In general, the SWF and JS sides look the same. There are some differences which I'm working on, but these should be usable. In doing this I've uncovered some incomplete work and/or expo

Re: [FlexJS]Layout redux

On 2/23/17, 1:54 AM, "Alex Harui" wrote: >A few comments/questions: > >What does flex-box do when it runs out of room? Doesn't it wrap to a new >row/column? Or can that be controlled? I think most folks expect >VerticalLayout to not create a new column but to keep going vertically and >be cl

Re: [FlexJS]Layout redux

I just checked. I have 24 classes with position: absolute and 16 classes with position: relative in a responsive app we use for PrintUI. The default for the app is absolute. It also has three media queries to set the percentage size of the main (relative) sections for responsive layout. It also

Re: [FlexJS]Layout redux

A few comments/questions: What does flex-box do when it runs out of room? Doesn't it wrap to a new row/column? Or can that be controlled? I think most folks expect VerticalLayout to not create a new column but to keep going vertically and be clipped or scrolled. On the SWF side, I am hopefully

Re: [FlexJS]Layout redux

Great. Thanks. I will take a look at these tomorrow. ‹peter On 2/22/17, 5:19 PM, "Harbs" wrote: >This too: >https://philipwalton.github.io/solved-by-flexbox/ > >> On Feb 23, 2017, at 12:16 AM, Harbs wrote: >> >> BTW, this might be useful: >> https://github.com/philipwalton/flexbugs >>

Re: [FlexJS]Layout redux

First, I like the idea of moving as much into CSS as possible, at least to the extent we can support in on the SWF side. Secondly, I think the layouts setting the display makes sense in this case, based on what Harbs said. I was thinking of this: A. UIBase does not set position and display. The

Re: [FlexJS]Layout redux

This too: https://philipwalton.github.io/solved-by-flexbox/ > On Feb 23, 2017, at 12:16 AM, Harbs wrote: > > BTW, this might be useful: > https://github.com/philipwalton/flexbugs > > >> On Feb 23, 2017, at 12:08 AM, Harbs >

Re: [FlexJS]Layout redux

BTW, this might be useful: https://github.com/philipwalton/flexbugs > On Feb 23, 2017, at 12:08 AM, Harbs wrote: > > How well do these work in IE? > > It looks like Flexbox is not supported at all in IE prior to IE10 and even in > IE10 and 11, it only has buggy support.[1] > > [1]http://caniu

Re: [FlexJS]Layout redux

For that to work, the bead will need to append the class name of the component. It cannot be applied to the bead itself. Harbs > On Feb 23, 2017, at 12:05 AM, Carlos Rovira > wrote: > > Hi Peter, > > one of the things I'd want to do is remove "styles" in source code and move > to css. > For

Re: [FlexJS]Layout redux

How well do these work in IE? It looks like Flexbox is not supported at all in IE prior to IE10 and even in IE10 and 11, it only has buggy support.[1] [1]http://caniuse.com/#feat=flexbox > On Feb 22, 2017, at 11:40 PM, Peter Ent wrote: > > I just pushed new layouts: VerticalFlexLayout and Hor

Re: [FlexJS]Layout redux

Hi Peter, one of the things I'd want to do is remove "styles" in source code and move to css. For example: viewBead.contentView.element.style["display"] = "flex"; What do you think about to move this to default.css class, i.e.: HorizontalFlexLayout { display: flex; ... } I think we should m

Re: [FlexJS]Layout redux

I totally agree with this. There should be a simple Container (with H and V variants) and a separate ChromeContainer. The vast majority of Containers do not need the extra div. Moving Panel to Express is an option, but I’m not sure it’s necessary. > On Feb 22, 2017, at 11:40 PM, Peter Ent wrot

Re: [FlexJS]Layout redux

Hi Peter, although I still not look into the code, that seems very promising. As you say we need a component with just one div, and then we could have more of then for chrome and other things. in old Flex Group was a container that doesn't have the width of subitems into account, so maybe the Flex

Re: [FlexJS]Layout redux

Hi, I just pushed new layouts: VerticalFlexLayout and HorizontalFlexLayout as well as a change to DataBindingExample to use them. I consider these temporary and would like to make them be the VerticalLayout and HorizontalLayout in the near future. If you look at their code you will see the COMPIL

Re: [FlexJS]Layout redux

Hi Peter, that sound very good :) thanks! 2017-02-22 16:53 GMT+01:00 Peter Ent : > That's a good strategy. My experiments this morning look like Flexbox is > the way to go. Its widely supported now and seems pretty easy to use. > > I'm going to create VerticalFlexLayout and HorizontalFlexLayout a

Re: [FlexJS]Layout redux

That's a good strategy. My experiments this morning look like Flexbox is the way to go. Its widely supported now and seems pretty easy to use. I'm going to create VerticalFlexLayout and HorizontalFlexLayout and have them extend the current versions just so the SWF side stays the same for right now

Re: [FlexJS]Layout redux

That looks very promising Peter. Look forward to see some progress :) If flexbox is the future, I think we should always look to go with that specs, and in case that still is not in some browsers, search for a polyfill that could do the job for not supported browsers for now. At the end browsers wi

Re: [FlexJS]Layout redux

I'm going to try some experiments in my own space. Basically, figuring out the best way to do simple layouts using CSS - vertical and horizontal with alignment options (center, left, right for vertical, top, middle, bottom for horizontal). Because alignment will probably require more cycles when im

Re: [FlexJS]Layout redux

> On Feb 22, 2017, at 9:46 AM, Alex Harui wrote: > > It is probably time for our annual "revisiting of the layout code". I > think if you look at source code history, Peter or I do this every so > often as we get more examples to work with. > > From memory, there are issues like whether we hav

Re: [FlexJS]Layout redux

using absolute positioning? It would have the benefit of being easier to maintain, as bugs would probably appear in both versions and fixed together. There can also be more code reused across implementations. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJ

Re: [FlexJS]Layout redux

It is probably time for our annual "revisiting of the layout code". I think if you look at source code history, Peter or I do this every so often as we get more examples to work with. From memory, there are issues like whether we have to set position:relative or not that came out of the MDL swc.

Re: [FlexJS]Layout redux

+1 for that. Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Layout-redux-tp59725p59736.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS]Layout redux

Hi, > Yishay just mentioned the fact that padding is not working It not working for me either - see https://issues.apache.org/jira/browse/FLEX-35274 > This seems totally wrong. Why is the padding being added when we’re using > box-sizing: border-box? Also seems wrong to me. > 3. Percentage s

Re: [FlexJS]Layout redux

I think this is generally a good approach. I've been thinking that we have some refactoring to do which might help. For instance, Core should probably be edited to include interfaces, events, and whatever else works across all packages. HTML should probably be just the HTML classes (Div, H1, TextN

Re: [FlexJS]Layout redux

Hi Peter, it seems HTML rely for this task heavily on CSS to the point that almost nothing is done in html or js code. So maybe we are not in the right way for HTML platform and we should make our code be mainly CSS. An example is here: https://css-tricks.com/snippets/sass/placing-items-circle/

Re: [FlexJS]Layout redux

A lot of this work is mine and it seems to need to be thought through once again. The dichotomy of SWF & JS has presented problems for me in the past. Maybe the layouts, for JS platform, should do as little as possible, replying on CSS as much as possible. Then make the SWF platform mimic that. O

[FlexJS]Layout redux

We’re really struggling with layout. Yishay just mentioned the fact that padding is not working, but the problems seem to go much deeper than that. 1. VerticalLayout has the following code: for (i = 0; i < n; i++) {

[FlexJS] Layout Problem

Can you confirm the fix proposed in [1] ? It'll have to be done in layouts other than BasicLayout. [1] https://issues.apache.org/jira/browse/FLEX-35263 -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Layout-Problem-tp59255.html Sent fro

Re: FlexJS Layout performance (was Re: [FlexJS] Do we have a similar invalidation/commit concept as with the old Flex SDK?)

On 1/10/17, 1:45 PM, "Christofer Dutz" wrote: >Hi, > >As we were discussing this in another thread. Wouldn’t layout be one of >the things that our invalidateSize() + measure() logic of the regular SDK >would be beneficial. >Otherwise I bet some layouting operations would be executed serially an

Re: FlexJS Layout performance (was Re: [FlexJS] Do we have a similar invalidation/commit concept as with the old Flex SDK?)

Hi, As we were discussing this in another thread. Wouldn’t layout be one of the things that our invalidateSize() + measure() logic of the regular SDK would be beneficial. Otherwise I bet some layouting operations would be executed serially and multiple times (sort of executing the logic of “mea

Re: FlexJS Layout performance (was Re: [FlexJS] Do we have a similar invalidation/commit concept as with the old Flex SDK?)

It should be possible to remove the content of non displayed items by implementing a different collapse bead. Sounds like a good optimization. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-Do-we-have-a-similar-invalidation-commit-concept-as-with-th

Re: FlexJS Layout performance (was Re: [FlexJS] Do we have a similar invalidation/commit concept as with the old Flex SDK?)

On 1/10/17, 12:25 AM, "Harbs" wrote: >Once we’re on the topic of layout performance, I’d like to point out some >observations that we had: > >1. Layouts happen twice. I think this is because both setting height and >width trigger a resize event. This pattern causes every layout to take >twice a

FlexJS Layout performance (was Re: [FlexJS] Do we have a similar invalidation/commit concept as with the old Flex SDK?)

Once we’re on the topic of layout performance, I’d like to point out some observations that we had: 1. Layouts happen twice. I think this is because both setting height and width trigger a resize event. This pattern causes every layout to take twice as long as it should. I’m not sure how to fix

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

In Radiate I convert Flex UIComponents to HTML components and had this problem. I made an option to allow styles to be defined inline or in a style sheet. If the option was stylesheet then if the component had an id the styles were declared by id. This included position, size, etc: #myLabel {

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

I took a look and saw that your ListItemRenderer is in the application project, not a library project, but it contains conditional compile code. I'm not sure we've ironed out that workflow. The main idea was that application developers wouldn't need conditional compilation. All APIs they would ne

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

Hi Alex, I uploaded all my code in the two last commits so you can see it. Is mostly Peter's Code but the itemRenderer is a copy of StringItemRenderer but put the class in the project example (since people will use normaly a List with different IRs. I had to remove the related SWF code since compi

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

What does your code look like? Sounds like DataItemRenderers are still being created and added. I think the display: block is from VerticalLayout. It uses that to tell the browser to lay things out vertically. position: relative might also come from the layout or some container logic as we've s

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

One more thing, Where come from the 8px width in List? The styles in items are as well suspicious 2016-12-03 1:37 GMT+01:00 Carlos Rovira : > Hi, > > just integrate the new List component and beads in MDL. As I changed it > and introduced a custom item renderer (called > itemRenderers/ListItemR

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

Hi, just integrate the new List component and beads in MDL. As I changed it and introduced a custom item renderer (called itemRenderers/ListItemRenderer.as) in MDLExample (that is what people will do), I found a strange behaviour. The custom IR is running since I put a trace statement and I see on

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

Hi Peter, so cool! I just created the pom.xml and fill the licenses to build with maven. Run the example and check the code. I still eating that food to be able to comment, but seems what I expect :) So many thanks, I'll be playing with it in the following days to apply to MDL components I think

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

This seems mostly right to me. The top-level component is aggregating the interfaces onto itself. More inline... On 12/2/16, 12:41 PM, "Peter Ent" wrote: > >GenericListView does not extend ListView because that leads to this >nesting business we are trying to avoid. Instead, it just extends >Be

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

I've checked in a new example: flex-asjs/examples/flexjs/ListExample. Let me know if this is close to what you are looking for. —peter On 12/2/16, 3:41 PM, "Peter Ent" wrote: >I have something working now. It took a bit more doing than I'd like, but >it is relatively clean. I have to create a n

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

I have something working now. It took a bit more doing than I'd like, but it is relatively clean. I have to create a new example for this or add it to an existing example. But here is the overview: I created a new component called GenericList (since SimpleList is already taken). On the SWF side th

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

Hi Josh, right. As I get some few components more, I think I could refactor removing the dependencies from some HTML comps so we could manage better MDL set. So for example, I will took things from Core, like UIBase or ContainerBase while removing html things like TextButton, Container and so on..

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

excelent Peter! I'll be waiting for this :) 2016-12-02 15:47 GMT+01:00 Peter Ent : > I will be looking into this, this morning (shortly). Just for background: > > The ListView creates two things: an outer containment area (div) to house > the chrome (scroll bars, title bars, footer bars, etc) and

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

Alex's first point about using the same beads, but not subclassing sounds cleaner to me, Carlos. Kind of the same idea from the other day where all components should be possible to recreate from UIBase with the right set of beads. You should consider trying that out for MDL. - Josh On Dec 1, 2016

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

I will be looking into this, this morning (shortly). Just for background: The ListView creates two things: an outer containment area (div) to house the chrome (scroll bars, title bars, footer bars, etc) and the content area (ContainerContentArea). When we first set this up, the JS side wasn't sup

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

Re-ordering your post so I can address higher-level points first: On 12/1/16, 4:55 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: > >But Basic set is at the core of >all. Is at the core of MDL set > > This statement doesn't have to be true, and makes me think that the old Flex

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

On Thu, Dec 1, 2016 at 4:55 PM, Carlos Rovira wrote: > > I wish I could agree, but I don't think I can. IMO, some component > > features can only be implemented by setting style properties. In the > > example above, to keep Label as single-line (so you don't have to us >   > > and can just use

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

> I wish I could agree, but I don't think I can. IMO, some component > features can only be implemented by setting style properties. In the > example above, to keep Label as single-line (so you don't have to us   > and can just use space), we must set white-space:no-wrap. Allowing folks > to twe

Re: [FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

I'll look into this tomorrow. Peter On Dec 1, 2016, at 7:09 PM, Carlos Rovira wrote: >> >> Anyway, Peter might be able to better answer your question, but it appears >> that if you create some new subclass of UIBase and have it return 'this' >> for layoutHost and contentView, that the ListV

Re: [FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

On 12/1/16, 4:01 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >to separate things: > >Such as? Depending on your layout, left, top, width, and height will be >> set in CSS. In UIBase, setting the x value sets style.left, etc. If >> there is an alternative, please let me kn

[FlexJS] (Att: Peter Ent) Get rid of extra divs layers we don't want (was Re: [FlexJS]Layout problems)

> > Anyway, Peter might be able to better answer your question, but it appears > that if you create some new subclass of UIBase and have it return 'this' > for layoutHost and contentView, that the ListView might then just stick > the children in the outer div. See how MXMLItemRenderer (which I > m

[FlexJS] get rid of inline styles (was Re: [FlexJS]Layout problems)

to separate things: Such as? Depending on your layout, left, top, width, and height will be > set in CSS. In UIBase, setting the x value sets style.left, etc. If > there is an alternative, please let me know what it is. > -Alex > > I get this: some texta button from this:

Re: [FlexJS]Layout problems

On 12/1/16, 2:43 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >> Can you be more specific? I thought most components were picking up all >> of their styles from defaults.css. Which components aren't doing this? >> >> >Most used like Container, Label or Button not. If you ch

Re: [FlexJS]Layout problems

> Can you be more specific? I thought most components were picking up all > of their styles from defaults.css. Which components aren't doing this? > > Most used like Container, Label or Button not. If you check html output you will see kilometric properties assigned to style attribute. > I don'

Re: [FlexJS]Layout problems

On 12/1/16, 1:57 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: > >In MDL we don't need any style tag and percents works ok. But if I use >some >HTML.swc comps I get the styles bloating my html and I don't want that. So >for that reason I think we should refactor styles to CSS.

Re: [FlexJS]Layout problems

If a VIEW bead could solve that problem and remove the nested div, that would be right for me...but we need some working example and a description of how to make that. With js:List I was searching without luck how to remove the extra div layer 2016-12-01 11:12 GMT+01:00 Harbs : > That’s something

Re: [FlexJS]Layout problems

That’s something I alluded to in my post. Container components have double divs to accommodate View and (scroll viewports?). I don’t think this is generally needed in HTML and I think it causes more problems than it solves. There should probably be “lightweight” Container and “heavyweight” Cont

Re: [FlexJS]Layout problems

Hi, just to add something more here. I already mentioned the problems of div relative positioning in other threads. I as well think that having the basic set with predefined styles is not PAYG, and we get a bloated html full of tags with style attributes (div, span...). The problem Alex comment in

Re: [FlexJS]Layout problems

I’m not blaming the concepts. I’m just stating that as it stands, layout is really hard. Part of the problem I was able to see was due to the fact that there were nested divs with alternating absolute and relative positioning. This killed all padding settings to the sub-objects. Basically the d

Re: [FlexJS]Layout problems

On 11/27/16, 3:31 AM, "Harbs" wrote: >FlexJS makes it way too hard to solve simple layout challenges. I don't know if it is fair to blame the patterns and principles of FlexJS for that, but it certainly is possible that the Layout you need hasn't been written yet. Keep in mind that regular Fl

[FlexJS]Layout problems

FlexJS makes it way too hard to solve simple layout challenges. 1. I have an application with a bunch of buttons. I want to buttons to take up the width of the view with a 5 px margin on each side. In classic Flex, this was easy. You’d just specify right=“5” left=“5”, and you’re done. In FlexJS,

Re: [FLEXJS] Layout

Turns out OneFlexibleChildVerticalLayout was what I needed. Pseudo code: Also, I found out that setting x or y explicitly will change positioning to absolute, which facilitates overlaying. -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FLEXJS

Re: [FLEXJS] Layout

creen. In FlexJS scrollableContainer takes up the screen size and together with the toolbar overflows it. Any suggestions? -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FLEXJS-Layout-tp48805p54896.html Sent from the Apache Flex Development mailing list ar

Re: [FlexJS]Layout

On 6/6/16, 5:01 PM, "jude" wrote: >I was looking to add some default styles to the HTML page and it looks >like >Falcon JX is creating it dynamically >, >"The FalconJX compiler will generate an index.html file and a single

Re: [FlexJS]Layout

I was looking to add some default styles to the HTML page and it looks like Falcon JX is creating it dynamically , "The FalconJX compiler will generate an index.html file and a single minified .js file in bin/js-release and a

Re: [FlexJS]Layout

I had put it on the application after I had put it in the view. My mistkae was that I forgot to remove it from the view. It’s working now… On Jun 6, 2016, at 2:20 PM, Alex Harui wrote: > > > On 6/6/16, 10:49 AM, "jude" wrote: > >> I think for HTML5 we want to set the html and body width an

Re: [FlexJS]Layout

On 6/6/16, 10:49 AM, "jude" wrote: >I think for HTML5 we want to set the html and body width and height to >100%. That should enable elements on the body to be constrained to the >edge >of the browser window. > >Peter, on the layout containers, I think we may be able to use a single >container

Re: [FlexJS]Layout

On 6/6/16, 10:40 AM, "Harbs" wrote: >To answer my own question, I see this was already answered in another >discussion: > > > >However, when I add this, I get an error on this line: > var /** @type {org.apache.flex.core.UIBase} */ initialView = >org.apache.flex.ut

Re: [FlexJS]Layout

I think for HTML5 we want to set the html and body width and height to 100%. That should enable elements on the body to be constrained to the edge of the browser window. Peter, on the layout containers, I think we may be able to use a single container if we don't have any chrome but still want scr

Re: [FlexJS]Layout

To answer my own question, I see this was already answered in another discussion: However, when I add this, I get an error on this line: var /** @type {org.apache.flex.core.UIBase} */ initialView = org.apache.flex.utils.Language.as(this.app.initialView, org

Re: [FlexJS]Layout

Next question: Is there a canned way to trigger a re-layout on a browser window resize? CSS constraints only work if the parent element is big enough. On Jun 6, 2016, at 12:41 PM, Harbs wrote: > Never mind. I see you answered this question in the other discussion: > > > >

Re: [FlexJS]Layout

Never mind. I see you answered this question in the other discussion: This seems to work well. I could definitely get used to this. On Jun 6, 2016, at 11:48 AM, Harbs wrote: > If I’m understanding correctly, the constraints are already working as css > for both b

Re: [FlexJS]Layout

If I’m understanding correctly, the constraints are already working as css for both browser and Flash. Correct? What’s the right way to go about declaring these values? Assuming I have some markup like this:

Re: [FlexJS]Layout

On 6/6/16, 6:02 AM, "Harbs" wrote: >Well, constraint layout is really important. I’m fine with using css for >JS output, but that’s not going to help for a swf first workflow. What do you mean by "constraint layout"? The Spark layout with ConstraintColumns and ConstraintRows? IIRC, it used a

Re: [FlexJS]Layout

I did a lot of work on the layouts - in fact I re-wrote it at least once. For BasicLayout, we pull each child's CSS values and use them. They should work. The other layouts, vertical and horizontal, use some CSS styles too (padding and margin). The layout beads try to watch for changes in the siz

Re: [FlexJS]Layout

I’m a bit confused. In BasicLayout.layout() there’s the following code: var left:Number = ValuesManager.valuesImpl.getValue(child, "left"); var right:Number = ValuesManager.valuesImpl.getValue(child, "right"); var top:Number = ValuesMa

Re: [FlexJS]Layout

Well, constraint layout is really important. I’m fine with using css for JS output, but that’s not going to help for a swf first workflow. I’d be happy to do some work on this, but frankly, I’m not sure where to start. If you could give me some pointers, it might help. I’ll try and look at the

Re: [FlexJS]Layout

On 6/5/16, 11:26 AM, "Harbs" wrote: >How is layout handled in FlexJS? Is there a layout manager? It looks like >there’s no constraints (i.e. top, bottom,left and right). Is that >something that’s particularly difficult to add? > Layouts are beads. We have a HorizontalLayout and VerticalLayout

[FlexJS]Layout

How is layout handled in FlexJS? Is there a layout manager? It looks like there’s no constraints (i.e. top, bottom,left and right). Is that something that’s particularly difficult to add?

  1   2   >