Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Alex Harui
OK, good start. It should have a noticeable reduction in the number of lines in our examples. -Alex On 1/3/17, 12:24 PM, "Peter Ent" wrote: >I've pushed an initial set of classes for this Express project. I did not >hook it up to the main build of flex-asjs yet but you should be able to >build

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Peter Ent
I've pushed an initial set of classes for this Express project. I did not hook it up to the main build of flex-asjs yet but you should be able to build it from the project itself. I basically extended the standard HTML classes and added some default beads. —peter On 1/3/17, 3:11 PM, "carlos.rov.

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Carlos Rovira
I think name should came after we have something with a bit of face that could inspire us, for the meantime I'll go a codename route with whatever name. 2017-01-03 21:07 GMT+01:00 Josh Tynjala : > I like Express too! > > - Josh > > On Jan 3, 2017 10:31 AM, "Peter Ent" wrote: > > > I think "Expre

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Josh Tynjala
I like Express too! - Josh On Jan 3, 2017 10:31 AM, "Peter Ent" wrote: > I think "Express" isn't a bad name for this. It implies that you can get > something running quickly. > > Another name I thought of was "Star" (FlexJS Star). > > A third choice might be "Prime", meaning the main one to use

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Dev LFM
Maybe this indecision is related to how each one of us translate to our native language "default/standard/basic".. I really feel like the basic should indeed be called basic, like on Flex a ButtonBase. Hardly is used directly... and the Button is a component. If I will use flexjs, I'll use for su

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Greg Dove
I'll chime in with a sugestion: "Origin" As in FlexJS Origin Components. Origin has both the general meaning of 'starting point' and also has the coordinate system meaning that is a loose metaphor for the possibility of increasing or decreasing something (e.g. features/weight) along an axis/conti

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread piotrz
View this message in context: http://apache-flex-development.247.n4.nabble.com/FLEXJS-New-Default-Component-Set-was-Re-FlexJS-MDL-Why-binding-is-not-working-in-MDL-example-tp57831p57846.html Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread OmPrakash Muppirala
Sorry, I am a bit late into this thread, but I like 'default' for heavy and 'lightweight' for the basic ones. Thanks, Om On Tue, Jan 3, 2017 at 10:39 AM, Alex Harui wrote: > IMO, "Express" is the best idea so far. I also thought of "Loaded" (with > beads), "Beaded", "Quickstart". > > Peter,

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Alex Harui
IMO, "Express" is the best idea so far. I also thought of "Loaded" (with beads), "Beaded", "Quickstart". Peter, if you want to get started, make a folder called Express. We can always change it later. -Alex On 1/3/17, 10:31 AM, "Peter Ent" wrote: >I think "Express" isn't a bad name for this.

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Peter Ent
I think "Express" isn't a bad name for this. It implies that you can get something running quickly. Another name I thought of was "Star" (FlexJS Star). A third choice might be "Prime", meaning the main one to use. ‹peter On 1/3/17, 12:14 PM, "Dev LFM" wrote: >I've been listening this thread,

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Carlos Rovira
Hi Alex, I think MDL is needed right now to get some flexjs kind of "traction" out there, and I think it could be used to people out there, but I think it should not be what define us. FlexJS should have their own look and feel that would be quickly recognized and compite with the main ones out th

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Alex Harui
On 1/3/17, 9:12 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" wrote: >Hi, > >I think that one important thing that should be introduced in the >standard, >default, heavier component set should be a FlexJS original component set >design. That should not be MDL, nor bootstrap or whatev

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-03 Thread piotrz
Jira created: https://issues.apache.org/jira/browse/FLEX-35236 - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Why-binding-is-not-working-in-MDL-example-tp57738p57834.html Sent from the Apache Flex

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Dev LFM
I've been listening this thread, sorry my intrusion.. Why not simply: - ComponentBase for the current set without beads, and "Component" for the ones with default beads included? I like "Express" too but not making much sense to me. My 2 cents ^^ 2017-01-03 16:53 GMT+00:00 Alex Harui : > Hi,

Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Carlos Rovira
Hi, I think that one important thing that should be introduced in the standard, default, heavier component set should be a FlexJS original component set design. That should not be MDL, nor bootstrap or whatever other common out there. That should be created by a top designer that would want to be

[FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)

2017-01-03 Thread Alex Harui
Hi, The original thread is another example of where PAYG becomes PITA. On another thread, Om wants to bake in HTML sanitization by default. IMO, these are things that should go in a heavier component set with more things baked in. IMO, this new, heavier component set would be the default for Fl

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-03 Thread Alex Harui
That would be a bug, IMO. -Alex On 1/3/17, 4:13 AM, "piotrz" wrote: >I see what was the problem: > >If my VO has [Bindable] on the top of the class it is not working. > >[Bindable] >public class MenuItemVO {} > >If I have [Bindable] on each properties it's working. > >public class MenuItemVO >

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-03 Thread piotrz
I see what was the problem: If my VO has [Bindable] on the top of the class it is not working. [Bindable] public class MenuItemVO {} If I have [Bindable] on each properties it's working. public class MenuItemVO { [Bindable] public var label:String; } Piotr - Apache F

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread piotrz
Alex, That's what I'm missing. It's a bit better cause when I add bead "ItemRendererDataBinding" my getter has been fired, although binding is still not working. I've just pushed my code. - Not sure what can be wrong. I have to admit I'm still thinking to much Flex instead of FlexJS :) Piotr

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread Alex Harui
DataBinding expressions turn into data structures. A bead like ContainerDataBinding has to be on the strand for the MXML file in order to interpret the data structure and set up and execute the actual binding. Maybe all you are missing is that. See ProductListItem.mxml in the FlexJSStore example

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread piotrz
Alex, That's how it looks like: public class MenuItemRenderer extends MXMLItemRenderer public class MXMLItemRenderer extends DataItemRenderer implements ILayoutParent, ILayoutHost, IStrand public class DataItemRenderer extends UIItemRendererBase public class UIItemRendere

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread Alex Harui
What does MenuItemRenderer extend? I don't see the ContainerDataBinding or ItemRendererDataBinding beads. Are they in a base class? -Alex On 1/2/17, 2:24 PM, "piotrz" wrote: >I have following code [1]. MenuItemRenderer is extending >org.apache.flex.html.supportClasses.MXMLItemRenderer > >[1]

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread piotrz
I have following code [1]. MenuItemRenderer is extending org.apache.flex.html.supportClasses.MXMLItemRenderer [1] https://paste.apache.org/y0DG Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MD

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread Alex Harui
How are you using it? Are you getting compiler errors? Did you put a ContainerDataBinding or ItemRendererDataBinding in the MXML? -Alex On 1/2/17, 2:17 PM, "piotrz" wrote: >Alex, > >I did simple test: > >[Bindable("dataChange")] >public function get menuItem():MenuItemVO >{ > return data

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread piotrz
Alex, I did simple test: [Bindable("dataChange")] public function get menuItem():MenuItemVO { return data as MenuItemVO; } override public function set data(value:Object):void { super.data = value; dispatchEvent(new org.apache.flex.events.Event("dataChange")); } Above code do

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread piotrz
You cane check fresh results - Menu tab [1]. Item renderer with my code is under: itemRenderers/CustomMenuItemRenderer.mxml http://apacheflexbuild.cloudapp.net:8080/job/MDLExample/lastSuccessfulBuild/artifact/examples/flexjs/MDLExample/bin/js-debug/index.html - Apache Flex PMC piotrzarzyck

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread piotrz
Nope warning are gone. Previously I've missed Bindable property in VO object. - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Why-binding-is-not-working-in-MDL-example-tp57738p57756.html Sent from

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread Alex Harui
Are you still getting the warning at compile time? On 1/2/17, 7:39 AM, "piotrz" wrote: >I just tried "__NoChangeEvent__" and results is same. If it is like you >said >my renderer should pickup from each object property at creation required >value. - It still not working for me. > >I will try to

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread piotrz
I just tried "__NoChangeEvent__" and results is same. If it is like you said my renderer should pickup from each object property at creation required value. - It still not working for me. I will try to check whether it's working in FlexJSStore. Piotr - Apache Flex PMC piotrzarzyck...@gmail

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread Alex Harui
On 1/2/17, 12:54 AM, "piotrz" wrote: >Alex, > >I have such property: > >[Bindable("dataChange")] >public function get menuItem():MenuItemVO >{ > return data as MenuItemVO; >} > >My item renderer inherits from MXMLItemRenderer. I see that property >"data" >in my item renderer is being assigned

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread piotrz
Alex, I have such property: [Bindable("dataChange")] public function get menuItem():MenuItemVO { return data as MenuItemVO; } My item renderer inherits from MXMLItemRenderer. I see that property "data" in my item renderer is being assigned and "data" from MXMLItemRenderer dispatch event "data

Re: [FlexJS, MDL] Why binding is not working in MDL example

2017-01-02 Thread Alex Harui
If data and menuitem are Object then these are legitimate warnings. There is no way to tell without introspection what the change events are. See FlexJSStore's ProductListItem for one way to deal with it. It declares a custom property of the type of the ValueObject. You can also cast the data p