If you do the Insert / Markup, then you’ll have to police the code
you’re pasting in to be certain that it won’t clash with your page the
way you’ve set Freeway to code it. For example, if your page is set to
HTML 4 Transitional, and you paste in some XHTML, you’ve just made
your page invalid. Normal browsers don’t really care, but if you are
subsequently trying to figure out why it looks funny in one browser
and not most, that will be the first thing anybody asks you: “does it
validate?” This sort of thing can be very subtle – the difference of
a few / characters here and there – so it’s not completely easy to
figure out without a lot of practice and experience.
Iframes, on the other hand, create an entire new browser “sandbox” for
the inserted code. This means that you can host a complete Web page
inside another Web page, so you don’t have to fuss with stripping off
the HTML and HEAD and BODY tags from a full page-size lump of code.
Iframes require that the host page (the page where you add the iframe
tag, not the target page you point it to) be set to one of the
Transitional DOCTYPEs, because iframe is not a recognized tag in any
Strict DOCTYPE.
When you use an iframe for content on your page, you can let that
inserted code be as crazy as it wants to be, because it’s not your
page, and it won’t “infect” your page with any of its content or
mistakes. An iframe is a hole, laser-cut through your page, through
which you can see another page in the distance.
So that brings me to the real rule of iframes: you can only put into
them something that you could ordinarily display “bare” in a browser:
full pages, or file types that the browser recognizes and handles
natively. In the case of your Vimeo code, if you take THEIR iframe
code, and strip it down to just the content of the src attribute (look
for src=“foo/bar/baz” and use only the ‘foo/bar/baz’ part) and put
just that address into the iframe Action in Freeway, you should be
golden – you’ll be able to see the movie just as Vimeo presents it,
with just the controller and none of the surrounding page. But if you
link your iframe to the page with the video on it, you will see the
entire page, and if you link to the source of the SWF file itself, you
won’t see anything at all (because you can’t play a Flash movie
directly from a URL in a browser window – you have to add the object/
embed/pluginspage code around it to get the plugin to wake up and play
it.
Walter
On Jan 9, 2011, at 5:41 AM, Martin Rice wrote:
Thanks, David. Is there an advantage one way or another in using
either the Insert->Markup Item or Insert->Action Item->iFrame?
Martin
On Jan 8, 2011, at 7:47 PM, DeltaDave wrote:
The other method - because this creates an iFrame in your FW page -
is to use FW’s own iFrame action.
Insert>Action Item>iFrame
Then size the iFrame on your page to width=”400” height=”265” and
in the Action palette set the URL to other using ”Spring Lake Farm: Inspiring the Grass Fed Movement in Upstate New York on Vimeo
” (without the quotes)
David
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options