Re: [FlexJS] OneFlexibleChildVerticalLayout

[Peter Ent]

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 HTML sizing and layout process. The
feature/chart-work has better - but by no means perfect - layouts. I've
been looking at several examples, like the Tour, and finding small things
to change in the code to make the layouts better.

On the JS-side, the VerticalFlexLayout, HorizontalFlexLayout,
OneFlexiableChild*, etc layouts ALL use CSS Flexbox in one way or another.
If you don't care about making your app work on the SWF side, consider
always using Groups and putting your sizing and styling into CSS, just as
you would if you were writing the code in HTML/JS rather than MXML/AS.
Container, layouts, etc. are all really for the SWF side; their JS code
bits just go and change various style settings so you don't have to it in
CSS.

If you want a column with one child taking up the majority of the space,
then make sure the container will have an

We may have more complex layouts that would have to be written in JS, so
the layout "engine" is designed to do that.

One thing that did change is that layouts no longer resize their container
when you have size-to-fit. That is, if you do:


   
   


The VerticalLayout will not resize the Container to fit the content. The
Container (actually, GroupView), will do that after it runs the layout. So
if you are seeing that a container is NOT sizing to fit its content -
that's a bug. I have however, found cases in HTML where a DIV will not
size to fit its content. Still not 100% sure on those cases, yet.

Thanks for trying this out and a big Thank You for your patience.

Peter

On 4/2/17, 7:54 AM, "yishayw"  wrote:

>That works for the test case, but in our real case we have a toolbar
>container which lays its children out horizontally and sizes its height
>according to its child buttons. Changing the layout to VerticalFlexLayout
>doesn't seem right...
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-OneFlexibleChildVerticalLayou
>t-tp60953p60959.html=02%7C01%7C%7C42f1df302dc54f552bdb08d479c02dab%7C
>fa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636267313684441085=ns9ofe
>gHWKWSG%2BirEEPwMEhiP0KI6wejHg7drvV7j60%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] MDL Help Needed

[Peter Ent]

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, but I was able to get your
smaller example to work. I will continue to work the MDL library to get
the MDLExample running.

When you have a chance, please re-try to smaller example to verify my
changes.

Thanks again,
Peter

On 4/2/17, 9:54 AM, "piotrz"  wrote:

>Hi Peter,
>
>I was thinking that would be a solution, but I prefered to leave fix for
>you
>cause I wasn't sure.
>
>Thanks,
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-MDL-Help-Needed-tp60946p60965
>.html=02%7C01%7C%7Ca8e1c2d1fa1f43d35ad508d479d0fa40%7Cfa7b1b5a7b34438
>794aed2c178decee1%7C0%7C0%7C636267385847753416=WOo9%2BdRbE7ZhVIuV7%2
>FoilVkCD7MKw%2FaFHd3kCROrQeg%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] MDL Help Needed

[Peter Ent]

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 those bases contributing something along the way. But now anything that
relied on ContainerBase for its MXML needs to extend Group or Container.
For MDL, I think Group is best since it doesn't need the
viewport/contentView stuff.  The List-based classes are affected as well.

In the end, I think this will result in simpler code, cleaner HTML.
Fingers crossed anyway!

Thanks again for your help.
‹peter


On 4/2/17, 5:08 PM, "Harbs"  wrote:

>Our MDL is not working because it does not support MXML.
>
>My understanding is that Peter is working on that, though.
>
>Harbs
>
>> On Apr 2, 2017, at 3:05 PM, piotrz  wrote:
>> 
>> Peter,
>> 
>> My simple example is working for me. I was looking into the MDL library
>>but
>> it look there are also work with other components which are based on
>>List.
>> 
>> If you are looking into that just let me know if you find some
>>stoppers. 
>> 
>> Piotr
>> 
>> 
>> 
>> -
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>ex-development.247.n4.nabble.com%2FFlexJS-MDL-Help-Needed-tp60946p609
>>69.html=02%7C01%7C%7Cf8b367e8608c460ead2808d47a0c7788%7Cfa7b1b5a7b34
>>438794aed2c178decee1%7C0%7C0%7C636267641346880904=qEUjIY7CL13M7tdzw
>>sPhsqWeTftD121DoYyXLGmeN%2FM%3D=0
>> Sent from the Apache Flex Development mailing list archive at
>>Nabble.com.
>

[FlexJS] feature/chart_work status

[Peter Ent]

Hi,

Yesterday I intended to merge the feature/chart_work branch into develop. After 
I ran some more tests with more complex container structures I found a problem 
with one of the layouts. I finally worked it out, so now I'm running through 
all of the examples to make sure they compile so 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] feature/chart_work status

[Peter Ent]

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 being added.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-feature-chart-work-status-tp6
>1035p61036.html=02%7C01%7C%7Ceab9e55a09c44c3abba808d47d38ecc1%7Cfa7b1
>b5a7b34438794aed2c178decee1%7C0%7C0%7C636271130849952954=WQwjZQCjhYE
>ugbdoLNyqOtuIJX%2FtAh94muXgCW9GKIs%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] Merge feature/chart-work into develop

[Peter Ent]

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-examinging the class structures of the containers. I cleaned this up and 
kept the HTML/JS side output to a minimum. I have also improved the SWF-side 
layouts to more closely mimic CSS Flexbox.

It looks like most, if not all, of MDLExample is working. DataBindingExample, 
DataGridExample, ChartExample are working. I will go back and try the Tour and 
several others as well.

Regards,
Peter

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

[Peter Ent]

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 blank ?
>If it's not working I would say -1 till we have it look ok.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Merge-feature-chart-work-into
>-develop-tp61019p61020.html=02%7C01%7C%7C5d646cbc71544f2db0c808d47c3a
>eeae%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636270039930866144
>=FcdgwvNpXrJKpBYZFABsml8ww27%2B75P3eYM8%2FNNNWf0%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

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

[Peter Ent]

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 MDLDynamicTabsExample:
>I see that switching between tabs, once I add Tab dynamically is broken.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Merge-feature-chart-work-into
>-develop-tp61019p61031.html=02%7C01%7C%7Ca61c76fe02a3403fbdd508d47c6e
>81c1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636270261444943615
>=AGxXFnSHBUum2L1OaMO4fw%2B2hORlmjW0PpNOorXt%2F5g%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

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

[Peter Ent]

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"  wrote:

>Peter I just merged falcon develop branch to your chart-work.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Merge-feature-chart-work-into
>-develop-tp61019p61027.html=02%7C01%7C%7C781716181b2b415be00308d47c4b
>7a92%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636270111006084015
>=fRYvuMsfPzFz7V7JU8K%2BCmpWiWFDokA%2FM8f8RBZAzoY%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

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

[Peter Ent]

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:

>Peter,
>
>I just tested your changes. They are breaking the cases where I would like
>to change whole data provider once everything is renderer. I'm going to
>get
>back to the previous version and implement beads as I wrote above, late I
>will deeply look into the Tabs problems.
>
>Thanks,
>Piotr 
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FRe-git-commit-flex-asjs-refs-heads-f
>eature-chart-work-Updates-to-MDL-tp61043p61062.html=02%7C01%7C%7C67f6
>2c2e6d78473cc45c08d47f50565e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C
>636273430404170114=4eDrhNX%2BaPt0UDNbmmEybSlhOWqTLvOJKQeMZrERQhk%3D&
>reserved=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] feature/chart_work status

[Peter Ent]

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 went back through examples to see what was depending on the
eliminated events and adjusted them. This is probably the same case. Once
this works out the event flow should be consistent.

‹peter

On 4/9/17, 6:26 PM, "piotrz"  wrote:

>Ahh I forgot to mention that you can see issue when you look into
>MDLExample.
>Main TabBar do not display Tabs.
>
>Basically in TabBarView itemsCreated method has not been called.
>
>If you lost in there I will put some basic example.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-feature-chart-work-status-tp6
>1035p61069.html=02%7C01%7C%7Ca87dd5981445498e7c8508d47f98cec9%7Cfa7b1
>b5a7b34438794aed2c178decee1%7C0%7C0%7C636273741673604657=%2BiQ9rmODB
>jFFdb9Ii3fx8Ci1OAWwUPUBiVbTK0RRrHY%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] feature/chart_work status

[Peter Ent]

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 were Arrays and
not ArrayLists. 

I changed the data models to supply ArrayLists for the dataProviders and
now the tabs are working. I think our changes together made this work
again.

Perhaps MDL should have a single item renderer data factory that is
universal in that it can accept either Array or ArrayList data and help
prevent this from happening in the future. I set this type of thing up in
the Express package (which I still have to test, now that I write this).

This is the feature/chart-work branch.

Regards,
Peter

On 4/9/17, 6:26 PM, "piotrz"  wrote:

>Ahh I forgot to mention that you can see issue when you look into
>MDLExample.
>Main TabBar do not display Tabs.
>
>Basically in TabBarView itemsCreated method has not been called.
>
>If you lost in there I will put some basic example.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-feature-chart-work-status-tp6
>1035p61069.html=02%7C01%7C%7Ca87dd5981445498e7c8508d47f98cec9%7Cfa7b1
>b5a7b34438794aed2c178decee1%7C0%7C0%7C636273741673604657=%2BiQ9rmODB
>jFFdb9Ii3fx8Ci1OAWwUPUBiVbTK0RRrHY%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Examples

[Peter Ent]

Thanks for the note about the US Census data. Census data, coupled with
maps, always provides interesting information. It does however, take a bit
of time to figure out what to query, how to query it, and how to present
it. I think we could work this into a very nice example at some point.

Does anyone know of something more real-time?

‹peter

On 4/15/17, 10:48 AM, "1600...@gmail.com on behalf of Douglas McCarroll"
<1600...@gmail.com on behalf of list.apache-flex@brightworks.com>
wrote:

>IIRC, James Ward's benchmarking app...
>
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.james
>ward.com%2F2007%2F04%2F30%2Fajax-and-flex-data-loading-benchmarks%2F=
>02%7C01%7C%7C685b06dde1ce4c6a215f08d484546721%7Cfa7b1b5a7b34438794aed2c178
>decee1%7C0%7C0%7C636278945430535468=jAuct%2B8oS4FnFAX9WC3xFvxZFpGCLG
>UvWvKgzJMPe2s%3D=0
>
>... used US Census data.
>
>Sadly, the benchmark app doesn't seem to work any more, but I found this
>via google:
>
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.censu
>s.gov%2Fdata%2Fdevelopers%2Fdata-sets.html=02%7C01%7C%7C685b06dde1ce4
>c6a215f08d484546721%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636278945
>430535468=S1AMDnRVAKtdy0QGfKv24JZ%2FEj5CghHZvx991%2Ff1UxE%3D
>d=0
>
>Douglas
>
>On Sat, Apr 15, 2017 at 9:30 AM, Christofer Dutz
><christofer.d...@c-ware.de>
>wrote:
>
>> We should ask Apache Infra Š they have several streams of publically
>> available data. Not financial data, but stuff we could display.
>>
>> Chris
>>
>> Am 15.04.17, 14:36 schrieb "Peter Ent" <p...@adobe.com>:
>>
>> Hi,
>>
>> A couple of examples no longer work: DataBinding et al and
>> MobileTrader et al. These examples depend on an API URL from Yahoo
>> Financial which seems to no longer be working.
>>
>> Does anyone know of a free, Apache license compatible, API to query
>> financial data? This data does not have to be current, just something we
>> can use for examples of HTTPService.
>>
>>     Barring that, if anyone knows another source of data (Apache license
>> compatible) that would be interesting in an example, please share and
>> perhaps we can make an example around it.
>>
>> Thanks,
>> Peter Ent
>> Adobe Systems/Apache Flex Project.
>>
>>
>>

[FlexJS] Examples

[Peter Ent]

Hi,

A couple of examples no longer work: DataBinding et al and MobileTrader et al. 
These examples depend on an API URL from Yahoo Financial which seems to no 
longer be working.

Does anyone know of a free, Apache license compatible, API to query financial 
data? This data does not have to be current, just something we can use for 
examples of HTTPService.

Barring that, if anyone knows another source of data (Apache license 
compatible) that would be interesting in an example, please share and perhaps 
we can make an example around it.

Thanks,
Peter Ent
Adobe Systems/Apache Flex Project.

Re: [FlexJS] Layouts

[Peter Ent]

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 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: 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.247.n4.nabble.com%2FFlexJS-Layouts-tp61120p61128.html=02%7C01%7C%7C34cce7f02f334aa64e9d08d4841e895d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636278714068445857=sewthVxykzQHYESCOCbR%2Fj2RVNvPWXDyiwPVVcTnYag%3D=0
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] Layouts

[Peter Ent]

Hi,

I just pushed feature/layouts branch for your consideration. The changes in 
this branch affect how layouts are run. I moved code from GroupView into 
LayoutBase, making layouts more autonomous. That is, layouts now listen for the 
events they need rather than relying on GroupView to listen for the events and 
trigger the layout. This will make it possible for layouts to work with other 
types of components that are not container based.

If you check out this branch, flex-asjs should build (ant and maven) as should 
the examples (ant and maven). I test DataBinding, Chart, DataGrid, 
DateControls, and MDLExample. I know that the Mobile package does not work 
correctly. FlexJSStore runs but has some layout issues to address, but I don't 
think it will change any fundamentals with the core changes to layouts.

Regards,
Peter

Re: [4/6] git commit: [flex-asjs] [refs/heads/develop] - replace existing format bead if it exists

[Peter Ent]

It is supposed to work like this:

A: You may have zero or more beads defined inline in MXML for your
component using  property.

B: You may have zero or more beads defined in CSS for your component.

When addElement is called on your component, it will add the underlying
element to the display list and then call addedToParent() on the component
and process the inline beads first (situation A).

Once the inline beads are added (and their strand setters are called), the
"standard" set of beads may be added: model, view, and controller. This
done by first seeing if one is already on the beads list (e.g. added
inline). If it is not present, then the CSS (situation B) is examined
using ValuesManager. If a bead class is found, it is instantiated and then
added to the strand's beads list (the bead's strand setter is called).

When the "standard" beads have been added, addedToParent() finished by
dispatching "beadsAdded" on the strand.

C: Any beads in CSS that are non-standard are not automatically added.

If your component class overrides addedToParent() it should call
super.addedToParent() right away to load the inline and standard beads.

After calling super.addedToParent(), your component can then load custom
beads (e.g., a date formatter) by following the same pattern
addedToParent() follows: Using an interface type, does the bead already
exist on the strand (added inline)? If not, is there a class for it in CSS
via ValuesManager? If so, create a new instance and add it to the bead
list.

The reason for this sequence is to allow inline beads to override default
beads (default beads being added in addedToParent()). So if your component
loads the ABCBead in its addedToParent() override, I can use your
component and put in my custom DEFBead which either extends ABCBead or
implements IMyCustomBead interface (which ABCBead should also implement).
This bead will be loaded early (in super.addedToParent()) and will not get
replaced by the default later.

Since "beadsAdded" was already dispatched, your component might want to
either dispatch "initComplete" or some custom event. Note that the
container classes (GroupBase/Group, ContainerBase/Container, etc.) all
dispatch "initComplete" so if your basing your component on a container
type, you don't have to dispatch "initComplete" but you can dispatch a
custom event.

I hope that helps.
‹peter

On 4/18/17, 4:41 AM, "jus...@classsoftware.com" 
wrote:

>Hi,
>
>> It looks to related to a bug in getBeadByType.
>
>And the reason for that is the addBead call to add DateFormatDDMMBead
>is called after DateField addedToParent is called Or if you prefer at the
>time addedToParent is called the beads have not been added so it will add
>the one defined in the CSS. Only the first iFormat bead will have an
>effect.
>
>Thanks,
>Justin

[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

Re: [FlexJS] Table

[Peter Ent]

I would imagine a DataTable would be what you are suggesting. 

Peter 


> On Apr 22, 2017, at 6:09 AM, piotrz  wrote:
> 
> Hi Carlos!
> 
> +1 for this :)
> 
> Piotr
> 
> 
> 
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.247.n4.nabble.com%2FRe-FlexJS-Table-tp61274p61283.html=02%7C01%7C%7Cd10ec7063e224c5e08d008d48967b7c4%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636284525944460193=bH19Fviywf2N%2Fikg6PnLgcLFKjMkemL9uLXxPjwktsY%3D=0
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] Table

[Peter Ent]

Hi,

I've just committed/pushed a new FlexJS component (and its helpers) to the HTML 
project. It is the  component. I saw that there were JS-only 
fragments of Table present and decided to make an official SWF/JS version.

The idea is to create a clean  HTML structure and mimic it in the Flash 
Player. For a first-pass, it does a pretty good job.

It works something like this:



 
   
 
 



 






You can place nearly anything inside of a cell (I tried it with another Table 
and Groups). If you need it to scroll, place it within  and add a 
 bead to the Container.

Regards,
Peter

Re: [FlexJS] Examples

[Peter Ent]

Thanks. I'll take a look.
—peter

On 4/21/17, 12:36 PM, "Alex Harui" <aha...@adobe.com> wrote:

>It appears the format changed.  I got it working for DataBindingExample in
>the dual branch.
>
>-Alex
>
>On 4/17/17, 9:47 AM, "Alex Harui" <aha...@adobe.com> wrote:
>
>>I think the service may have been temporarily down or the format changed.
>>See this, for example:
>>
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fquery.ya
>>h
>>ooapis.com%2Fv1%2Fpublic%2Fyql%3Fq%3Dselect%2520*%2520from%2520yahoo.fina
>>n
>>=02%7C01%7C%7Ca55b41534c114adcef4808d485b18254%7Cfa7b1b5a7b34438794a
>>e
>>d2c178decee1%7C0%7C0%7C636280444823641555=PSX2eoGfTUEG4Uhag8Cheala7
>>a
>>tUJquzmxnt1jPygo8%3D=0
>>ce.quotes%20where%20symbol%20in%20(%22YHOO%22)=json=store%3A%2
>>F
>>%
>>2Fdatatables.org%2Falltableswithkeys=
>>
>>
>>-Alex
>>
>>On 4/17/17, 6:07 AM, "Peter Ent" <p...@adobe.com> wrote:
>>
>>>Thanks for the note about the US Census data. Census data, coupled with
>>>maps, always provides interesting information. It does however, take a
>>>bit
>>>of time to figure out what to query, how to query it, and how to present
>>>it. I think we could work this into a very nice example at some point.
>>>
>>>Does anyone know of something more real-time?
>>>
>>>‹peter
>>>
>>>On 4/15/17, 10:48 AM, "1600...@gmail.com on behalf of Douglas McCarroll"
>>><1600...@gmail.com on behalf of list.apache-flex@brightworks.com>
>>>wrote:
>>>
>>>>IIRC, James Ward's benchmarking app...
>>>>
>>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ja
>>>>m
>>>>e
>>>>s
>>>>ward.com%2F2007%2F04%2F30%2Fajax-and-flex-data-loading-benchmarks%2F
>>>>t
>>>>a
>>>>=
>>>>02%7C01%7C%7C685b06dde1ce4c6a215f08d484546721%7Cfa7b1b5a7b34438794aed2c
>>>>1
>>>>7
>>>>8
>>>>decee1%7C0%7C0%7C636278945430535468=jAuct%2B8oS4FnFAX9WC3xFvxZFpG
>>>>C
>>>>L
>>>>G
>>>>UvWvKgzJMPe2s%3D=0
>>>>
>>>>... used US Census data.
>>>>
>>>>Sadly, the benchmark app doesn't seem to work any more, but I found
>>>>this
>>>>via google:
>>>>
>>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ce
>>>>n
>>>>s
>>>>u
>>>>s.gov%2Fdata%2Fdevelopers%2Fdata-sets.html=02%7C01%7C%7C685b06dde1
>>>>c
>>>>e
>>>>4
>>>>c6a215f08d484546721%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636278
>>>>9
>>>>4
>>>>5
>>>>430535468=S1AMDnRVAKtdy0QGfKv24JZ%2FEj5CghHZvx991%2Ff1UxE%3D
>>>>r
>>>>v
>>>>e
>>>>d=0
>>>>
>>>>Douglas
>>>>
>>>>On Sat, Apr 15, 2017 at 9:30 AM, Christofer Dutz
>>>><christofer.d...@c-ware.de>
>>>>wrote:
>>>>
>>>>> We should ask Apache Infra Š they have several streams of publically
>>>>> available data. Not financial data, but stuff we could display.
>>>>>
>>>>> Chris
>>>>>
>>>>> Am 15.04.17, 14:36 schrieb "Peter Ent" <p...@adobe.com>:
>>>>>
>>>>> Hi,
>>>>>
>>>>> A couple of examples no longer work: DataBinding et al and
>>>>> MobileTrader et al. These examples depend on an API URL from Yahoo
>>>>> Financial which seems to no longer be working.
>>>>>
>>>>> Does anyone know of a free, Apache license compatible, API to
>>>>>query
>>>>> financial data? This data does not have to be current, just something
>>>>>we
>>>>> can use for examples of HTTPService.
>>>>>
>>>>> Barring that, if anyone knows another source of data (Apache
>>>>>license
>>>>> compatible) that would be interesting in an example, please share and
>>>>> perhaps we can make an example around it.
>>>>>
>>>>> Thanks,
>>>>> Peter Ent
>>>>> Adobe Systems/Apache Flex Project.
>>>>>
>>>>>
>>>>>
>>>
>>
>

Re: [FlexJS] Panel

[Peter Ent]

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 Panel that it requires scrolling, these items do not
scroll. You can consider the fixed scrollbars in the SWF version to be
chrome pieces too.

Let's say you wanted to have a special type of title bar that did have
images and other buttons. If your component implements IChrome, then you
could add it to a container that knew how to handle chrome:


   
   


Where your MyTitleBar.mxml might be:



   




Then the ChromedContainer would place the MyTitleBar at the top of the
container outside of the content area. But you could also do this as:



   



   
 
   
   
 


This would accomplish the same thing. The problem with "chrome" is that
you could put the chrome into the middle of the container and then I'm not
sure how the layout algorithm would handle that.

‹peter


On 3/9/17, 11:16 AM, "PKumar"  wrote:

>ChromeContainer should be fine. We should be able to modify the panel
>title
>bar style as header corlor , border etc.
>
>Can Panel title bar contain other controls as image , button , check box?
>
>
>On 09-Mar-2017 9:37 PM, "piotrz [via Apache Flex Development]" <
>ml-node+s247n60286...@n4.nabble.com> wrote:
>
>Hi Peter,
>
>Let's say that you reconstructed Panel using new Group container - How can
>we use there Chrome ?
>
>I would go with ChromedContainer.
>
>Piotr
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>
>
>--
>If you reply to this email, your message will be added to the discussion
>below:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Panel-
>tp60285p60286.html
>To start a new topic under Apache Flex Development, email
>ml-node+s247n1...@n4.nabble.com
>To unsubscribe from Apache Flex Development, click here
>.jtp?macro=unsubscribe_by_code=1=cHJhc2hha3VtYXJAZ21haWwuY29tfDF
>8LTU0MTcyMzE2NA==>
>.
>NAML
>.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.
>naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-na
>bble.view.web.template.NodeNamespace=notify_subscribers%21nabb
>le%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21
>nabble%3Aemail.naml>
>
>
>
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Panel-tp60285p
>60287.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] Panel

[Peter Ent]

Hi,

I'm trying to determine if "chrome" is a necessity as part of Container or if a 
specialty "ChromedContainer" should be made (or if at all).

Panel is one component that uses chrome (the TitleBar and ControlBar implement 
IChrome). Is Panel used a lot?

As an alternative, 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] Panel

[Peter Ent]

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 being
recognized!! It looks like Panel is special-casing it somehow, but right
now Panel is very messed up for me due to changes I've made in my
workspace, so I'm not really certain what is going on it with.

‹peter

On 3/9/17, 2:34 PM, "yishayw"  wrote:

>I think it makes sense to start the coordinates axis below the titlebar.
>In
>ExtJS they have the concept of docked components such as toolbars and
>titles. So I think you can do (I changed syntax to pseudo-mxml)
>
>
>
>
>docked="top"/>
>
>
>In other words, docked items override the container's layout and change
>the
>coordinates axis point of origin.
>
>
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Panel-tp60285p
>60307.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Coordinate Space

[Peter Ent]

Hi,

I think I understand this now.

When you set x, y on a component, you will be setting the left and top
styles on the HTML element. Setting these properties will no longer set
the position style (which will remain unchanged it has been set).

The Container classes will no longer have a default layout. This means you
can use Container and place items in there and style or layout everything
using CSS if you want to go that route. Some of that may not be supported
by the SWF version, however. At least not right away.

The BasicLayout will set the container's position to "relative" if it is
not already set. Then it will go through the children and set their
position styles to "absolute". This way the left and top (as well as
bottom and right) styles will work. Without setting a position of
"absolute" those styles will not locate the components (using a position
of "relative" means that items will be placed in relation to each other,
which you can now do if you do not use the BasicLayout and set position to
"relative" yourself).

NOTE: unlike normal HTML/CSS, FlexJS containers are sized by their
contents: if you do not give a container a size, the layout will determine
the size of that container. In HTML/CSS, you would probably see the
container/div span the entire page by default or have a zero height by
default depending on the placement of the children.

You need to be aware of how margin affects placement. When using absolute
position along with margin, the item will be offset by the margin
value(s). For example, if you set left:10 (or item.x = 10) and add a
margin-left:10, then item's content position will be 20. This will be the
value the x property returns. If you are migrating from Flex 4, just leave
margin settings out.

Also, for BasicLayout (aka, a container with position:relative|absolute
and children with position:absolute), container's padding has no effect.
That is, a container with padding:10 will not change the location of any
of the children placed with BasicLayout. The padding style will affect
other types of layouts.

For the Flexbox layouts, as long as you do not set the left, top (x, y)
style (or property) the items will be placed correctly. Pixel and
percentage dimensions will be honored as well. When you examine the HTML
DOM, you should not see any position or placement styles on the items in a
Flexbox type layout.

Essentially, you should be able to do a lot more of the layout in CSS if
you are targeting HTML/CSS/JS as your main platform. The layout beads are
helpful to do programmatic placement and are how the SWF version will know
what to do.

Finally, there will probably be some new container components. Not sure
what just yet, but we need to have very light ones and others that handle
scrolling and chrome. Stay tuned.

I now need to make these changes, which I will do in a separate branch.

Thank you for your input and suggestions. I think this will solve our
layout issues 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 JS might yield
>different results if padding, border, and margins are set on the parent
>element. If you don't want your coordinates messed with, then nest your
>containers and apply padding, border, background, etc to the outer
>container. And definitely do not use margins.
>
>If you want to use CSS to position items, use the top, left, bottom, right
>style properties (and margin on the children). On the SWF side, these
>styles will look at the parent's padding and border values and position
>the elements accordingly (it will use x, y). If you intend to read the
>values back, they will not necessarily be what you set since the values
>are determined by the parent's padding and border as well as the child's
>own margin values.
>
>You need to specify layouts inside containers so that the SWF side knows
>what to do. If you don't intend on using the SWF output, you can just set
>the style on the container and let HTML/CSS/JS take care of it. If you
>supply a layout bead, the bead will set the display, positioning, and
>other styles on the container as necessary and may even impose styles on
>the children for the JS side. The SWF side is purely programmatic to mimic
>the JS side and it will be as close as possible but may need to be
>multiple passes.
>
>Scrolling provides more challenges for the SWF side as nested containers
>need to be used with the outer container used to mask the inner which is
>then repositioned to simulate scrolling. When you want scrolling, use
>ScrollableContainer. This class simply sets overflow:auto on the JS side.
>If you do not want or care about the SWF output, then just s

[FlexJS] Group container

[Peter Ent]

Hi,

Today I've introduced the FlexJS Group container - a lightweight alternative to 
the Container class. The Group container provides hardly more than  on the 
HTML platform and the code generated using it should produce a DOM without the 
nested  elements that Container gives you. Further, Group does not have a 
default layout. This allows you to size and position the Group's children using 
CSS.

Along with this commit is an updated BasicLayout designed to work with Group 
(the VerticalFlexLayout and HorizontalFlexLayout beads should work as well).

The SWF side for Group may or may work too well at the moment - I have to 
complete updates to BasicLayout for that to work correctly.

The real power from Group will come when I check in additional changes to 
UIBase and some of the other core components. Right now some of those 
components automatically set an element's position style to either "absolute" 
or "relative". To provide a better experience on HTML/CSS/JS, FlexJS code 
should not be setting the position style unless it is done by a layout (or done 
via CSS).  I will also be changing the View (the one we use as MyInitialView in 
the examples) 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: git commit: [flex-asjs] [refs/heads/develop] - Introducing the Group container.

[Peter Ent]

Will do on the my check-in.
‹peter

On 3/6/17, 2:28 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote:

>Hi Peter,
>
>Nice job! Could you please add @productversion FlexJS 0.8 ? I think it can
>be useful in future.
>
>Thanks,
>Piotr
>
>2017-03-06 19:15 GMT+01:00 <p...@apache.org>:
>
>> Repository: flex-asjs
>> Updated Branches:
>>   refs/heads/develop 8fe2f0831 -> 79d45cba0
>>
>>
>> Introducing the Group container.
>>
>>
>> Project: http://git-wip-us.apache.org/repos/asf/flex-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
>> Commit: 79d45cba0616e394fddb68835859b1ffc87e6c48
>> Parents: 8fe2f08
>> Author: Peter Ent <p...@apache.org>
>> Authored: Mon Mar 6 13:15:34 2017 -0500
>> Committer: Peter Ent <p...@apache.org>
>> Committed: Mon Mar 6 13:15:34 2017 -0500
>>
>> --
>>  .../projects/HTML/src/main/flex/HTMLClasses.as  |   4 +-
>>  .../main/flex/org/apache/flex/core/GroupBase.as | 301
>>+++
>>  .../src/main/flex/org/apache/flex/html/Group.as |  92 ++
>>  .../org/apache/flex/html/beads/GroupView.as | 269 +
>>  .../flex/html/beads/layouts/BasicLayout.as  |  73 +
>>  .../HTML/src/main/resources/basic-manifest.xml  |   1 +
>>  .../HTML/src/main/resources/defaults.css|  10 +
>>  7 files changed, 689 insertions(+), 61 deletions(-)
>> --
>>
>>
>> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
>> 79d45cba/frameworks/projects/HTML/src/main/flex/HTMLClasses.as
>> --
>> diff --git a/frameworks/projects/HTML/src/main/flex/HTMLClasses.as
>> b/frameworks/projects/HTML/src/main/flex/HTMLClasses.as
>> index bfe204b..41cb877 100644
>> --- a/frameworks/projects/HTML/src/main/flex/HTMLClasses.as
>> +++ b/frameworks/projects/HTML/src/main/flex/HTMLClasses.as
>> @@ -26,8 +26,7 @@ package
>>   *  from the classes specified in manifest.xml.
>>   */
>>  internal class HTMLClasses
>> -{
>> -
>> +{
>>  import org.apache.flex.html.ToolTip; ToolTip;
>> import 
>>org.apache.flex.html.accessories.NumericOnlyTextInputBead;
>> NumericOnlyTextInputBead;
>> import org.apache.flex.html.beads.DispatchInputFinishedBead;
>> DispatchInputFinishedBead;
>> @@ -45,6 +44,7 @@ internal class HTMLClasses
>> }
>> import org.apache.flex.html.beads.ComboBoxView; ComboBoxView;
>>  import org.apache.flex.html.beads.ContainerView; ContainerView;
>> +   import org.apache.flex.html.beads.GroupView; GroupView;
>> COMPILE::SWF
>> {
>> import org.apache.flex.html.beads.ControlBarMeasurementBead;
>> ControlBarMeasurementBead;
>>
>> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
>> 79d45cba/frameworks/projects/HTML/src/main/flex/org/apache/
>> flex/core/GroupBase.as
>> --
>> diff --git 
>>a/frameworks/projects/HTML/src/main/flex/org/apache/flex/core/GroupBase.a
>>s
>> 
>>b/frameworks/projects/HTML/src/main/flex/org/apache/flex/core/GroupBase.a
>>s
>> new file mode 100644
>> index 000..7b945cc
>> --- /dev/null
>> +++ b/frameworks/projects/HTML/src/main/flex/org/apache/flex/
>> core/GroupBase.as
>> @@ -0,0 +1,301 @@
>> +///
>> /
>> +//
>> +//  Licensed to the Apache Software Foundation (ASF) under one or more
>> +//  contributor license agreements.  See the NOTICE file distributed
>>with
>> +//  this work for additional information regarding copyright ownership.
>> +//  The ASF licenses this file to You under the Apache License, Version
>> 2.0
>> +//  (the "License"); you may not use this file except in compliance
>>with
>> +//  the License.  You may obtain a copy of the License at
>> +//
>> +//  http://www.apache.org/licenses/LICENSE-2.0
>> +//
>> +//  Unless required by applicable law or agreed to in writing, software
>> +//  distributed under the License is distributed on an "

Re: [FlexJS] Group container

[Peter Ent]

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 thinking that Panel would be a good case for a composite component and
maybe even move it into Express. In theory, you can compose a Panel from:

 with VerticalFlexLayout
 with Horizontal Flex Layout for the Title Bar
 to provide scrollable area
 with Horizontal Flex Layout for the Control Bar


We'll see how this goes.
‹peter

On 3/6/17, 5:02 PM, "Alex Harui"  wrote:

>
>
>On 3/6/17, 1:26 PM, "piotrz"  wrote:
>
>>Hi Peter,
>>
>>It looks awesome. Cause if I'm enough skilled in CSS I can do whatever
>>layout I want and I don't need to know any other one. - In theory. :)
>
>True, but like with everything else in FlexJS, we are trying to
>encapsulate common patterns and make them easier to use.
>
>So for example if you have 3 children in a container and want to make the
>first one stretchy,  you might have to write:
>
>
>  
>  
>  
>
>
>Whereas with a layout you could write:
>
>  
>
>  
>
>
>That way you don't have to remember the names of the styles or look up how
>to do it.
>
>Hopefully our Layouts will essentially do just that once Peter's done with
>this refactor.
>
>Of course, I could be wrong...
>-Alex
>

Re: [FlexJS] Group container

[Peter Ent]

Thanks for the feedback!

As I go through the examples, I see that we (mostly me) created a number
of nested elements, such as a  for an item renderer.
That makes it more difficult to lay out since the content of the div is
not always set to fill the div's space. I think each of the components and
renderers need to be examined and updated.

—peter

On 3/7/17, 10:04 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
<carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> wrote:

>Hi Peter, I think this awesome. get rid of the hardcoded styles in
>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>:
>
>> 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 thinking that Panel would be a good case for a composite component
>>and
>> maybe even move it into Express. In theory, you can compose a Panel
>>from:
>>
>>  with VerticalFlexLayout
>>  with Horizontal Flex Layout for the Title Bar
>>  to provide scrollable area
>>  with Horizontal Flex Layout for the Control Bar
>> 
>>
>> We'll see how this goes.
>> ‹peter
>>
>> On 3/6/17, 5:02 PM, "Alex Harui" <aha...@adobe.com> wrote:
>>
>> >
>> >
>> >On 3/6/17, 1:26 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>> >
>> >>Hi Peter,
>> >>
>> >>It looks awesome. Cause if I'm enough skilled in CSS I can do whatever
>> >>layout I want and I don't need to know any other one. - In theory. :)
>> >
>> >True, but like with everything else in FlexJS, we are trying to
>> >encapsulate common patterns and make them easier to use.
>> >
>> >So for example if you have 3 children in a container and want to make
>>the
>> >first one stretchy,  you might have to write:
>> >
>> >
>> >  
>> >  
>> >  
>> >
>> >
>> >Whereas with a layout you could write:
>> >
>> >  
>> >
>> >  
>> >
>> >
>> >That way you don't have to remember the names of the styles or look up
>>how
>> >to do it.
>> >
>> >Hopefully our Layouts will essentially do just that once Peter's done
>>with
>> >this refactor.
>> >
>> >Of course, I could be wrong...
>> >-Alex
>> >
>>
>>
>
>
>-- 
>
>Carlos Rovira
>Director General
>M: +34 607 22 60 05
>http://www.codeoscopic.com
>http://www.avant2.es
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.

Re: [FlexJS] Group container

[Peter Ent]

As I go through FlexJS, I am wondering if we need to continue the idea of
chrome. Chrome is not something built into HTML/CSS/JS, it is artificial.
We use it for the title bar and control bar in a Panel, but a Panel can be
composed of nesting Groups and applying the correct styles.

In Flex, scroll bars were chrome but they do not have that status in HTML.
In fact, just using overflow:auto will get scrollbars (when needed) on a
Group (aka ). To get scrollbars on the SWF side we do need to embed a
scrollable area within an area that will mask the overflowing bits and
provide interactive scroll bars.

In my mind, Container serves the purpose of allowing those apps that run
on SWF or SWF/JS platforms to have scrollable content. If you were to run
only on JS, then you don't need Container, you can just style the div
provided by Group. But we need to give SWF a hint which can be done by
using Container instead of Group when you suspect the content will need to
be scrolled. The CSS style for Container can have overflow:auto set and
otherwise extend Group for the JS side. The SWF side can nest
DisplayObjectContainers and put scrollbars into the outer container and
use it as a mask. 

Panel can be composed of an outer Group, with a Group for the title bar, a
Container for the content, and another Group for the control bar. If
anyone really needs to have chrome pieces they can do the same thing.

What do you think? Should Container continue to support chrome (aka,
components 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, such as a  for an item renderer.
>That makes it more difficult to lay out since the content of the div is
>not always set to fill the div's space. I think each of the components and
>renderers need to be examined and updated.
>
>—peter
>
>On 3/7/17, 10:04 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
><carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com>
>wrote:
>
>>Hi Peter, I think this awesome. get rid of the hardcoded styles in
>>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>:
>>
>>> 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 thinking that Panel would be a good case for a composite component
>>>and
>>> maybe even move it into Express. In theory, you can compose a Panel
>>>from:
>>>
>>>  with VerticalFlexLayout
>>>  with Horizontal Flex Layout for the Title Bar
>>>  to provide scrollable area
>>>  with Horizontal Flex Layout for the Control Bar
>>> 
>>>
>>> We'll see how this goes.
>>> ‹peter
>>>
>>> On 3/6/17, 5:02 PM, "Alex Harui" <aha...@adobe.com> wrote:
>>>
>>> >
>>> >
>>> >On 3/6/17, 1:26 PM, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>>> >
>>> >>Hi Peter,
>>> >>
>>> >>It looks awesome. Cause if I'm enough skilled in CSS I can do
>>>whatever
>>> >>layout I want and I don't need to know any other one. - In theory. :)
>>> >
>>> >True, but like with everything else in FlexJS, we are trying to
>>> >encapsulate common patterns and make them easier to use.
>>> >
>>> >So for example if you have 3 children in a container and want to make
>>>the
>>> >first one stretchy,  you might have to write:
>>> >
>>> >
>>> >  
>>> >  
>>> >  
>>> >
>>> >
>>> >Whereas with a layout you could write:
>>> >
>>> >  
>>> >
>>> >  
>>> >
>>> >
>>> >That way you don't have to remember the names of the styles or look up
>>>how
>>> >to do it.
>>> >
>>> >Hopefully our Layouts will essentially do just that once Peter's done

Re: [FlexJS] Coordinate Space

[Peter Ent]

How about this…

If you are migrating from Flex 4 to FlexJS, then you:
- use (x,y) to set position
- do not put margins on your elements (margins weren't in Flex anyway)
- Use PaddedContainer[1] whenever you need a Container.
- you can safely apply padding to PaddedContainer and the child elements'
(x,y) will not be adjusted.

If you are creating things from scratch:
- only use (x,y) in Containers[2] where you do not set the Container's
padding and you do not set margins on your elements. Otherwise the value
of (x,y) will be adjusted by the margins and padding (and border thickness
as per HTML).
- instead, set the left, top, right, bottom styles to position elements.
- or use layouts and do not set any positioning.

[1] PaddedContainer will be the current Container, just renamed to reflect
the fact that it can use padding values and will still deliver (x,y)
unchanged unless you put margins on your elements. It does this because it
nests one container inside another with the inner container offset by the
padding values. PaddedContainer will automatically use a scrollable
viewport as its default so there will no extra beads needed. You can
replace the viewport with the non-scrollable one.

[2] Regular Container will be simplified to be a single containing
element. When you use this and give it padding, elements placed into it
will be offset by the padding and their (x,y) will be calculated
accordingly. You should use left, top, right, bottom styles to place these
items or use layouts.

I recommend that Container not allow scrolling and we should instead
introduce ScrollableContainer that will provide scrollbars on the SWF side
and set overflow:auto on the JS side. If you do not care about the SWF
side, then use Container but set overflow:auto in its style. Having
scrollable content on the SWF side involves nested containers.
ScrollableContainer on the SWF side will be nested containers, but padding
will apply to the inner content area. This will make left, top, right,
bottom styles work consistently between SWF and JS while delivering (x,y)
as offset values same as Container.

Regards,
Peter

On 3/1/17, 11:52 AM, "Alex Harui" <aha...@adobe.com> wrote:

>I think there are a couple of things going on:
>
>1) Some folks have asked for an API that reduces migration pain when
>porting existing Flex apps.
>2) We want the thinnest possible overhead over hand-coded HTML/JS/CSS.
>
>These two goals are in opposition because Flex:
>A) didn't support margins
>B) had properties for x,y,width,height instead of styles
>C) used % differently for width and height
>D) you "get what you set".  If you set x=0, then on the next line of code
>(x == 0) is true.
>
>Meanwhile, it has been my experience that there are some pain points in
>HTML layouts, like making one object stretch to fill all remaining space
>horizontally or vertically.
>
>It feels like in native HTML/JS you set styles and read properties.  There
>is no read/write x and y properties.  So one option is to hide the x and y
>properties.  But that would probably make migration harder.
>
>So maybe, the first question is:
>What should x and y set, and what should it report back?
>
>Now, IMO, it is totally fine for different component sets to have
>different rules.  In the "dual" branch, I've split the more Flex-like
>components (Label, Container, Button) out into the Basic.SWC and HTML.swc
>now contains the thin wrappers of HTMLElements Carlos made which may need
>more work in order to run on SWF, but have HTML element names like A, H1,
>Select, etc.
>
>For these direct HTMLElement-named components, maybe we really should hide
>x and y properties.  Then you'd have to set left or leftMargin
>appropriately instead of x.  And read back clientX and/or offsetX.
>
>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" <p...@adobe.com> wrote:
>
>>I agree with this. Now that these layouts and containers are really
>>getting used in a more practical way we can see what's going on.
>>
>>I was thinking that .x and .y would be "native" setters. On SWF, .x = 0
>>would read x back as 0 but on JS it might read back as 20, depending on
>>padding and border styles.
>>
>>Then .left, .top, .bottom, and .right would be universal and take
>>padding,
>>margin, and border into consideration so that both SWF and JS got the
>>same
>>result.
>>
>>Since most layouts are built in SWF to mimic JS, the SWF side code would
>>use the native .x and .y to position the elements so that each pass would
>>not have to retri

[FlexJS] Coordinate Space

[Peter Ent]

Hi,

In an effort to clean up Container and layouts, we need to look at the 
coordinate system of FlexJS. Since the goal is to have the SWF side mimic the 
JS side, perhaps we should visit the "coordinate system" of HTML. You'll find 
an Apache Paste at [1] below. If you could run that and make any changes you'd 
like and see what you think.

Basically: in Flex 4 and Flash, when you position something at (0,0) and you 
read its x coordinates back, it is at (0,0). In HTML land, that isn't exactly 
how it works. There are several things that influence the position of an 
element: the position style of its parent, the padding of its parent, the 
margin style of the element and the position style of the element.

If you set a div to have a padding of 10 and an element to have 
position:relative with left:0 it will appear 10 pixels from the left edge of 
the div. That's what would expect. However, if you try to read that element's 
position, you need to use its read-only property, offsetLeft. That value will 
be 10, not 0.

How would you feel if FlexJS worked the same way?








When you ask for testButton's x or y values it would return 10 due to the 
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

Re: [FlexJS] MDL Help Needed

[Peter Ent]

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 some reason compiler is not generating second span:
> 
> 
> - this span will be missing in HTML.
> 
> 
> If you launch even simpler application than my example [2] you will see in
> the HTML DOM that second span is missing:
> 
> 
>  
> 
> [1] 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2F1drv.ms%2Fu%2Fs!ApVpLyjpHDC2zQBWadDWCpbMMBKM=02%7C01%7C%7Ce4cd079979434e380a9d08d479283621%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63620989299044=%2BTzTxfZpu9sHw3x4gZfMliboJRM70Hubh9QA0tHxCBY%3D=0
> [2] 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2F7ImM=02%7C01%7C%7Ce4cd079979434e380a9d08d479283621%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63620989309056=yo6gCdGzzUvYYy%2BcxBjgnhODWW7RhB44ijWLmaEgR7U%3D=0
> 
> Piotr
> 
> 
> 
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.247.n4.nabble.com%2FFlexJS-MDL-Help-Needed-tp60946p60950.html=02%7C01%7C%7Ce4cd079979434e380a9d08d479283621%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63620989309056=FDbFl1ZyQ25CZ1b1f%2BWqpms4RwUx0B9Q2lk1ry7y%2FAQ%3D=0
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] feature/chart_work status

[Peter Ent]

I've been working on this most of the day. I think there is something more
fundamental going on that this example has uncovered. There appear to be
duplicate events happening causing event handlers to be registered
multiple times. I'm not comfortable releasing this yet into develop.

I'll continue 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, "piotrz" <piotrzarzyck...@gmail.com> wrote:
>
>>Hi Peter,
>>
>>I just tried MDLExample and it look good, but MDLDynamicTabsExample has
>>same
>>problem. Something is going wrong when Tab is being added.
>>
>>Piotr
>>
>>
>>
>>-
>>Apache Flex PMC
>>piotrzarzyck...@gmail.com
>>--
>>View this message in context:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>e
>>x-development.247.n4.nabble.com%2FFlexJS-feature-chart-work-status-tp
>>6
>>1035p61036.html=02%7C01%7C%7Ceab9e55a09c44c3abba808d47d38ecc1%7Cfa7b
>>1
>>b5a7b34438794aed2c178decee1%7C0%7C0%7C636271130849952954=WQwjZQCjhY
>>E
>>ugbdoLNyqOtuIJX%2FtAh94muXgCW9GKIs%3D=0
>>Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [FlexJS] feature/chart_work status

[Peter Ent]

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 is-active set and the new panel gets
is-active set; no other tab or panel has is-active set.

Then I click from the new tab to a previous tab and the new tab has
is-active removed and the other tab has is-active set. But the new panel
is still is-active while the panel corresponding to the tab I clicked also
has is-active set. I'm trying to figure out where that is happening, but
the tab selection code isn't being called as far as I can tell. Is it now
just happening in CSS?

There is also a number of extra events happening, but I don't think that
is specific to the MDL code. Since a lot of this code is reused for
multiple components, its a little difficult to tell what is actually
happening. 

Thanks for any help or advice you can give.

‹peter

On 4/7/17, 2:46 PM, "piotrz"  wrote:

>Peter,
>
>If you stack on something let me know I will have some free cycles on
>Sunday. 
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-feature-chart-work-status-tp6
>1035p61041.html=02%7C01%7C%7Cc624155aceee4a08d1b608d47de7b1ad%7Cfa7b1
>b5a7b34438794aed2c178decee1%7C0%7C0%7C636271881449970250=K4snMf9mXOg
>z7a80ci98IBhOckcZxWuv1LxhhOP3P0M%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layouts

[Peter Ent]

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 done I will work on updating
the Wiki.

Thanks,
Peter

On 4/13/17, 12:06 PM, "Peter Ent" <p...@adobe.com> wrote:

>Hi,
>
>I just pushed feature/layouts branch for your consideration. The changes
>in this branch affect how layouts are run. I moved code from GroupView
>into LayoutBase, making layouts more autonomous. That is, layouts now
>listen for the events they need rather than relying on GroupView to
>listen for the events and trigger the layout. This will make it possible
>for layouts to work with other types of components that are not container
>based.
>
>If you check out this branch, flex-asjs should build (ant and maven) as
>should the examples (ant and maven). I test DataBinding, Chart, DataGrid,
>DateControls, and MDLExample. I know that the Mobile package does not
>work correctly. FlexJSStore runs but has some layout issues to address,
>but I don't think it will change any fundamentals with the core changes
>to layouts.
>
>Regards,
>Peter

Re: [FlexJS] ClippingViewport

[Peter Ent]

I must have forgotten to delete that. 

Peter 


> On Jul 30, 2017, at 7:20 AM, Harbs  wrote:
> 
> Is anyone using ClippingViewport?
> 
> It seems to be extraneous at this point. Viewport does clipping by default.
> 
> Thanks,
> Harbs

Re: [FlexJS] findPopupHost issue

[Peter Ent]

I'm taking a look at this. Would you mind filing a JIRA on this?

Thanks,
Peter

On 7/19/17, 1:23 PM, "PKumar"  wrote:

>​Panel , close event not firing on JS side. swf side it is working fine.
>This may  be an issue.​
>
>On Wed, Jul 19, 2017 at 11:00 PM, Prashant Kumar 
>wrote:
>
>> ​I am having a gird  with one view column. On clicking view link , i
>>want
>> to open a popup to view information. I was unaware  about actual use of
>> findPopupHost so i pass this. I was thinking it will work same as
>> PopupManager works.
>>
>>
>>
>> On Tue, Jul 18, 2017 at 8:02 PM, Alex Harui-2 [via Apache Flex
>> Development]  wrote:
>>
>>> I guess I should have been more clear.  FlexJS supports multiple
>>> component
>>> sets and runtimes.  An Application class is probably always going to be
>>> the entry point of an application, but there is no guarantee in any
>>> application that the Application class will be a display object or even
>>> the correct display object in the case of a multi-window desktop
>>> application.
>>>
>>> IPopUpHost is an API for a good place to hang popups, but it is only a
>>> coincidence that in the currently supported runtimes and most popular
>>> component sets that the Application is mapped to a display object and
>>> thus
>>> an IPopUpHost.  We should not presume that will always be the case.
>>>
>>> If you are looking for a good place to hang a popup you probably want
>>>it
>>> to popup over some UI component.  So, it is best to start with that
>>>known
>>> IUIBase and find an IPopUpHost that will display the popup over that
>>> IUIBase.  That way, your code will work in a multi-window app someday,
>>> and
>>> other future runtime environments as well.  And that's why
>>>findPopUpHost
>>> takes an IUIBase.  And in other future runtimes, it should be
>>>implemented
>>> to return a useful thing, but that thing may not be the Application
>>> instance.
>>>
>>> So, the recommended practice is to use UIUtils.findPopupHost and pass
>>>it
>>> an IUIBase that you want the popup to float over.
>>>
>>> HTH,
>>> -Alex
>>>
>>> On 7/17/17, 10:48 PM, "Yishay Weiss" <[hidden email]
>>> > wrote:
>>>
>>> >Even if the Application instance isn’t an IPopUpHost the method will
>>> just
>>> >return null, so the effect is the same as just doing (appInstance as
>>> >IPopUpHost). I suspect the method is being misused rather than there
>>> >being a problem with the method.
>>> >
>>> >From: Alex Harui>> >
>>> >Sent: Tuesday, July 18, 2017 8:33 AM
>>> >To: [hidden email]
>>>
>>> >> >
>>> >Subject: Re: [FlexJS] findPopupHost issue
>>> >
>>> >FWIW, it may not be safe to assume that Application will always be an
>>> >IPopUpHost, hence the utility function.
>>> >
>>> >Thanks,
>>> >-Alex
>>> >
>>> >On 7/17/17, 9:59 PM, "piotrz" <[hidden email]
>>> > wrote:
>>> >
>>> >>Hi Yishay,
>>> >>
>>> >>That's a good point - Application is itself an IPopupHost. I've asked
>>> him
>>> >>what is the use case for his host popup search.
>>> >>
>>> >>Thanks,
>>> >>Piotr
>>> >>
>>> >>
>>> >>
>>> >>-
>>> >>Apache Flex PMC
>>> >>[hidden email] 
>>> >>--
>>> >>View this message in context:
>>> >>https://na01.safelinks.protection.outlook.com/?url=http%
>>> 3A%2F%2Fapache-fl
>>> >>e
>>> 
>x-development.247.n4.nabble.com%2FFlexJS-findPopupHost-issue-tp633
>62p
>>>
>>> >>6
>>> 
>3366.html=02%7C01%7C%7Cbfd19d2deba646c64df208d4cd9c9798%7Cfa7b1b5
>a7b
>>>
>>> >>3
>>> 
>4438794aed2c178decee1%7C0%7C0%7C636359519816386890=CyeQuoJ0gVVl2
>UHU
>>>
>>> >>B
>>> >>W%2B6hbyDNw%2FOSFuswfzeLTqUf3c%3D=0
>>> >>Sent from the Apache Flex Development mailing list archive at
>>> Nabble.com.
>>> >
>>>
>>>
>>>
>>> --
>>> If you reply to this email, your message will be added to the
>>>discussion
>>> below:
>>> 
>>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-f
>>>lex-development.247.n4.nabble.com%2FFlexJS-=02%7C01%7C%7Cdbbe7d
>>>adabb14873df6408d4cecda439%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C
>>>636360830010202344=oGGZq5DF8kfi%2BpWLjJj75rbtkq7hz1hie9A2jQp3s5I%3
>>>D=0
>>> findPopupHost-issue-tp63362p63395.html
>>> To start a new topic under Apache Flex Development, email
>>> ml+s247n1...@n4.nabble.com
>>> To unsubscribe from Apache Flex Development, click here
>>> 
>>>>>flex-development.247.n4.nabble.com%2Ftemplate%2FNamlServlet.jtp%3Fma
>>>cro%3Dunsubscribe_by_code%26node%3D1%26code%3DcHJhc2hha3VtYXJAZ21haWwuY2
>>>9tfDF8LTU0MTcyMzE2NA=02%7C01%7C%7Cdbbe7dadabb14873df6408d4cecda439%

Re: [FlexJS] findPopupHost issue

[Peter Ent]

I fixed this and committed/pushed it on the develop branch.

The issue was that the TitleBar was dispatching "close" with bubbles=true.
This works fine on SWF but not on the HTML platform without some extra
work. So I just had PanelView intercept the event and dispatch one from
its strand. 

—peter

On 7/20/17, 1:45 PM, "Peter Ent" <p...@adobe.com.INVALID> wrote:

>I'm taking a look at this. Would you mind filing a JIRA on this?
>
>Thanks,
>Peter
>
>On 7/19/17, 1:23 PM, "PKumar" <prashaku...@gmail.com> wrote:
>
>>​Panel , close event not firing on JS side. swf side it is working fine.
>>This may  be an issue.​
>>
>>On Wed, Jul 19, 2017 at 11:00 PM, Prashant Kumar <prashaku...@gmail.com>
>>wrote:
>>
>>> ​I am having a gird  with one view column. On clicking view link , i
>>>want
>>> to open a popup to view information. I was unaware  about actual use of
>>> findPopupHost so i pass this. I was thinking it will work same as
>>> PopupManager works.
>>>
>>>
>>>
>>> On Tue, Jul 18, 2017 at 8:02 PM, Alex Harui-2 [via Apache Flex
>>> Development] <ml+s247n63395...@n4.nabble.com> wrote:
>>>
>>>> I guess I should have been more clear.  FlexJS supports multiple
>>>> component
>>>> sets and runtimes.  An Application class is probably always going to
>>>>be
>>>> the entry point of an application, but there is no guarantee in any
>>>> application that the Application class will be a display object or
>>>>even
>>>> the correct display object in the case of a multi-window desktop
>>>> application.
>>>>
>>>> IPopUpHost is an API for a good place to hang popups, but it is only a
>>>> coincidence that in the currently supported runtimes and most popular
>>>> component sets that the Application is mapped to a display object and
>>>> thus
>>>> an IPopUpHost.  We should not presume that will always be the case.
>>>>
>>>> If you are looking for a good place to hang a popup you probably want
>>>>it
>>>> to popup over some UI component.  So, it is best to start with that
>>>>known
>>>> IUIBase and find an IPopUpHost that will display the popup over that
>>>> IUIBase.  That way, your code will work in a multi-window app someday,
>>>> and
>>>> other future runtime environments as well.  And that's why
>>>>findPopUpHost
>>>> takes an IUIBase.  And in other future runtimes, it should be
>>>>implemented
>>>> to return a useful thing, but that thing may not be the Application
>>>> instance.
>>>>
>>>> So, the recommended practice is to use UIUtils.findPopupHost and pass
>>>>it
>>>> an IUIBase that you want the popup to float over.
>>>>
>>>> HTH,
>>>> -Alex
>>>>
>>>> On 7/17/17, 10:48 PM, "Yishay Weiss" <[hidden email]
>>>> <http:///user/SendEmail.jtp?type=node=63395=0>> wrote:
>>>>
>>>> >Even if the Application instance isn’t an IPopUpHost the method will
>>>> just
>>>> >return null, so the effect is the same as just doing (appInstance as
>>>> >IPopUpHost). I suspect the method is being misused rather than there
>>>> >being a problem with the method.
>>>> >
>>>> >From: Alex Harui<mailto:[hidden email]
>>>> <http:///user/SendEmail.jtp?type=node=63395=1>>
>>>> >Sent: Tuesday, July 18, 2017 8:33 AM
>>>> >To: [hidden email]
>>>><http:///user/SendEmail.jtp?type=node=63395=2>
>>>> <mailto:[hidden email]
>>>> <http:///user/SendEmail.jtp?type=node=63395=3>>
>>>> >Subject: Re: [FlexJS] findPopupHost issue
>>>> >
>>>> >FWIW, it may not be safe to assume that Application will always be an
>>>> >IPopUpHost, hence the utility function.
>>>> >
>>>> >Thanks,
>>>> >-Alex
>>>> >
>>>> >On 7/17/17, 9:59 PM, "piotrz" <[hidden email]
>>>> <http:///user/SendEmail.jtp?type=node=63395=4>> wrote:
>>>> >
>>>> >>Hi Yishay,
>>>> >>
>>>> >>That's a good point - Application is itself an IPopupHost. I've
>>>>asked
>>>> him
>>>> >>what is the use case for his host popup search.

Re: [FlexJS] findPopupHost issue

[Peter Ent]

I needed events to bubble for the drag and drop work. While that was fine
for the Flash Player, the FlexJS/Google/Browser event mix didn't work.
Alex suggested I used setParentTarget on the event to work up the tree and
then the event would be dispatched at each level, thus mimicking bubbling.
I did this exclusively for drag events (see DragEvent class).

Rather than putting that in as the solution for this, I took a simpler
approach. 

‹peter

On 7/21/17, 2:35 AM, "Harbs"  wrote:

>Bubbling does not work very well in FlexJS in general.
>
>When you can rely on native browser event bubbling, it usually works
>okay, but custom events don¹t bubble.
>
>> On Jul 21, 2017, at 1:49 AM, Justin Mclean 
>>wrote:
>> 
>> Hi,
>> 
>>> The issue was that the TitleBar was dispatching "close" with
>>>bubbles=true.
>>> This works fine on SWF but not on the HTML platform without some extra
>>> work. So I just had PanelView intercept the event and dispatch one from
>>> its strand. 
>> 
>> Out of interest is this because of a missing cloneEvent method or that
>>it wasn¹t listening on a parent of the item that dispatched the bubbling
>>event or something else?
>> 
>> Thanks,
>> Justin
>

[FlexJS] MouseEvent

[Peter Ent]

I've been doing work with Drag and Drop and that involves mouse events. I'm 
wondering if someone could give me a history on the Apache FlexJS MouseEvent? 
Specially, its use of localX/Y and screenX/Y.

I'm wondering why the platform implements do not simply assign their version of 
screenX/Y as the screenX/Y values instead of the screenX/Y being getter 
functions?

I've run into cases where the localX/Y == screenX/Y in the FlexJS MouseEvent 
but the original event had different values.

Why would we not want the FlexJS MouseEvent to reflect the platform's mouse 
event values?

SWF: flexJSMouseEvent.screenX = swfMouseEvent.stageX;
JS: flexJSMouseEvent.screenX = jsMouseEvent.pageX;

Thanks.
Peter Ent
Adobe Systems/Apache Flex Project

Re: [FlexJS] MouseEvent

[Peter Ent]

I feel like I'm not grasping some concept. Seems to be that

a) you would want at least two points in a MouseEvent: the screen position
and the local position that is relative to the event.target. You could
derive one from the other but why go through that hassle when both
platforms provide that, as far as I can tell.
b) you would want to know other conditions such as which button is used,
if it is up, down, or moved (either with or without a button pressed), if
any keyboard key was also pressed at the same time.

I don't see why computations need to be made unless some value in one
platform is unavailable and needs to be calculated, but I don't see any
that fall into this category.

Having FlexJS MouseEvent extend a platform event class seems to have it
drawbacks, but it also makes the event work in the current system, so I
would let that go. 

What's disturbing is that events like Mouse and Keyboard and pretty
fundamental and it seems very late in the game that we are discussing
this. I can probably do what I need to do with DnD with what's there, but
it is just exposing a fundamental issue to me.

‹peter

On 7/25/17, 3:08 PM, "Harbs" <harbs.li...@gmail.com> wrote:

>I¹m personally not sure that MouseEvent actually works. Any case of
>MouseEvents in the Framework actually dispatch BrowserEvents. The only
>exception to this case that you will currently find is in TLF where there
>is code which generates MouseEvents from points.
>
>Check out my browser-event branch for my attempt to make MouseEvents and
>KeyboardEvents behave the way you¹d expect.
>
>I¹m currently struggling with figuring out how to make artificially
>created MouseEvents behave properly. Maybe we should compare notesŠ
>
>Harbs
>
>> On Jul 25, 2017, at 9:49 PM, Peter Ent <p...@adobe.com.INVALID> wrote:
>> 
>> I've been doing work with Drag and Drop and that involves mouse events.
>>I'm wondering if someone could give me a history on the Apache FlexJS
>>MouseEvent? Specially, its use of localX/Y and screenX/Y.
>> 
>> I'm wondering why the platform implements do not simply assign their
>>version of screenX/Y as the screenX/Y values instead of the screenX/Y
>>being getter functions?
>> 
>> I've run into cases where the localX/Y == screenX/Y in the FlexJS
>>MouseEvent but the original event had different values.
>> 
>> Why would we not want the FlexJS MouseEvent to reflect the platform's
>>mouse event values?
>> 
>> SWF: flexJSMouseEvent.screenX = swfMouseEvent.stageX;
>> JS: flexJSMouseEvent.screenX = jsMouseEvent.pageX;
>> 
>> Thanks.
>> Peter Ent
>> Adobe Systems/Apache Flex Project
>

Re: [FlexJS]TileLayout

[Peter Ent]

I just left things as open as possible as I recall. Thanks Harbs.

On 7/23/17, 6:06 AM, "Harbs"  wrote:

>Agreed, but I think the defaults should match Flash between and HTML.
>
>He did not set stretch. Nothing was set. ³stretch² is the default css.
>
>> On Jul 23, 2017, at 12:23 PM, Alex Harui 
>>wrote:
>> 
>> There doesn't have to be one TileLayout.  There can be
>> TileLayoutWithFlexStart, TileLayoutWithStretch, and
>> TileLayoutWithAlignContent with a property that allows you to set it.
>> 
>> Peter may remember why he chose "stretch".
>> 
>> -Alex
>> 
>> On 7/23/17, 1:28 AM, "Harbs"  wrote:
>> 
>>> I just discovered something which is worth bringing up:
>>> 
>>> The default for css flex layouts is align-content: stretch This adds
>>> space between elements if the total height (or width) of the elements
>>>are
>>> less than the parent. I don¹t think that¹s an appropriate default for a
>>> tile layout. The layout should be packed from the top left and only add
>>> space if there is padding/margins in the itemRenderers.
>>> 
>>> I believe the correct default css is align-content: flex-start which
>>>has
>>> the behavior that I would expect from a tile layout.
>>> 
>>> Of course, it might be interesting to have a tile layout which offers
>>> different spacing options. That could be alternate layouts, or even
>>>beads
>>> attached to the layout beads.
>>> 
>>> I fixed this issue in my app by just adding some align-content:
>>> flex-start css to my TileLayout component. This works because I don¹t
>>> need swf rendering, but I think it¹s something that should be addressed
>>> in the TileLayout.
>>> 
>>> Let me checkŠ
>>> 
>>> I just (fixed and) ran ContainerTest, and the swf behavior is in fact
>>> different than the HTML behavior. I think we can classify this as a
>>>bug.
>>> I¹m committing this change.
>>> 
>>> FWIW, there¹s lots of other differences between the swf output and the
>>>JS
>>> output in ContainerTest. It¹s probably worth looking into the rest of
>>> those issues as wellŠ
>>> 
>>> Harbs
>> 
>

[FLEXJS] ASDoc Issues

[Peter Ent]

I'm running the asdoc target in flex-asjs and it has rejected a couple of 
things in Core/main/flex/Promise.as such as:

[asdoc] 
/Users/pent/dev/flex-asjs/frameworks/projects/Core/src/main/flex/Promise.as(270):
 col: 19 Error: Syntax error: expecting identifier before catch.
[asdoc]
[asdoc] public function catch(onRejected:Function = null):IThenable

Since "catch" is a keyword I'm surprised this compiles at all. Should 
Promise.as be excluded from ASDoc for now?

—peter

Re: [FLEXJS] ASDoc Issues

[Peter Ent]

Ah, I misunderstood which asdoc-config file.

On 6/30/17, 1:31 PM, "Alex Harui" <aha...@adobe.com.INVALID> wrote:

>The asdoc target doesn't work because we've extended ActionScript for
>FlexJS.  We only care about the ASDoc Example.  I guess we should comment
>out the asdoc target for now.  Also, it looks like the ASDoc example uses
>its own asdic-config.xml file in its src/main/config folder.
>
>-Alex
>
>On 6/30/17, 10:25 AM, "Peter Ent" <p...@adobe.com.INVALID> wrote:
>
>>I'm running the asdoc target in flex-asjs and it has rejected a couple of
>>things in Core/main/flex/Promise.as such as:
>>
>>[asdoc] 
>>/Users/pent/dev/flex-asjs/frameworks/projects/Core/src/main/flex/Promise.
>>a
>>s(270): col: 19 Error: Syntax error: expecting identifier before catch.
>>[asdoc]
>>[asdoc] public function catch(onRejected:Function = null):IThenable
>>
>>Since "catch" is a keyword I'm surprised this compiles at all. Should
>>Promise.as be excluded from ASDoc for now?
>>
>>‹peter
>

Re: [FlexJS,TLF] Tlf branch and Maven build

[Peter Ent]

I just added something to TLF branch, in the DragDrop project. There is
now a dependency on Collections; does a pom file need to be changed to
reflect that or is the compile-swf-config file enough?

‹peter

On 6/27/17, 4:41 PM, "Alex Harui"  wrote:

>I had to update some poms.
>
>-Alex
>
>On 6/27/17, 12:15 PM, "piotrz"  wrote:
>
>>I think it is related to his changes. I just tried build Basic locally
>>and
>>it's failed with same stacktrace. I got update of falcon beforehand.
>>
>>Maybe Alex will have some thoughts on that.
>>
>>Thanks,
>>Piotr
>>
>>
>>
>>-
>>Apache Flex PMC
>>piotrzarzyck...@gmail.com
>>--
>>View this message in context:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>e
>>x-development.247.n4.nabble.com%2FFlexJS-TLF-Tlf-branch-and-Maven-bui
>>l
>>d-tp62452p62645.html=02%7C01%7C%7C18001132a7cf490a9d0308d4bd94f8de%7
>>C
>>fa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636341894903818427=SIN%2
>>F
>>zvPD4WV65%2FRFAuixK%2B2vEJjDSFtjRUwwfgDgUnE%3D=0
>>Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [FlexJS] Layouts

[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 bead will have a setAbsolutePosition(child, x, y) function
that on Flash, just sets x and y while on HTML, sets left and top styles
as well as setting position:absolute style.

You could use it like this: Create a view bead class that extends this
class and set your custom view bead class in CSS for your control or add
it programmatically. The super.strand setter will take care of setting the
strand's position style. After you have created any elements required for
your control, position them using setAbsolutePosition() and do so in
response to changes in your control's size.

—peter



On 4/25/17, 4:47 PM, "Alex Harui" <aha...@adobe.com> wrote:

>
>
>On 4/25/17, 12:35 PM, "Peter Ent" <p...@adobe.com> 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 position:absolute on each of the control's parts?
>>Setting part.x and part.y won't be enough. You still need set
>>part.style.position = "absolute". I don't think that will translate over
>>to the HTML side and will not be useful to Flash.
>
>Well, you are right that there is more to it than just the ViewBase.
>
>However, we are in the business of encapsulating patterns.  We could do
>any combination of the following:
>
>1) have setter for x and y set position="absolute" but it won't change the
>parent's position style.  AbsolutePositioningViewBase would still do that.
>2) add a setChildPosition method on AbsolutePositioningViewBase.
>3) add xChanged,yChanged listeners to children
>4) add childAdded listener to parent and check the child's x,y value
>
>Thoughts?
>-Alex
>
>>
>>‹peter
>>
>>On 4/25/17, 2:08 PM, "Alex Harui" <aha...@adobe.com> wrote:
>>
>>>
>>>
>>>On 4/25/17, 10:55 AM, "yishayw" <yishayj...@hotmail.com> 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).
>>>
>>>Agreed, which is why we'd offer different base classes for views, one of
>>>which assigns the position style.
>>>
>>>-Alex
>>>
>>
>

Re: [FlexJS] FlexJS Wiki Update

[Peter Ent]

Hi,

I've placed my answers in-line.

On 4/24/17, 4:17 AM, "OK"  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=02%7C01%7C%7C6ef80b5dc46a4c66852008d48aec69e8%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636286195376443487=BBvguzdClc1PuV
>V0LUIgAeyTZznmTG%2FCYxA38EA3vag%3D=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=02%7C01%7C%7C6ef80b5dc46a4c66852008d48aec69e8%7Cfa7b1b5a7
>b34438794aed2c178decee1%7C0%7C0%7C636286195376443487=0ZXB5qAlXETXae9
>Zlpj74bn0D1Qdvb4ce%2FevosJgmzI%3D=0
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-FlexJS-Wiki-Update-tp61292p61
>304.html=02%7C01%7C%7C6ef80b5dc46a4c66852008d48aec69e8%7Cfa7b1b5a7b34
>438794aed2c178decee1%7C0%7C0%7C636286195376443487=k7rIxjyzhY1inSIdkR
>IZwN5lh1fcqVnyUV7jneJQ%2BNY%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layouts

[Peter Ent]

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 part.x and part.y won't be enough. You still need set
part.style.position = "absolute". I don't think that will translate over
to the HTML side and will not be useful to Flash.

‹peter

On 4/25/17, 2:08 PM, "Alex Harui"  wrote:

>
>
>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).
>
>Agreed, which is why we'd offer different base classes for views, one of
>which assigns the position style.
>
>-Alex
>

Re: [FlexJS] Status of Slider and NumericStepper?

[Peter Ent]

NumericStepper must not have been finished for some reason. Or perhaps the
view bead was operating (at some point in time) on both the JS and SWF
sides. The NumericStepperView bead is now in a COMPILE::SWF block.

This is one of those cases where there *may be* enough overlap with the
SWF and JS sides that perhaps both platforms should use a view bead.

Josh's changes work, of course, so I guess we are good here.

‹peter

On 4/28/17, 7:11 PM, "Josh Tynjala"  wrote:

>I updated NumericStepper to fix this issue on the dual branch.
>
>- Josh
>
>On Thu, Apr 27, 2017 at 5:11 PM, Josh Tynjala 
>wrote:
>
>> I'm trying to use NumericStepper or Slider with the latest nightly
>>(tried
>> both develop and dual), but they don't seem to be working.
>>
>> The initial values are not displayed, and while I can change the value
>> with NumericStepper, Slider doesn't seem to be interactive.
>>
>> 
>> 
>>
>> Are they currently in a bad state?
>>
>> - Josh
>>

Re: [FlexJS] Layouts

[Peter Ent]

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 the element is positioned on the
first item in the parent chain that has position relative or absolute.
This is why BasicLayout sets the host component's position if it isn't
already set.

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.

We could also make a specialized Group subclass that has a
positionElement(element, x, y) function that will also set
position:absolute. Perhaps we could call it "BasicGroup" that would also
make BasicLayout its default but you would not necessarily need to run the
layout every time.

Maybe there are some other ideas?

‹peter

On 4/25/17, 5:41 AM, "yishayw"  wrote:

>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:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layouts-tp61120p61330.html
>ta=02%7C01%7C%7Ce0b936af7e38411d815a08d48bc0c368%7Cfa7b1b5a7b34438794aed2c
>178decee1%7C0%7C0%7C636287107406338981=iY0A2%2FsLf%2BCVgWsNlxZl%2BBR
>C20YTFTjPuX3%2BulkUBss%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layouts

[Peter Ent]

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
is probably only partially accurate as I always have to run a half dozen
experiments to understand the differences. We don't have anything like
that in Flash. Eventually I want to a ConstraintLayout that makes use of
that, but probably next release.

Anyway, back to your original question. If component-specific code (i.e.,
COMPILE::JS) is not available to component authors outside the framework
space, then you are left with CSS.

If you were to give all of your sub-elements a common class name, then you
could do:

.MyComponent .commonName {
position:absolute;
}

And still programmatically position them using .x and .y properties. The
Flash side will work as intended and now the JS side should as well.

‹peter

On 4/25/17, 9:06 AM, "yishayw" <yishayj...@hotmail.com> wrote:

>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 make a specialized Group subclass that has a
>> positionElement(element, x, y) function that will also set
>> position:absolute. Perhaps we could call it "BasicGroup" that would
>>also 
>> make BasicLayout its default but you would not necessarily need to run
>>the 
>> layout every time.
>
>That's not a bad idea, but again I'm curious about what we'll do for
>components that are not based off group or container. Also, what would the
>flash behavior be? AFAIK x and y in flash act like absolute in HTML, even
>without layout.
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layouts-tp61120p61332.html
>ta=02%7C01%7C%7C15aa43a0230b4d7e725c08d48bdd724c%7Cfa7b1b5a7b34438794aed2c
>178decee1%7C0%7C0%7C636287230601148452=OPPvWFPqY4d44ZyVe0OH7Cz5LOThR
>CIo1LuXZMnUBws%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

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" <yishayj...@hotmail.com> 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.247.n4.nabble.com%2FFlexJS-FlexJS-Wiki-Update-tp61292p61
>307.html=02%7C01%7C%7Cb1eb1f5332c24bcca97b08d48b0e8a09%7Cfa7b1b5a7b34
>438794aed2c178decee1%7C0%7C0%7C636286341942886874=HokbLXfdHwUh0cJIsn
>EFqddxh9G0xPYX24%2BS9IosZUE%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: FlexJS Express Components

[Peter Ent]

You make good points.

The Express package is in its infancy. I packaged things together that
were, I felt, the most common combinations, such as all Views and
Container classes have data binding. This also means Containers have
scrolling with the idea that you would use Group if you did not want
scrolling. But Group does not support background and border.

I agree that more options on the Express components could be presented as
well as allowing scrolling to be removed for a specific Express container
or all Express containers.

‹peter

On 8/6/17, 4:36 PM, "Harbs"  wrote:

>I¹m looking at the Express components for the first time, and I have some
>observations/questions.
>
>1. Container adds a ScrollingViewport bead. I was kind of expecting the
>bead to be added via CSS so it could be overridden in an app. What is an
>express app client supposed to do if they don¹t want scrolling?
>
>2. ScrollingViewport does not have a way to specify horizontal/vertical
>scrolling. I¹m wondering if there shouldn¹t be a more do-it-all bead
>which has options to turn on and off horizontal and vertical scrolling
>separately.
>
>3. The Express components do not have convenience methods for setting
>bead properties. It would seem to me that convenience methods would be
>very helpful.
>
>4. I seems like there¹s lots of additional compound components which
>would be useful. I¹m going to try and add someŠ
>
>Harbs

Re: git commit: [flex-asjs] [refs/heads/develop] - Added example of building a Table from a data source to the TableExample example.

[Peter Ent]

Hi,

Yes - you are right about getting "initComplete" twice. I wrote the code
and forgot about it! The DataTable should probably dispatch
"dataTableComplete" so that the data mapper can detect that as the
all-finished event.

Thanks,
‹peter

On 5/2/17, 5:39 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote:

>Hi Peter,
>
>I was going through the DataTable class code and I see that you are adding
>mapper bead in addedToParent.
>
>override public function addedToParent():void
>{
>   super.addedToParent();
>
>   addBead(new DataTableMapperForArrayListData());
>
>   dispatchEvent( new Event("initComplete") );
>}
>
> If I add event listener to DataTable class I will get "initComplete"
>two times.
>
>You will not have issue with added bead, but developer who will get
>this class and use it could have.
>
>Piotr
>
>
>2017-05-02 22:34 GMT+02:00 <p...@apache.org>:
>
>> Repository: flex-asjs
>> Updated Branches:
>>   refs/heads/develop 82ff1840e -> 336fac64c
>>
>>
>> Added example of building a Table from a data source to the TableExample
>> example.
>>
>>
>> Project: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Frepo=02%7C01%7C%7C973eb1da4
>>7de43ee8ff308d491a3d089%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6362
>>93580155655469=lugSmNuyjCCVZ%2BPoSqlfac2LM4%2BwoALMml9%2FWJ12nMM%3D
>>=0
>> Commit: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fcommit%2F336fac64=02%7C01%7
>>C%7C973eb1da47de43ee8ff308d491a3d089%7Cfa7b1b5a7b34438794aed2c178decee1%7
>>C0%7C0%7C636293580155655469=N4yb6S%2Ftiq2Bmy3dYMzB6DWOcnUbhCmHlIfqp
>>48%2FE%2Bk%3D=0
>> Tree: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Ftree%2F336fac64=02%7C01%7C%
>>7C973eb1da47de43ee8ff308d491a3d089%7Cfa7b1b5a7b34438794aed2c178decee1%7C0
>>%7C0%7C636293580155655469=Od4twsqmJ%2BiQLJjGV7W5Lv%2F48N16La6zNvIBp
>>Rzxrf8%3D=0
>> Diff: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fdiff%2F336fac64=02%7C01%7C%
>>7C973eb1da47de43ee8ff308d491a3d089%7Cfa7b1b5a7b34438794aed2c178decee1%7C0
>>%7C0%7C636293580155655469=cemmUkVwsZERSGDQVIUoxnIcJAtm8AetP4cTbcyOj
>>FE%3D=0
>>
>> Branch: refs/heads/develop
>> Commit: 336fac64c0eed8b063213a72899f658e9d490cea
>> Parents: 82ff184
>> Author: Peter Ent <p...@apache.org>
>> Authored: Tue May 2 16:33:57 2017 -0400
>> Committer: Peter Ent <p...@apache.org>
>> Committed: Tue May 2 16:33:57 2017 -0400
>>
>> --
>>  .../src/main/flex/MyInitialView.mxml|  31 -
>>  .../src/main/flex/TableExample.mxml |   3 +
>>  .../src/main/flex/dataTable/DataColumn.as   |  33 ++
>>  .../src/main/flex/dataTable/DataTable.as|  69 
>>  .../mapper/DataTableMapperForArrayListData.as   | 112
>>+++
>>  .../main/flex/dataTable/model/DataTableModel.as |  40 +++
>>  .../src/main/flex/models/ProductsModel.as   |  47 
>>  7 files changed, 334 insertions(+), 1 deletion(-)
>> --
>>
>>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fblob%2F=02%7C01%7C%7C973eb1
>>da47de43ee8ff308d491a3d089%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
>>36293580155665477=lKg4ES5s2EUHsYKZqLX2ADXkVYodqZxqmtbLE6443yM%3D
>>served=0
>> 336fac64/examples/flexjs/TableExample/src/main/flex/MyInitialView.mxml
>> --
>> diff --git 
>>a/examples/flexjs/TableExample/src/main/flex/MyInitialView.mxml
>> b/examples/flexjs/TableExample/src/main/flex/MyInitialView.mxml
>> index c2f81dd..11d2e29 100644
>> --- a/examples/flexjs/TableExample/src/main/flex/MyInitialView.mxml
>> +++ b/examples/flexjs/TableExample/src/main/flex/MyInitialView.mxml
>> @@ -18,7 +18,9 @@ limitations under the License.
>>
>>  -->
>>  >xmlns:fx="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2
>>Fns.adobe.com%2Fmxml%2F2009=02%7C01%7C%7C973eb1da47de43ee8ff308d491a
>>3d089%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636293580155665477
>>ta=KQ1v3zxgipqPUoRjx%

Re: [FlexJS] Layouts

[Peter Ent]

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" <p...@adobe.com> wrote:

>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 bead will have a setAbsolutePosition(child, x, y) function
>that on Flash, just sets x and y while on HTML, sets left and top styles
>as well as setting position:absolute style.
>
>You could use it like this: Create a view bead class that extends this
>class and set your custom view bead class in CSS for your control or add
>it programmatically. The super.strand setter will take care of setting the
>strand's position style. After you have created any elements required for
>your control, position them using setAbsolutePosition() and do so in
>response to changes in your control's size.
>
>—peter
>
>
>
>On 4/25/17, 4:47 PM, "Alex Harui" <aha...@adobe.com> wrote:
>
>>
>>
>>On 4/25/17, 12:35 PM, "Peter Ent" <p...@adobe.com> 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 position:absolute on each of the control's parts?
>>>Setting part.x and part.y won't be enough. You still need set
>>>part.style.position = "absolute". I don't think that will translate over
>>>to the HTML side and will not be useful to Flash.
>>
>>Well, you are right that there is more to it than just the ViewBase.
>>
>>However, we are in the business of encapsulating patterns.  We could do
>>any combination of the following:
>>
>>1) have setter for x and y set position="absolute" but it won't change
>>the
>>parent's position style.  AbsolutePositioningViewBase would still do
>>that.
>>2) add a setChildPosition method on AbsolutePositioningViewBase.
>>3) add xChanged,yChanged listeners to children
>>4) add childAdded listener to parent and check the child's x,y value
>>
>>Thoughts?
>>-Alex
>>
>>>
>>>‹peter
>>>
>>>On 4/25/17, 2:08 PM, "Alex Harui" <aha...@adobe.com> wrote:
>>>
>>>>
>>>>
>>>>On 4/25/17, 10:55 AM, "yishayw" <yishayj...@hotmail.com> 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).
>>>>
>>>>Agreed, which is why we'd offer different base classes for views, one
>>>>of
>>>>which assigns the position style.
>>>>
>>>>-Alex
>>>>
>>>
>>
>

Re: git commit: [flex-asjs] [refs/heads/develop] - Added AbsolutePositioningViewBeadBase so control components can position their sub-elements using absolute positioning.

[Peter Ent]

Hi,

This is the finished bead. We put "base" on it to indicate it is a class
you can use as the basis for control view beads. But feel free to change
it now before it gets too much use.


‹peter

On 5/3/17, 1:17 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote:

>Hi Peter,
>
>Is this finished bead which I can use straight in my components ? If this
>is not class which should be extended - I think better would be name
>without "Base".
>
>Just my feeling when I look without going into the code.
>
>Piotr
>
>
>
>2017-05-03 19:08 GMT+02:00 <p...@apache.org>:
>
>> Repository: flex-asjs
>> Updated Branches:
>>   refs/heads/develop 7965c6de2 -> 88f0bcbe0
>>
>>
>> Added AbsolutePositioningViewBeadBase so control components can position
>> their sub-elements using absolute positioning.
>>
>>
>> Project: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Frepo=02%7C01%7C%7Cb4705bba1
>>ccf4c8d0bfa08d492484269%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6362
>>94286433550282=76h%2FPdcpqBabnqn%2BJlZpiP4Vp5XzSizXlHTS5EUNd%2BY%3D
>>=0
>> Commit: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fcommit%2F88f0bcbe=02%7C01%7
>>C%7Cb4705bba1ccf4c8d0bfa08d492484269%7Cfa7b1b5a7b34438794aed2c178decee1%7
>>C0%7C0%7C636294286433550282=oM9XL7xk139jn12ioIful8YwO%2BNgKoqCWVvPg
>>BLpE20%3D=0
>> Tree: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Ftree%2F88f0bcbe=02%7C01%7C%
>>7Cb4705bba1ccf4c8d0bfa08d492484269%7Cfa7b1b5a7b34438794aed2c178decee1%7C0
>>%7C0%7C636294286433550282=YHG%2FTeTBVMccD%2FCzVNUZO9e74fT9gjAqXv7k2
>>rW94uw%3D=0
>> Diff: 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fdiff%2F88f0bcbe=02%7C01%7C%
>>7Cb4705bba1ccf4c8d0bfa08d492484269%7Cfa7b1b5a7b34438794aed2c178decee1%7C0
>>%7C0%7C636294286433550282=KH7zotCmcVuj7GLuKHa20cUYCxh189IeobJk%2FLK
>>d1Js%3D=0
>>
>> Branch: refs/heads/develop
>> Commit: 88f0bcbe0728e2831e097a1b9593f835cf3c564d
>> Parents: 7965c6d
>> Author: Peter Ent <p...@apache.org>
>> Authored: Wed May 3 13:08:08 2017 -0400
>> Committer: Peter Ent <p...@apache.org>
>> Committed: Wed May 3 13:08:08 2017 -0400
>>
>> --
>>  .../Basic/src/main/flex/BasicClasses.as |   1 +
>>  .../beads/AbsolutePositioningViewBeadBase.as| 113
>>+++
>>  2 files changed, 114 insertions(+)
>> --
>>
>>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fblob%2F=02%7C01%7C%7Cb4705b
>>ba1ccf4c8d0bfa08d492484269%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
>>36294286433550282=kVtfAYLBRzSsOY4OWt4F1UGCg1gZbrCrYsDaoH5RpOo%3D
>>served=0
>> 88f0bcbe/frameworks/projects/Basic/src/main/flex/BasicClasses.as
>> --
>> diff --git a/frameworks/projects/Basic/src/main/flex/BasicClasses.as
>> b/frameworks/projects/Basic/src/main/flex/BasicClasses.as
>> index 4436e43..c7655cc 100644
>> --- a/frameworks/projects/Basic/src/main/flex/BasicClasses.as
>> +++ b/frameworks/projects/Basic/src/main/flex/BasicClasses.as
>> @@ -32,6 +32,7 @@ internal class BasicClasses
>>  import org.apache.flex.html.beads.DispatchInputFinishedBead;
>> DispatchInputFinishedBead;
>> import org.apache.flex.html.accessories.PasswordInputBead;
>> PasswordInputBead;
>> import org.apache.flex.html.accessories.TextPromptBead;
>> TextPromptBead;
>> +   import 
>>org.apache.flex.html.beads.AbsolutePositioningViewBeadBase;
>> AbsolutePositioningViewBeadBase;
>>  import org.apache.flex.html.beads.AlertView; AlertView;
>>  import org.apache.flex.html.beads.models.AlertModel; AlertModel;
>> COMPILE::SWF
>>
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgit-wip-u
>>s.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fblob%2F=02%7C01%7C%7Cb4705b
>>ba1ccf4c8d0bfa08d492484269%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6
>>36294286433550282=kVtfAYLBRzSsOY4OWt4F1UGCg1gZbrCrYsDaoH5RpOo%3D
>>served=0
>> 88f0bcbe/frameworks/proj

Re: [FlexJS] CSS Pruning

[Peter Ent]

The reason for .DataGridListArea is that the SWF side does not recognize a 
selector of:

DataGrid Container { ... }

So I gave the Container used for the list area a class name. Perhaps I can try 
to change it to a type name and see if that's more helpful and if so look at 
replacing as many specialty class names with type selectors. 

Peter 


> On May 15, 2017, at 11:46 AM, Alex Harui  wrote:
> 
> Hi,
> 
> While waiting for more folks to examine the release branch packages, I try
> find time to find easy ways to make HelloWorld smaller.  Currently, it is
> 62K of minified JS.  IMO, that's too big!
> 
> I think I can get some classes to drop away via more
> @flexjsignorecoercions.  The list of interfaces in the output is pretty
> large and I'll bet most are not needed at runtime.
> 
> But another sore spot for me is the CSS output.  This is true even for
> regular Flex:  the CSS output contains EVERY class selector.  The compiler
> knows how to prune out unused type selectors, but it always keeps every
> class selector.  IOW, if you look at the CSS and see ".DataGridListArea",
> that's a class selector.  But if you see "DataGrid" (no starting '.')
> that’s a type selector and for HelloWorld, which has just a Label, the
> DataGrid type selector is not in the output and any dependencies it brings
> it are not in the output either.
> 
> But in HelloWorld today, ".DataGridListArea" is in the output for
> HelloWorld.  In looking at the compiler code, we could somehow mark our
> class selectors in a way that they will be removed if the type related to
> the name isn't in the output.  IOW, we need to know to keep class
> selectors like ".myClassSelector", but know to get rid of
> .DataGridListArea if DataGrid is not in the output.
> 
> I've worked around this in the past by creating new classes.  In this
> case, if .DataGridListArea is applied to a Group, then make a subclass of
> Group called DataGridListArea and change the class selector to a type
> selector.  The problem is that the definition of the DataGridListArea
> class takes up room in the output, so it would be slightly better to find
> a way to prune class selectors.
> 
> Maybe class selectors we want to prune should start with the type name
> surrounded by '$", so .$DataGrid$ListArea.  Then the compiler could easily
> check for two '$' and see if the class in-between is being kept in the
> output or not.
> 
> Thoughts?
> -Alex
> 

Re: Moonshine 1.4.0 Release

[Peter Ent]

On Mac macOS Sierra: When I start this new version of Moonshine, I get a
dialog that tells me that due to an Apple sandbox issue, my Apache Flex
and Apache FlexJS SDKs must be located in the Downloads folder. OK, fine,
so I click on the button that takes me to a Moonshine downloads page, but
there is only a download for Moonshine
(http://moonshine-ide.com/moonshine-app-store-helper/) Helper. Thinking
that is probably it (I was actually expecting to do to the Apache
Flex/FlexJS page to get the SDKs), I downloaded the package and launched
it.

That did "something" (not sure what) and then offered to delete itself,
which I did. This left my Downloads folder in its original condition
(which is currently empty).

So I'm not really sure this part of the set up worked.

Regards,
Peter Ent
Adobe Systems/Apache Flex Project

On 5/15/17, 4:30 PM, "JoelProminic" <j...@prominic.net> wrote:

>I am pleased to announce that Moonshine 1.4.0 has been released at
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmoonshine-
>ide.com%2F=02%7C01%7C%7Cf4c257aead604dcde0ad08d49bd320ee%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636304778468882690=wMoLsDsaRFuRc6wa
>ahe84LzbdNBl%2F598mEJykwg5w5E%3D=0 and on the App Store.
>
>This release was focused mostly on adding some more common IDE features,
>including:
>- Command-Click to go to the definition for a variable, function, or class
>- View code problems in a list or by in-line highlighting
>- Find all references for a variable, function, or class.
>- List and search all definitions in a file or project
>
>
>We also added code-completion support for FlexJS 0.8.0 nightly builds.
>
>Let us know if you encounter any issues with the update.
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FMoonshine-1-4-0-Release-tp61632.html
>=02%7C01%7C%7Cf4c257aead604dcde0ad08d49bd320ee%7Cfa7b1b5a7b34438794ae
>d2c178decee1%7C0%7C0%7C636304778468882690=P3PuvUqVioWi6R6q%2B0pTIOWm
>XEX1%2B2HtyKotoain41Y%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [2/4] git commit: [flex-asjs] [refs/heads/develop] - LayoutBase Fix for strand set to null in remove bead, plus performance improvements in js

[Peter Ent]

Maybe I'm misunderstanding again.


   
  

This is what a developer should do so that the contents of the panel are
laid out horizontally.

I constructed Panel as a subclass of Group so that I could take advantage
of VerticalFlexLayout so that Container content area of the Panel would
grow to fit the Panel's vertical space; any TitleBar or ControlBar would
then remain fixed in size and place.

But making Panel be a sub-class of Group meant that adding a layout
in-line in MXML would cause that layout to supersede the Panel's
VerticalFlexLayout. So Panel moves any layout bead supplied by the user
and puts it onto its Container content area.

Panel could have been constructed in another way and given the issues that
we seem to be having with it, I suggest a re-write in version 0.9.0.

Panel also suffers from having to re-parent any children given to it and
place them into the Container (this happens for JS and SWF platforms).
Container then re-parents those children, but only on the SWF platform, to
its content view.

‹peter

On 6/9/17, 11:59 PM, "Alex Harui"  wrote:

>Yes, thanks for removing unnecessary coercions.
>
>While debugging examples, I also noted the removal of Layout in Panel.
>Makes me wonder if we our container architecture/lifecycle is designed
>properly.  The base classes may need to have a pattern for "proxies" and
>"wrappers", which may be the essence of what Panels and Scrolling
>Containers do (along with exposing instead of hiding the
>addElement/removeElement APIs).
>
>Looking at the code for bead removal, it seems so heavy it makes you want
>to avoid it all together.  For the password input bead, for example, we
>know there can be a version of the bead with a flag to enable/disable the
>password characters.  How heavy is that implementation vs the one that
>requires removal?  For Panel, maybe the lifecycle should just not assume
>that the Container has a layout bead so there isn't one to replace.
>
>Food for thought,
>-Alex
>
>On 6/9/17, 4:00 PM, "Greg Dove"  wrote:
>
>>I happened to be testing against FlexJSStore at the time I discovered the
>>need for this, and there is some removing going on.
>>
>>I think I improved performance compared to how it was originally by
>>removing coercion in js and using local references for some of the repeat
>>listener references/avoiding repeat closure lookups on js, so it is
>>probably 'less' PAYG than it was before, with more safety, but I get the
>>point.
>>
>>I'm not sure about injection, but I will come back to this and add a
>>removable layout subclass for the FlexJSStore demo (not sure if the
>>PanelView or whatever seems to be doing this is also used in other
>>examples, I have not checked).
>>
>>
>>
>>
>>On Sat, Jun 10, 2017 at 10:45 AM, Alex Harui  wrote:
>>
>>> I guess I don't believe that removing beads is so common that every app
>>> needs to carry this code around.  I wonder if there is a way to inject
>>> removability as needed.
>>>
>>> Having a RemovableXXXLayout could override the strand setter and remove
>>> listeners if the handlers are protected.
>>>
>>> Thoughts?
>>> -Alex
>>>
>>> On 6/8/17, 3:22 PM, "gregd...@apache.org"  wrote:
>>>
>>> >LayoutBase Fix for strand set to null in remove bead, plus performance
>>> >improvements in js
>>> >
>>> >
>>> >Project:
>>> >https://na01.safelinks.protection.outlook.com/?url=
>>> http%3A%2F%2Fgit-wip-us
>>> >.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Frepo=02%
>>> 7C01%7C%7Cb863f5cff77
>>> >e41e305b708d4aebcd62e%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C6363255
>>> >73442866659=NsSQs6LJBQaYIJ36tZ%2FgMmMyuffAlo7pAuwtopOok2g%3D&
>>> reserve
>>> >d=0
>>> >Commit:
>>> >https://na01.safelinks.protection.outlook.com/?url=
>>> http%3A%2F%2Fgit-wip-us
>>> >.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fcommit%
>>> 2F08af60c7=02%7C01%7C%
>>> >7Cb863f5cff77e41e305b708d4aebcd62e%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%
>>> >7C0%7C636325573442866659=a8HJuqkEEii03BRyFH6lMcvkLFirlc
>>> lo6HwG%2F6w4J
>>> >kA%3D=0
>>> >Tree:
>>> >https://na01.safelinks.protection.outlook.com/?url=
>>> http%3A%2F%2Fgit-wip-us
>>> >.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Ftree%2F08af60c7&
>>> data=02%7C01%7C%7C
>>> >b863f5cff77e41e305b708d4aebcd62e%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C
>>> >0%7C636325573442866659=CcHeFSf6IMQ75kKXSE%
>>> 2BWY23J7VrbJauoxO1TvG%2BHS
>>> >Yk%3D=0
>>> >Diff:
>>> >https://na01.safelinks.protection.outlook.com/?url=
>>> http%3A%2F%2Fgit-wip-us
>>> >.apache.org%2Frepos%2Fasf%2Fflex-asjs%2Fdiff%2F08af60c7&
>>> data=02%7C01%7C%7C
>>> >b863f5cff77e41e305b708d4aebcd62e%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C
>>> >0%7C636325573442866659=E%2B6iEUFqZB3%2BO15%
>>> 2BK3sHlnaiuIkWgm8DvWVcmUm
>>> >nnIk%3D=0
>>> >
>>> >Branch: refs/heads/develop
>>> >Commit: 08af60c7755a9c7dd64ab62cbfff97443841bda7
>>> >Parents: b0f7013
>>> >Author: greg-dove 
>>> >Authored: Fri Jun 9 10:07:20 2017 +1200

Re: [FlexJS] more on undefined / non initialised values

[Peter Ent]

Perhaps we can look to other languages for guidance. For example, in Swift:

var val:Boolean

is illegal. It MUST be initialized or declared to be optional:

var val:Boolean = false
var val:Boolean?

The Swift people felt that leaving variables uninitialized and defaulted
caused too many issues and so force values to be given. If you don't have
a value then you must declare it to be optional, in which case its value
is nil until it is assigned a value.

Neither AS nor JS has the luxury of syntax that enforces this, but perhaps
we could have the compiler issue a warning (at least) that scalar values
are uninitialized. 

‹peter

On 6/11/17, 4:21 AM, "Harbs"  wrote:

>It seems like the general case is better to have the initialization.
>Thanks for implementing that.
>
>It would probably be nice for the compiler to be intelligent and only
>initialize if the code does not initialize too.
>
>So:
>
>var val:Boolean;
>// further down before val is actually accessed
>val = true;// or val = false;
>
>should not initialize val, but:
>
>var val:Boolean;
>// further down 
>if(val == someotherval){
>// do something
>}
>should initialize it.
>
>But I don¹t see this as critical for now.
>
>Harbs
>
>> On Jun 11, 2017, at 10:56 AM, Justin Mclean 
>>wrote:
>> 
>> Hi,
>> 
>>> The changes you made look fine.
>> 
>> Do you want them as the default and an option to turn them off? I¹m
>>assuming you will you at some later point add other switches to turn
>>other optimisations (whatever they may be) on?
>> 
>>> Seems like eventually we'll have to initialize other types as well.
>> 
>> I¹d guestimate there would be a performance boost for string and for
>>object as well / but the size cost may be different. Won't know until I
>>or someone tries it.
>> 
>>> Safe, but inefficient at times.
>> 
>> So far I not seen any inefficiency in fact the opposite. But sure there
>>may be specific cases that perform better, please post any you find to
>>the list.
>> 
>> Thanks,
>> Justin
>

Re: [VOTE] Release Apache FlexJS 0.8.0 RC1

[Peter Ent]

I tried the approval XML script.

+1
Package 
https://dist.apache.org/repos/dist/dev/flex/flexjs/0.8.0/rc1/apache-flex-fl
exjs-0.8.0-src.tar.gz
Java 1.7
OS: Mac OS X x86_64 10.12.5
Source kit signatures match: y
Source kit builds: y
README is ok: y
RELEASE_NOTES is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives: y
No unapproved binaries: y


Package 
https://dist.apache.org/repos/dist/dev/flex/flexjs/0.8.0/rc1/binaries/apach
e-flex-flexjs-0.8.0-bin.tar.gz
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y

‹peter


On 6/9/17, 6:00 PM, "Alex Harui"  wrote:

>Hi,
>
>This is vote for the 0.8.0 release of Apache FlexJS.
>
>The release candidate can be found here;
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apac
>he.org%2Frepos%2Fdist%2Fdev%2Fflex%2Fflexjs%2F0.8.0%2Frc1%2F=02%7C01%
>7C%7C96fe96b29b154e53fd4808d4af83054a%7Cfa7b1b5a7b34438794aed2c178decee1%7
>C0%7C0%7C636326424639372231=jnXSXIgt8ffpDyOng8JaDka42IGnQwwuD%2FGWsW
>PL5To%3D=0
>
>Before voting please review the section,'What are the ASF requirements on
>approving a release?', at:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache
>.org%2Fdev%2Frelease.html%23approving-a-release=02%7C01%7C%7C96fe96b2
>9b154e53fd4808d4af83054a%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6363
>26424639372231=0mocrXOP%2BmX0%2B%2BhM58iaXG3Ql8BHzPyVJhZUTOxhcMA%3D&
>reserved=0
>
>At a minimum you would be expected to check that:
>- MD5 and signed packages are correct
>- README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
>- That the build script completes successfully
>- That you can compile and cross-compile a simple example using the SDK.
>
>The source package is set up the same way as the repo.  This means that
>the results of the build are not the same as an IDE-compatible SDK.  The
>compiled source package can be used in combination with the FalconJX
>source package to compile some of the sample applications.
>
>The most convenient way to use the binary package is to install it via Ant
>or the Installer.  To use an Installer you must use InstallApacheFlex
>version 3.1 or later.  You can get InstallApacheFlex here:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache
>.org%2Fdyn%2Fcloser.cgi%3Fpath%3D%2Fflex%2Finstaller%2F3.1%2Fbinaries%2F
>ata=02%7C01%7C%7C96fe96b29b154e53fd4808d4af83054a%7Cfa7b1b5a7b34438794aed2
>c178decee1%7C0%7C0%7C636326424639372231=CnaAfc%2Bs9YlqNJiL%2FQpXjeQr
>1tVv49JYHXuRS8sGW8c%3D=0
>
>Please vote to approve this release:
>+1 Approve the release
>-1 Veto the release (please provide specific comments to why)
>
>This vote will be open for 72 hours or until a result can be called.
>
>The vote passes if there is:
>- At least 3 +1 votes from the PMC
>- More positive votes than negative votes
>
>Remember that this is a 'beta-quality' release so I expect there
>will be many bugs found.  IMO the goal is not to try to find and fix bugs
>in the RC, but to make sure we have the packaging right, and enough
>functionality that folks will have some success trying to use it.
>
>People who are not in PMC are also encouraged to test out the release and
>vote, although their votes will not be binding, they can influence how the
>PMC votes.
>
>When voting please indicate what OS, IDE, Flash Player version and AIR
>version you tested with.
>
>For your convenience, there is an ant script that automates the common
>steps to validate a release.  Instead of individually downloading the
>package and signature files, unzipping, etc, you can instead:
>1) create an empty folder,
>2) download into that folder this file:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apac
>he.org%2Frepos%2Fdist%2Fdev%2Fflex%2Fflexjs%2F0.8.0%2Frc1%2FApproveFlexJS&
>data=02%7C01%7C%7C96fe96b29b154e53fd4808d4af83054a%7Cfa7b1b5a7b34438794aed
>2c178decee1%7C0%7C0%7C636326424639372231=0DOjbbNMaRurOLPrMzyPZKR5a4G
>poqm1QfJBsoR9IVc%3D=0.
>xml
>3) run the script: ant -e -f ApproveFlexJS.xml -Drelease.version=0.8.0
>-Drc=1
>
>You are not required to use this script, and more testing of the packages
>and build results are always encouraged.
>
>
>Please put all discussion about this release in the DISCUSSION thread not
>this VOTE thread.
>
>Thanks,
>Alex Harui
>

Re: [FlexJS] getElementIndex()

[Peter Ent]

I was wondering why React keeps its own DOM and why it is so fast. Perhaps
this is the reason.

On 6/22/17, 10:56 AM, "Alex Harui"  wrote:

>Feel free to test your theory.  It sounds like duplication of work to me
>as in: The DOM does have some sort of list so why keep our own?  Making
>and manipulation Array is supposedly also not very performant.
>
>Regarding text nodes, I haven't looked to see when text nodes are
>intentionally children of a UIBase.  Maybe the elements should be allowed
>to be text nodes.
>
>-Alex
>
>On 6/22/17, 4:11 AM, "Harbs"  wrote:
>
>>Is there a reason we are using the underlying node lists for our
>>collection of elements?
>>
>>I would think that it would be more performant (at the possible cost of
>>some extra memory) to keep a list of FlexJS elements.
>>
>>childNodes are live collections which need to constantly be resolved so
>>they should not be very performant. They also contain text nodes, so I¹m
>>not sure that the index will always be correct.
>

Re: [FlexJS] TileLayout

[Peter Ent]

You could write a new TileLayoutWithGapAndPadding to handle that specific
situation. On the JS side, TileLayout uses Flexbox and perhaps you need
more control.

‹peter

On 6/22/17, 10:14 AM, "yishayw"  wrote:

>Adding margins adds a gutter on the right side of the host. This is
>probably
>because each child's width is calculated according to the parent's width
>divided by the number of children, disregarding the margins. I'm using
>padding instead, but that has the drawback that in a tiled list, for
>example, there are no non-selectable gaps.
>
>I think the fix is to take margins into account, but there might be
>performance implications.
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-TileLayout-tp62568p62570.html
>=02%7C01%7C%7C1256d4c11ee54c60a90e08d4b97b6725%7Cfa7b1b5a7b34438794ae
>d2c178decee1%7C0%7C0%7C636337387035370705=Lt0zEPpqPr2Hj7eng2EIwehxJ2
>sdhoTLinXT3qBZ6lE%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] TileLayout

[Peter Ent]

Hi,

Use margins on the items.

‹peter

On 6/22/17, 9:48 AM, "yishayw"  wrote:

>What is the preferred way to set gaps between columns and between rows?
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-TileLayout-tp62568.html=
>02%7C01%7C%7Ca0c719ba202142b1722c08d4b977c8a7%7Cfa7b1b5a7b34438794aed2c178
>decee1%7C0%7C0%7C636337371492919591=DyQk9yp6FLBacjJp1orJR5OugwUbqGGm
>7qyC8lBIXsA%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [LAST CALL] Release FlexJS/FalconJX 0.8.0

[Peter Ent]

Just an FYI:

I'm trying to fix a bug in Mobile project with the Camera class. I am
hoping to wrap it up today.

Regards,
Peter
>

Re: [ApacheCon/FlexJS Summit] FlexJS 1.0 Discussion Round - Summary

[Peter Ent]

The Storage package is definitely incomplete. We should address access from 
browser (JS & SWF) air, and Cordova. 

Peter 


> On May 21, 2017, at 10:44 AM, PKumar <prashaku...@gmail.com> wrote:
> 
> Peter,
> 
> As compare to regular FlexSDK , there is no way to select any file from
> file system and adding file type filter on selection. Also no way to open
> FileSave dialogue box.
> 
> On 21-May-2017 7:18 PM, "Peter Ent-2 [via Apache Flex Development]" <
> ml+s247n61714...@n4.nabble.com> wrote:
> 
>> The FlexJS Storage package address some storage concerns. It provides file
>> handling when run via AIR and on mobile devices via Cordova. Since there
>> are sandboxing issues with the Flash Player, I'm not sure what else we can
>> do there besides local storage.
>> 
>> ‹peter
>> 
>> On 5/21/17, 7:25 AM, "PKumar" <[hidden email]
>> <http:///user/SendEmail.jtp?type=node=61714=0>> wrote:
>> 
>>> FileHandling  can also be a option in the list. Right now FlexJS not
>>> having
>>> any file handling capabilities.
>>> 
>>> On 20-May-2017 5:45 PM, "yishayw [via Apache Flex Development]" <
>>> [hidden email] <http:///user/SendEmail.jtp?type=node=61714=1>>
>> wrote:
>>> 
>>>> Items 1-9 were considered musts.
>>>> 
>>>> Fontkit library port (item 7) made it to the list because it was
>>>> blocking
>>>> Maven builds. I think Chris has found a workaround, so maybe we can
>>>> strike
>>>> that off.
>>>> 
>>>> Post meeting there was some agreement that a better looking default
>>>> theme
>>>> was also a must. Leonidas said he would provide us with the graphics.
>>>> That
>>>> would be very helpful in my opinion.
>>>> 
>>>> 
>>>> --
>>>> If you reply to this email, your message will be added to the
>> discussion
>>>> below:
>>>> 
>>>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fapache-fl
>>>> ex-development.247.n4.nabble=02%7C01%7C%7C9e768268022a4555dcd008
>> 
>>>> d4a03dfbb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63630963545957906
>> 
>>>> 9=D4m8GDMEUC5WcEpHcxKSDOGHnc4MXZx3fhT4ksecVw0%3D=0.
>>>> com/ApacheCon-FlexJS-Summit-FlexJS-1-0-Discussion-Round-
>>>> Summary-tp61700p61703.html
>>>> To start a new topic under Apache Flex Development, email
>>>> [hidden email] <http:///user/SendEmail.jtp?type=node=61714=2>
>>>> To unsubscribe from Apache Flex Development, click here
>>>> 
>>>> <https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fapache-f
>>>> lex-development.247.n4.nabble.com%2Ftemplate%2FNamlServlet.jtp%3Fmacr
>> 
>>>> o%3Dunsubscribe_by_code%26node%3D1%26code%3DcHJhc2hha3VtYXJAZ21haWwuY29tf
>> 
>>>> DF8LTU0MTcyMzE2NA=02%7C01%7C%7C9e768268022a4555dcd008d4a03dfbb9%7Cfa
>> 
>>>> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636309635459579069=FGQ9vpd
>> 
>>>> yMvICZ4dTpGxOsYF0hWp%2FMPg6x%2FwB3thsayM%3D=0==>
>>>> .
>>>> NAML
>>>> 
>>>> <https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fapache-f
>>>> lex-development.247.n4.nabble.com%2Ftemplate%2FNamlServlet.jtp%3Fmacr
>> 
>>>> o%3Dmacro_viewer%26id%3Dinstant_html%2521nabble%253Aemail.naml%26base%3Dn
>> 
>>>> abble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNames
>> 
>>>> pace-nabble.view.web.template.NodeNamespace%26breadcrumbs%3Dnotify_subscr
>> 
>>>> ibers%2521nabble%253Aemail.naml-instant_emails%2521nabble%253Aemail.naml-
>> 
>>>> send_instant_email%2521nabble%253Aemail.naml=02%7C01%7C%7C9e76826802
>> 
>>>> 2a4555dcd008d4a03dfbb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63630
>> 
>>>> 9635459579069=VVuCGtlA2uJ2eu4LI9uKVYKFElfHNdBz0uQpNe%2F%2BBGY%3D
>> 
>>>> served=0>
>>>> 
>>> 
>>> 
>>> 
>>> 
>>> --
>>> View this message in context:
>>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fapache-fle
>>> x-development.247.n4.nabble.com%2FApacheCon-FlexJS-Summit-FlexJS-1-0-D
>> 
>>> iscussion-Round-Summary-tp61700p61713.html=02%7C01%7C%7C9e768268022a4
>> 
>>> 555dcd008d4a03dfbb9%7Cf

Re: [ApacheCon/FlexJS Summit] FlexJS 1.0 Discussion Round - Summary

[Peter Ent]

The FlexJS Storage package address some storage concerns. It provides file
handling when run via AIR and on mobile devices via Cordova. Since there
are sandboxing issues with the Flash Player, I'm not sure what else we can
do there besides local storage.

‹peter

On 5/21/17, 7:25 AM, "PKumar"  wrote:

>FileHandling  can also be a option in the list. Right now FlexJS not
>having
>any file handling capabilities.
>
>On 20-May-2017 5:45 PM, "yishayw [via Apache Flex Development]" <
>ml+s247n6170...@n4.nabble.com> wrote:
>
>> Items 1-9 were considered musts.
>>
>> Fontkit library port (item 7) made it to the list because it was
>>blocking
>> Maven builds. I think Chris has found a workaround, so maybe we can
>>strike
>> that off.
>>
>> Post meeting there was some agreement that a better looking default
>>theme
>> was also a must. Leonidas said he would provide us with the graphics.
>>That
>> would be very helpful in my opinion.
>>
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>> 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>ex-development.247.n4.nabble=02%7C01%7C%7C9e768268022a4555dcd008
>>d4a03dfbb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63630963545957906
>>9=D4m8GDMEUC5WcEpHcxKSDOGHnc4MXZx3fhT4ksecVw0%3D=0.
>> com/ApacheCon-FlexJS-Summit-FlexJS-1-0-Discussion-Round-
>> Summary-tp61700p61703.html
>> To start a new topic under Apache Flex Development, email
>> ml+s247n1...@n4.nabble.com
>> To unsubscribe from Apache Flex Development, click here
>> 
>>>lex-development.247.n4.nabble.com%2Ftemplate%2FNamlServlet.jtp%3Fmacr
>>o%3Dunsubscribe_by_code%26node%3D1%26code%3DcHJhc2hha3VtYXJAZ21haWwuY29tf
>>DF8LTU0MTcyMzE2NA=02%7C01%7C%7C9e768268022a4555dcd008d4a03dfbb9%7Cfa
>>7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636309635459579069=FGQ9vpd
>>yMvICZ4dTpGxOsYF0hWp%2FMPg6x%2FwB3thsayM%3D=0==>
>> .
>> NAML
>> 
>>>lex-development.247.n4.nabble.com%2Ftemplate%2FNamlServlet.jtp%3Fmacr
>>o%3Dmacro_viewer%26id%3Dinstant_html%2521nabble%253Aemail.naml%26base%3Dn
>>abble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNames
>>pace-nabble.view.web.template.NodeNamespace%26breadcrumbs%3Dnotify_subscr
>>ibers%2521nabble%253Aemail.naml-instant_emails%2521nabble%253Aemail.naml-
>>send_instant_email%2521nabble%253Aemail.naml=02%7C01%7C%7C9e76826802
>>2a4555dcd008d4a03dfbb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63630
>>9635459579069=VVuCGtlA2uJ2eu4LI9uKVYKFElfHNdBz0uQpNe%2F%2BBGY%3D
>>served=0>
>>
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FApacheCon-FlexJS-Summit-FlexJS-1-0-D
>iscussion-Round-Summary-tp61700p61713.html=02%7C01%7C%7C9e768268022a4
>555dcd008d4a03dfbb9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636309635
>459579069=BTZ1%2FXsfjGT7XLQEFFvVz5L%2F1F0XIqB5BzxxaVT0%2Fb0%3D
>ved=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [ApacheCon/FlexJS Summit] FlexJS 1.0 Discussion Round - Summary

[Peter Ent]

Looks like you got some good advice about being a contributor/committer.

As for the file system/storage issue. The FlexJS Storage project seems
like a good place for all of storage/repository/file system functions to
go. We can give them different package names within the project, too, of
course.

The key is providing functionality across the platforms which are: the
browser, the Flash Player, Cordova, and Air. From an application
developer's point of view, they should have a generic way to access
storage that works on all the platform, or at least, does not crash on any
particular platform if the platform does not support the feature. For
example, if you want to make the device's file system available, that's
really only available when run in Air and on mobile using Cordova; the
browser environment prevents direct access to the underlying file system
for security reasons. In this case, any file system classes or functions
should compile for browser and Flash Player, even if they won't do
anything (e.g., saving a file).

Here's an example: The HTML  element provides the UI for selecting
a file to upload. That needs to have Flash Player, equivalence
(FileReference API), Air has a richer API for this, and I believe Cordova
does as well. But the FlexJS class(es) that a developer would use should
be generic:

  

or something like that.

I hope that helps.
—peter

On 5/25/17, 1:42 AM, "PKumar" <prashaku...@gmail.com> wrote:

>Peter,
>
>If u can give me few pointers then I am willing to work on this.
>
>One more point, right now I am not a flexjs contributer. Since one year I
>am using flexjs and creating demos so that I can get good grip on it.
>Now I am having free time and want to contribute to FlexJS. So What are
>the
>process to become official FlexJS contributer? Please suggest.
>
>
>On 22-May-2017 5:50 PM, "Peter Ent-2 [via Apache Flex Development]" <
>ml+s247n61737...@n4.nabble.com> wrote:
>
>> The Storage package is definitely incomplete. We should address access
>> from browser (JS & SWF) air, and Cordova.
>>
>> Peter
>>
>>
>> > On May 21, 2017, at 10:44 AM, PKumar <[hidden email]
>> <http:///user/SendEmail.jtp?type=node=61737=0>> wrote:
>> >
>> > Peter,
>> >
>> > As compare to regular FlexSDK , there is no way to select any file
>>from
>> > file system and adding file type filter on selection. Also no way to
>> open
>> > FileSave dialogue box.
>> >
>> > On 21-May-2017 7:18 PM, "Peter Ent-2 [via Apache Flex Development]" <
>> > [hidden email] <http:///user/SendEmail.jtp?type=node=61737=1>>
>> wrote:
>> >
>> >> The FlexJS Storage package address some storage concerns. It provides
>> file
>> >> handling when run via AIR and on mobile devices via Cordova. Since
>> there
>> >> are sandboxing issues with the Flash Player, I'm not sure what else
>>we
>> can
>> >> do there besides local storage.
>> >>
>> >> ‹peter
>> >>
>> >> On 5/21/17, 7:25 AM, "PKumar" <[hidden email]
>> >> <http:///user/SendEmail.jtp?type=node=61714=0>> wrote:
>> >>
>> >>> FileHandling  can also be a option in the list. Right now FlexJS not
>> >>> having
>> >>> any file handling capabilities.
>> >>>
>> >>> On 20-May-2017 5:45 PM, "yishayw [via Apache Flex Development]" <
>> >>> [hidden email]
>><http:///user/SendEmail.jtp?type=node=61714=1>>
>> >> wrote:
>> >>>
>> >>>> Items 1-9 were considered musts.
>> >>>>
>> >>>> Fontkit library port (item 7) made it to the list because it was
>> >>>> blocking
>> >>>> Maven builds. I think Chris has found a workaround, so maybe we can
>> >>>> strike
>> >>>> that off.
>> >>>>
>> >>>> Post meeting there was some agreement that a better looking default
>> >>>> theme
>> >>>> was also a must. Leonidas said he would provide us with the
>>graphics.
>> >>>> That
>> >>>> would be very helpful in my opinion.
>> >>>>
>> >>>>
>> >>>> --
>> >>>> If you reply to this email, your message will be added to the
>> >> discussion
>> >>>> below:
>> >>>>
>> >>>> https://na01.safelinks.protection.outlook.com/?url=
>> >> http%3A%2F%2F

Re: [FlexJS] Accordion broken

[Peter Ent]

I am looking into it. I will also create an example for Accordion so it
will be easier to test it in the future.
‹peter

On 5/30/17, 6:39 AM, "Harbs"  wrote:

>It seems like the new layouts totally broke Accordion.
>
>Accordion relied on absolute sizing to handle expanding and collapsing of
>content. I tried to add a new layout which is basically a copy of the old
>OneFlexibleVerticalLayout and use that for accordion, but that does not
>seem to work either due to changes in containers (I think).
>
>Peter, do you thin you could look into this?
>
>Thanks,
>Harbs

Re: [FlexJS] Accordion broken

[Peter Ent]

Hi,

Do you have a quick example of how to use the FlexJS Accordion? The ASDoc
on it is thin. The children of the Flex SDK Accordion were navigation
components that supported things like title so each section could be
labeled. I don't see an AccordionChild or something similar that can be
used with Accordion. I took a guess and made Container a child of it, but
it just blew up. 

Thanks,
‹peter

On 5/30/17, 6:39 AM, "Harbs"  wrote:

>It seems like the new layouts totally broke Accordion.
>
>Accordion relied on absolute sizing to handle expanding and collapsing of
>content. I tried to add a new layout which is basically a copy of the old
>OneFlexibleVerticalLayout and use that for accordion, but that does not
>seem to work either due to changes in containers (I think).
>
>Peter, do you thin you could look into this?
>
>Thanks,
>Harbs

Re: [FlexJS] Accordion broken

[Peter Ent]

OK, thanks. Alex some alternative layouts I can try.
—peter

On 5/30/17, 11:35 AM, "Harbs" <harbs.li...@gmail.com> wrote:

>The reasons it’s broken is (at least) thee-fold:
>
>1. Panels contain content and need to be collapsed despite the fact that
>content exists.
>2. The Collapse bead can only infer that it’s collapsed by the fact that
>the size is the collapsed size — which only makes sense if the size is
>set.
>3. The title must be measured to set the collapsed height correctly.
>
>> On May 30, 2017, at 6:21 PM, Harbs <harbs.li...@gmail.com> wrote:
>> 
>> Something like this:
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>> This is the markup of an Accordion which used to work, which doesn’t
>>anymore.
>> 
>>  
>>
>>
>>  
>>  
>>      
>>  
>>
>>
>>
>> 
>> 
>>> On May 30, 2017, at 4:54 PM, Peter Ent <p...@adobe.com.INVALID> wrote:
>>> 
>>> Hi,
>>> 
>>> Do you have a quick example of how to use the FlexJS Accordion? The
>>>ASDoc
>>> on it is thin. The children of the Flex SDK Accordion were navigation
>>> components that supported things like title so each section could be
>>> labeled. I don't see an AccordionChild or something similar that can be
>>> used with Accordion. I took a guess and made Container a child of it,
>>>but
>>> it just blew up.
>>> 
>>> Thanks,
>>> ‹peter
>>> 
>>> On 5/30/17, 6:39 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>>> 
>>>> It seems like the new layouts totally broke Accordion.
>>>> 
>>>> Accordion relied on absolute sizing to handle expanding and
>>>>collapsing of
>>>> content. I tried to add a new layout which is basically a copy of the
>>>>old
>>>> OneFlexibleVerticalLayout and use that for accordion, but that does
>>>>not
>>>> seem to work either due to changes in containers (I think).
>>>> 
>>>> Peter, do you thin you could look into this?
>>>> 
>>>> Thanks,
>>>> Harbs
>>> 
>> 
>

Re: [FlexJS] Accordion broken

[Peter Ent]

Hi,

It looks like this is the last thing to be resolved before we can make
FlexJS 0.8 release.

I'm seeing two title bars per item in the Accordion. Any suggestions for
how to resolve this, based on the information I've given below?

Thanks,
Peter

On 6/1/17, 3:49 PM, "Peter Ent" <p...@adobe.com> wrote:

>I've checked in my changes to the Accordion components. It still is not
>working correctly and I cannot figure out what is happening. The
> used as the data to the Accordion are being placed as children
>of AccordionItemRenderers which are themselves Panels. So there are two
>TitleBars present per Accordion section.
>
>The layout mechanism changed so that the GroupView (the base view bead for
>all container-type view beads) no longer controls when layouts run; that
>is done by the layouts themselves. GroupView et al has a beforeLayout()
>and afterLayout() functions called by the layout classes which might be
>helpful, I'm not sure.
>
>Panel also changed quite a bit. A Panel is now a Group with its own layout
>that controls the placement of the TitleBar and Container which is its
>content area. When you specify a layout bead on a Panel, the Panel
>actually moves it to the content area Container. Perhaps this has
>something to do with the behavior we are now seeing.
>
>Please let me know if you have any suggestions on how to handle the
>Accordion as it now sits and I'll be happy to answer any questions about
>how the current view/layout system works now.
>
>If I may, perhaps Accordion could be changed as follows:
>
>
>
>   
>
>
>
>
>
>
>The Accordion + AccordionView would create 2 children for each
>AccordionSection in the Accordion's space: an AccordionHeader + child>. 
>
>The model would indicate which  is being viewed and the
>layout, such as OneFlexibleChildVerticalLayout or
>OneFlexibleChildHorizontalLayout, would take care of sizing and
>positioning the AccordionHeader and  elements. The child> elements not visible would simply have visible=false set; the
>layout will then ignore them.
>
>For the HTML side, this example would create a  with four children
>and not have any deep nesting unless that what the 
>produces. The  that's visible would have overflow:auto or
>overflow:hidden while the other  elements would have
>display:none set. 
>
>Merely a suggestion, and could probably use some refinement.
>
>‹peter
>
>
>On 6/1/17, 2:03 PM, "yishayw" <yishayj...@hotmail.com> wrote:
>
>>Harbs wrote
>>> \2. The Collapse bead can only infer that it¹s collapsed by the fact
>>>that
>>> the size is the collapsed size ‹ which only makes sense if the size is
>>> set.
>>
>>Shouldn't .height return the measured height, regardless of whether it
>>was
>>explicitly set?
>>
>>
>>
>>
>>--
>>View this message in context:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fl
>>e
>>x-development.247.n4.nabble.com%2FFlexJS-Accordion-broken-tp61937p620
>>0
>>8.html=02%7C01%7C%7C9b640697ac694828308808d4a91a8573%7Cfa7b1b5a7b344
>>3
>>8794aed2c178decee1%7C0%7C0%7C636319378749470812=I%2BJ9TjnMxtY8VD4b4
>>h
>>6ljmTghd1Wy8yG8xo2eR9s6OY%3D=0
>>Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: [FlexJS] Layout of NumericStepper is broken

[Peter Ent]

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 incrementing
button and the JS version has the buttons just slightly misaligned with
the input field. Running this on macOS Sierra, Safari 10.1.1, Firefox
50.0.3, and Chrome 58.0.3.

on which OS(es) and browser(s) are you seeing this?

‹peter

On 6/5/17, 10:31 AM, "piotrz"  wrote:

>Hi,
>
>I just tried NumericStepper on our release branch and it looks horrible. I
>have following code [1], can someone look into that ? I will raise jira
>later.
>
>ex-development.247.n4.nabble.com%2Ffile%2Fn62108%2Fbroken_numeric_step
>per.png=02%7C01%7C%7Cccc8644d5a054e8cd1e508d4ac21a197%7Cfa7b1b5a7b344
>38794aed2c178decee1%7C0%7C0%7C636322707827257340=uLxglwUpmvJYZRzMtXF
>iAi0W65ytuPaVL1DxfVYBCUo%3D=0>
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2FwbLN=02%7C01%7C%7Cccc8644d5a054e8cd1e508d4ac21a197%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636322707827257340=8wSGQeRReell
>5enJgXlniYVCvf9Jq0OQazKyfksWBdI%3D=0
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layout-of-NumericStepper-is-b
>roken-tp62108.html=02%7C01%7C%7Cccc8644d5a054e8cd1e508d4ac21a197%7Cfa
>7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636322707827257340=VESRAJBK
>DR%2FiSQd6M3xC7tB78jqMEgq%2Bh%2BPPMfj7f%2FM%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Accordion broken

[Peter Ent]

I haven't sync'd anything since Friday, but I don't seem to be having the
measurement problem you are talking about.

I changed the Accordion children to VContainer and added the
TitleBarModel. Now I see the TitleBar (although it is blank) and the
segment contents. When I expose or hide the segments, I see all of the
bars stacked above and below the opened segment.

On SWF, the title bars are blank; on HTML the title bars are "undefined"
(as expected and noted in another thread on null vs undefined).

—peter

On 6/4/17, 5:57 AM, "Harbs" <harbs.li...@gmail.com> wrote:

>1. Seems to be a data binding problem. (See other thread.) Yishay
>committed a temporary work-around, but we don’t think that’s the right
>way to fix the problem.
>2. seems to be a measurement problem. The titleBar height is not being
>measured correctly. This is a workaround (in a custom item renderer)
>
>override public function get collapsedHeight():Number{
>return 30;
>}
>
>
>> On Jun 4, 2017, at 12:41 AM, Harbs <harbs.li...@gmail.com> wrote:
>> 
>> I worked around the Promise issue (by copying js.swc to my project and
>>not using the one in the SDK).
>> 
>> There’s at least 2 issues still:
>> 1. The title property from the model is not being applied to the view
>>of the item renderer.
>> 2. The collapsed height of the collapsed items are 0 instead of the
>>title bar height.
>> 
>>> On Jun 4, 2017, at 12:10 AM, Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>> Yishay did the implementation of this so I was a bit shaky on the
>>>details.
>>> 
>>> I just looked at our code, and it appears that we did not actually use
>>>panels for the children.
>>> 
>>> It turns out the children are actually Containers which have a
>>>TitleBarModel bead. Sorry about the confusion. It might make sense to
>>>have an interface for an accordion-compatible container.
>>> 
>>> We will put together an example which should work better in the
>>>morning.
>>> 
>>> I cannot test my app which uses the Accordion right now because
>>>Promise is currently broken (like I wrote in my other email).
>>> 
>>> Harbs
>>> 
>>>> On Jun 2, 2017, at 7:01 PM, Peter Ent <p...@adobe.com.INVALID> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> It looks like this is the last thing to be resolved before we can make
>>>> FlexJS 0.8 release.
>>>> 
>>>> I'm seeing two title bars per item in the Accordion. Any suggestions
>>>>for
>>>> how to resolve this, based on the information I've given below?
>>>> 
>>>> Thanks,
>>>> Peter
>>>> 
>>>> On 6/1/17, 3:49 PM, "Peter Ent" <p...@adobe.com> wrote:
>>>> 
>>>>> I've checked in my changes to the Accordion components. It still is
>>>>>not
>>>>> working correctly and I cannot figure out what is happening. The
>>>>>  used as the data to the Accordion are being placed as
>>>>>children
>>>>> of AccordionItemRenderers which are themselves Panels. So there are
>>>>>two
>>>>> TitleBars present per Accordion section.
>>>>> 
>>>>> The layout mechanism changed so that the GroupView (the base view
>>>>>bead for
>>>>> all container-type view beads) no longer controls when layouts run;
>>>>>that
>>>>> is done by the layouts themselves. GroupView et al has a
>>>>>beforeLayout()
>>>>> and afterLayout() functions called by the layout classes which might
>>>>>be
>>>>> helpful, I'm not sure.
>>>>> 
>>>>> Panel also changed quite a bit. A Panel is now a Group with its own
>>>>>layout
>>>>> that controls the placement of the TitleBar and Container which is
>>>>>its
>>>>> content area. When you specify a layout bead on a Panel, the Panel
>>>>> actually moves it to the content area Container. Perhaps this has
>>>>> something to do with the behavior we are now seeing.
>>>>> 
>>>>> Please let me know if you have any suggestions on how to handle the
>>>>> Accordion as it now sits and I'll be happy to answer any questions
>>>>>about
>>>>> how the current view/layout system works now.
>>>>> 
>>>>> If I may, perhaps Accordion could be changed as fol

Re: [FlexJS] List

[Peter Ent]

That had to be accidental. I see in defaults.css that List has a Viewport
rather than ScrollingViewport. Just change that and lists should default
to scrolling.

Need to watch the DataGrid because its lists should not scroll - they just
grow and the enclosing container scrolls them all together.

‹peter

On 6/5/17, 3:01 AM, "Harbs"  wrote:

>It looks like List defaults to overflow: hidden while it used to allow
>scrolling by default.
>
>Was this an intentional change?

Re: [FlexJS] Accordion broken

[Peter Ent]

With some guidance from Alex, I have the Accordion "working". The problem
now is that it appears as a Panel-in-Panel for each item. For example,
with two Panels in the dataProvider, there are two bars and whichever is
"open" or "selected" shows the Panel from the dataProvider along with its
title bar. I understand using a Panel as the itemRenderer, but I don't see
how there cannot be two title bars. I will continue to sort this out.

—peter

On 5/31/17, 2:47 PM, "Harbs" <harbs.li...@gmail.com> wrote:

>Yishay had some code to handle the cases where it’s not set via MXML
>which you removed.
>
>I changed his code to simply intialize the document if it was not set by
>MXML like this:
>
>   //Needed if the layout is not declared using MXML
>   private function 
> initializeDocument(contentView:ILayoutView):void
>   {
>   document = {};
>   for (var i:int = 0; i < contentView.numElements; i++)
>   {
>   var child:IStyleableObject = 
> contentView.getElementAt(i) as
>IStyleableObject;
>   document[child.id] = child;
>   }
>   }
>
>and in layout():
>   if(document == null)
>   initializeDocument(contentView);
>
>An AccordionLayout might make sense though. And switching to selection
>rather than checking collapsed might make sense as well.
>
>Thanks for working on this.
>
>> On May 31, 2017, at 7:47 PM, Peter Ent <p...@adobe.com.INVALID> wrote:
>> 
>> I'm still working on this and ran into a couple of issues.
>> 
>> The flexible child layouts no longer provide a way to explicitly set a
>> child; instead they rely in the child's id being used to retrieve the
>> child from the document. Unfortunately, a layout that is not referenced
>>in
>> MXML will not get its document set.
>> 
>> Perhaps a better solution is to write "AccordionLayout" that will expand
>> the child selected by the model, but I'm still looking at making use of
>> what is already there.
>> 
>> —peter
>> 
>> 
>> 
>> On 5/30/17, 11:35 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>> 
>>> The reasons it’s broken is (at least) thee-fold:
>>> 
>>> 1. Panels contain content and need to be collapsed despite the fact
>>>that
>>> content exists.
>>> 2. The Collapse bead can only infer that it’s collapsed by the fact
>>>that
>>> the size is the collapsed size — which only makes sense if the size is
>>> set.
>>> 3. The title must be measured to set the collapsed height correctly.
>>> 
>>>> On May 30, 2017, at 6:21 PM, Harbs <harbs.li...@gmail.com> wrote:
>>>> 
>>>> Something like this:
>>>> 
>>>>   
>>>>   
>>>>   
>>>>   
>>>>   
>>>>           
>>>>   
>>>>   
>>>> 
>>>> This is the markup of an Accordion which used to work, which doesn’t
>>>> anymore.
>>>> 
>>>>
>>>>   
>>>>   
>>>>
>>>>
>>>>
>>>>
>>>>   
>>>>   
>>>>   
>>>> 
>>>> 
>>>>> On May 30, 2017, at 4:54 PM, Peter Ent <p...@adobe.com.INVALID>
>>>>>wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> Do you have a quick example of how to use the FlexJS Accordion? The
>>>>> ASDoc
>>>>> on it is thin. The children of the Flex SDK Accordion were navigation
>>>>> components that supported things like title so each section could be
>>>>> labeled. I don't see an AccordionChild or something similar that can
>>>>>be
>>>>> used with Accordion. I took a guess and made Container a child of it,
>>>>> but
>>>>> it just blew up.
>>>>> 
>>>>> Thanks,
>>>>> ‹peter
>>>>> 
>>>>> On 5/30/17, 6:39 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>>>>> 
>>>>>> It seems like the new layouts totally broke Accordion.
>>>>>> 
>>>>>> Accordion relied on absolute sizing to handle expanding and
>>>>>> collapsing of
>>>>>> content. I tried to add a new layout which is basically a copy of
>>>>>>the
>>>>>> old
>>>>>> OneFlexibleVerticalLayout and use that for accordion, but that does
>>>>>> not
>>>>>> seem to work either due to changes in containers (I think).
>>>>>> 
>>>>>> Peter, do you thin you could look into this?
>>>>>> 
>>>>>> Thanks,
>>>>>> Harbs
>>>>> 
>>>> 
>>> 
>> 
>

Re: [FlexJS] Accordion broken

[Peter Ent]

I've checked in my changes to the Accordion components. It still is not
working correctly and I cannot figure out what is happening. The
 used as the data to the Accordion are being placed as children
of AccordionItemRenderers which are themselves Panels. So there are two
TitleBars present per Accordion section.

The layout mechanism changed so that the GroupView (the base view bead for
all container-type view beads) no longer controls when layouts run; that
is done by the layouts themselves. GroupView et al has a beforeLayout()
and afterLayout() functions called by the layout classes which might be
helpful, I'm not sure.

Panel also changed quite a bit. A Panel is now a Group with its own layout
that controls the placement of the TitleBar and Container which is its
content area. When you specify a layout bead on a Panel, the Panel
actually moves it to the content area Container. Perhaps this has
something to do with the behavior we are now seeing.

Please let me know if you have any suggestions on how to handle the
Accordion as it now sits and I'll be happy to answer any questions about
how the current view/layout system works now.

If I may, perhaps Accordion could be changed as follows:



   






The Accordion + AccordionView would create 2 children for each
AccordionSection in the Accordion's space: an AccordionHeader + . 

The model would indicate which  is being viewed and the
layout, such as OneFlexibleChildVerticalLayout or
OneFlexibleChildHorizontalLayout, would take care of sizing and
positioning the AccordionHeader and  elements. The  elements not visible would simply have visible=false set; the
layout will then ignore them.

For the HTML side, this example would create a  with four children
and not have any deep nesting unless that what the 
produces. The  that's visible would have overflow:auto or
overflow:hidden while the other  elements would have
display:none set. 

Merely a suggestion, and could probably use some refinement.

‹peter


On 6/1/17, 2:03 PM, "yishayw"  wrote:

>Harbs wrote
>> \2. The Collapse bead can only infer that it¹s collapsed by the fact
>>that
>> the size is the collapsed size ‹ which only makes sense if the size is
>> set.
>
>Shouldn't .height return the measured height, regardless of whether it was
>explicitly set?
>
>
>
>
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Accordion-broken-tp61937p6200
>8.html=02%7C01%7C%7C9b640697ac694828308808d4a91a8573%7Cfa7b1b5a7b3443
>8794aed2c178decee1%7C0%7C0%7C636319378749470812=I%2BJ9TjnMxtY8VD4b4h
>6ljmTghd1Wy8yG8xo2eR9s6OY%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layout of NumericStepper is broken

[Peter Ent]

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
size change handler runs.

If I remove the test and always call the size change handler, both this
simple test and the FlexJSStore work fine. But there are some minor
alignment issues which I can also correct.

I don't want to check in my changes without having Alex think about why
those changes were put in place since there may be consequences of
returning the NS to a more simpler form.

‹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=02%7C01%7C%7Cafd0984b2a2d4a2643
>d308d4acae46fd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63632331191193
>2511=6aA%2FoP%2BRTmEXaHh0aU2pRgufprYkfmGw7tmkipKsFMM%3D=0
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layout-of-NumericStepper-is-b
>roken-tp62108p62149.html=02%7C01%7C%7Cafd0984b2a2d4a2643d308d4acae46f
>d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636323311911932511=io
>xNCT03PcPjwOIytCr2%2FUjst9mGuqx2b%2BCTLqBJ7Kw%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] List

[Peter Ent]

Yes. I think people expect lists to scroll by default. Sorry I missed that
when I made those changes.
—peter

On 6/5/17, 1:43 PM, "Harbs" <harbs.li...@gmail.com> wrote:

>That’s what I did for my app css. Changing it to ScrollingViewport fixed
>it.
>
>I did not know whether I should change defaults.css in Basic. It sounds
>like you are saying yes.
>
>> On Jun 5, 2017, at 5:25 PM, Peter Ent <p...@adobe.com.INVALID> wrote:
>> 
>> That had to be accidental. I see in defaults.css that List has a
>>Viewport
>> rather than ScrollingViewport. Just change that and lists should default
>> to scrolling.
>> 
>> Need to watch the DataGrid because its lists should not scroll - they
>>just
>> grow and the enclosing container scrolls them all together.
>> 
>> ‹peter
>> 
>> On 6/5/17, 3:01 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>> 
>>> It looks like List defaults to overflow: hidden while it used to allow
>>> scrolling by default.
>>> 
>>> Was this an intentional change?
>> 
>

Re: [FlexJS] Accordion broken

[Peter Ent]

Thanks. I'll look into this today if I get a chance and definitely tomorrow. 

Peter 


> On Jun 4, 2017, at 6:05 AM, yishayw  wrote:
> 
> Here's [1] an example app.
> 
> The 2 problems I see:
> 
> 1) DataBinding problems [2] cause titles to be undefined. I hacked a fix on
> TLF branch, but this should probably addressed differently.
> 2) TitleBar.height returns 0, even though the measured height is 30. I think
> this is a bug, am I wrong?
> 
> Thanks.
> 
> [1] 
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2FQUj1=02%7C01%7C%7Cb335b9934ee44b3faf9d08d4ab3143ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636321675477479646=0qp76vTwMIdyOnFnuFZh1CPn62T3ALjIvYV47j3Aqvs%3D=0
> [2]
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.247.n4.nabble.com%2FFlexJS-DataBinding-Problem-td62073.html=02%7C01%7C%7Cb335b9934ee44b3faf9d08d4ab3143ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636321675477489658=1y0o9R2qZWimrsFH%2FTyU%2B5061RVbnFQgpRsQ5CKtmfc%3D=0
> 
> 
> 
> 
> --
> View this message in context: 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.247.n4.nabble.com%2FFlexJS-Accordion-broken-tp61937p62080.html=02%7C01%7C%7Cb335b9934ee44b3faf9d08d4ab3143ce%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636321675477489658=s3BPfklP65X5fXGknNX0ZB%2FfREeToXzsiGhKV%2BSpSJo%3D=0
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [2/2] git commit: [flex-asjs] [refs/heads/release0.8.0] - fix event types for valuechange. Otherwise Binding would break. Events are global and should be compatible for any given event type

[Peter Ent]

I don't think PAYG is always obvious and I continue to struggle with the
question. Some examples:

a. Anything that can be expressed as a style probably does not need a
bead, unless the style is not native to the platform. Border and
backgroundColor are good examples. These are built into HTML, but not the
Flash Player. So the border and background styles are implemented as beads
but they are only available on the Flash Player platform. Width, height,
x, y, etc. are also styles in HTML but properties in Flash, so they don't
need beads either. Plus they are pretty fundamental to UI systems.

b. Completeness also gives me pangs. You would think that a slider's basic
properties of a minimum value, maximum value, and a current value would
not need to be questioned. And that's true, as properties they are
necessary to define a slider. But should a slider emit an event whenever
its min, max, or value changes? Many apps will just go get the current
value when they need it. The slider's mouse controller observes the
dynamic changes in the thumb position and emits an event for each movement
- but not everyone needs that so such a controller could be optional, but
without a controller, you can't actually change the thumb with the mouse
so you need the controller regardless, but do you need to emit the event
when the thumb is being moved?

c. When you do have to have something, like a slider mouse controller, to
make the component work at its basic level, do you make an option as to
whether or not to emit the event or do you have one controller that emits
events as the thumb moves and one controller that does not emit the event?
Is one controller a subclass of the other or a duplicate version?

d. Its often difficult to tell if something should be present just because
it always has been present (in Flex). When you have a set of properties
and events, we need to ask if those are essential to making the component
work. Or rather, what is the component's default behavior. For a text
input component, the default because is accepting keyboard input, without
filtering. Making it a secure input with a mask, is extra work/behavior
and thus becomes a bead. Beads enhance and augment the default behavior as
a rule of thumb.

PAYG for me, raises lots of questions about programming practices and
patterns. Do you make it easier on developers by packaging common
properties/events/options even if some are not used that often, or do you
break them down into many versions?

One way to handle this is by looking at the Express project. There, the
most commonly used patterns are put together. For instance, data binding
is in everything. Or you might have the slider always emit every event it
can. 

The Basic project should be the bare-bones components with lots of options
as beads. Then package them into common use cases and put that into
another project, like Express, to make it more palatable.

I would argue (just a little) that more complex components, like DataGrid,
and perhaps even NumericStepper, should be in a project that lives between
Basic and Express. This would leave Basic being very, well, basic (label,
button, text input, group and container for instance).

I hope that helps a little.

‹peter

On 6/7/17, 1:27 AM, "Justin Mclean"  wrote:

>Hi,
>
>> I agree that there could be a even smaller bead that doesn't track
>>changes
>> as you move the thumb.  Something to do in the next release, IMO.
>
>Could be or must be? Again just trying to understand why PAYG wasn¹t
>followed in this case.
>
>Was this just an accidental design omission that no body picked up on it
>OR is it sometimes OK to have optional feature code in beads?
>
>Thanks,
>Justin

Re: Beads and DRY (was Re: [FlexJS] Removing PasswordInputBead has no effect)

[Peter Ent]

If you look at the layouts, you can see these questions for real. Take
VerticalLayout. The idea is to stack children of some component
vertically. Those children can be given a) no explicit size, b) an
explicit size as pixel values, c) a percentage size. You know what the
VerticalLayout is supposed to do, but how it does it depends on the
platform. Plus there are some questions:

Do you provide an option to space them (a gap) or is that
VerticalLayoutWithGap?
Do you provide an option to horizontally align them or is that
VerticalLayoutWithHorizontalAlignment?
What if you want both a gap and an alignment? Is that
VerticalLayoutWithGapAndHorizontalAlignment?

Achieving a gap and alignment is pretty easy and I believe can be done
within the same loop pass as stacking the elements.

We circumvented the gap issue by saying you achieving by giving the
children being stacked margin style values. So that eliminates two of the
variations. But that comes at a cost on the SWF side (JS side handles
margins in the browser) since it is way more complex to account for those
margins and it might rightly be put into its own layout bead.

And when you make these altered versions, its hard to subclass since you
have the layout algorithm that you've have to tap into from the subclass
and then call out or use a delegate.

‹peter

On 6/6/17, 9:08 PM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
 wrote:

>On Tue, Jun 6, 2017 at 5:29 PM, Justin Mclean 
>wrote:
>
>> Hi,
>>
>> > In FlexJS we have a preference towards utility classes.
>>
>> So say we have existing bead A and we want to add some functionality to
>> to. In order to use utility classes we would need to modify bead A and
>>pull
>> out some of the code into a utility class so bead B can use it.
>>
>> This will increase the size/runtime cost to existing people using bead
>>A.
>> Is this accectable?
>>
>
>Yes, there will be a size cost, which is why the inheritance approach is
>better than Utils approach for Beads.
>
>*Utils approach:*
>
>Bead A supports feature X
>Bead B needs to support feature X and Y
>
>Create a Util class called FeatureXAndY
>
>Bead A calls util:FeatureXAndY (Now Bead A loads code for unnecessary
>feature Y)
>Bead B calls util:FeatureXAndY
>
>*Inheritance approach:*
>
>Bead A supports feature X
>Bead B needs to support feature X and Y
>
>Bead A has code for feature X alone (no extra code)
>Bead B extends Bead A and adds code for feature Y (no extra code)
>Moreover, no extra util class to maintain.

Re: Beads and DRY (was Re: [FlexJS] Removing PasswordInputBead has no effect)

[Peter Ent]

We have never really discussed the use of delegates. Its not something
that ties in that well with FlexJS I think. But using a delegate to
off-load some of the work, just when that work is needed, might be another
solution.

‹peter

On 6/7/17, 2:36 AM, "Harbs"  wrote:

>That¹s not what I¹m suggesting at all.
>
>If utility classes (or utility functions) are bloated with lots of
>functionality then they are not done right.
>
>Utilities should be reserved for well defined functionality. A good
>example of this is AnimationUtil. Imagine you have two animation beads
>which do different things, they would both use AnimationUtil for
>requestFrame and cancelFrame.
>
>The same goes for SolidBorderUtil (which should really be split into
>two). Any bead which needs to apply a border just calls the utility.
>
>So:
>Bead A supports feature X
>Bead B needs to support feature X and Y
>
>feature x used functionality a and b
>feature y uses functionality c and d
>Create a Util classes a, b, c and d which beads a and b use as needed.
>
>This is obviously not a pattern useful everywhere, but where applicable,
>has many advantages.
>
>Harbs
>
>
>> On Jun 7, 2017, at 4:08 AM, OmPrakash Muppirala 
>>wrote:
>> 
>> *Utils approach:*
>> 
>> Bead A supports feature X
>> Bead B needs to support feature X and Y
>> 
>> Create a Util class called FeatureXAndY
>

Re: [FlexJS] Layout Issue/Change

[Peter Ent]

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 propose is to eliminate those event listeners on the children. So
if you resize one of the buttons you will have dispatch "layoutNeeded" on
the Group to get the VerticalLayout to reformat the Group.

If you resize the Group, that will continue to re-run the layout.

Another example is FirstFlexibleChildHorizontalLayout (or whatever that's
called). If you delete that first child, the layout will not run. My
change will not affect this situation - you must still dispatch
"layoutNeeded" to get the layout to recalculate the next child as the
flexible item. On the JS side, this is crucial because this layout sets
flex-grow:1 on the first child and flex-grow:0 on the rest. When you
remove the first child, all children have flex-grow:0, so you must re-run
the layout.

This is the inconsistency: sometimes you need to dispatch "layoutNeeded"
and sometimes you do not. I propose you always dispatch "layoutNeeded"
whenever you add a child, remove a child, resize a child, or do anything
that would require the layout to run.

‹peter

On 5/1/17, 10:27 AM, "piotrz"  wrote:

>Hi Peter,
>
>It look like we have partially implemented "layoutNeeded".
>
>Your suggestion in #1 - is to completely remove current listeners which
>are
>dispatch "layoutNeeded". - Am I understand correctly ? - So if I will add
>children later - those will resize itself, but in order to correct parent
>resizing it will need to dispatch "layoutNeeded" ? Am I understand
>correctly
>?
>
>In case of #2 and #3 - I think both cases are good for express components,
>but Option #3 seems to me to complicated in case of later usage.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layout-Issue-Change-tp61440p6
>1442.html=02%7C01%7C%7C3f4bcd255fbb43120cbc08d4909fcd58%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636292463395237341=stp%2Fct7tHsUCkn8
>X5ZeFclHxbyIal3vC%2F5KUoRYin4Y%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Null Pointer Exception in HorizontalFlexLayout

[Peter Ent]

OK. I will look at the other layouts and probably do the same for them
where it makes sense.

On 5/1/17, 10:06 AM, "piotrz"  wrote:

>Thank you Peter. That helped. I was thinking about such solution, but
>wasn't
>sure whether it won't break anything. If I'm thinking more about that it
>makes sense do not bother non UIBase component here.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-MDL-Null-Pointer-Exception-in
>-HorizontalFlexLayout-tp61437p61441.html=02%7C01%7C%7C61b665f8d3134b4
>d5cf708d4909cf543%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63629245119
>9825874=7%2Bpqd%2FKFt%2FRaA%2Bvml%2BcTIspcY2r9iuxYRUcdKegANRg%3D
>erved=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS, MDL] Null Pointer Exception in HorizontalFlexLayout

[Peter Ent]

Hi Piotr,

I mostly understand. It seems like the child is not UIBase so it is null,
at least in one of the cases. The layout code should be changed to check
for null and skip that child.  Can you see if that helps?

‹peter

On 5/1/17, 8:35 AM, "piotrz"  wrote:

>Hi Peter,
>
>During creation of DropDownList component in MDL I have experienced Null
>Pointer Exception in HorizontalFlexLayout. [1]
>
>Issue:
>My DropDownList contains 3 elements: Div with selected text, Material icon
>(i) and Menu.
>
>Case 1: If I create DropDownList in MXML - MDL library handle properly
>upgrading. 
>
>Menu is a simple ul, but once upgrade is done MDL library surround it by
>additional div [2] "mdl-menu__container".
>
>HorizontalFlexLayout is going through the children of View in function
>"layout". Array contains 3 elements from my DropDownList - the last one is
>menu - in moment of layout perform it contains "ul" not
>"mdl-menu__container".
>
>ex-development.247.n4.nabble.com%2Ffile%2Fn61437%2Fhorizontalflex_layo
>ut.png=02%7C01%7C%7C92f8ef48e030413571a708d490902c50%7Cfa7b1b5a7b3443
>8794aed2c178decee1%7C0%7C0%7C636292396295241298=TTsjYE1G7SohYeujGKKB
>DvIAC7JYha3fPcUbkF4TbaY%3D=0>
>
>This "ul" has been created by FlexJS and has element.flexjs_wrapper. and
>function getElementAt returns child one by one.
>
>Case 2 - ISSUE:
>
>I would like to create DropDownList dynamically:
>
>var dropDown:DropDownList = new DropDownList();
>addElement(dropDown);
>
>In order to do this Menu inside DropDownList need to be "upgraded"
>manually
>- I need to tell MDL library that I've created Menu component - I have
>bead
>for that purpose which doing his job: UpgradeElement.
>
>Upgrade is completed successfully and MDL is surrounding "ul" by
>"mdl-menu__container".
>
>Now HorizontalFlexLayout is doing "layout" and trying to go through the
>children. In array for some reason there is no "ul" MDL Menu, but this
>"mdl-menu__container" which wasn't created by FlexJS. In that case it
>doesn't have element.flexjs_wrapper, so getElementAt returns null. And we
>are getting NPE.
>
>It look like everything what HorizontalFlexLayout is doing in Case 1
>happened before upgrading - in case 2 I'm doing upgrade during whole life
>cycle performance.
>
>I hope this long explanation help you understand issue and provide some
>feedback. I'm attaching simple project where you can reproduce this issue
>[3]
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2F9oRP=02%7C01%7C%7C92f8ef48e030413571a708d490902c50%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636292396295241298=O3iz6XdYaDIO
>6408JrznUhIN%2BU3oiBC2U4eqj4rMTsE%3D=0
>[2] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2FiN4K=02%7C01%7C%7C92f8ef48e030413571a708d490902c50%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636292396295241298=6ur7OO4g%2Fi
>Sj1IFmWpfJDMwNvQk6PfbuEM2yfackVlE%3D=0
>[3] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2F1drv.ms%2
>Fu%2Fs!ApVpLyjpHDC2zTehS-kv_1g0cgSY=02%7C01%7C%7C92f8ef48e030413571a7
>08d490902c50%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6362923962952412
>98=wnCIo8EFiKQLZFZVLRMcj%2Fnqg1G1Kwb%2BMJPhN6x1ltE%3D=0
>
>Piotr
>
> 
>
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-MDL-Null-Pointer-Exception-in
>-HorizontalFlexLayout-tp61437.html=02%7C01%7C%7C92f8ef48e030413571a70
>8d490902c50%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63629239629524129
>8=FMk2TnkFIbtdFUEg0ifVD3X%2FmDZq%2BmMoQe2o4RyIi1Y%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

[FlexJS] Layout Issue/Change

[Peter Ent]

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.

Right now, the LayoutBase class sets up event listeners on the layout host to 
automatically re-run the layout under certain conditions. The more I think 
about this the less PAYG it is and it is also inconsistent how things are 
handled.

The layout code is set up to recognize changes in the layout host's size. When 
that happens the layout is re-run. That, to me, is a good thing.

The layout code also waits for the initial "childrenAdded" event and if it sees 
it, the layout code will set event listeners for size changes on the children. 
If you later add children, those new children may not have listeners attached 
(this is an inconsistency). It is the responsibility of the app developer to 
dispatch a "layoutNeeded" event on the layout host to trigger the layout. 
Again, this is inconsistent as a component could dispatch "childrenAdded" while 
another component may not.

I see three possibilities here:


  1.  Do nothing with children (PAYG). The layout code would listen for size 
changes to the layout host, but it would not set up listeners on the children. 
An application that changes an items size or adds or removes an item will have 
to dispatch "layoutNeeded" on the item's (or items') parent. This way you can 
change a component frequently and only trigger its layout when the changes are 
complete.
  2.  Do everything (Pay Heavily). The layout code would really try to listen 
for all sorts of events on the layout host and respond to them.  The cost would 
be high however, if a large number of items were being changed inside of a 
loop: the layout code would be run for each pass of the loop.
  3.  Do everything, but wait (Partial Payment). The layout code would do the 
same as #2, but allow for updating loops. A number of systems have this: 
host.beginUpdate(); /* do a bunch of things */ host.endUpdate(). While the loop 
is running the layout would ask the host if it is OK to update and if not, the 
layout would not run. Once the endUpdate() was executed, the host would 
dispatch a final "layoutNeeded" and the layout would run once.

I am in favor of #1. It is in the spirit of PAYG and if you decided you needed 
either #2 or #3, you could extend a layout and build that yourself. Or we could 
add it to the Express package or something like that.

In choice 1, changing an item's size trigger's its own layout. If you have a 
Group with 100 elements, all of which are Groups themselves, and you were to 
resize each sub-Group in a loop, the resize of a sub-Group would trigger its 
layout. This is desired behavior. Once that loop has completed, the outer Group 
would also need its layout run to account of the newly resized children and 
that's where you do: outer.dispatchEvent(new Event("layoutNeeded")); In choice 
2 or choice 3, each time a sub-Group was resized, the outer Group's layout 
would run for a total of 100 times, which may even cause some of the 
sub-Group's layouts to run again, depending on the layout algorithm.

If I were to remove the child event listeners in the layout code, any place 
your app or example that counted on the layout running, you would need to add a 
dispatch event for "layoutNeeded" if you did not resize the component.

I hope that made sense.
Peter

Re: [FlexJS] Layout Issue/Change

[Peter Ent]

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 width, the
browser automatically pushes the children apart to make room. Since the
Flash Player does not have that capability, the HorizontalLayout, SWF
version, must watch for changes in the size of the children and re-run the
layout. This is the mimicking part.

I put the children size watching into the LayoutBase, thinking it was a
common enough, frequent enough process that it could be done in the base
class. But that really is not the case. Each layout is different.

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
HorizontalLayoutWatchForAddAndRemoveChild

Here's the catch: going back to the HorizontalLayout, if you remove a
child, the browser will automatically reposition the children to close the
space left by the child removed. You do not need to write a specialty
layout to do. So for HorizontalLayout, do we including watching for
children added and removed because it mimics the browser or is it really a
specialty? 

Right now, the event listeners watching for changes in the children are
multi-platform. A better, more PAYG approach (I think), is to make those
event listeners SWF-side only and they should be part of the layouts that
actually need them to mimic what the browser can do.

So perhaps that best thing to do now is wait for FlexJS 0.9 and try this
out an another branch to determine what the procedure should be.

‹peter


On 5/2/17, 2:52 AM, "piotrz"  wrote:

>Understand. It is not bad changes in terms of complex layout.
>I think this changes need to be done on feature branch. I would like to
>test
>it and see how it affects current examples.
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layout-Issue-Change-tp61440p6
>1459.html=02%7C01%7C%7Ce012b30ad5354126a6a908d491297b5e%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636293054727198273=2NhFc2LDt8sTFE17K
>Ylnjms1oE6YvbWo6lFVcolThHk%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layouts

[Peter Ent]

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 pattern things should work
out.

‹peter



On 5/5/17, 10:58 AM, "piotrz"  wrote:

>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 all layouts will be working.
>
>Any thoughts from others ?
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layouts-tp61120p61501.html
>ta=02%7C01%7C%7Cb742d8c1f6d44087f65f08d493c8dce3%7Cfa7b1b5a7b34438794aed2c
>178decee1%7C0%7C0%7C636295938289099392=Kt0Qd5IA1PEdNjvRF0SQN87vjYl0D
>hWjLOBlPGHaeIo%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Layouts

[Peter Ent]

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
>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 View.
>
>[1] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2FoQRi=02%7C01%7C%7C247c58abd1ef48ae7de608d4937fbd81%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636295624251898329=s6R8lLuDcUjf
>x%2FSoGYvLeaBLd2a7iFtYFZMzSw2DF48%3D=0
>[2] 
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apa
>che.org%2FHn3G=02%7C01%7C%7C247c58abd1ef48ae7de608d4937fbd81%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636295624251898329=dUrANaUf5Kd6
>yAmaf7NAssyRHj2clQFjfhecHxYrXJo%3D=0
>
>Thanks,
>Piotr
>
>
>
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layouts-tp61120p61494.html
>ta=02%7C01%7C%7C247c58abd1ef48ae7de608d4937fbd81%7Cfa7b1b5a7b34438794aed2c
>178decee1%7C0%7C0%7C636295624251898329=Ezju83uKcTRx4n748WEIz9zKf8C4Z
>Qq5M1rbNuVnObY%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FlexJS] Accordion broken

[Peter Ent]

I'm still working on this and ran into a couple of issues.

The flexible child layouts no longer provide a way to explicitly set a
child; instead they rely in the child's id being used to retrieve the
child from the document. Unfortunately, a layout that is not referenced in
MXML will not get its document set.

Perhaps a better solution is to write "AccordionLayout" that will expand
the child selected by the model, but I'm still looking at making use of
what is already there.

—peter



On 5/30/17, 11:35 AM, "Harbs" <harbs.li...@gmail.com> wrote:

>The reasons it’s broken is (at least) thee-fold:
>
>1. Panels contain content and need to be collapsed despite the fact that
>content exists.
>2. The Collapse bead can only infer that it’s collapsed by the fact that
>the size is the collapsed size — which only makes sense if the size is
>set.
>3. The title must be measured to set the collapsed height correctly.
>
>> On May 30, 2017, at 6:21 PM, Harbs <harbs.li...@gmail.com> wrote:
>> 
>> Something like this:
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>> 
>> This is the markup of an Accordion which used to work, which doesn’t
>>anymore.
>> 
>>  
>>
>>
>>  
>>  
>>          
>>  
>>
>>
>>
>> 
>> 
>>> On May 30, 2017, at 4:54 PM, Peter Ent <p...@adobe.com.INVALID> wrote:
>>> 
>>> Hi,
>>> 
>>> Do you have a quick example of how to use the FlexJS Accordion? The
>>>ASDoc
>>> on it is thin. The children of the Flex SDK Accordion were navigation
>>> components that supported things like title so each section could be
>>> labeled. I don't see an AccordionChild or something similar that can be
>>> used with Accordion. I took a guess and made Container a child of it,
>>>but
>>> it just blew up.
>>> 
>>> Thanks,
>>> ‹peter
>>> 
>>> On 5/30/17, 6:39 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>>> 
>>>> It seems like the new layouts totally broke Accordion.
>>>> 
>>>> Accordion relied on absolute sizing to handle expanding and
>>>>collapsing of
>>>> content. I tried to add a new layout which is basically a copy of the
>>>>old
>>>> OneFlexibleVerticalLayout and use that for accordion, but that does
>>>>not
>>>> seem to work either due to changes in containers (I think).
>>>> 
>>>> Peter, do you thin you could look into this?
>>>> 
>>>> Thanks,
>>>> Harbs
>>> 
>> 
>

Re: [FlexJS] Layout of NumericStepper is broken

[Peter Ent]

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=02%7C01%7C%7Cafd0984b2a2d4a2643
>d308d4acae46fd%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63632331191193
>2511=6aA%2FoP%2BRTmEXaHh0aU2pRgufprYkfmGw7tmkipKsFMM%3D=0
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>--
>View this message in context:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.247.n4.nabble.com%2FFlexJS-Layout-of-NumericStepper-is-b
>roken-tp62108p62149.html=02%7C01%7C%7Cafd0984b2a2d4a2643d308d4acae46f
>d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636323311911932511=io
>xNCT03PcPjwOIytCr2%2FUjst9mGuqx2b%2BCTLqBJ7Kw%3D=0
>Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: home.apache.org

[Peter Ent]

I get permission denied (public key). I remember having to set up
something for the old people site (I think) and have been trying to hunt
down the instructions.

‹peter

On 9/13/17, 12:49 PM, "Alex Harui" <aha...@adobe.com.INVALID> wrote:

>Should just be:
>  sftp home.apache.org
>
>Hope you remember your passphrase.
>
>-Alex
>
>On 9/13/17, 9:16 AM, "Peter Ent" <p...@adobe.com.INVALID> wrote:
>
>>Hi,
>>
>>Does anyone have the instructions on how to set up access to your
>>home.apache.org space? I've looked on the apache.org site and all I can
>>find are instructions about the old people.apache.org. I guess I haven't
>>accessed my home.apache.org since I set up my newer computer.
>>
>>I'm going to update my ASDocs info to point to our FlexJS ASDocs app page
>>since Google is pointing to my old ASDoc and it needs to be more current.
>>
>>Thanks.
>>Peter
>

Re: home.apache.org

[Peter Ent]

Thanks, Mark.

I think I've done all the right stuff. As I started to do it, I began to
remember doing it once before for SSH. I've been waiting awhile and still
get permission denied, so I'll just keep waiting. I'm pretty sure I sent
my key to a public key server. I'll go out for coffee and I hope it works
when I get back.

—peter

On 9/13/17, 1:22 PM, "Mark Thomas" <ma...@apache.org> wrote:

>On 13/09/2017 18:05, Peter Ent wrote:
>> I get permission denied (public key). I remember having to set up
>> something for the old people site (I think) and have been trying to hunt
>> down the instructions.
>
>You should be able to set up your key through id.apache.org
>
>You then need to allow enough time (I think it is about an hour) for the
>public key to sync to the servers you have access to. Then you should be
>able to sftp to home.a.o.
>
>Mark
>
>
>> 
>> ‹peter
>> 
>> On 9/13/17, 12:49 PM, "Alex Harui" <aha...@adobe.com.INVALID> wrote:
>> 
>>> Should just be:
>>>  sftp home.apache.org
>>>
>>> Hope you remember your passphrase.
>>>
>>> -Alex
>>>
>>> On 9/13/17, 9:16 AM, "Peter Ent" <p...@adobe.com.INVALID> wrote:
>>>
>>>> Hi,
>>>>
>>>> Does anyone have the instructions on how to set up access to your
>>>> home.apache.org space? I've looked on the apache.org site and all I
>>>>can
>>>> find are instructions about the old people.apache.org. I guess I
>>>>haven't
>>>> accessed my home.apache.org since I set up my newer computer.
>>>>
>>>> I'm going to update my ASDocs info to point to our FlexJS ASDocs app
>>>>page
>>>> since Google is pointing to my old ASDoc and it needs to be more
>>>>current.
>>>>
>>>> Thanks.
>>>> Peter
>>>
>> 
>

Re: [VOTE] What should be the new Project Name for Proposed fork of FlexJS?

[Peter Ent]

1) Royale (binding)
2) Braid

‹peter ent

On 9/17/17, 3:19 PM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote:

>Hi,
>
>In this thread I've gathered list of names proposition for fork of FlexJS
>project.
>
>LIST:
>
>Royale
>Boja
>Strand
>Bead
>Limber
>Boinga
>Braid
>Arise
>
>HOW DO WE VOTE:
>1) Pick up 3 names from the list and order them from the most favorite
>2) We will give points for each items in the list which you have choose
>3) In your list you can propose your own name - others can follow it in
>their lists
>
>EXAMPLE:
>1) Name1 - 3 points
>2) Name2 - 2 points
>3) Name3 - 1 point
>
>WINNER:
>We will pickup winner based on gathered points by one of the name.
>
>The vote will be open until Tuesday September 19, 23:00 UTC
>
>Thanks,
>
>Piotr

Re: [DISCUSS] Name of the FlexJS Fork

[Peter Ent]

I'm inclined to favor "Braid" over Limber (however you want to spell it)
because I can think of too many puns associated with Limber and the first
thing that comes to mind, for me, is cheese that smells.

I don't remember how to pronounce "Borja" and while English always seems
to dominate, English-speaks will most likely pronounce it Boar-JA and a
few will go with Boar-YA or Boar-HA. So there will probably always be a
need for correction.

While "Apache Royale" has a nice ring to it for me, I think "Braid" has
the right feel. You get things intertwined for a purpose, things in a
pattern, strands woven together, that sort of thing.

"Braid" also brings to mind "Helix". I haven't looked to see if there are
any projects that use "Helix" which I'm sure there are. And if so, maybe
"Felix" to give a nod back to Flex along with the helix.

—peter



On 9/19/17, 2:59 PM, "Alex Harui"  wrote:

>I am not an expert, but AIUI, trademarks are intended to avoid confusion
>in a marketplace.  There are lots of products named Flex, such as cars,
>diabetes testing kits, and more.  There are even other software products
>called Flex and we need to consider whether it confuses potential
>customers about what Flex is being talked about.
>
>Mostly, we will use the term "Apache " instead of just
> when publishing things, but later in those documents we'll
>probably just refer to it as .
>
>So, IMO, having other projects on GitHub called Braids isn't a deal killer
>and your link [1] probably won't cause confusion.  I was more concerned
>about the Braids project related to Tensor-flow as Tensor-flow might
>become the new hot thing in software in general and if that Braids took
>off lots of mentions of Braids would be about that.  There is also a
>Braids "static staging compiler" for TypeScript.
>
>That's why I'm concerned about Royale when there is a GitHub project
>called Royale that is a "A React-esque framework for Javascript".  Think
>of it this way.  If you did a search on GitHub for our project name and
>didn't realize we were associated with Apache, would you click on one of
>these other project instead, and how long would it take you to realize it
>wasn't the right one?  If you go try to sell writing an app in Royale and
>a competitor has proposed writing it in React with the other GitHub
>Royale, will that be confusing to your client?
>
>I wrote to trademarks@ to see if they are similarly concerned.  They don't
>always respond right away.  If they are not concerned, I will probably
>vote for Royale just so we have a name for tomorrow.
>
>HTH,
>-Alex
>
>On 9/19/17, 11:43 AM, "Piotr Zarzycki"  wrote:
>
>>I checked Braid on github and found [1]. It was quite popular - can we
>>just
>>grab that name - I still do not understand fully those trademarks
>>implications.
>>
>>[1] 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>o
>>m%2Fcristibalan%2Fbraid=02%7C01%7C%7C5ebf232812004352ad0108d4ff8e4f1
>>7
>>%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636414434060882785=A6
>>I
>>IL4SNYWP2XFTvOife92gA1t8Km4E%2Fr7QpvQ3B3mI%3D=0
>>
>>2017-09-19 20:38 GMT+02:00 Kessler CTR Mark J
>>:
>>
>>> Apache Bob...
>>>
>>>
>>> -Original Message-
>>> From: Harbs [mailto:harbs.li...@gmail.com]
>>> Sent: Tuesday, September 19, 2017 2:20 PM
>>> To: dev@flex.apache.org
>>> Subject: [Non-DoD Source] Re: [DISCUSS] Name of the FlexJS Fork
>>>
>>> Ick…
>>>
>>> Why do these things have to be so complicated? ;-)
>>>
>>> Harbs
>>>
>>> > On Sep 19, 2017, at 8:58 PM, Dave Fisher 
>>>wrote:
>>> >
>>> > There are any number of meanings for boja in many languages with and
>>> without diacritics.
>>> >
>>> > 
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.m.wi
>>>k
>>>tionary.org%2Fwiki%2Fboja=02%7C01%7C%7C5ebf232812004352ad0108d4ff8e
>>>4
>>>f17%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636414434060882785
>>>a
>>>=IObJoB2mvH3y8iHRBlUvDSDBXiTXitc2FPR1tPHKQ1o%3D=0
>>> >
>>> > Sent from my iPhone
>>> >
>>> >> On Sep 19, 2017, at 1:45 PM, Andrew Wetmore 
>>> wrote:
>>> >>
>>> >> I can think of three ways* to pronounce "bo-ja" without even
>>>resorting
>>> to a
>>> >> South African "click" language. This makes it a challenge to refer
>>>to
>>> the
>>> >> product to anyone who does not already use it.
>>> >>
>>> >> *bodja, booya, boha.
>>> >>
>>> >> On Tue, Sep 19, 2017 at 2:42 PM, Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
>>> >> wrote:
>>> >>
>>> >>> Om,
>>> >>>
>>> >>> No offend :) That is why it is so hard to choose ;) I think "bo-ja"
>>>is
>>> the
>>> >>> closes to how I pronounce it. :)
>>> >>>
>>> >>> Piotr
>>> >>>
>>> >>> 2017-09-19 19:31 GMT+02:00 OmPrakash Muppirala
>>>:
>>> >>>
>>>  Boja is one name I really dislike.  Sorry Piotr
>>> 
>>>  Also I dont know how to pronounce it. Is it Bo-ha, or boo-ha or
>>>bo-ja,
>>> >>> etc?
>>> 

Re: [DISCUSS] Name of the FlexJS Fork

[Peter Ent]

I swear all the good names are already taken. I think we just need to
throw letters into a box and shake them at this point.
‹peter

On 9/19/17, 3:48 PM, "Harbs"  wrote:

>Helix is nice.
>
>Possible conflict:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.helixs
>dk.org%2F=02%7C01%7C%7C035543dca81c4819f48408d4ff976d6e%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636414473216014007=50CnTkqOULTC01jAt
>uA2i2vcB6aW0jlKyPZsS%2BfJnaQ%3D=0
>sdk.org%2F=02%7C01%7C%7C035543dca81c4819f48408d4ff976d6e%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636414473216014007=50CnTkqOULTC01jA
>tuA2i2vcB6aW0jlKyPZsS%2BfJnaQ%3D=0>
>
>> On Sep 19, 2017, at 10:40 PM, OmPrakash Muppirala
>> wrote:
>> 
>>> 
>>> 
>> 
>> "Braid" also brings to mind "Helix". I haven't looked to see if
>>there
 are
>> any projects that use "Helix" which I'm sure there are. And if so,
 maybe
>> "Felix" to give a nod back to Flex along with the helix.
>> 
>> ‹peter
 
>>> 
>> I love Helix.  It actually describes the shape:
>> 
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wikip
>>edia.org%2Fwiki%2FHelix=02%7C01%7C%7C035543dca81c4819f48408d4ff976d6
>>e%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636414473216014007=9
>>RKN1g881XvPn6H6ffBvMGPSwagSyfePAhzrQ3nqBxc%3D=0
>> 
>> DNA is in the shape of a double Helix, guess what DNA is made of?
>>Strands!
>> 
>> The name has a good ring to it as well.
>

Re: Royale is now an Apache Project

[Peter Ent]

1) royale-asjs just so we can expand later if needed. I like
royale-compiler.
2) Let's get off of SVN!
‹peter

On 9/21/17, 11:42 AM, "Alex Harui"  wrote:

>We have to decide a few more things for setup:
>
>1) our current repos are named flex-asjs, flex-typedefs, etc.  I assume we
>want them renamed to royale-asjs, royale-typedefs, royale-tourjs,
>royale-falcon?
>
>Or do we want to change the "last names" as well?
>
>royale-framework, royale-typedefs, royale-tourjs, royale-compiler
>
>2) The flex.apache.org website is still on SVN.  Do we want to use Git for
>Royale?  I think yes.
>
>3) Do we want a Confluence Wiki or are there wiki-equivalents in GitHub?
>
>-Alex
>
>On 9/21/17, 2:27 AM, "Piotr Zarzycki"  wrote:
>
>>Let's wait for their response.
>>
>>Thank you!
>>
>>On Thu, Sep 21, 2017, 11:17 Alex Harui  wrote:
>>
>>> In the sub task I asked if we "must" use JIRA or can use GH Issues.
>>>
>>> Thanks,
>>> -Alex
>>>
>>> On 9/21/17, 2:14 AM, "Erik de Bruin"  wrote:
>>>
>>> >>
>>> >> Maybe we should have discussion whether we need Jira for new
>>>project?
>>> >> Maybe we should use Github only?
>>> >>
>>> >
>>> >That sound like a plan. KISS [1] all the way ;-)
>>> >
>>> >EdB
>>> >
>>> >1:
>>> >
>>> 
>>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fen.wiki
>>>p
>>>e
>>> >dia.org
>>> %2Fwiki%2FKISS_principle=02%7C01%7C%7C9bf9ee2d27d84511b11508d5
>>> 
00d155c2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63641582144717182
2

>>> >data=J3se5Id4dPrOLITxNfk0hKOCKeTwtl3KIhhablawMwU%3D=0
>>> >
>>> >
>>> >
>>> >--
>>> >Ix Multimedia Software
>>> >
>>> >Jan Luykenstraat 27
>>> >3521 VB Utrecht
>>> >
>>> >T. 06-51952295 <06%2051952295>
>>> >I.
>>> >
>>> 
>>>https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl
>>>a
>>>=
>>> 
02%7C01%7C%7C9bf9ee2d27d84511b11508d500d155c2%7Cfa7b1b5a7b34438794aed2c
1
78
>>> 
decee1%7C0%7C0%7C636415821447171822=0RA5xX24wJ%2Bf1HdGZE6vOjoRHNC
i
SA
>>> >zNtyrgiSrTOOY%3D=0
>>>
>>>
>

Re: home.apache.org

[Peter Ent]

My LDAP entry at id.apache.org has a OpenPGP Public Key Primary
Fingerprint set. I assume when I do sftp p...@home.apache.org it looks up
'pent' and sees the OpenPGP fingerprint, goes out to some key server and
fetches whatever it needs.

And after all this time I still get Permission denied. Maybe that's not a
real PGP key. I looked up PGP for the Mac and found GPG Keychain which it
says makes OpenPGP keys. Just very confused.

—peter

On 9/13/17, 3:15 PM, "Mark Thomas" <ma...@apache.org> wrote:

>On 13/09/17 19:27, Peter Ent wrote:
>> Thanks, Mark.
>> 
>> I think I've done all the right stuff. As I started to do it, I began to
>> remember doing it once before for SSH. I've been waiting awhile and
>>still
>> get permission denied, so I'll just keep waiting. I'm pretty sure I sent
>> my key to a public key server. I'll go out for coffee and I hope it
>>works
>> when I get back.
>
>That sounds like you might be mixing up OpenPGP release keys and SSH
>keys. Anyway...
>
>I've checked your LDAP record and you do have a public SSH key
>configured. If it doesn't work when you try again let me know the time
>(UTC) and IP address (send it privately if you have privacy concerns)
>and I'll check the logs.
>
>Mark
>
>
>> 
>> —peter
>> 
>> On 9/13/17, 1:22 PM, "Mark Thomas" <ma...@apache.org> wrote:
>> 
>>> On 13/09/2017 18:05, Peter Ent wrote:
>>>> I get permission denied (public key). I remember having to set up
>>>> something for the old people site (I think) and have been trying to
>>>>hunt
>>>> down the instructions.
>>>
>>> You should be able to set up your key through id.apache.org
>>>
>>> You then need to allow enough time (I think it is about an hour) for
>>>the
>>> public key to sync to the servers you have access to. Then you should
>>>be
>>> able to sftp to home.a.o.
>>>
>>> Mark
>>>
>>>
>>>>
>>>> ‹peter
>>>>
>>>> On 9/13/17, 12:49 PM, "Alex Harui" <aha...@adobe.com.INVALID> wrote:
>>>>
>>>>> Should just be:
>>>>>  sftp home.apache.org
>>>>>
>>>>> Hope you remember your passphrase.
>>>>>
>>>>> -Alex
>>>>>
>>>>> On 9/13/17, 9:16 AM, "Peter Ent" <p...@adobe.com.INVALID> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Does anyone have the instructions on how to set up access to your
>>>>>> home.apache.org space? I've looked on the apache.org site and all I
>>>>>> can
>>>>>> find are instructions about the old people.apache.org. I guess I
>>>>>> haven't
>>>>>> accessed my home.apache.org since I set up my newer computer.
>>>>>>
>>>>>> I'm going to update my ASDocs info to point to our FlexJS ASDocs app
>>>>>> page
>>>>>> since Google is pointing to my old ASDoc and it needs to be more
>>>>>> current.
>>>>>>
>>>>>> Thanks.
>>>>>> Peter
>>>>>
>>>>
>>>
>> 
>