Article:		What Is a Flash MX Component?
Subject:		NO ... I don't use them
Date:		2003-02-09 03:42:28
From:		anonymous2
I'm speaking from a coder point of view, and here all the things that I dislike in components: - Macromedia doesn't provide any guideline, standards, rules or internal documentation of their components. - I didn't like smartclips in flash5 too, and I'm happy not to have waisted my time to use or build them, because now they are obsolete, detroned by flashMX components, is it gonna be the same things with components when flash 7 will go out and promote a new way of doing things ? - the way components work and how they are structured, sorry but that's bad coding practice ... http://c2.com/cgi/wiki?CodeSmell I will not be a dummy programmer following blindly Macromedia components bad OO coding style.

Showing messages 1 through 1 of 1.

• NO ... I don't use them
  2003-07-23 07:35:14  Colin Moock [Reply | View]
  
  
  components are here to stay, trust me. if you develop windows apps, you don't write a Menu or DialogBox class yourself, you use the corresponding MFC class. if you're developing java apps, you likely don't write a Tree class yourself, you use JTree. if you're developing flash apps, you use components. after all, you're developing apps, not UI widgets. of course, in some situations you'll produce your own specialized UI widgets for any platform, but for standard apps, you use the built in UI libraries.
  
  the mx components are not perfect. they are version 1 of flash's UI library. but they are quite usable, and lay a good foundation upon which macromedia will certainly build. i agree that the flash mx component authoring process needs improvement, and in some cases so do the components themselves...but that's why software companies release new versions of products, right? merging an animation tool with an app development IDE isn't something that happens overnight. it takes years to evolve. and along the way i think we're all learning to create better, more engaging content.