I do like that idea. And make it top of list to fix for next version. At least that way we keep the known bug away as an eye soar for those interested in flex.
-1 vote for that Chris -----Original Message----- From: "OmPrakash Muppirala" <bigosma...@gmail.com> Sent: 8/20/2014 11:59 PM To: "dev@flex.apache.org" <dev@flex.apache.org> Subject: Re: [DISCUSS] TourDeFlex Release Candidate 3 Can we at least remove the stuff that we know does not work? It should be straightforward to just remove it from explorer.xml. Thanks, Om On Aug 20, 2014 9:00 PM, "Alex Harui" <aha...@adobe.com> wrote: > > > On 8/20/14 7:30 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > > >> MX controls deal with that, but I don't think Spark > >> controls do. > >So that would be a bug then? > IMO, yes, but I think last time I looked into it, the load is done by OSMF > which we can't change. They probably wouldn't want to use our > mx.utils.LoaderUtil which the MX classes do. It might just be that we fix > up the URL sent in by adding LoaderUtil to the example. > > -Alex > >
