Friday, May 02, 2003
FireFly: Invasion of the Body Snatcher
Downloaded and installed FireFly components on my machine, looks interesting except that I have major problems with my copy of Flash. Launching it means a 5 minute plus wait while it consumes 97% of CPU. Once it's running it's fine. I've got no particular need for it right now so I tried an uninstall which fixed the problem immediately.
Posted by at 01:14 PM | Permalink
Trackback:
$10 bucks (about 20 Aussie) says that it's the bloody Reference Panel documentation.
Peter Hall had a mention on Flashcoders about if you leave like your closing P tags out or some junk, it slows the XML parser used to make the refrence panel. If Firefly has tons of documentation, I bet that's the problem. Don't know the fix off-hand, and am about to pass out, but I'll see if I can find the post in da morn.
Posted by: JesterXL on May 2, 2003 01:36 PM
Jesse, interesting idea, I do have the Resource Panel always open (but collapsed) just in case, and there's a lotta stuff put in there by FireFly.
Posted by: Andrew Muller on May 2, 2003 01:42 PM
You can screw Flash MX if you put in rogue data in there. Just get drunk, and start messing with CustomActions, and you'll see what I mean. Anytime you re-install Flash MX, make sure when installing components, install them one at a time, and see how Flash responds. You'll usually spot the culprit easier that way. Worked for me.
Posted by: JesterXL on May 3, 2003 01:57 AM
Mines screwd big time CURSED FIREFLY CRAP
QA your shit MM FFS!
Posted by: Scott Barnes on May 10, 2003 01:31 PM
Think Jesse is gonna win his bet.
The problem is CyberSage created the docs using FlashDoc. Take a look and you'll see 68 XML files that start with Fx. These are the FireFly docs. There's only supposed to be 2--one for reference and one for api/hints/etc.
FlashDoc doesn't aggregate the classes into one reference, it creates one reference per class.
Posted by: Samuel Neff on May 13, 2003 10:32 AM
$10 bucks (about 20 Aussie) says that it's the bloody Reference Panel documentation.
Peter Hall had a mention on Flashcoders about if you leave like your closing P tags out or some junk, it slows the XML parser used to make the refrence panel. If Firefly has tons of documentation, I bet that's the problem. Don't know the fix off-hand, and am about to pass out, but I'll see if I can find the post in da morn.
Posted by: JesterXL on May 2, 2003 01:36 PM
Jesse, interesting idea, I do have the Resource Panel always open (but collapsed) just in case, and there's a lotta stuff put in there by FireFly.
Posted by: Andrew Muller on May 2, 2003 01:42 PM
You can screw Flash MX if you put in rogue data in there. Just get drunk, and start messing with CustomActions, and you'll see what I mean. Anytime you re-install Flash MX, make sure when installing components, install them one at a time, and see how Flash responds. You'll usually spot the culprit easier that way. Worked for me.
Posted by: JesterXL on May 3, 2003 01:57 AM
Mines screwd big time CURSED FIREFLY CRAP
QA your shit MM FFS!
Posted by: Scott Barnes on May 10, 2003 01:31 PM
Think Jesse is gonna win his bet.
The problem is CyberSage created the docs using FlashDoc. Take a look and you'll see 68 XML files that start with Fx. These are the FireFly docs. There's only supposed to be 2--one for reference and one for api/hints/etc.
FlashDoc doesn't aggregate the classes into one reference, it creates one reference per class.
Posted by: Samuel Neff on May 13, 2003 10:32 AM