> For example, I can do OO techniques when creating full apps > in VB, but I've never used them in Director - even the most > advanced projects I've worked on just haven't required it.
Well, it surprises me a bit that this is the case. IMO the OOP architecture introduced in Director has made development 100x easier to create, manage and maintain. I don't go into a project anymore without whipping up an object diagram in Visio. > The same goes for Imaging Lingo. Now I admit I'm not too > familiar with it, but apart from a little colour matching and > a drop shadow routine for nav menus, I've simply found no use > for it. Do we really need to manipulate and process images in > Director? I second Buzz's remark that IL is my "favorite post-d7 feature." I've used it in drag-and-drop menus to create the "drag" image. I've use it to generate tool tip balloons on the fly. I've used it to create a flow-chart maker application, and a tile-based game engine. Once you get the commands down for IL and bend your head to the idea that a cast member or sprite doesn't _have_ to exist during authoring you can pull some spiffy tricks. > The question is this: can Director do more than we really need? Never. =) Case in point: I've only used video in Director for one project. If Director didn't have video support up to now I wouldn't have even been affected. However, there are innumerable Director developers out there that couldn't get on without video support. Just because a feature generates little use for some of us in no way means it shouldn't have been added to Director's toolkit (although...there is the Real Media Xtra...). <br /> [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!]
