[FlexJS] Merge feature into develop

, Peter Ent Adobe Systems/Apache Flex Project

Re: [FlexJS] feature/chart_work status

ain, which is a rather desirable thing ;-) > >Chris > > >Am 10.04.17, 20:40 schrieb "Peter Ent" <p...@adobe.com>: > >I now have the feature/chart-work branch in good shape: the frameworks >projects build and so do all of the examples; both

Re: [FlexJS] feature/chart_work status

can. Regards, Peter On 4/10/17, 9:44 AM, "Peter Ent" <p...@adobe.com> wrote: >I know have MDLExample working. > >I think I did this unwittingly: The MaterialDesignLite project's >default.css has the IDateProviderItemRendererMapper for the Tabs and

Re: [FlexJS] feature/chart_work status

I know have MDLExample working. I think I did this unwittingly: The MaterialDesignLite project's default.css has the IDateProviderItemRendererMapper for the Tabs and TabBar components specified as TabsItemRendererFactoryForArrayListData. But the dataProvider being supplied to the tab components

Re: [FlexJS] feature/chart_work status

I will look into it and let you know. I changed the life cycle for lists just a little. I found that the item renderers were being created more than once (sometimes) and the layouts were being run several times (sometimes) so I tracked down redundant event dispatches and eliminated them. Then I

Re: git commit: [flex-asjs] [refs/heads/feature/chart-work] - Updates to MDL.

I don't need to have DataProviderChangeNotifier do what I made it do. I was thinking that using the same event was causing the problem in the MDL tabs because that event causes all of the item renderers to be thrown away. ‹peter On 4/9/17, 9:47 AM, "piotrz" wrote:

Re: [FlexJS] feature/chart_work status

Thanks. I'm having trouble understanding what code is changing the active tab panel. I can see in the DOM, a tab with is-active set and a corresponding tab panel has is-active set. After I add a new tab, things look normal in the DOM. I can now select the new tab and see that the new tab gets

Re: [FlexJS] feature/chart_work status

to work on it over the weekend and we'll see where I get by Monday. Regards, Peter On 4/7/17, 7:41 AM, "Peter Ent" <p...@adobe.com> wrote: >I see that. I thought I fixed that. I'll look it while I'm building the >examples. >‹peter > >On 4/6/17, 5:55 PM, "piotr

Re: [FlexJS] feature/chart_work status

I see that. I thought I fixed that. I'll look it while I'm building the examples. ‹peter On 4/6/17, 5:55 PM, "piotrz" wrote: >Hi Peter, > >I just tried MDLExample and it look good, but MDLDynamicTabsExample has >same >problem. Something is going wrong when Tab is

[FlexJS] feature/chart_work status

the build completes. I will not merge into develop until tomorrow, Friday 7 Apr 2017, in the afternoon EDT (after 6pm UTC). I will keep you posted. Regards, Peter Ent Adobe Systems/Apache Flex Project

Re: [FlexJS] Merge feature/chart-work into develop

I fixed the missing piece for the text fields example. Still looking into the tabs. ‹peter On 4/5/17, 5:46 PM, "piotrz" wrote: >Peter, > >I just tried your changes and check MDLExample and MDLDynamicTabsExample. > >In MDLExample: >TextFields are not displayed > >In

Re: [FlexJS] Merge feature/chart-work into develop

I have decided not to merge today. I ran an example with DataGrid embedded within a Container and sized to width="100%" and it did not respond properly to the resize. I know what happened, just working on how to make it work correctly. ‹peter On 4/5/17, 1:35 PM, "piotrz"

Re: [FlexJS] Merge feature/chart-work into develop

I just changed Menu to extend DataContainer and now that works fine, for me, in MDLExample. Thank you for reminding me. ‹peter On 4/5/17, 11:37 AM, "piotrz" wrote: >Hi Peter, > >I didn't check MDLExample after your last push, but didn't you mention >that >MDL Menu is

[FlexJS] Merge feature/chart-work into develop

Hi, I would like to merge the feature/chart-work into the develop branch in about 5 hours from now which would make it 4:30pm EDT (9:30pm UTC, I think). Does anyone have a strong objection to that? To recap: The thrust of this feature branch was to get Charts working, but that lead to

Re: [FlexJS] State of the examples

I haven't tried it yet. I have it on my list. I'll take a look at it today. ‹peter On 4/4/17, 11:05 AM, "Harbs" wrote: >Has anyone tested js:ComboBox recently? I just tried one and it¹s not >working very well. I don¹t know if it¹s something I¹m doing wrong, or >it¹s

Re: [FlexJS] MDL Help Needed

Much, much more of the MDLExample is now working the changes to Tabs and TabBar. - In the MDLDynamicTabsExample, the tabs appear and can be selected, but when a new tab is added, the information about what tab was previously selected is lost. - In the MDLExample, Tabs selection, the first tab

Re: [FlexJS] MDL Help Needed

Thanks. I didn't see that. I will work on that next. ‹peter On 4/3/17, 4:38 PM, "piotrz" wrote: >Peter, > >There is such app in the example: MDLDynamicTabsExample :) > >Try it out - it also do not display Tabs. > >Piotr > > > >- >Apache Flex PMC

Re: [FlexJS] MDL Help Needed

Hi, I think I need your help again. I noticed that when I tap on something I'm taken to getmdl.io. Could you put another sample together that uses Tabs? That should help make it go faster. Thanks. Peter On 4/3/17, 11:28 AM, "piotrz" wrote: >Peter, > >I think falcon

Re: [FlexJS] MDL Help Needed

I guess I forgot what the example actually looked like - so much stuff appeared when I ran it! I will look into Tabs, and you are probably right, it would extend List if it were a list. ‹peter On 4/3/17, 11:28 AM, "piotrz" wrote: >Peter, > >I think falcon on your

Re: [FlexJS] MDL Help Needed

Hi, I now have the MDLExample running. I've committed and pushed my changes onto feature/chart-work. I have not sync'd with flex-falcon in a while - so I don't know if that makes a difference. I am hoping that any issues now are related to SWF-side layout code. Going forward, if your component

Re: [FlexJS] OneFlexibleChildVerticalLayout

run your sample using the correction I just pushed, I see a green bar all the way across the top of the browser and blue fills the rest of the browser space. Regards, Peter On 4/3/17, 8:50 AM, "Peter Ent" <p...@adobe.com> wrote: >Something is not right with the layouts. I'm lo

Re: [FlexJS] OneFlexibleChildVerticalLayout

Something is not right with the layouts. I'm looking into it today. ‹peter On 4/3/17, 2:43 AM, "yishayw" wrote: >I just tested the test case upthread on feature/chart-work and I'm getting >the same problem. 'cont2' does not get sized and is not shown. > > > >-- >View

Re: [FlexJS] MDL Help Needed

Yes. I hope to resolve this quickly. What I did was move the MXML support from the GroupBase/ViewBase/ContainerBase classes into the Group/View/Container classes. I did this so that there was an easy inheritance chain: ChartBase->ListBase->DataContainerBase->ContainerBase->GroupBase with each of

Re: [FlexJS] MDL Help Needed

I've pushed changes to HTML and MDL libraries in the feature/chart-work branch. In order to get the small example you made to work, I had to change MDL's List. Actually, I simplified it a great deal so that is 90% the HTML List with just a few changes now. The main MDLExample still isn't running,

Re: [FlexJS] OneFlexibleChildVerticalLayout

<harbs.li...@gmail.com> wrote: >It looks like the problem is that layoutViewAfterContentLayout(); is now >wrapped in a COMPILE::SWF block. > >> On Apr 2, 2017, at 8:56 AM, yishayw <yishayj...@hotmail.com> wrote: >> >> Peter Ent wrote >>> >&

Re: [FlexJS] MDL Help Needed

HI, I haven't got MDL working completely, but I found the cause of the problem. The Span class is extending ContainerBase. That won't work now because ContainerBase no longer supports MXML children - I moved that into Container (and Group and View). I also don't think you need Container for

Re: [FlexJS] OneFlexibleChildVerticalLayout

Hi - just saw this (Sunday morning here). When you use the "flexible" layouts, you don't need percent sizing. If you do put explicit or percent sizing in, the layout code (SWF side) probably won't do the right thing with it and I'd have to see what HTML does with it. I'm still understanding the

Re: [FlexJS] MDL Help Needed

Thanks. I will try this as soon as I can. Peter > On Apr 1, 2017, at 1:54 PM, piotrz wrote: > > Peter, > > I got it! :) After 3 hours of fight I was able to expose problem. I've > prepared simple application where you can reproduce it [1]. > > In general for

Re: [FlexJS] MDL Help Needed

Thanks so much. I'm pretty sure it will be an easy fix, depending on how MDL thinks of things, container-wise. ‹peter On 3/31/17, 4:51 PM, "piotrz" wrote: >Hi Peter, > >I will try to expose bug in simpler example over the weekend. I will let >you >know. > >Piotr > >

[FlexJS] MDL Help Needed

Hi, I've finalized the changes I wanted to make to get the core of FlexJS to be more efficient. Most of the projects seem to work now, except MDL. The MDLExample was working for me before I undertook this last change, but now it fails and it looks like it is failing down in some Google JS

Re: [FlexJS] feature branch

It looks like there is more work to do with Falcon, if I'm reading this right. ‹peter On 3/31/17, 1:32 AM, "piotrz" wrote: >Peter, > >Develop has exactly same issue and Jenkins reported it also [1] > >[1]

Re: [FlexJS] feature branch

of its location) now that nesting of elements has disappeared. The charts look back to normal except for the "optimized" SVG version; I think that's a position style issue, too. Thanks, Peter PS: This feature branch thing really was a good idea. On 3/29/17, 5:28 PM, "Peter Ent&q

Re: [FlexJS] feature branch

Base class that extends GroupBase and puts in BasicLayout. Then you just need to trigger the layout once your view has been created and whenever it changes side. —peter On 3/30/17, 8:23 AM, "Peter Ent" <p...@adobe.com> wrote: >Yes, please push the changes when you can. Thank y

Re: [FlexJS] feature branch

Hi, I took a look at your changes to ListExample. I see I forgot to put in a ReadMe or some comments to show why the example is written the way it is. The example is supposed to show a deconstruction of a list, by starting with UIBase and adding in the things that make a list a "List". The point

Re: [FlexJS] feature branch

Yes, please push the changes when you can. Thank you! ‹peter On 3/30/17, 12:59 AM, "piotrz" wrote: >Hi Peter, > >I just checked your branch and MDL look fine. In order to build it I had >to >merge current develop to your branch I hope that you don't mind if I >pushit

Re: [FlexJS] feature branch

Thanks! ‹peter On 3/30/17, 3:34 AM, "Christofer Dutz" wrote: >And I just added that branch to compiler and typedefs and now you have >your free Jenkins Build ( > >https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuilds.ap

[FlexJS] feature branch

Hi, I've pushed feature/chart-work that contains updates to the Chart package, but also other structural changes to HTML to support it. If you have time, check it out and see if your work builds and runs with it. MDL might need a little refactoring; I have it compiling but I do not know yet

Re: [FlexJS] Summary of Changes

> id="scrollContainer" >>width="100%" height="100%"> >> >> >> >>

Re: [DISCUSS] Changing our general mode of development?

so everyone can try it out first before it gets merged into develop. We need to clean FlexJS up - I believe there are lots of unused files and the HTML project is way too big. So keep that in mind for the near future if you want do that. Regards, Peter Ent On 3/28/17, 12:49 PM, "

Re: [FlexJS] Summary of Changes

I just pushed a change to the tour code. It should be better. We should be able to do this with the regular horizontal and vertical layouts with % sizing, I think, and not just with Flexbox layouts. One thing I changed was to remove the grow="1" on the layouts. I put that in there to make it easy

Re: [FlexJS] Summary of Changes

e things have >become stable. > > >On Tue, Mar 28, 2017 at 9:52 AM, Peter Ent <p...@adobe.com> wrote: > >> Does the HTML look OK - the structure. Is there anything missing? You >> should see a simplified nesting of DIVs. If that's the case, then maybe >>

Re: [FlexJS] Summary of Changes

I forgot to add that "align-items:center" is not supported on the SWF side yet. The Flexbox has a number of properties that I still have to implement on the flex side. On 3/28/17, 8:11 AM, "Peter Ent" <p...@adobe.com> wrote: >The HorizontalLayout and VerticalLayou

Re: [FlexJS] Summary of Changes

="scrollContainer" >>width="100%" height="100%"> >> >> >> >> > id="des

Re: [FlexJS] Summary of Changes

o have that in the mxml, once things have >become stable. > > >On Tue, Mar 28, 2017 at 9:52 AM, Peter Ent <p...@adobe.com> wrote: > >> Does the HTML look OK - the structure. Is there anything missing? You >> should see a simplified nesting of DIVs. If that's the case, th

Re: [FlexJS] Summary of Changes

sed to create a centered group of buttons. Now, the container >has a height of 0 and the buttons don’t show up. > >2. >id="scrollContainer" >width="100%" height="100%"> > > > > id=&quo

Re: [FlexJS] Summary of Changes

sformations. > >We really need the old behavior in some components. > >Is there any components which work the same as they used to? > >Harbs > >> On Mar 26, 2017, at 6:55 PM, Peter Ent <p...@adobe.com> wrote: >> >> For the time being, the Tour main view should h

Re: [FlexJS] Summary of Changes

For the time being, the Tour main view should have a width and a height: Then in the style section, give everything flex-grow: 1; and it should look better. I think some padding and/or margins might be needed, but I think I have more work do with the layouts. I'll bump getting the tour to the

Re: [FlexJS] Summary of Changes

I'm looking at the Tour right now. When you use the Flexbox layouts, you need to specify flex-grow:1 for anything you want to grow to fill the remaining space; otherwise it uses its native or explicit size. You could try to switch over to the normal horizontal and vertical layouts and see if they

Re: [FlexJS] Anyone working on the build problems?

I didn't think the build, built the examples. If that's the case, I'll build the examples and see what fails and then exclude those from the build and work on them to get them running again. ‹peter On 3/26/17, 11:30 AM, "Christofer Dutz" wrote: >Hi, > >For the last 4

Re: [FlexJS] Struggling with custom HTML

The way it stands now, you do need to create a new component in the framework somewhere. In the long run, developers will want to make their own component sets that make use of conditional compilation, so now would be a good time to come up with that. You should be able to do this outside of the

Re: [MAVEN-BUILD] FlexJS Framework (maven) - Build # 819 - Still Failing

I deliberately didn't work on Basic because it would almost be a complete duplicate of the work in HTML. I think need to decide how to proceed here and begin to divide up the projects more. HTML has way too much in it, I think. Perhaps start a discussion thread on it again? ‹peter On 3/24/17,

Re: [FlexJS] Summary of Changes

/a-guide-to-flexbox/ Regards, Peter On 3/24/17, 8:33 AM, "Peter Ent" <p...@adobe.com> wrote: >Amendment to these changes: > >Charts: This package should compile now, but will probably not work >completely. Next on my list. > >MDL: This package compiles and runs

Re: [FlexJS] Summary of Changes

t controls that life cycle (I removed redundant code where I found it). Cheers, Peter On 3/23/17, 1:27 PM, "Peter Ent" <p...@adobe.com> wrote: >FlexJS Container and Layout Upgrade > >My goal when starting this process was to have FlexJS produce leaner HTML >structures and t

Re: [FlexJS] Container and Layout Progress

Things should build now. Charts will not work yet, but MDL example (at least one) now runs for me. ‹peter On 3/24/17, 2:58 AM, "Christofer Dutz" wrote: >Hi Guys, > >Well I am expecting to be able to build develop Š if there are changes >that break things, these

Re: [FlexJS] Summary of Changes

see how they play out. > >There might be a need to easily flip position between absolute and >relative, but we¹ll see. > >I¹m looking forward to seeing how the changes behave. :-) > >Harbs > >> On Mar 23, 2017, at 7:27 PM, Peter Ent <p...@adobe.com> wrote: >

Re: [FlexJS] Container and Layout Progress

changes since it JS-side only which makes it easier now. —peter On 3/23/17, 2:01 PM, "Peter Ent" <p...@adobe.com> wrote: >Yes, Chris does have a good point and from now on* I will definitely use >feature branches. I thought I could squeeze this through. > >I checked in

Re: [FlexJS] Container and Layout Progress

exploding at the moment … > > Chris > > > > Am 23.03.17, 17:02 schrieb "Peter Ent" <p...@adobe.com>: > >Hi, > >I've committed the changes!! The build should skip, MDL, Charts, and Basic >projects. I will get MDL and Charts running next. But b

Re: [FlexJS] Container and Layout Progress

Yes, Chris does have a good point and from now on* I will definitely use feature branches. I thought I could squeeze this through. I checked in changes to Chart that should make it compile. I doubt it will run, but that is on the list. I will look into MDL now. That will take longer. I am leary

[FlexJS] Summary of Changes

of the layouts, but the common ones have tested correctly. Regards, Peter Ent Adobe Systems/Apache Flex Project

Re: [FlexJS] Container and Layout Progress

I guess I should have used a feature branch. I'm not sure how long Charts will take. I wrote most of that code and it got pretty gnarly using List as a basis. It probably is better to use a feature branch. Let me see if I understand the rollback process and can get that going. Definitely a lesson

Re: [FlexJS] Container and Layout Progress

breaks. I will tell you that the biggest difference is the UIBase no longer sets position style so any elements you have that require positioning via x,y, will need to use a Group or Container that has the BasicLayout. Regards, Peter On 3/22/17, 5:02 PM, "Peter Ent" <p...@adobe.com>

Re: [FlexJS] Container and Layout Progress

Update: I'm 99% ready to commit. I will do this tomorrow morning, my time. I've spent today fixing some last issues in HTML package, while cosmetic, just didn't make things look too good. There are a couple more but I'll do them later. I did a local merge of the latest FlexJS code and my changes

[FlexJS] Before and After

Hi, I have some before and after code to show you. I don't know if the HTML will come through and if it does not I'll put it into an Apache paste. I ran an example of the following MXML snippet. It is a series of nested Containers with different layouts. This is what the

[FlexJS] Before and After

Hi, I have some before and after code to show you. I sent it out earlier but since I didn't see it come back into my inbox I'll assume the HTML I put into it didn't pass the filters, so I've put the code into a paste[1] below. I ran an example of the following MXML snippet. It is a series of

Re: [FlexJS] MDL - Project is failing to compile, help!

I just re-sync'd myself since I am planning to merge my code and I'm having the same issue. I did try maven and that does build, so that's good. But the ant build should work, too. Thanks, Peter On 3/22/17, 10:34 AM, "Christofer Dutz" wrote: >Hi Sankar, > >Have you

Re: [FlexJS] Container and Layout Progress

Hi, One more thing: When I make this commit, I'm pretty sure Charts will be broken until I address it. I can hold off the commit and address Charts first, but I would prefer to commit Core and HTML and then fix Charts and anything else. Would that strategy (commit first, fix Charts etc after)

[FlexJS] Container and Layout Progress

Hi, I'm am making progress toward simplifying the JS output generated from the components. I should be making a commit either tomorrow or the next day. There will be some things not working 100% correctly, mostly because they need to be tuned to use the new layouts or are making assumptions

Re: [FlexJS] Container work status

Hi, I've fixed a number of layout issues. I'm still putting things together and testing, but this problem should be addressed in my next commit. ‹peter On 3/20/17, 3:26 AM, "yishayw" wrote: >I think some of your changes in BasicLayout have broken some layout >behavior

Re: [FlexJS] Datagrid?

I just saw this - sorry for the delay. I'm working on changing the structure of the container classes which also affects list and therefore DataGrid. Once I have things stable and checked in I'll look at the bugs and see if they are resolved and if not, start addressing them. Regards, Peter Ent

Re: [FlexJS] Container work status

Thanks for letting me know. I will try to be quick. ‹peter On 3/16/17, 4:11 AM, "Justin Mclean" wrote: >Hi, > >The current changes have broken the layout in our application (not >unexpected). When you feel it at a stable state just say so and we set if >we can fix it

[FlexJS] Container work status

ns, please let me know. Regards, Peter Ent Adobe Systems/Apache Flex Project.

Re: [FlexJS] Panel

The way things are set up right now, due to the nesting of containers (div or DisplayObjectContainer), you do get (0,0) at the top. It will usually be necessary to have nested containers for scrolling purposes if nothing else. As I'm going through the code, I don't see that IChrome is actually

Re: [FlexJS] Panel

The idea of "chrome" is that these are components that do not count as regular children and have special locations within the component. The TitleBar and ControlBar are considered chrome because if you ask for the children of the Panel, they are not listed and if you have so many children in the

[FlexJS] Panel

ive, Panel can be re-constructed to look as it does now without the use of chrome simply by using Group for the Panel itself and Group for the TitleBar and ControlBar and a Container with a ScrollingViewport for the content. Please let me know your thoughts. Thanks, Peter Ent Adobe Systems/Apache Flex Project

Re: [FlexJS] Group container

implementing IChrome interface) or should it just be for scrollable content? Thanks, Peter On 3/7/17, 10:31 AM, "Peter Ent" <p...@adobe.com> wrote: >Thanks for the feedback! > >As I go through the examples, I see that we (mostly me) created a number >of nested elements, suc

Re: [FlexJS] Group container

>component classes is such important thing and first point not only in your >effort of create a good layout strategy, but an important previous step if >we want to implement theming in FlexJS. > >Great! :D > >Carlos > > >2017-03-07 14:23 GMT+01:00 Peter Ent <p...@adobe.com&

Re: [FlexJS] Group container

This is the theory, yes. A way to do your own thing using AS and MXML to construct the app which then generates the right amount of HTML structure, making it easier to style. Or use pre-built constructions and layouts as templates that also generate the right amount of HTML structure. I'm

Re: git commit: [flex-asjs] [refs/heads/develop] - Introducing the Group container.

asjs/repo >> Commit: http://git-wip-us.apache.org/repos/asf/flex-asjs/commit/79d45cba >> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/79d45cba >> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/79d45cba >> >> Branch: refs/heads/develop >>

[FlexJS] Group container

to be based on Group rather than Container which will also eliminate another layer. Please give Group a test if you can. Thanks. Peter Ent Adobe Systems/Apache Flex Project

Re: [FlexJS] Coordinate Space

ssues once complete. Regards, Peter On 3/2/17, 9:37 AM, "Peter Ent" <p...@adobe.com> wrote: >We still have to have FlexJS work on both JS and SWF sides with some >compatibility. We could do this: > >x,y sets "native" values. Reading them back on SWF vs

Re: [FlexJS] Coordinate Space

We still have to have FlexJS work on both JS and SWF sides with some compatibility. We could do this: x,y sets "native" values. Reading them back on SWF vs JS might yield different results if padding, border, and margins are set on the parent element. If you don't want your coordinates messed

Re: [FlexJS] Coordinate Space

> >For the Flex-like components in Basic, we could make everything always use >absolute positioning. And Container would have a more Flex-like >coordinate space. Don't know if that would help or not. > >Thoughts? >-Alex > >On 3/1/17, 7:28 AM, "Peter Ent&

Re: [FlexJS] Coordinate Space

r for >cases where that¹s important (which I think is a lot more rare than is >currently assumed). > >My $0.02. >Harbs > >> On Mar 1, 2017, at 3:56 PM, Peter Ent <p...@adobe.com> wrote: >> >> I think we have confusion over what FlexJS is trying to deliver

Re: [FlexJS] Coordinate Space

t localToGlobal etc.. did for Flex? > >Personally I would like testButton.x to return 0 in all instances. Unless >I >want it's actual screen position where I use the helper functions like >localToGlobal etc.. > >On Tue, Feb 28, 2017 at 8:50 PM, Peter Ent <p...@adobe.com>

Re: [FlexJS] content being push out of the way in container

I believe at this point, Container and perhaps the layouts need a re-write. These are fundamental to FlexJS and must be correct. FlexJS is trying to bridge two worlds with different ideas about coordinate systems and it is behaving erratically at times, like this. I think the solution is more

[FlexJS] Coordinate Space

e padding on its Container parent. Right now Container has this inner contentArea that tries to make sure testButton is (0,0) but it is a headache to maintain, I think. [1] https://paste.apache.org/IM1W Regards, Peter Ent Adobe Systems/Apache Flex Project

[FlexJS] Container

Hi, I've been wrestling with Container all day. I was working on the Flex layouts, but then went down the rabbit hole of Containers while trying to get the layouts to look right. The issue really isn't the HTML/JS side. That's pretty easy really (in concept). A FlexJS Container's element is a

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

Re: [FlexJS]Layout redux

, "Peter Ent" <p...@adobe.com> wrote: > > >On 2/23/17, 1:54 AM, "Alex Harui" <aha...@adobe.com> 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

Re: [FlexJS]Layout redux

t the generated HTML, there's way too much forcing of size and position that a natural HTML author would not use. But I'm not sure how to really do this programmatically while allowing all sorts of situations to work. > >My 2 cents, >-Alex > >On 2/22/17, 2:31 PM, "Peter Ent"

Re: [FlexJS] Horizontal list missing scrollbar

Not sure yet but I will look into it tomorrow. Peter > On Feb 22, 2017, at 5:45 PM, Justin Mclean wrote: > > Hi, > > Anyone have any ideas here? > > Thanks, > Justin

Re: [FlexJS]Layout redux

t;>> >>> 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 <http://caniuse.com/#fea

Re: [FlexJS]Layout redux

bs <harbs.li...@gmail.com>: >> >>> 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. >

Re: [FlexJS] Spacers and positioning

it. Percentage sizing for the children works, too, although the Flexbox will override them if it feels it must. Personally, I think it does a great job of presenting the information. On 2/22/17, 8:55 AM, "Peter Ent" <p...@adobe.com> wrote: >I'll be including the issues of spacing an

Re: [FlexJS]Layout redux

scopic.com> wrote: >Hi Peter, that sound very good :) >thanks! > >2017-02-22 16:53 GMT+01:00 Peter Ent <p...@adobe.com>: > >> That's a good strategy. My experiments this morning look like Flexbox is >> the way to go. Its widely supported now and seems prett

Re: [FlexJS]Layout redux

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 will support it, and polyfill will end in no use (and we >could >eventually remove) > >2017-02-22 14:47 GMT+01:00 Peter Ent <p...@adobe.com&

Re: [FlexJS] Spacers and positioning

I'll be including the issues of spacing and positioning in my work with layouts. ‹peter On 2/21/17, 5:56 AM, "yishayw" wrote: >That sounds like a good idea. Let me know if I can help. > > > >-- >View this message in context:

Re: [FlexJS] resize event not working?

Alex will need to chime in here, but I believe his philosophy has been to keep the number of specialized events to a minimum. I'm not 100% sure I agree with that since it can be a lot easier to write code when you are responding to specific events, but it does expand the final footprint of the app

Re: [FlexJS]Layout redux

t;percentage, left,right,top,bottom properties to do proper constrained >layout. I think that constrained layout (right,left,top,bottom) is common >enough that it doesn’t warrant a separate layout as long as we have the >bare-bones CSSLayout for cases that need it. > >> For sure

Re: [FlexJS]Layout redux

yout" (for example for circle, >if we have circle-layout, we should have a "circleLayout" css class >selector, that we could assign to out flexjs "list component" > >2.- in SWF -> we should stick with the way this was done in Flex4 but >implementing as a be

<    1   2   3   4   5   6   7   >