Hi Harbs I asked here for the best way to reference <body> tag from Dialog. I did the actual implementation as a workaround since at that moment you discussed it but no definite solution was opted. So considere it as a temporal code. If you see Dialog:
https://getmdl.io/components/index.html#dialog-section you only need a robust way to refer <body> since Dialogs are always attached to body (and could not be other tag) So feel free to change it if you have a better implementation thanks! 2017-02-22 14:41 GMT+01:00 Harbs <harbs.li...@gmail.com>: > I just looked at that code for the first time. > > I’m confused. Why are you attaching it to Application? Why not just add > dialog to <body>? I don’t see why you need a reference to Application at > all. > > Unless, of course the dialog should be centered in the application (which > might not be <body>). > > Additionally, does it make sense to have a property which allows > specifying an HTML element to attach the dialog to (be it <body> or > something else)? > > > On Feb 22, 2017, at 11:53 AM, Carlos Rovira < > carlos.rov...@codeoscopic.com> wrote: > > > > Regarding mdl:Application in concrete, is just a js:Application with a > > static var to handle body since is needed for Dialog, and that's what MDL > > Dialog impose. > > so just a static var is the difference... > > > > 2017-02-22 9:53 GMT+01:00 Harbs <harbs.li...@gmail.com>: > > > >> “Must” is too strong. > >> > >> Our app needs MDL for controls, but the main functionality doesn’t and > >> CAN’T rely on MDL. If mdl:Application can do everything a > basic:Application > >> can do, then that’s fine (as long as it can be sub-classed, because our > app > >> cannot be based off <body>), but if mdl:Application cannot take other > >> components, it’s a not starter. > >> > >> I do think it’s fine to say that it’s “batteries not included” (with > >> documentation on what needs to be done) if you don’t use > mdl:Application / > >> mdl:Container, but it’s absolutely necessary for components to be mixed > and > >> matched. I don’t think our app is so unique that others will not have > the > >> same issue. > >> > >> Harbs > >> > >>> On Feb 22, 2017, at 9:03 AM, Alex Harui <aha...@adobe.com> wrote: > >>> > >>> IMO, it is fine to say that folks must use mdl:Application > >>> instead of basic:Application and mdl:Container instead of > basic:Container > >>> if that gives you control over the lifecycle that you need in order to > >>> help your customer. > >> > >> > > > > > > -- > > > > 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. > > -- 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.
