Sometimes you can't. There's a lot of stuff that would make more sense being public but isn't (it's worse in the Web Services code, trust me). But Adobe is (IMHO) doing the right thing by thinking long and hard about changing established APIs.
Keep in mind though that Adobe's made it pretty clear that there'll be substantial changes to the way the UI Components work in Flex 4, so the less "secret sauce" you can get by with, the better. I doubt they'll break anything public, but mx_internal:: stuff will probably change, and the newer APIs might be harder to switch to if you're doing less standard stuff with what's in SDK3. In short, I don't think there's anything wrong with it, and with things like UI components, it's (probably) not going to change in a point release, but YMMV, Caveat Emptor, etc etc... Just be aware any complaints will likely fall on deaf ears if the internal APIs change and your stuff breaks :) -Josh On Tue, Jul 15, 2008 at 11:42 AM, Manu Dhanda <[EMAIL PROTECTED]> wrote: > > Yes, for me as well, it's for custom components. > > So, what could be the better way around to avoid it even in custom > components? > > > > Jeffry Houser wrote: > > > > > > Cool, thanks! > > I've found that I almost never use mx_internal when dealing with > > 'normal' development. But, it does come up when building custom > > components. > > > > Josh McDonald wrote: > >> I don't think I ever use mx_internal variables, but occasionally I > >> call or override the methods. If you prefix your references with the > >> namespace identifier "mx_internal::" it becomes something akin to an > >> admission that "yeah ok, I probably shouldn't be messing with this" > >> and lets other developers as well as your future forgetful self know > >> that that particular reference is to something that's not part of the > >> published API. > >> > >> -Josh > >> > >> On Mon, Jul 14, 2008 at 9:56 PM, Jeffry Houser <[EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]>> wrote: > >> > >> Josh, > >> > >> Your post insinuates that you do use mx_internal variables, but > >> without the "use namespace mx_internal" command in there. Is that > >> correct? If so, what is the alternative? > >> > >> Josh McDonald wrote: > >>> I don't. That way you can tell at a glance which parts of your > >>> code reference the internal stuff (and may be pain points in the > >>> future against new framework versions). > >>> > >>> -Josh > >>> > >>> On Mon, Jul 14, 2008 at 11:37 AM, Manu Dhanda > >>> <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > wrote: > >>> > >>> > >>> Hi guys, > >>> > >>> As I am trying to get into this Flex world, I am coming > >>> across to a few > >>> things where I need expertise advice like why and what should > >>> be done in an > >>> appropriate way. > >>> > >>> So here is one more question: why one should (not) use the > >>> following line of > >>> code and in what scenario's it could be avoided and how? > >>> > >>> use namespace mx_internal; > >>> > >>> Any comments/guidance would be great. > >>> > >>> Thanks. > >>> -- > >>> View this message in context: > >>> > >>> > http://www.nabble.com/How-appropriate-is-it-using-mx_internal---tp18436139p18436139.html > >>> Sent from the FlexCoders mailing list archive at Nabble.com. > >>> > >>> > >>> ------------------------------------ > >>> > >>> -- > >>> Flexcoders Mailing List > >>> FAQ: > >>> > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > >>> Search Archives: > >>> http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! > >>> Groups Links > >>> > >>> > >>> mailto:[EMAIL PROTECTED] > >>> <mailto:[EMAIL PROTECTED]> > >>> > >>> > >>> > >>> > >>> > >>> -- > >>> "Therefore, send not to know For whom the bell tolls. It tolls > >>> for thee." > >>> > >>> :: Josh 'G-Funk' McDonald > >>> :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >> > >> -- > >> Jeffry Houser > >> Flex, ColdFusion, AIR > >> AIM: Reboog711 | Phone: 1-203-379-0773 > >> -- > >> Adobe Community Expert > >> <http://www.adobe.com/communities/experts/members/JeffryHouser.html> > >> My Company: <http://www.dot-com-it.com> > >> My Podcast: <http://www.theflexshow.com> > >> My Blog: <http://www.jeffryhouser.com> > >> > >> > >> > >> > >> -- > >> "Therefore, send not to know For whom the bell tolls. It tolls for > thee." > >> > >> :: Josh 'G-Funk' McDonald > >> :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > >> > > > > -- > > Jeffry Houser > > Flex, ColdFusion, AIR > > AIM: Reboog711 | Phone: 1-203-379-0773 > > -- > > Adobe Community Expert > > <http://www.adobe.com/communities/experts/members/JeffryHouser.html> > > My Company: <http://www.dot-com-it.com> > > My Podcast: <http://www.theflexshow.com> > > My Blog: <http://www.jeffryhouser.com> > > > > > > > > -- > View this message in context: > http://www.nabble.com/How-appropriate-is-it-using-mx_internal---tp18436139p18456573.html > Sent from the FlexCoders mailing list archive at Nabble.com. > > > ------------------------------------ > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > Links > > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
