> On Feb 22, 2017, at 6:08 PM, Alex Harui <aha...@adobe.com> wrote: > > > > On 2/22/17, 7:24 AM, "Harbs" <harbs.li...@gmail.com> wrote: > >> So, this is going to be a problem. >> >> Right now Application is always attached to <body>, but that is probably >> going to change. A very common use case of RIAs is embedded in web pages. >> In that case, the base element will not be <body> unless it’s in an >> iframe. iframes are not always a good solution. For example, iOS has a >> bug where you can not use the soft keyboard in an iframe. >> >> I’m going to commit a change which will hopefully work… ;-) > > Or create another Application class, maybe called "NonBodyApplication" (I > thought of EmbeddedApplication as well).
Right. I’m planning on that. The problem is I want to use mdl dialogs in an EmbeddedApplication. That’s not gonna work with the way dialogs are currently done. > >>>>> 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. > > > No component set should be required to accept mix-and-match. If it can be > supported via beads, then great. > I thought MDL was for UI. What other app functionality are you referring > to? Lots. First of all, mdl is not a full component set. Also, we have interactive elements which is mostly svg, but there’s also HTML wrapped stuff. We are likely going to have a canvas component before we’re done as well. > -Alex >
