I have been successful using compc with conditional compiles outside the framework, but I was not successful using mxmlc.
> On Mar 26, 2017, at 3:20 PM, Peter Ent <p...@adobe.com> wrote: > > The way it stands now, you do need to create a new component in the > framework somewhere. In the long run, developers will want to make their > own component sets that make use of conditional compilation, so now would > be a good time to come up with that. You should be able to do this outside > of the framework, IMO. > > You could even imagine a company that has a bunch of JavaScript > "components" that they'd like to use. We have the extern mechanism, and > maybe that's appropriate when there is a lot of JavaScript to reference, > but perhaps a developer will just want to copy a component's JavaScript > code into their project - even temporarily - and I think we should be able > to provide for that. > > ‹peter > > On 3/26/17, 6:36 AM, "Harbs" <harbs.li...@gmail.com> wrote: > >> I want to use a Topcoat checkbox in an app. That requires some HTML like >> this: >> >> <label class="topcoat-checkbox"> >> <input type="checkbox"> >> <div class="topcoat-checkbox__checkmark"></div> >> Checkbox Label >> </label> >> >> I cannot think of a normal way of including something like this in my app >> without creating a whole new framework component. Conditional compiles do >> not seem to work. I don¹t know why. I also considered using an InnerHTML >> bead, but that does not allow handling the checkbox clicks. >> >> The fact that FlexJS abstracts the HTML and JS most of the time is great, >> but I think there needs to be an easy way to use bog-standard HTML when >> the need comes up. >> >> Thoughts? >> >> Harbs >
