iFrame as an alternative to external web page

iFrame as an alternative to external web page

- Brad Lowry の投稿
返信数: 4
Hi I almost posted this to the Tips & Tricks, but since I think perhaps it ought to be part one of the options available I am posting it here.

So I created a Camtasia video.

I make it a linked page, new window: confusing to the end user.

I make it a linked pae, same window: the "Jump to..." right pointing arrow did not take away the clumsy lower frame -- users would need to be very "frame savvy" to negotiate this (who is frame savvy?) not end users that is for sure.

So, I turned off the WYSIWYG HTML editor, created a "Compose a web page" resource and pasted the following code:
[code]
<html>
<body>

<iframe height="624px" width="751px"
src ="http://mysite.com/demos/CamtasiaDemo/CamtasiaDemo.html">
</iframe>

</body>
</html>
[/code]

I played with it and found that if you publish as web content without a Table Of content the content is 727 by 600, when you add 24 pixels to both dimensions you get a very nice look.

Now I can have linked content that keeps you "in moodle" and where the "Jump Navigation Arrows" still work as expected.

Wouldn't this be a good thing in general?

(Should I cross post in Tips & Tricks or is that considered "bad form")

Thanks,
Brad
Brad Lowry への返信

Re: iFrame as an alternative to external web page

- Martin Dougiamas の投稿
画像 Core developers 画像 Documentation writers 画像 Moodle HQ 画像 Particularly helpful Moodlers 画像 Plugin developers 画像 Testers
The only problem with frames is that they are not XHTML Strict 1.0 compliant, so if we care about being compliant then we really shouldn't use them at all.
Martin Dougiamas への返信

Re: iFrame as an alternative to external web page

- Brad Lowry の投稿
Hi All,

First, I will x-post to Tips & Tricks,thanks.

As per XHTML compliance, indeed that is important, but since Moodle as it is now uses old fashioned frames, the use of iFrames can't be soooo much of an abrogation can it -- unless there is a commitment forward.

Also, that iFrames aren't XHTML complaint must be a blow to the entire AJAX community? -- this seems like it might resolve in favor of iFrames considering the AJAX explosion, no?

Thanks for your great responses,
Brad