> Not DMX, no. DMX2004 is supposed to allow this. Please keep in mind that you will _not_ be able to drag all your Flash MX 2004 components over to Director MX 2004, drop them in and have them auto-magically work. The trouble here is that unfortunately many of the components in Flash MX 2004 rely heavily upon having a bunch of ActionScript written out dynamically upon publishing as a SWF (such as the data components, most if not all require Flash authoring to write a bunch of AS upon export). Director is simply not capable of doing all that dynamic AS writing so many of the components will not work if dropped into Director's app folder (MX 2004 only). Some will, some won't, we're shipping the app with a set of components that do work but they're all UI components. For those SWC files that need this dynamic AS output, you can always publish the SWC as a SWF file from Flash MX 2004 then import the SWF, that way you'll get all that dynamic AS that's required.
That having been said, we do have support for the general component architecture (write a SWC, have it publicly expose certain properties and methods, have those props initializable via the Property Inspector in Director), so folks can write their own, use some they found on-line, etc. It's just that a lot of the current SWC files in Flash MX 2004 were written with the specific intent of only using them in Flash authoring thus excluding use in Director unless exported first as normal SWF files, ugh. Cheers, Tom Higgins Product Specialist - Director Team Macromedia Announcing Director MX 2004, de lekkerste! http://www.macromedia.com/software/director ... [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
