OK, fair enough. You should be able to use resourceManager.getClass() and the 'new' operator to dynamically create instances of locale-specific components. But there's no way to make the class that an MXML tag like <MyView> represents be locale-specific... an MXML tag maps to a specific class, regardless of locale, as determined by the manifest file.
Another approach you might want to consider is having an English module, a French module, etc. Each can have its own manifest file so that <MyView> in the English module could map to a different class than <MyView> in the French module. Gordon Smith Adobe Flex SDK Team ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dhimiter Bozo Sent: Friday, May 30, 2008 11:46 AM To: [email protected] Subject: Re: [flexcoders] Re: ClassReference and resourceBundles Because not all the features are available to all the regions. Besides, different region may have different features all together. On 5/30/08 2:26 PM, "Gordon Smith" <[EMAIL PROTECTED]> wrote: Why would you want users in the U.S. to see more information (i.e., an extended view) than users in France (who see a quick view)? Why don't you want them to see the same information, either in English or in French? Gordon Smith Adobe Flex SDK Team ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> On Behalf Of Durres76 Sent: Friday, May 30, 2008 10:57 AM To: [email protected] Subject: [flexcoders] Re: ClassReference and resourceBundles the idea is that each locale will have it's own views that are linked to the same app. i want to switch to the correct view Clases for the selected locale. here's my logic: if US use the extededView which is declared in the properties file for that locale. if FR use the quickView which is declared in the properties file for that locale. am i thinking about this the wrong way? btw, the views would probably either extend or implement the same parent classes. Thanks, d
