Hi, IMHO, MDL is a good exercise that test FlexJS and what is capable, and put another facility to people coming to the technology. We could start doing Apps with FlexJS in MDL that looks pretty. That's a great goal.
But in the other hand, for me is a step in the road, and we should pursue to create our own style, look and feel and set and get themes working with js namespace. But as that seems more work, I think MDL was better to come first... in the other hand we could make some buzz and hopefully make people come to us and start playing with FlexJS and joining. 2017-01-19 17:28 GMT+01:00 Alex Harui <aha...@adobe.com>: > > > On 1/19/17, 7:17 AM, "sankar" <santanu4...@gmail.com> wrote: > > >Carlos Rovira-3 wrote > >> Right, many of the MDL controls are extensions from the HTML ones. > >>Others > >> don't have counterpart. > > > >So as I see in MDL the UI components were complete re-work than what we > >have > >in HTML package of FlexJS. MDL has different codes and approach to the > >problems. So I wonder a few things: > > > >1. If someone worked in HTML package components to fix something, if we > >want > >to carry those fixes in MDL - then it has to be different codes/approach; > >in > >that regard the fixes to HTML package will no use in MDL > > The goal of each component set is to thinly wrap an existing set of > components. HTML thinly wraps bare HTMLElements. MDL thinly wraps MDL > aggregations of HTMLElements. In theory, if the MDL version was mostly > the same as the HTML version, then the MDL version subclassed the HTML > version. In other cases, the MDL version might re-composite beads from > HTML. So sure, it is possible that there will be code changes that need > to be applied in more than one place, but it is more likely that if the > same code affects more than one component set, that the code is already > shared by subclassing or composition, and if it isn't, it is a hint that > something should be shared. > > >2. In HTML package we have many different utility beads, i.e. > >DataProviderChangeNotifier to DataGrid component. Since in MDL it's Table, > >so we'll need to create custom bead that works like > >DataProviderChangeNotifier but works to Table(?) > > IMO, the goal for MDL Table is just to replicate what MDL Table does, > which may or may not be the same as what we think of as a Flex DataGrid. > > >3. We can't mixed-match API from HTML package with MDL component > > There is no guarantee that you can mix components from two different > component sets any more than you can expect to mix two different JS > frameworks when writing code in plain JS. IMO, it isn't a goal to unify > all JS framework components, it is just to show that we are agnostic about > which JS framework you want to use and that MXML and AS is a more > efficient way to use your favorite JS framework. > > My 2 cents, > -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.
