Open letter to Macromedia
Out of context: Reply #43
- Started
- Last post
- 45 Responses
- Chip_Duggit0
I’ll step up to the mic.
One thing that bugs the piss out of me is that MX makes you save a file before you preview it in the app. The old ones didn’t make you do that, they created the file on their own. Build in a simple load text object that will also allow text fields to use a linked .css file. Too many people are linking text files and not being able to use .css for their formatting. Fix the damn problem with all MX products on the mac that make the panel sets disappear. Add in an auto keyframing feature, where it records your movements with an object over a time span...a la After Effects. Add the ability to throttle the frame rate based on processor stregnth, like Director, make it actually work at the fps you set it to, not an arbitrary fps that the processor can handle.
Finally, re-write the f*cking mac osx plugin to actually take advantage of pre-emptive multiprocessing. I hate the fact that if I have more than once instance of a browser open with a flash object in each, they both slow down because the plugin is a badly written pile of garbage. There isn’t an excuse anymore. Tear the thing down, use the quartz api and take advantage of the new abilites of osx. A carbon lib based plugin that is constantly in ‘beta’ does nothing for performance. Also only port the next version to osx and write it in cocoa.
That’s enough for tonight.