flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Tynjala <joshtynj...@gmail.com>
Subject Re: [FlexJS] MDL - Dynamic Child Problem
Date Tue, 21 Feb 2017 15:53:28 GMT
I think, since the core MDL library doesn't upgrade components by default,
it's okay if the FlexJS wrapper doesn't either. I think we should make sure
it's well documented, though. Maybe with a special section in the MDL
example app.

- Josh

On Feb 21, 2017 7:18 AM, "Carlos Rovira" <carlos.rovira@codeoscopic.com>
wrote:

What about to have a MDLUtils or UpgradeMDLUtils class with static methods?
So people that would create a component will do
"UpgradeUtils.upgradeElement(buttonToUpgrade);"
In this way people using a button 90% of times will not be affected by that
overhead.
(I'm thinking on a general scenario where 80-90% of uses are mxml
declaration vs 10-20 or less of dynamic creation)



2017-02-21 15:59 GMT+01:00 yishayw <yishayjobs@hotmail.com>:

> I agree. If you think this bead will be used very often you can create a
> subclass that bakes it in. ImageButton in Express is probably a good
> example, though I would use StrandUtils to save some code lines.
>
>
>
> --
> View this message in context: http://apache-flex-development
> .2333347.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59712.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>



--

Carlos Rovira
Director General
M: +34 607 22 60 05 <607%2022%2060%2005>
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.

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