1 Reply Latest reply on Feb 16, 2009 1:28 AM by j-araujo

    Decision to prefix the new components as Fx is final?

    matt_chotin Level 3
      Hi Jay,<br /><br />I think it's pretty much final, though if there was a major uproar in the community that came with suggestions for how we could address the issue in the timeframe that we have we'd certainly be open to it.  We do use beta feedback for this sort of thing.<br /><br />Matt<br /><br /><br />On 10/29/08 2:08 AM, "Jay A." <member@adobeforums.com> wrote:<br /><br />A new discussion was started by Jay A. in<br /><br />General Discussion --<br />  Decision to prefix the new components as  Fx   is final?<br /><br />Is the decision to prefix the new components with Fx-  final?<br /><br />It's really a show stopper for me.<br /><br />I understand that there technical reasons for this move, but it saddens me and I cannot but think that Flash is up for a tough battle for the developer's hearts & minds against SilverLight, and it definitely feels much more natural to developers to think in terms of a < Button > and a < List > than to work with prefixed classes.<br /><br />Also it saddens me to think  developers coming to Flex for the first time in 2010 and beyond will have to write annoying <FxThis>  <FxThat> all the time just because back in 2007 there was something called Halo components, which they will never even happen to use.<br /><br />________________________________<br />View/reply at Decision to prefix the new components as  Fx   is final? <a href=http://www.adobeforums.com/webx?13@@.59b6e05f><br />Replies by email are OK.<br />Use the unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b6e05f!folder=.3c060fa1>  form to cancel your email subscription.