CompuServe Thread

AA Studio

3 messages in this thread
#126751From: Mike BrennanOct 2, 1994 6:21 PM
I'm trying to find out if AAPro & AAStudio should be viewed as a complimentary pairing and have a couple of questions. – Will AAStudio be able to use Poco code? – If not will existing Poco code be easily portable to a new scripting language? – Will there be a translator-like utility to convert existing Poco code? Will we see a situation where Poco will be used in AAPro to create graphic/anim. effects & the resultant flc is brought into AAStudio as a source file for further enhancement as a multimedia project. Will AAStudio incorporate any of the authoring technology that Adesk acquired from Mediashare or is that to be a separate product? How do you see AAStudio in comparison to a product like Macromedia's Director? Thanks Mike
#127067From: Jeremy Hubbell [Adesk]Oct 4, 1994 10:53 AM
-Yes, it's best to think of AAPro and AAStudio as complementary since they do have unique features such as POCO. -The POCO language will be used only in AAPro. There have been no annoucements reagarding portability of the code. -There is a scriptor module that will ship with AAStudio that will allows you to do everything that the DOS based scripting language that AAPro used for playing back FLICs, but now it's visual(yes!). -You're right in assuming that you'll create the special effects in AAPro and then go into AAStudio for 24-bit paint/animation and sound enhancement. That's the natural progression while Windows 3.1 is still around. Jeremy
#127094From: Mike BrennanOct 4, 1994 12:35 PM
I realize that you can't speak directly to this, but I'll try anyway <g>. Is there likely to be any announcement about the future direction/development of Poco or a successor? It seems to me that the apparent lack of a programming language in Studio is a pretty big hole to fill. Have you seen Ed Kellerman's particle system? This kind of code can be invaluable. It would be a real shame to lose this work through the lack of a Pgm. language. I hope that there is at least some method for porting the Poco code over to a 'new' Poco in Studio. Will there be some sort of plug-in system? Time-based filters for elapsed effects? Any importation of files from packages such as Powerpoint, Astound, etc? Sorry! I can think of all kinds of questions, but I guess you may want to save something for the release announcement <g>. The visual scripting module sounds very nice. How would you compare Studio and Macromedia's Director? Thanks Mike P.S. I never thought I'd be shilling for someone else for beta testing, but have you asked Ed Kellerman (71532,3255).