flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlos.rov...@codeoscopic.com>
Subject Re: [FLEXJS] New Default Component Set (was Re: [FlexJS, MDL] Why binding is not working in MDL example)
Date Tue, 03 Jan 2017 17:12:19 GMT

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
involved in this project.

Not taking this into account means people not using FlexJS, or using a set
like MDL...

What do you think?

2017-01-03 17:53 GMT+01:00 Alex Harui <aharui@adobe.com>:

> 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 FlexJS.  No more forgetting to add DataBinding beads, or
> SimpleCSSValuesImpl, etc.  Fewer tags to write.
> I've asked Peter to start on it so you can see how to bake stuff in and
> how much simpler it will make our examples.  I think it will help in
> getting folks started with fewer problems.  I think we've proven that we
> can composite basic things into more complex things.
> But, we need a good name for this set.  I don't like "Heavy".  Makes me
> think it would be too fat and slow.  I've ruled out for now "Kitchen
> Sink", and "Full" (because it won't contain every bead).  I've thought
> about "Medium", "Typical", "Common", "Popular", "POC" (Proof of Concept)",
> "RP" (Rapid Prototyping).  Don't like any of them.  What name would
> suggest that it is not on the place to start but that you could use it in
> production if you don't run into size/performance issues?
> Thoughts?
> -Alex
> On 1/2/17, 11:20 PM, "piotrz" <piotrzarzycki21@gmail.com> wrote:
> >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
> >
> >
> >
> >-----
> >Apache Flex PMC
> >piotrzarzycki21@gmail.com
> >--
> >View this message in context:
> >http://apache-flex-development.2333347.n4.nabble.
> com/FlexJS-MDL-Why-bindin
> >g-is-not-working-in-MDL-example-tp57738p57795.html
> >Sent from the Apache Flex Development mailing list archive at Nabble.com.


Carlos Rovira
Director General
M: +34 607 22 60 05

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

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message