BTW I had an idea for this for the next iteration: extend the swf import to also search the browser cache directories. That way you just go (in microb) to the page where the swf is located, and then it will automagically show up in import. Not sure what to to with those later, though (obviously will disappear in time, so... copy over ? what if it's made up of several files ?).

EDIT:
@qwerty12:
Yeah, still, there might good reasons to do it if the docs/examples can be dug up (smaller memory footprint, quicker startup)... If you take a look at the launcher, you'll see that I wrote it in an (intentionally ) ugly way so the launch itself is done through a separate process, which in turn means that we're not at all tied to Qt (as in, I don't need the Qt event loop, etc), so GTK/GObject stuff is perfectly fine, too.