Another help with web page request

serowe · **Posted:** Tue Feb 07, 2012 11:21 pm

Interesting - viewing the source of the iFrame doesn't show the source of the main page - and vice versa...

PaulMy · **Posted:** Wed Feb 08, 2012 12:11 am

Quote:

Might have something to do with it (height attribute)

I really don't know what I am doing but with trial and error I get along :oops:

Yes, I have been gradually increasing the height as I have been adding images so that all the images can appear in the main frame. The longest is the daily images for the Sunrecorder monthly history pages and that is why I have it at 17000 now. Some day I'll learn how to do that different/better

I have it now working in six browsers, except that in Chrome and Safari the left menu frame has a very long top margin (coloured blank area) before the links show. I have just begun to search on what settings impact the different browsers so I can work on correcting that issue. I have been using Notepad++ to fix the index.html file that appeared to have been corrupted and will try again in DW later in the week to see how/why things may change with DW. Once I feel comfortable and safe with DW I'll try working on the colours again.

Any quick suggestion that will help me why/how different browsers are affected by the same code, like mentioned above?

Thanks for your comment,

Paul

serowe · **Posted:** Wed Feb 08, 2012 1:15 am

Paul - I have to ask, though - why are you using an iFrame in the first place? Whilst it is (possibly) Ok to use in HTML, it is depracted in XHTML so really shouldn't be used.

Also, by stipulating such a horrendously long length you are more than doubling the total length of the display screen that you need.

http://www.w3schools.com/tags/tag_iframe.asp

PaulMy · **Posted:** Wed Feb 08, 2012 2:03 am

Quote:

Paul - I have to ask, though - why are you using an iFrame in the first place?

Becasue that was the template set up for me early in my site's startup, and I don't know yet how else to have the separate side menu. And by the looks of the length of the December and January Sunrecorder history files I can shorten it a bit, but not very much. Having said that, I will be using DW, or at least hope to, to present the history differently by using the Sunrecorder's saved daily image files instead of the screen capture I now do for each day. As I've said before, trial and error and one step at a time

and that's been some of the fun :lol:

Paul

serowe · **Posted:** Wed Feb 08, 2012 2:24 am

Try playing around without the iFrame in it then - as I said, it is old coding style/practice now and really shouldn;t be used.

I presume you are testing it on a home based server first (XAMPP or WAMP) which would make it a lot easier to test and try things out.

Even try it without the height=1700 code - it *should* dynamically size itself without it.

PaulMy · **Posted:** Wed Feb 08, 2012 2:43 am

Quote:

I presume you are testing it on a home based server first (XAMPP or WAMP) which would make it a lot easier to test and try things out.
Even try it without the height=1700 code - it *should* dynamically size itself without it.

I have seen reference to XAMPP or WAMP here on the forum but have no idea what that is so no, I am not using that, just do frequent save, backup, ftp and check out on the different browsers. That is one reason I want to use DW to make that process a bit less onerous.

On the length, I had found that unless I kept lengthening it I would be missing some images or parts of images.

As I am adding and modifying I am seeing and learning about what the code actually does but still a looong way from getting any good grasp in understanding much of it. I admire those of you to whom it just seems to be so simple, but then I've come a long way as well from when I first started to get into the code.

Paul

serowe · **Posted:** Wed Feb 08, 2012 2:49 am

Of course, if you specify a length, it may well miss parts of images but what I am suggesting is try it WITHOUT any specified length.

But also try and work without the iFrame altogether as you are only making the page look - well, odd, because you have all this white space that isn't needed. You are trying to cater for the largest page which, on short pages, only messes them up.

As for XAMPP or WAMP - suggest you look at it. You are already using a software package I certainly would never recommend to a beginner - DW is *not* a simple package to use (as you are finding out) and adding something like XAMPP or WAMP to your local machoine means you don;t have to continually FTP files to your external web site - they can be tested in house (ie your local PC) and helps if you break the code and/or your web site. You oly then break what is on the local machine, not the web site itself.

It's all part of the learning process - DW is part of it - and certainly not, IMHO, the best way to learn.

beteljuice · **Posted:** Wed Feb 08, 2012 4:34 am

Just remove the scrolling=no, and give a reasonable height value.

PaulMy · **Posted:** Thu Feb 09, 2012 5:39 am

Thanks again beteljuice,
I've been playing with the various settings and for the moment settled at 1690 and scrolling "yes". Not totally satisfied and haven't checked on other browsers as yet but for most of the pages it is much better. Another lesson learned.

Paul

	It is currently Tue May 21, 2013 11:22 am
Please click here before posting. Help me to help you!
Useful Links: Cumulus FAQ • Enhancement requests • Wiki (documentation)
Please put your approximate location into your profile
Add your web site to the Cumulus user map
Vantage Pro2 users with firmware 3.00 should upgrade to fw 3.12 and Cumulus 1.9.4
Latest Cumulus release v1.9.3 (build 1059) - Feb 09 2013 Latest Cumulus beta v1.9.4 build 1076 - May 12 2013 --> Latest Cumulus Realtime v1.0.0.5 - Sep 05 2009

Sandaysoft

Another help with web page request

Who is online