Linking directly to a SWF, what are the downsides?,
Usually Flash and Flex applications are embedded on in HTML using either a combination of
Update don’t get hung up on the 100+ lines, I simply mean that the the amount of code needed to embed a SWF is quite a lot (and I mean including libraries like SWFObject), and it’s just for displaying the SWF, which can be done without a single line by linking to it directly.
Upsides for linking directly to SWF file:
- Faster access
- You know it’s a flash movie even before you click on the link
- Skipping the html & js files (You won’t use CSS to display 100% flash movie anyway)
- You have little control on movie defaults.
- You can’t use custom background colors, transparency etc.
- You can’t use flashVars to send data to the movie from the HTML
- Can’t use fscommand from the movie to the page
- Movie proportions are never the same as the user’s window’s aspect ratio
- You can’t compensate for browser incompetability (The next new browser comes out and you’re in trouble)
- No SEO
- No page title, bad if you want people to bookmark properly.
- No plugin information, download links etc.
- If your SWF connects to external data sources, you might have cross domain problems.
- Renaming the SWF file will also rename the link. Bad for versioning.
In short, for a complicated application – always use the HTML. For a simple animation movie you can go either way.
That’s the answer Linking directly to a SWF, what are the downsides?, Hope this helps those looking for an answer. Then we suggest to do a search for the next question and find the answer only on our site.
The answers provided above are only to be used to guide the learning process. The questions above are open-ended questions, meaning that many answers are not fixed as above. I hope this article can be useful, Thank you