Decision to prefix the new components as Fx is final?


hi jay,<br /><br />i think it's pretty final, though if there major uproar in community came suggestions how address issue in timeframe have we'd open it.  use beta feedback 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 started jay a. in<br /><br />general discussion --<br />  decision prefix new components as  fx   final?<br /><br />is decision prefix new components fx-  final?<br /><br />it's show stopper me.<br /><br />i understand there technical reasons move, saddens me , cannot think flash tough battle developer's hearts & minds against silverlight, , feels more natural developers think in terms of < button > , < list > work prefixed classes.<br /><br />also saddens me think  developers coming flex first time in 2010 , beyond have write annoying <fxthis>  <fxthat> time because in 2007 there called halo components, never happen use.<br /><br />________________________________<br />view/reply @ decision prefix new components as  fx   final? <a href=http://www.adobeforums.com/webx?13@@.59b6e05f><br />replies email ok.<br />use unsubscribe <a href=http://www.adobeforums.com/webx?280@@.59b6e05f!folder=.3c060fa1>  form cancel email subscription.

"... though if there major uproar in community [...] we'd open it. "

major uproar delivered!

thanks listening ;-)


More discussions in Archived Spaces


adobe

Comments

Popular posts from this blog

invalid use of void expresion in FlexiTimer2 library

error: a function-definition is not allowed here before '{' token

LED Strip Code