In theory, a different implementation will still have the same API, or the API will be 'smart enough' to know which implementation it is using. ;) I'm glad I don't have to design it.
superabe superabe wrote: > > > Ok. That makes sense I guess ... > Though in your example , what if the File class for mobile needs to have > a different implementation (lightweight?) than the File class for > desktop devices (AIR) ? > > - superabe > > On 9/17/07, *Gordon Smith* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > No. This decision is consistent with the fact that the AIR team has > put their new classes like File into the flash.* package. > > Both decisions are motivated by the fact that it's hard to know what > classes will exist on which platforms in the future. For example, > the Flash Player for mobile devices -- which isn't AIR -- may have a > File class. So our rule is that packages do not indicate the platform. > > - Gordon > > ------------------------------------------------------------------------ > *From:* flexcoders@yahoogroups.com <http://ups.com> > [mailto:flexcoders@ <mailto:flexcoders@>yahoogroups.com > <http://yahoogroups.com>] *On Behalf Of *superabe superabe > *Sent:* Saturday, September 15, 2007 5:03 AM > *To:* flexcoders@yahoogroups.com <http://ups.com> > *Subject:* [flexcoders] air namespace (adobe) > > Are there any plans to create a separate namespace for AIR related > components in the SDK? > For e.g. I am looking inside the mx.controls package and I see > controls like FileSystemComboBox and FileSystemDataGrid listed, > which dont seem to be usable in a non-AIR flex context, thus leading > to confusion. > > - superabe > > > -- Jeffry Houser, Technical Entrepreneur, Software Developer, Author, Recording Engineer AIM: Reboog711 | Phone: 1-203-379-0773 -- My Company: <http://www.dot-com-it.com> My Podcast: <http://www.theflexshow.com> My Blog: <http://www.jeffryhouser.com>
